Denial CO-16: Claim Lacks Information

What CO-16 is, and is not

CO-16 is a processing outcome, not a coverage decision. The payer’s system found a required element missing, invalid, or contradictory, and stopped. Nothing about the medical service was judged. That has two implications: the claim can usually be paid quickly once the defect is fixed, and treating it like a real denial (appeal letters, clinical documentation) wastes weeks on a problem a field correction solves in days.

CO-16 never arrives alone. It is required to be paired with remark codes (RARCs) that identify what was missing or wrong. The RARC is the actual message; CO-16 is just the envelope.

The usual OB culprits

Maternity claims have field requirements that ordinary E/M claims do not, which is why CO-16 shows up disproportionately on them:

• Missing delivery date on global claims. Many payers require the delivery date on 59400-family claims, in the claim’s date fields or as a supplemental date element, in addition to the date of service. A global claim without it is unprocessable at some payers.
• Missing or conflicting LMP date. The last-menstrual-period date is a standard data element on pregnancy claims (box 14 on the paper form, its electronic equivalent otherwise), and some payers hard-require it with the correct qualifier.
• TC/26 modifier gaps. Ultrasounds and NSTs billed by a provider who should be reporting only the professional component, with no modifier 26, or a facility claim missing TC. The payer cannot tell which component is being claimed, so it processes nothing. See the component split mechanics.
• Rendering NPI mismatches. The rendering provider’s NPI absent, not matching the enrolled group, or belonging to a provider not credentialed with that payer. Common in OB groups where the delivering physician differs from the physician on the account.
• Missing outcome or weeks-of-gestation data. Some payers require an outcome-of-delivery diagnosis (Z37.-) on delivery claims, or reject pregnancy diagnoses missing the trimester or weeks-of-gestation coding (Z3A.-) their edits expect.

Read the RARC, not the CARC

The remittance’s remark codes point at the defective element. The ones that recur on OB claims:

Two or more RARCs can appear on one line. Fix all of them before resubmitting; correcting one defect and bouncing on the next costs a full adjudication cycle each time.

Fix and resubmit vs appeal

The decision rule is short: if the information genuinely was missing or wrong, correct the claim and resubmit. Follow the payer’s corrected-claim process (frequency code 7 with the original claim number, or the payer’s portal workflow) rather than submitting a fresh duplicate, which risks a duplicate-claim denial stacking on top of the original problem.

Appeal only when the payer’s edit is wrong on the facts: the modifier was present, the NPI was valid and enrolled, the date was transmitted. That happens, particularly with clearinghouse translation issues where a field was populated in your system but dropped or reformatted in transit. In that case, pull the actual 837 file your clearinghouse transmitted before appealing; if the field died in transit, the fix is a clearinghouse correction and a resubmission, and an appeal to the payer would have gone nowhere.

Note the MA130 special case: Medicare treats unprocessable claims as never filed, so there is nothing to appeal by design. The corrected claim is the only path, and the timely filing clock keeps running while you fix it. That last point is the real cost of CO-16: defects that linger can push a claim past filing deadlines. Work these denials within days, not at end-of-month.

Preventing the repeat

CO-16 is the most preventable denial family in OB billing because the defects are structural, not clinical:

• Build claim edits that hold global delivery claims until a delivery date and outcome diagnosis are present
• Require LMP with the correct qualifier on every pregnancy claim before release
• Scrub imaging claims for component modifiers matching the place of service
• Reconcile rendering NPIs against each payer’s enrollment roster quarterly, not just at onboarding

FAQ

What does denial code CO-16 mean? The claim lacks information or contains a submission or billing error and could not be processed. The remark codes on the remittance identify the specific missing or invalid element.

Should I appeal a CO-16 denial? Usually no. Fix the identified defect and submit a corrected claim through the payer’s replacement-claim process. Appeal only when you can show the information was actually present and valid as transmitted.

Does CO-16 stop the timely filing clock? No, and with Medicare’s MA130 the original claim is treated as never filed. Correct and resubmit quickly; a defect left sitting can turn a fixable rejection into a permanent write-off.