CO-252 Denial Code: Attachment or Documentation Required to Adjudicate

What Does CO-252 Mean?

CO-252 means the payer won't decide the claim until it sees supporting documentation — an operative note, invoice, primary EOB, certificate of medical necessity, or whatever the accompanying remark code names. The claim isn't rejected on its merits; it's parked, waiting for paper.

Code group: CO (Contractual Obligation) · Appealable: Not an appeal situation — a document-delivery-and-follow-up situation. Escalate only when submitted records aren't being processed.

Why CO-252 Happens

The service type routinely triggers documentation review: unlisted codes, high-dollar claims, modifier 22 (increased procedural services), cosmetic-adjacent procedures, and new-technology codes.
A required attachment was expected and not received — invoices for unlisted codes, primary EOBs on secondary claims, CMNs for DME.
You're under a prepayment review or targeted probe, and every claim of a certain type now demands records.
The documentation WAS sent but didn't connect — faxed to a queue, uploaded without the claim number, or sent before the claim arrived so nothing matched.

How to Fix a CO-252 Denial — Step by Step

Read the remark codes for exactly what's wanted, and check the payer portal — many list required attachments per claim.

Send precisely what's requested, labeled with the claim number, member ID, and DOS on every page — unmatched documentation is the silent killer of CO-252 resolution.

Use the payer's attachment channel of record (portal upload beats fax; fax beats mail) and keep transmission proof.

Calendar a follow-up 15–30 days out; documentation review has its own clock, and claims 'awaiting documentation' can quietly die of old age.

If you're seeing CO-252 in volume, ask provider relations whether you're on prepayment review — and address the underlying audit trigger, not just each claim.

CO-252 Appeal Letter Template

Adapt this wording to your claim — replace the bracketed fields and attach the documentation it references:

CO-252 wants fulfillment, not argument: send the records. Escalate when the process fails: 'Claim [number] pended CO-252; the requested [documentation] was submitted on [date] via [channel, confirmation #]. Adjudication remains outstanding beyond your published review timeline. We request immediate processing or written notice of any additional requirements.'

How to Prevent CO-252

Send known-required attachments WITH the claim (or immediately after) for unlisted codes, modifier 22, and secondaries — don't wait to be asked.
Label every page of every attachment with claim number, member ID, and DOS.
Track pended-for-documentation claims as their own AR category with follow-up dates — they aren't denials, but they age like them.

Related Denial Codes

CO-16 — Missing information CO-50 — Not medically necessary CO-29 — Timely filing

← Back to the full denial code library

Reviewed by the LegitMedBilling denial management team. This guide is general billing information, not legal or payer-specific advice — always verify against your payer contract and current policy.

Frequently Asked Questions

Is CO-252 a denial?

Technically no — it's a pend: the payer is holding adjudication until documentation arrives. But treat it with denial-level urgency, because pended claims that nobody follows up on become timely-filing write-offs. Same discipline, different label.

We sent the records twice and the claim still shows pending. Now what?

Escalate with proof: submission dates, channels, confirmation numbers, and a demand for processing per the payer's own review timelines. Documentation that isn't labeled with the claim number frequently lands in a queue and matches nothing — relabel and resend through the portal, then escalate to provider relations if it persists.

Why are ALL our claims for one procedure suddenly asking for records?

That pattern usually means prepayment review — the payer flagged something (often modifier 22 usage, an outlier billing pattern, or a high-cost code) and now audits every instance. Ask provider relations directly. The exit is demonstrating consistent, clean documentation over a review period; the entry was usually a pattern worth understanding anyway.