Denial Knowledge Center
CO-16 — 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.
D01
Resolves: Billing/Follow-Up
Prevents: Registration/Patient Access (demographic fields) or Coding/HIM (code-format fields) or IT (interface/export defects), depending on which field is defective.
Primary CARCCO-16
RelatedCO-125CO-227CO-226
Common RARCsMA130M51M76M20M77MA27N4
Denial Identifier
- Primary CARC: CO-16 — "Claim/service lacks information or has submission/billing error(s)... At least one Remark Code must be provided (may be comprised of either the NCPDP Reject Reason Code, or Remittance Advice Remark Code that is not an ALERT.)" (X12)
- Common RARCs: MA130 (unprocessable claim, no appeal rights), M51 (missing/incomplete/invalid procedure code), M76 (missing/incomplete/invalid diagnosis), M20 (missing/incomplete/invalid HCPCS), M77 (missing/incomplete/invalid place of service), MA27 (missing/incomplete/invalid entitlement number/name), N4 (missing/incomplete/invalid prior insurance carrier EOB) (X12 RARC)
- CARC/RARC combination: CO-16 is a "container" code — by X12 usage rule it must always carry at least one RARC identifying the specific defect. The RARC, not the CARC, tells the biller what is actually wrong.
- Other related CARCs: CO-125 (deactivated 2013, historically similar), CO-226/CO-227 (info requested not provided — see D20)
- Combinations vary by payer and by which data element is defective; do not assume a fixed RARC accompanies CO-16.
Plain-Language Meaning
- 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.
Why the Claim Was Denied
- Registration: incorrect demographic or insurance field captured at intake
- Claim construction: required loop/segment omitted in the 837 transaction, or paper claim field left blank
- Coding: invalid or truncated CPT/HCPCS/ICD-10 code format
- Charge capture: missing units, missing revenue code pairing
- Information systems: practice-management system dropping a required field on export
Information the Biller Must Review
- Patient name/DOB, Member ID, payer ID, CPT/HCPCS, diagnosis codes, NPI (billing/rendering), place of service, ERA/EOB remark text, original claim form (CMS-1500/UB-04) or 837 file.
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.
Resolution Workflow
- Read the RARC paired with CO-16 — it names the defective field.
- Pull the original claim and source documentation (registration record, order, chart).
- Compare the submitted field to the source; identify whether the data was wrong on the claim or wrong at the source.
- Correct the claim field.
- 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.
- Document the correction and root cause.
- If the same field triggers the denial across multiple claims/providers, escalate to the workqueue owner for scrubber-edit or template review.
Corrected Claim vs Appeal vs Other Action
- 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).
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.
Department Most Likely Responsible
- Resolves current claim: Billing/Follow-Up. Prevents recurrence: Registration/Patient Access (demographic fields) or Coding/HIM (code-format fields) or IT (interface/export defects), depending on which field is defective.
Prevention Control
- Front-end claim scrubber edits validating required fields before submission; registration double-entry verification against insurance card/eligibility response; periodic 837 file audits for systemic field drops.
Escalation Trigger
- 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).
Sample Scenario
- Scenario: Claim denied CO-16 with RARC M76 (missing/incomplete/invalid diagnosis).
- Finding: The diagnosis code field was truncated during 837 export due to a character-length interface defect.
- Action: Corrected claim submitted with full diagnosis code; IT ticket opened to fix the interface truncation.
Resolution path at a glance
IdentifyAssign ownerCorrectResubmit / AppealPrevent
AI Search Terms / Synonyms
- CO16; CO-16; claim lacks information; missing information denial; unprocessable claim;
- MA130; incomplete claim.
AI Answer Guardrail
- Verify the specific RARC paired with CO-16 before advising any correction — the CARC alone never identifies the defective field.
Sources
- X12 CARC list; X12 RARC list
Validated ClaimetryX Source — Denial Management Knowledge Base, 2026 Research Edition
Research date August 18, 2026. CARC/RARC combinations and payer processes vary. Always check the specific remittance advice and the payer's current requirements before acting on any denial.
Work this denial faster
Denial trackers, corrected-claim checklists, and appeal templates.
Get denial trackers & appeal templates