Get the sample weekly report

Denial code · group CO

CO-16: The claim is missing information the payer needs to process it

Short answer

CO-16 means the payer could not process the claim because something it needs is missing, incomplete or invalid. It is not a judgment on medical necessity or coverage. The remark code (RARC) sent with it names the field, and the fix is almost always a corrected claim rather than an appeal.

Look up other codes in the denial code library.

Last reviewed by the Remitwright billing team. Editorial policy

  • Group CO · Contractual obligation

Group CO means contractual obligation: the balance is written off, not billed to the patient. The number is the reason; the two-letter group says who carries the balance.

Remark codes that usually come with CO-16

M51
The procedure code is missing, incomplete or invalid
MA130
The claim has a defect that stops it being processed; it has to be resubmitted, not appealed
N286
The referring provider's identifier is missing, incomplete or invalid
N290
The rendering provider's identifier is missing, incomplete or invalid
MA04
The secondary cannot work out its share until the claim names the primary and shows what it paid

Common causes

A required identifier is blank or wrong

The rendering NPI, referring NPI, taxonomy code or payer-assigned provider number is missing, or the NPI on the claim does not match the one the payer has enrolled. The remark code (N286, N290 and their neighbours) tells you which one.

A code or date field is incomplete

A CPT or HCPCS code is missing a required modifier, a unit count is blank, a diagnosis pointer is missing, or the date of service is outside the statement period. Payers process these as missing-information errors even when the service itself is fine.

Secondary claim sent without the primary's adjudication

A claim sent to the secondary payer without the primary payer's paid amount, adjustment codes and remittance date is returned with CO-16 and MA04. The claim is not denied for coverage; the payer simply cannot calculate its share.

Attachment or extra field the payer requires

Some payers require an NDC on drug claims, an attachment control number, an accident date on injury claims, or a prior authorization number in a specific field. When the field is empty, the whole claim comes back as CO-16.

How to fix it and resubmit

  1. 1

    Read the remark code before touching the claim

    CO-16 on its own is not actionable. The RARC next to it on the 835 or the remittance notice names the missing field. Fix the field the remark names, not the one you suspect.

  2. 2

    Send a corrected claim, not an appeal

    Use the payer's corrected-claim process: frequency code 7 with the original claim number for most commercial payers and Medicaid plans, or a new claim where the payer treats CO-16 as a rejection that never entered its system. An appeal letter for a missing data field is ignored or returned.

  3. 3

    Check timely filing on the corrected claim

    A corrected claim usually has to arrive inside the original filing window, or inside the payer's corrected-claim window counted from the remittance date. If the original was filed late in the window, the corrected claim goes out the same day.

  4. 4

    Confirm the fix landed

    Watch for the acceptance on the clearinghouse report and the next remittance. If the same CO-16 returns with the same remark code, the field is still wrong at the payer's end (an enrollment record, not the claim) and it needs a call.

How to prevent it

  • A scrubber rule for each remark code you have seen in the last year, so the field is checked before the claim leaves
  • Provider enrollment records matched to the NPI and taxonomy on the claim for every payer, and re-checked after any revalidation
  • Secondary claims held until the primary 835 is posted, then released with the primary's adjudication attached automatically
  • A short list of payer-specific required fields (NDC, authorization number position, attachment control number) kept with the payer's claim rules and applied at charge entry
Worked example · hypothetical

A CO-16 with N290 on a group practice claim

A family practice adds a new physician and bills her first week of visits under the group NPI. Every claim returns CO-16 with N290. The payer has not finished linking her individual NPI to the group, so the rendering provider field fails. The fix is not a corrected claim: the biller confirms the enrollment date with the payer, holds her claims until the link is active, then releases them inside the filing window. This is a hypothetical example.

Official text: the X12 claim adjustment reason code list. The meaning above is our paraphrase for billers; the list is the authority.

Next step

The fix for CO-16 sits with claim submission.

See claim submission

FAQ

Questions about CO-16

Is CO-16 a denial or a rejection?

Both happen. Some payers process the claim and deny it with CO-16 on the remittance; others reject it at the front door so it never enters their system. The difference matters for timely filing: a rejected claim was never adjudicated, so the resubmission still has to arrive inside the original filing window.

Can I appeal a CO-16?

Appealing rarely works because nothing was adjudicated. The payer needs the missing information, so the route is a corrected or replacement claim with the field filled. Keep the appeal route for cases where the payer insists a field was missing and your claim image shows it was there.

Why do I get CO-16 with no remark code?

X12 requires at least one remark code with reason code 16, but a few payers still send it without one, which leaves you guessing. Check the claim status in the payer portal or call provider services with the claim number; the representative can usually see the specific edit that fired.

Which remark codes commonly come with CO-16?

Common pairings include M51 (procedure code), MA130 (unprocessable claim), N286 and N290 (referring and rendering identifiers) and MA04 (secondary claim without primary information). The full remark code list is published by X12.

Does CO-16 count against timely filing?

It can. If the corrected claim arrives after the payer's filing limit, the payer may deny it with CO-29 instead. Keep the original claim's acceptance report as proof of timely filing and send the correction as soon as the remark code is read.

Next step

Seeing a lot of CO-16?

Tell us the payer and the volume. Three quick questions, no patient data, a written answer from a biller who works that queue.

  • Three questions, about two minutes
  • No patient data, no software to buy
  • A written reply from a biller, not a sales deck

What happens next

  1. You answer three questions

  2. A billing specialist reads them

  3. A written reply by email

Prefer email? sales@remitwright.com

Seeing a lot of CO-16?

See where claims are getting stuck. No patient data needed.

Step 1 of 3

What do you bill for?

A little about your volume
How many providers? (Medical practice)

Trips per month? (NEMT)

Active clients? (Home care / home health)

Orders per month? (DME)

How many clinicians? (Behavioral health / therapy)

Claims per month, roughly? (Something else)

What's the biggest problem right now?

Where should we send the review?

Add details (optional)

We work inside your system; this tells us which login to ask for.

Please don't include patient information in this form.

  • No patient data requested
  • No obligation
  • Reply in writing
Get a billing review
Billing review

Get a billing review

See where claims are getting stuck. No patient data needed.

Step 1 of 3

What do you bill for?

A little about your volume
How many providers? (Medical practice)

Trips per month? (NEMT)

Active clients? (Home care / home health)

Orders per month? (DME)

How many clinicians? (Behavioral health / therapy)

Claims per month, roughly? (Something else)

What's the biggest problem right now?

Where should we send the review?

Add details (optional)

We work inside your system; this tells us which login to ask for.

Please don't include patient information in this form.

  • No patient data requested
  • No obligation
  • Reply in writing

BAA signed before any access, a user you create, MFA on. Patient data stays in your systems. How access works