CO-16
Billing/Follow-Up

Missing/Invalid/Incomplete Claim Information

The payer is saying the claim itself was incomplete or contained an error somewhere — a required field is missing, invalid, or does not match what the payer has on file.

Guided troubleshooter available for this denial

Answer a few questions to reach the correct disposition. No patient or claim identifiers requested.

D01
PrimaryCO-16

In plain language

The payer is saying the claim itself was incomplete or contained an error somewhere — a required field is missing, invalid, or does not match what the payer has on file. The accompanying RARC names the specific field.

Start here

Read the RARC paired with CO-16 — it names the defective field.

Who resolves it

Billing/Follow-Up

Who prevents it

Registration/Patient Access (demographic fields) or Coding/HIM (code-format fields) or IT (interface/export defects), depending on which field is defective.

RelatedCO-125CO-227CO-226
Common RARCsMA130M51M76M20M77MA27N4
Resolution path
Work these steps in order for D01 / CO-16

How to resolve this denial, step by step

  1. 1

    Read the RARC paired with CO-16

    it names the defective field.

  2. 2

    Pull the original claim and source documentation (registration record, order, chart).

  3. 3

    Compare the submitted field to the source; identify whether the data was wrong on the claim or wrong at the source.

  4. 4

    Correct the claim field.

  5. 5

    Resubmit as a corrected claim (not a duplicate) if the original was processed as unprocessable/returned; use claim frequency code 7 (replacement) if the original was adjudicated.

  6. 6

    Document the correction and root cause.

  7. 7

    If the same field triggers the denial across multiple claims/providers, escalate to the workqueue owner for scrubber-edit or template review.

Then choose the correct disposition

Corrected claim

appropriate almost always, since CO-16/MA130 usually reflects an unprocessable claim with no appeal rights (RARC MA130).

Formal appeal

not applicable when the claim was never accepted as a "claim" for adjudication purposes (unprocessable submissions typically carry no appeal rights).

Stop and escalate when

  • Same field defect recurring across many claims/providers (systemic/IT issue); RARC indicates a field the biller cannot correct without provider or payer input (e.g., taxonomy mismatch tied to enrollment).

What Needs to Be Corrected

  • Claim correction: Fix the specific field identified by the RARC and resubmit.
  • Upstream correction: If the same field is repeatedly wrong (e.g., always missing NPI on a specific procedure), the source system template, scrubber edit set, or registration workflow needs a permanent fix, not just a one-off correction.

Do Not Do This

  • Do not guess at the missing field without checking the RARC and source documentation.
  • Do not resubmit the exact same claim unchanged expecting a different result.
  • Do not alter clinical or diagnosis data to "make the claim pass" scrubber edits without documentation support.