5 Claim Denial Codes Small Practices Should Understand

5 Claim Denial Codes Small Practices Should Understand

A denial code helps you decide where to investigate an unpaid claim. The next step depends on the accompanying remark codes, the service billed, the patient's plan and the payer's instructions.


Stephanie Jason Stephanie Jason Publish: Dec 9, 2025Last Modified: Dec 9, 20257 min read

Introduction

A denial code helps you decide where to investigate an unpaid claim. The next step depends on the accompanying remark codes, the service billed, the patient's plan and the payer's instructions.

This guide covers CO-16, CO-50, PR-49, CO-22 and CO-11. Use it as a working reference, then confirm the requirements for the claim in front of you. Your own remittance data will show which reasons account for the largest share of your practice's denials.

Read The Whole Remittance Before Changing a Claim

The number and letters in a code have different jobs:

  • A claim adjustment reason code, or CARC, explains a payment adjustment. An adjustment may affect part of a claim; it does not always mean the entire claim was denied.
  • A remittance advice remark code, or RARC, adds detail or provides processing information. Informational alerts have a different purpose from remarks that explain a specific adjustment.
  • The group code identifies the responsibility category. CO means Contractual Obligation; PR means Patient Responsibility.

Read these together with the affected service line and adjustment amount. CMS explains how remittance codes work together, and X12 maintains the group-code definitions.

Before moving a balance to the patient, verify the remittance, applicable law, payer contract and any required notice. A PR entry is not blanket permission to collect every unpaid charge. Do not transfer a CO amount to the patient simply because the payer has not paid. For Original Medicare, advance beneficiary notice requirements can also affect liability in specified circumstances.

First distinguish a rejection from a denial

A front-end rejection generally means the claim has not entered adjudication. A denial follows a payment or coverage determination. Some claims returned as unprocessable also appear on a remittance, so the document's title alone does not tell you which route to take.

For example, RARC MA130 identifies an unprocessable claim and directs submission of complete, corrected information without appeal rights for that submission. Noridian's reopening checklist distinguishes these claims from minor errors that may qualify for reopening. Verify your payer's process before resubmitting or appealing.

Types of medical billing denials

1. CO-16 A Claim Information or Billing Error

CARC 16 identifies missing claim information or a submission/billing error. X12 requires an accompanying non-alert remark code or NCPDP reject reason and excludes missing claim attachments or other documentation from this code's use. Check the current CARC list and usage notes.

Start with the remark, then inspect the corresponding field in the actual transmitted claim. Comparing only the patient chart with the practice-management screen can miss an interface or export problem.

Illustrative example: A CO-16 adjustment includes N290, which identifies a problem with the rendering provider's primary identifier. The biller checks the required identifier and how the rendering-provider field was transmitted before choosing the payer's correction route. X12's RARC list defines N290 and MA130.

To reduce repeat errors, record the specific field that failed and update its validation rule. A list that says only “CO-16” will hide different causes under the same heading.

2. CO-50 The Payer Questions Medical Necessity

CARC 50 means the payer has determined that the service does not meet its medical-necessity criteria. It does not establish that the service is permanently excluded from every plan or that an appeal cannot succeed.

Review the denial explanation and applicable coverage policy for the date of service. Compare the billed service and diagnosis with the documentation supporting why the service was needed. A coder can investigate claim accuracy; a clinician may need to explain the medical reasoning.

Illustrative example: A practice receives a medical-necessity denial for a diagnostic test. Its clinician reviews the documented symptoms and prior evaluation against the cited policy. If the record supports the claim, the practice can assemble that evidence for the payer's review process. It should not add an unsupported diagnosis to obtain payment.

Noridian's CARC 50 guidance illustrates why the next step varies: an appropriate response may involve supporting records, an appeal or a permitted clerical correction. That guidance is specific to its DME jurisdiction, so follow the instructions that apply to your claim.

3. PR-49 Routine or Preventive Service Coverage

CARC 49 concerns noncoverage of a routine/preventive examination or a diagnostic/screening procedure performed with that examination. It is not a general eligibility code.

Check the service performed, the benefits involved and the plan's coverage rules. A “wellness visit,” routine physical and problem-focused visit are not interchangeable descriptions for billing purposes.

Illustrative example: An Original Medicare patient schedules a routine physical. The practice later receives an adjustment identifying noncovered preventive care. The biller reviews the encounter with the clinician instead of automatically replacing the physical-exam code with an Annual Wellness Visit code.

CMS distinguishes a Medicare Annual Wellness Visit from a routine physical. An AWV has its own required service elements and eligibility conditions. Bill it only when the service actually performed, documentation and applicable requirements support it. Verify Medicare Advantage benefits separately.

At scheduling, clarify what the patient expects and what the planned visit includes. After an adjustment, verify patient liability before generating a statement.

4. CO-22 Another Payer May Be Responsible

CARC 22 signals that another payer may cover the care under coordination-of-benefits rules. The CO prefix does not turn this into a generic contractual-discount adjustment.

Confirm the insurance arrangements that applied on the date of service. Check whether payer records agree about coverage and payment order. A current insurance card alone may not resolve an outdated coordination-of-benefits record.

Illustrative example: A patient's former employer plan remains listed as primary after that coverage ends. Before sending another claim to that plan, the practice verifies the termination date and follows the affected payers' process for updating their records.

If another insurer is correctly primary, obtain its adjudication information and follow the secondary payer's submission requirements. For Medicare claims, CMS describes providers' billing responsibilities, including collecting other-insurance information and submitting the required primary-payer details.

5. CO-11 The Diagnosis and Procedure Are Inconsistent

CARC 11 identifies an inconsistency between the diagnosis and procedure. The code alone does not tell you which field, if any, is wrong.

Have a qualified coder compare the procedure, diagnoses and diagnosis pointers with the signed encounter documentation. Check the payer's explanation before changing either code.

Illustrative example: A correctly documented procedure was linked to the wrong diagnosis line during charge entry. If review confirms the linkage error, the practice follows the payer's correction process. If the submitted claim already reflects the record accurately, investigate the coverage determination and available appeal route.

Code selection must reflect the documented care. Choosing a different diagnosis merely because it appears on a payer's covered list can create a more serious problem than the original denial.

Denial codes

Choose The Route and Protect The Deadline

Use a short checklist for each claim:

  • Record the claim number, affected lines, group code, CARC, remarks and payer explanation.
  • Identify whether the issue is claim data, coverage, medical necessity or payer order.
  • Confirm the submission route. A corrected claim changes inaccurate claim information; an appeal challenges a determination. Some payers offer separate reconsideration or reopening processes.
  • Verify the deadline and what starts it. Initial filing, corrected-claim and appeal deadlines may differ by payer, plan, contract and jurisdiction.
  • Keep the submission confirmation, supporting records and next follow-up date. Check the resulting determination before closing the task.

CMS separates minor claim corrections from Medicare appeals. Commercial instructions also differ: UnitedHealthcare's guidance distinguishes corrected claims from reconsiderations and appeals. Do not assume another payer uses the same sequence or that submitting a correction extends an appeal deadline.

Turn Individual Fixes into a Manageable Workflow

Review denial patterns by payer, reason, affected service and dollars at risk. Assign an owner to each open claim and prioritize approaching deadlines. When an error repeats, fix the registration, coding or submission step behind it, then check whether the change worked.

For help reviewing unresolved claims and organizing corrections or appeals, explore Dastify's denial management services. If limited staff capacity affects the wider billing workload, see our medical billing support for small practices.

This guide provides general billing education. Apply the current payer policy, contract and applicable requirements to each claim, with coding or compliance review when needed.