Denial code CO-16 — claim lacks information or has a submission error
CO-16 is a contractual-obligation code: the payer is saying the claim is incomplete or incorrect as submitted. Most recoveries come from fixing the missing field and resubmitting — not from a formal appeal.
Last reviewed against published HFMA, CMS, MGMA, Premier, and related primary sources linked on this page on .
What CO-16 means
CO-16 (group code CO = contractual obligation) means the payer adjudicated the line as lacking required information or containing a submission/billing error. The short description alone rarely names the field — that detail almost always sits in a companion RARC (MA/N remark code) on the same remittance. First action: read every remark code on the line, then correct and resubmit within the timely-filing window rather than opening a formal appeal.
What the code actually says
X12 publishes Claim Adjustment Reason Code 16 with the short description: “Claim/service lacks information or has submission/billing error(s).” (X12 CARC list (opens in a new tab), as of this page’s last review). The group code CO on the remittance indicates the adjustment is a contractual write-off against the provider under the payer’s rules for that transaction — not automatically a patient balance (X12 CARC (opens in a new tab)).
What it means in practice is narrower and messier. CO-16 is a bucket: the claim failed a completeness or format check, but the specific missing item — diagnosis pointer, NPI taxonomy, prior-auth number, attachment control number, place of service, subscriber ID digit — lives on the RARC, not the CARC. X12 maintains those remark codes separately (X12 RARC list (opens in a new tab)). Billing teams that work CO-16 without opening the remark codes are guessing.
Medicare claim submission and remittance conventions are described in the Medicare Claims Processing Manual (Pub. 100-04) (opens in a new tab). Commercial payers use the same CARC/RARC vocabulary under HIPAA claim-status standards, but their required fields and companion-guide edits differ by plan.
Most common causes and where they originate
Missing or invalid diagnosis pointer
- Where it originates
- Charge entry / coding
- How to confirm on the remit
- RARC naming diagnosis, ICD, or pointer
- Prevention owner
- Coding + charge capture
Subscriber/member ID mismatch
- Where it originates
- Registration / eligibility
- How to confirm on the remit
- RARC on member ID, policy, or group number
- Prevention owner
- Front desk + eligibility
Rendering or billing NPI / taxonomy incomplete
- Where it originates
- Provider enrollment + claim build
- How to confirm on the remit
- RARC on NPI, taxonomy, or provider data
- Prevention owner
- Credentialing + billing ops
Prior-auth number not on claim
- Where it originates
- Auth desk + charge entry
- How to confirm on the remit
- RARC on authorization or referral number
- Prevention owner
- Clinical ops + billing
Missing attachment or medical records control number
- Where it originates
- Billing ops
- How to confirm on the remit
- RARC on attachment, PWK, or documentation
- Prevention owner
- Billing ops
Place of service / facility type mismatch
- Where it originates
- Scheduling + coding
- How to confirm on the remit
- RARC on POS or facility
- Prevention owner
- Coding + scheduling
Incomplete other-payer or COB loop
- Where it originates
- Registration + secondary billing
- How to confirm on the remit
- RARC on other insurance or coordination
- Prevention owner
- Registration + billing
Operational framing from common outpatient claim edits — not a ranked national study. Pull your own top CO-16 RARC pairs from a 90-day denial file.
Working the denial, in order
Step 1
Read every RARC / remark code on the line
Open the 835 or payer portal remit for the claim line. List every MA/N remark beside CO-16 before touching the claim ([X12 RARC](https://x12.org/codes/remittance-advice-remark-codes)). If the portal only shows CO-16, pull the electronic remittance — portals sometimes hide remark detail.
Step 2
Map the remark to a field, not a narrative
Translate each RARC into a concrete claim field (diagnosis pointer, auth number, NPI, attachment). If you cannot name the field, you are not ready to resubmit.
Step 3
Pull source-of-truth documentation
Eligibility response, auth letter, enrollment file, operative note, or face sheet — whichever owns the missing data. Do not invent a value to clear an edit.
Step 4
Correct and resubmit vs formal appeal
Most CO-16 recoveries are corrected claims or replacements, not appeals. Use a formal appeal only when the payer has the correct data and still denies, or when the remark is wrong on the facts. Medicare’s appeal ladder and deadlines are summarised in [MLN006562](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf) (as of that MLN publication).
Step 5
Check the timely-filing clock
Note original submission date, remit date, and payer timely-filing limit. Corrected claims still fail if the clock has run. Secondary claims often have shorter residual windows.
Step 6
Log the root cause for prevention
Tag the workqueue item with the RARC family and owning department. A CO-16 cleared without a process fix is a repeat denial pre-ordered. Labour cost of repeated adjudication is non-trivial — see [cost to collect](/cost-to-collect) and Premier’s published adjudication-cost work ([source](https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense)).
Before you resubmit
- Every RARC on the line is written down next to CO-16If the 835 and the portal disagree, trust the 835 and archive both.
- Diagnosis codes and pointers match the service linePrimary diagnosis supports medical necessity language for that procedure; pointers are not blank or out of range.
- Member ID, group, and subscriber relationship match the eligibility responseCopy from the current eligibility transaction, not last year’s card image.
- Billing and rendering NPI, taxonomy, and taxonomy qualifier are present where requiredCompare to the payer’s enrollment file for that TIN/NPI combination.
- Prior-auth or referral number is on the claim in the field the payer expectsAuth is active for the date of service and the billed codes.
- Required attachments have a control number and were acceptedPWK segment / portal upload confirmation stored with the claim.
- Place of service and facility NPI (if any) match the encounterTelehealth, POS, and modifier rules checked against the payer’s current policy for the date of service.
- Timely-filing and corrected-claim frequency codes are still validReplacement claim uses the correct claim frequency code and original reference number when required.
Preventing it upstream
CO-16 is overwhelmingly a front-end completeness problem. Ownership sits with registration (member data), clinical ops (auth numbers), coding (pointers and POS), and charge entry (NPI, attachments) — not with appeals specialists.
Controls that cut recurrence:
- Eligibility at scheduling and again at check-in, with automated comparison of member ID digits to the card on file.
- Auth number as a hard stop in charge entry when the payer/code combination requires authorization.
- Claim scrub rules that reject outbound 837s missing diagnosis pointers, taxonomy, or attachment flags the payer has historically returned as CO-16.
- Weekly RARC Pareto on CO-16 only — prevent the top two remark families before hiring more denial staff.
When denial labour dominates staff time, re-run the arithmetic on cost to collect. For the management frame (prevention vs appeal capacity), see the denials hub.
How this code differs from ones it gets confused with
CO-16 vs [CO-109](/denials/co-109). CO-16 says this payer needs more or better data on a claim it is processing. CO-109 says this is the wrong payer or contractor — stop fixing fields and re-route the claim.
CO-16 vs [CO-96](/denials/co-96) / [PR-204](/denials/pr-204). Missing information is not the same as non-covered. If the plan excludes the benefit entirely, correcting fields will not create coverage. PR-204 is a patient-responsibility non-coverage signal; CO-96 is a contractual non-covered charge framing. Read the RARC and the EOB benefit language before treating either as a scrub error.
CO-16 vs [CO-22](/denials/co-22). CO-22 is coordination of benefits — another plan may be primary. You may also see information edits on COB loops that travel with CO-16 remarks; still, the reason is COB order, not a missing CPT modifier.
When you are unsure, the remark codes and the group code (CO vs PR vs OA) decide who is billed next — not the biller’s narrative summary.
Common questions
- What does the CO-16 denial code description actually mean?
- X12’s short description is that the claim or service lacks information or has submission/billing error(s). In operations it means the payer could not fully adjudicate the line as submitted; the specific missing or invalid field is almost always on the companion RARC, not in the CO-16 text itself.
- Is CO-16 a patient balance?
- The CO group code marks a contractual obligation adjustment under the remittance standards — it is not itself a PR (patient responsibility) code. Do not automatically statement the patient for a CO-16. Fix the claim or appeal; only transfer balance when a PR group code or a verified patient liability applies.
- Should I appeal CO-16 or just correct the claim?
- Correct and resubmit when the RARC names data you can supply. Appeal when the payer already has complete, accurate data and still denies, or when the remark is factually wrong. Track labour cost — see the denials hub and cost-to-collect calculator.
- Why does CO-16 keep coming back on the same payer?
- Usually a systemic scrub or enrollment gap (taxonomy, auth workflow, diagnosis pointer rules), not bad luck on one claim. Rank CO-16 by RARC family and fix the top sources upstream.
Sources
- X12 Claim Adjustment Reason Codes (CARC) (opens in a new tab) — X12
- X12 Remittance Advice Remark Codes (RARC) (opens in a new tab) — X12
- CMS Medicare Claims Processing Manual (Pub. 100-04) (opens in a new tab) — Centers for Medicare & Medicaid Services
- CMS MLN006562 — Medicare Parts A & B Appeals Process (opens in a new tab) — Centers for Medicare & Medicaid Services
- Premier: claims adjudication costs providers $25.7 billion (opens in a new tab) — Premier Inc.
Last reviewed against published HFMA, CMS, MGMA, Premier, and related primary sources linked on this page on .
Every benchmark and formula on this page is sourced and dated above. Where a figure is a range, the range is the honest answer, not a hedge. If you think something here is wrong or out of date, tell us — corrections are logged and dated.