Blog Details
CO-22 denial code: what it means, what it prohibits, and how to resolve it
The X12 definition reads: this care may be covered by CO-22 means the payer believes another insurer should have paid another payer per coordination of benefits.
It does not mean the service isn’t covered. That distinction matters more than anything else on this page, because several widely-read explanations of CO-22 get it wrong, and a practice acting on the wrong definition writes off money it could have collected.
If you’re trying to understand how payer order gets decided in the first place, the birthday rule, Medicare thresholds, and the rest, that’s a different question and our coordination of benefits guide covers it. This page is for what to do with the denial in front of you.
What CO-22 is not
Worth clearing out first, because the confusion is common and expensive.
Not service not covered. Some published guidance defines CO-22 this way. It’s incorrect. Non-covered services carry CARC 96 (non-covered charge) or CARC 204 (not a covered benefit under the patient’s plan). Those codes mean the money isn’t there. CO-22 means the money is somewhere else.
Not a medical necessity denial. That’s CARC 50.
Not a terminated coverage denial. That’s CARC 27, and it means something quite different: no active coverage at all, versus coverage that exists but isn’t first in line.
Not a rejection. The claim was adjudicated. It reached the payer, was processed, and came back with a decision, which means appeal rights and timely filing rules apply in the normal way.
The practical translation: a CO-22 claim is usually payable. It went to the wrong door.
What the CO prefix prohibits
The two letters before the number are the group code, and they assign financial responsibility. CO stands for contractual obligation which per CMS guidance means the provider absorbs the adjustment under the payer contract. The patient cannot be billed for a CO-adjusted amount.
Beneficiaries may be billed only when an adjustment carries the PR (patient responsibility) group code. So while you’re working a CO-22 denial, the balance is not available to bill to the patient. For a Medicare beneficiary, billing a CO-22 amount directly violates the provider agreement, and repeated violations invite audits, recoupment demands, and in serious cases loss of network participation.
This produces something structurally unusual. Most denial categories offer some fallback: if the payer won’t pay, there’s often a path toward patient responsibility. CO-22 closes that path while simultaneously making resolution depend on information you may not hold. There’s no exit except getting the claim to the right payer.
Which is why these denials deserve faster handling than their apparent stakes suggest. Nothing about a CO-22 line looks urgent. It’s a routine, extremely common code. But it’s an all-or-nothing balance with a timely filing clock running against it, and the second payer’s clock may be running too.
The resolution workflow
Work it in this order. The sequence matters because steps two and three have very different turnaround times.
1. Determine who is actually primary. Not who the patient handed you at check-in. Apply the coordination rules: subscriber status, the birthday rule for dependent children, active employment versus retiree or COBRA coverage, court orders in custody situations, and for Medicare patients the Medicare Secondary Payer rules. MSP stands for Medicare Secondary Payer. It’s occasionally written as Medicaid Secondary Payer, including in published billing guidance, and that’s an error worth not repeating internally
2. Check what the payer has on record. Two different situations produce the same denial code, and they resolve differently:
- You billed the wrong payer. Straightforward. Rebill the correct primary, then submit to the secondary with the primary’s EOB attached.
- The payer’s COB record is stale or empty. Harder, because the fix isn’t yours to make. Insurers maintain coordination information from the member’s own reporting, and the member is the party who has to update it. No document you send resolves it, because the payer isn’t asking you for one.
3. Act on which situation you’re in. For the first, rebill immediately. For the second, contact the patient, explain that their insurer needs updated other-coverage information, and follow up rather than waiting. This is the step that stalls, and claims sitting in “waiting on patient” status age silently.
4. Submit the secondary claim properly. Once the primary has adjudicated, the secondary claim needs the primary’s EOB or remittance attached showing what was paid and adjusted. Secondary claims submitted without it get denied again for a different reason.
5. Watch both timely filing clocks. The primary’s window and the secondary’s window run independently, and the secondary’s may be measured from the primary’s adjudication date. A CO-22 resolved after both windows close is a permanent write-off that can’t be billed to the patient either, per the group code.
Read the paired RARC on the remittance line before starting. Payers use remark codes to add specifics about which payer they believe is primary, and that detail can save a phone call.
Why CO-22 keeps coming back
If you’re seeing this code repeatedly, the cause is almost always upstream rather than in billing.
Coverage changes and nobody asks. Patients change jobs, add a spouse’s plan, turn 65, have a baby, or move to COBRA, and none of those events notify your practice. A coverage question asked once at initial registration is a snapshot of a situation that changes constantly.
The fix is unglamorous: ask every patient at every visit whether they have any other coverage. Real-time eligibility verification at check-in catches much of it, and the question catches the rest. A minute at the front desk is worth considerably more than the same minute spent in AR three months later, when you’re asking a favor of someone who’s already gone home.
Recording the reasoning helps too. “Primary = Cigna per birthday rule” lets whoever works a future denial understand the original determination instead of re-deriving it.
Why these get abandoned
A structural note about how CO-22 denials get treated, consistent with what this series has found elsewhere.
Consider this denial from the perspective of a billing operation paid a percentage of collections. Resolution may depend on a patient making a phone call to their insurer, which you can’t control or schedule. The effort is unbounded. And unlike most denial types, there’s no patient-responsibility fallback, because the CO group code forecloses it. So the claim either gets to the right payer or earns nothing at all.
An unbounded-effort, third-party-dependent, all-or-nothing claim is close to the worst-ranked item on any queue prioritized by expected return. Meanwhile “waiting on patient” is a status that can persist indefinitely without anyone making a decision to abandon it, so the claim ages without ever being formally given up on.
That isn’t a claim about anyone’s diligence. It’s how prioritization works when revenue is a percentage of what gets collected. A flat fee doesn’t make patient outreach easier, but it removes the arithmetic that makes it irrational, and it makes the honest measurement visible: how many claims are currently parked in COB status, and how long they’ve been sitting there. Mediflows reports that number alongside rejection aging and allowed-amount variance, because they share a property. Each measures money that leaves without anyone deciding to let it go.
The bottom line
CO-22 means another payer is primary. The service is probably covered, the claim is probably payable, and the balance cannot be billed to the patient while you sort it out. Determine the real primary, find out whether the problem is your submission or the payer’s records, and move fast, because the filing clocks are running and this denial has no fallback.
If CO-22 keeps appearing on your remittances, the cause is at registration rather than in billing. A free revenue audit will show how many of your open claims are sitting in this status and how long they’ve been there. Call 888-305-4084 or start at our page denial management services page.
What does the CO-22 denial code mean?
CO-22 means the payer believes another insurer should have paid first. The X12 definition is that the care may be covered by another payer per coordination of benefits. It doesn't mean the service is uncovered; it means the claim went to the wrong payer or in the wrong order.
Ca nyou bill the patient for a CO-22 denial?
No. CO stands for contractual obligation, a group code meaning the provider absorbs the adjustment under the payer contract. Patients may only be billed for amounts carrying the PR (patient responsibility) group code. Billing a Medicare beneficiary for a CO-22 amount violates the provider agreement.
How do you fix a CO-22 denial?
Determine which plan is genuinely primary using the coordination rules, then find out whether you billed the wrong payer or the payer's records lack current coverage information. If it's the former, rebill the correct primary and then submit to the secondary with the primary's EOB attached. If it's the latter, the patient has to contact their insurer to update their record, because the member is the only party who can do that.
What is the difference between CO-22 and CO-96?
CO-22 means another payer is primary, so the service is likely covered but billed to the wrong insurer. CARC 96 means the charge is non-covered, and CARC 204 means the service isn't a covered benefit under the patient's plan. CO-22 points at a different payer; 96 and 204 point at an absence of coverage.
Categories