The CO-16 denial code is the payer’s way of saying “something is missing.” On its own it is frustratingly vague — but CO-16 is never supposed to travel alone. It is always paired with a Remittance Advice Remark Code (RARC) that pinpoints exactly what information is missing or wrong.
Master how to read that pair, and CO-16 becomes one of the fastest denials to resolve.
What the CO-16 denial code means
The X12 definition of CO-16 is: “Claim/service lacks information or has submission/billing error(s).”
By rule, CO-16 requires at least one accompanying RARC (codes beginning with M or N, such as N265 or MA27) that identifies the specific missing element. The CARC (CO-16) tells you that something is missing; the RARC tells you what.
How to read the RARC — the key to fixing CO-16
Always look past CO-16 to the remark code beside it. Common examples:
- Missing/invalid NPI — rendering, referring, or billing provider identifier is absent or wrong.
- Missing/invalid referring provider information — required for services that need a referral or order.
- Missing/incomplete diagnosis — a required ICD-10 code is absent or not to full specificity.
- Missing/invalid subscriber or member ID — patient demographic or insurance data doesn’t match the payer’s file.
- Missing prior payer information — for secondary claims, the primary payer’s payment details weren’t reported.
Common causes of CO-16 denials
- Incomplete provider identifiers — missing or mismatched NPI or taxonomy. Understanding the rendering vs billing provider distinction prevents many of these.
- Patient data mismatches — name, date of birth, or member ID that doesn’t match the payer’s records.
- Missing referral or authorization data where the plan requires it.
- Coordination-of-benefits gaps on secondary claims — our primary and secondary insurance guide explains what the secondary claim must include.
- Incomplete diagnosis coding — codes not carried to required specificity.
How to fix a CO-16 denial
- Find the RARC next to CO-16 on the remittance advice — this names the exact field.
- Look up the remark code to translate it into the missing element.
- Correct the specific field — add the NPI, fix the member ID, complete the diagnosis, or attach the referral data.
- Verify related fields for the same error type before resubmitting.
- Submit a corrected claim with the complete information.
Is CO-16 a rejection or a denial?
CO-16 appears on an adjudicated remittance, so technically it is a denial — the claim entered the system and came back with a reason code. That differs from a front-end rejection, which never reaches adjudication. The distinction changes how you resubmit, and we break it down fully in rejected vs denied claims.
Prevent CO-16 denials
- Validate patient demographics at every visit against the insurance card and payer portal.
- Use a claim scrubber that checks for missing NPIs, taxonomy codes, and required fields before submission.
- Confirm referral and COB data during intake and benefits verification.
- Standardize your data-entry checklist so required fields are never skipped.
CO-16 is highly preventable with clean intake. For the full set of adjustment codes, see our denial codes guide.
Frequently Asked Questions
What does CO-16 mean?
CO-16 means the claim lacks required information or contains a submission or billing error. It is always paired with a remark code (RARC) that identifies the exact missing element, such as an NPI, member ID, or diagnosis.
How do I fix a CO-16 denial?
Read the RARC (M or N code) beside CO-16 to find the specific missing field, correct that field (and any related ones), and submit a corrected claim with the complete information.
What are RARC codes and why do they matter for CO-16?
RARCs are Remittance Advice Remark Codes that supplement a CARC like CO-16. Because CO-16 only says information is missing, the RARC is what tells you precisely what to fix, making it the most important part of the denial to read.
Is CO-16 a claim rejection or a denial?
CO-16 is a denial — it appears on an adjudicated remittance after the claim was processed. A rejection is different: it fails front-end edits and never reaches adjudication.
