Guide

CO-22: the other payer is primary — now prove it

Summary

A CO-22 denial means the payer believes a different plan is primary for this claim and should have paid first. It is not a coverage denial — it is a sequencing problem, usually because the payer's coordination-of-benefits file is out of date. The fix is confirming which plan is actually primary today, updating that information directly with the payer's COB unit, and resubmitting secondary claims with the primary payer's EOB attached as proof of how much it already paid.

By Gale Editorial · Updated 2026-07-26. Every figure cited to a dated source. How we write.

What does a CO-22 coordination of benefits denial mean?

A CO-22 denial means the payer believes a different plan is primary for this claim and should have paid before this one does — it is a Claim Adjustment Reason Code specifically about payment order, not about whether the service is covered 1Ref 1X12 (2026).Claim Adjustment Reason Codes.That CARCs, including CO-22, are the standard X12 code list explaining why a claim paid differently than billed — used here as the definition of what a CO-22 actually signals: a dispute over payment order, not coverage.. Coordination of benefits is the process that determines which plan pays first when a patient has more than one, and CMS runs a national program to manage that order for Medicare specifically 2Ref 2Centers for Medicare & Medicaid Services (2026).Coordination of Benefits and Recovery Overview.That coordination of benefits determines primary vs secondary payer order and that CMS runs a national program to manage that order for Medicare — used here as the underlying mechanism a CO-22 denial is disputing, and why a secondary claim needs proof of what the primary plan paid..

The claim isn't necessarily wrong, and the service isn't necessarily uncovered — the payer is saying its records show another plan should be billed first, and it wants proof of what that plan actually did before it will process its own share.

Confirm what the payer's system currently believes

Before anything else, find out exactly what the payer's file shows: which plan it has listed as primary, and how old that information is. Coordination-of-benefits data goes stale constantly — a patient changes jobs, ages into Medicare, adds a spouse's plan, or drops one entirely — and payer systems do not always catch the change before the next claim runs through it.

A CO-22 on a claim where the patient's coverage genuinely hasn't changed is usually a stale-data problem, not a real dispute about payment order. Pulling the specific COB record the payer is working from is the fastest way to see whether it's simply out of date.

Verify with the patient which plan is actually primary today

The patient is usually the fastest source of truth on what changed. A short conversation — has coverage changed jobs, been added, or ended since the last visit — often resolves in minutes what a payer's outdated file cannot answer on its own.

Once the current, correct order is confirmed, that information needs to reach the payer directly, not just live in your chart: most payers have a coordination-of-benefits unit or an online attestation process built specifically for updating which plan is primary. Routing the correction through that channel, rather than simply resubmitting the claim, is what actually updates the record the next claim will be checked against.

Resubmit with the primary payer's EOB attached

Once the payer order is settled, a secondary claim needs more than a corrected form — it needs proof of what the primary plan actually paid. Attach the primary payer's explanation of benefits or remittance showing what it allowed, paid, and left as patient responsibility, since that is what a secondary payer uses to calculate its own share 2Ref 2Centers for Medicare & Medicaid Services (2026).Coordination of Benefits and Recovery Overview.That coordination of benefits determines primary vs secondary payer order and that CMS runs a national program to manage that order for Medicare — used here as the underlying mechanism a CO-22 denial is disputing, and why a secondary claim needs proof of what the primary plan paid..

A secondary claim submitted without that attachment often denies again for the same reason, because the payer still has no record of the primary's determination — the CO-22 doesn't clear itself just because the order is now correct on paper; it clears when the payer can see the primary's numbers.

When there's no other coverage at all

Sometimes the payer's file lists another plan the patient doesn't actually have, or no longer has, and there is no COB determination to prove because there's genuinely nothing to coordinate. In that situation, many payers place the claim on what's sometimes called a cob hold rather than issuing a hard denial, pending confirmation there's no other coverage to check against.

Clearing that hold usually means the patient directly confirming no other coverage exists, often through the payer's own attestation form or member portal rather than anything the practice submits on the claim itself. Until that confirmation lands, resubmitting the same claim without it tends to produce the identical result.

CO-22 isn't the same problem as a duplicate or a missing-authorization denial

It's worth keeping CO-22 separate in your head from other denial families that can look similar at a glance. It questions payment order, not whether the claim already exists or whether a service was authorized — co-18 duplicates, for instance, question whether this exact claim was already submitted and processed, an entirely different mechanism triggering an entirely different fix.

Treating a CO-22 like a duplicate — simply resending the claim unchanged — accomplishes nothing, because the payer's objection was never about having seen the claim before. The fix has to address payment order specifically: confirm it, document it, and attach proof of what the other plan did.

Reading the RARC and knowing which rulebook applies

The Remittance Advice Remark Code riding with a CO-22 often names which other plan the payer believes is primary, which turns a guess into a direct call to that plan or the patient 3Ref 3X12 (2026).Remittance Advice Remark Codes.That RARCs supply the supplemental detail beyond the CARC on a remittance, maintained by X12 as a public list, used here as the read that can name which other plan a payer believes is primary on a CO-22.. Reading it before making any calls saves a round of guessing which coverage to chase down first.

Coordination-of-benefits rules can also differ by plan type: a self-funded employer plan governed by federal ERISA law follows its own coordination and claims framework rather than a state-regulated plan's rules, and confirming which framework applies matters just as much for a COB dispute as it does for any other kind of appeal 4Ref 4U.S. Department of Labor (2026).ERISA.That self-funded employer plans are governed by ERISA rather than state insurance law, with their own claims and coordination framework, so a COB dispute can follow a different process depending on the plan type..

Common questions

It means the payer believes a different plan is primary for this claim and should be billed first — not that the service isn't covered. Coordination of benefits determines which plan pays before another, and a CO-22 signals a mismatch between what the payer's system shows and what actually applies to this claim today.

Coordination-of-benefits data on file with a payer can go stale even without a real change — a prior job's plan that was never formally dropped, an old spouse's coverage still listed, or a Medicare enrollment the payer hasn't caught up to. Confirming the current, correct order directly with the patient is usually faster than assuming the file is accurate.

The primary payer's explanation of benefits or remittance, showing what it allowed, paid, and left as patient responsibility. A secondary claim resubmitted without that attachment often denies again for the same reason, since the payer still has no record of what the primary plan actually did with the claim.

A cob hold is a claim paused pending confirmation of coverage, often used when a payer's file lists coverage the patient no longer has or never had. It usually clears once the patient confirms no other coverage exists directly with the payer, rather than through anything resubmitted on the claim itself.

No. A CO-22 questions which plan should pay first; a duplicate denial questions whether this exact claim was already submitted and processed. Treating a CO-22 like a duplicate — resending the same claim unchanged — doesn't fix it, since the payer's objection was never about having seen the claim before.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

1.X12 (2026). Claim Adjustment Reason Codes. X12. link ✓That CARCs, including CO-22, are the standard X12 code list explaining why a claim paid differently than billed — used here as the definition of what a CO-22 actually signals: a dispute over payment order, not coverage.
2.Centers for Medicare & Medicaid Services (2026). Coordination of Benefits and Recovery Overview. Centers for Medicare & Medicaid Services (CMS). link ✓That coordination of benefits determines primary vs secondary payer order and that CMS runs a national program to manage that order for Medicare — used here as the underlying mechanism a CO-22 denial is disputing, and why a secondary claim needs proof of what the primary plan paid.
3.X12 (2026). Remittance Advice Remark Codes. X12. link ✓That RARCs supply the supplemental detail beyond the CARC on a remittance, maintained by X12 as a public list, used here as the read that can name which other plan a payer believes is primary on a CO-22.
4.U.S. Department of Labor (2026). ERISA. U.S. Department of Labor. linkThat self-funded employer plans are governed by ERISA rather than state insurance law, with their own claims and coordination framework, so a COB dispute can follow a different process depending on the plan type.

https://www.gale.care/for-providers/dn-co22-cob · 4 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

← Back to for providers