Coordination of benefits denials: fixing CO-22 before you submit
CO-22 is a sequencing error, not a claim error. Where coordination-of-benefits denials come from at specialty clinics, how Medicare Secondary Payer rules decide the order, and how to catch an ambiguous record before the claim is built.
CO-22 is the denial that feels like the payer moved the goalposts. The claim is clean, the service was covered, and the remittance still says this care may be covered by another payer per coordination of benefits. CO-22 is sticky because it is not a claim error. It is a sequencing error. The payer is telling you that, in its records, someone else pays first, and nothing downstream adjudicates until the claim reflects that order. Most guidance stops at verify eligibility and list the primary first, which is correct and almost useless, because by the time you get the CO-22 the order was wrong at registration, not at submission.
This goes a level deeper: where coordination-of-benefits denials come from at specialty clinics, how Medicare Secondary Payer rules decide the order, what a secondary claim has to carry to adjudicate, and how to catch an ambiguous record before the claim is built.
Why specialty clinics see more COB denials
Coordination of benefits is a volume problem, and specialty clinics sit on the wrong side of it. Dual coverage is the norm here, not the exception. Infusion, behavioral health, fertility, and gender-affirming care draw patients who carry a commercial plan plus a secondary: a spouse's plan, a Medigap supplement, or Medicaid as the payer of last resort. High dollar amounts mean payers actually run their coordination-of-benefits checks, where a small office visit would pass unexamined. And patients update coverage between visits, so the record you verified in January is wrong by March. Coordination of benefits is not a one-time intake field. It decays.
The denial codes that actually mean COB
CO-22 gets the headlines, but coordination-of-benefits denials wear several jerseys, and treating them as one bucket hides the cause.
| Code | Meaning | Where it gets fixed |
|---|---|---|
| CO-22 / OA-22 | Care may be covered by another payer per coordination of benefits | Correct the payer order |
| OA-23 | Impact of the prior payer's adjudication, payments and adjustments | Rebuild the secondary claim from accurate primary data |
| MA04 | Secondary payment cannot be considered without the primary payer's identity or payment info | Attach the primary remittance data to the secondary claim |
| CO-109 | Claim not covered by this payer; send it to the correct payer | Reroute, for example to a behavioral-health carve-out |
CO-22 means wrong order. OA-23 and MA04 mean right order, broken secondary claim. They get fixed in different places, and lumping them together is why denial-management dashboards plateau.
Medicare Secondary Payer: the rules that bite
If your panel skews older or includes working-aged Medicare patients, Medicare Secondary Payer rules are where coordination of benefits gets genuinely hard, because the order is not a patient preference. It is federal rule.
| Scenario | Who pays first | Note |
|---|---|---|
| Working aged, 65+, employer with 20+ employees | Group health plan primary, Medicare secondary | Fewer than 20 employees flips Medicare to primary |
| Disability with a large employer (100+) | Group health plan primary | Tracks the employer-size threshold |
| ESRD | Group plan primary for a 30-month coordination period | Then Medicare becomes primary |
| Workers' comp, no-fault, liability | Pays before Medicare | For care related to the injury or claim |
None of this is discoverable from a 271 alone. The 271 tells you a plan is active. It does not tell you that a 68-year-old's active commercial plan is primary to their active Medicare. That gap, active coverage confirmed but primacy unknown, is the most common root cause of a CO-22, and it is invisible to a standard real-time eligibility check.
What a secondary claim has to carry
This is the part the checklists skip, and where the OA-23 and MA04 denials live. A secondary 837P does not just say the primary paid something. It reconstructs the primary's adjudication so the secondary payer can do its own math.
- SBR loops: SBR09 carries the claim filing indicator, and the 2320 loop describes the primary payer. Get the payer responsibility sequence wrong and the claim is internally inconsistent before it leaves your building.
- AMT segments in 2320: the primary's paid and allowed amounts, structured.
- CAS segments: claim-level and line-level adjustments, with the group codes, reason codes, and amounts the primary applied.
- Balancing: the submitted charge must equal primary paid plus primary adjustments plus the remaining balance. If the CAS and AMT do not balance to the line charge, the secondary payer cannot reconcile, and you get OA-23 or a flat reject.
A secondary claim is a faithful transcription of the primary's remittance. If your system cannot turn the primary remittance into a balanced secondary claim, secondary AR is where money quietly dies, not denied so much as never correctly born. It is the same data the ERA reconciliation process depends on.
The fix is upstream
Every durable fix for CO-22 happens before submission. The teams that beat it stop treating coordination of benefits as a denial to work and start treating it as a data-quality check to pass when the claim is assembled. That means answering three questions per claim, before it is built.
- 01Is the payer order knowable?Do we have an explicit, ordered list of payers for this patient on this date of service, or are we guessing?
- 02Is it internally consistent?Does the primary on the claim match the payer's coordination record, the Medicare Secondary Payer rules for this patient, and the order we used last time we got paid?
- 03Can we build a balanced secondary?Do we have the primary remittance with payment and adjustment data for the 2320 loop, or are we about to submit a claim that will OA-23?
Where the order is ambiguous, two active plans with no clear primacy, a Medicare Secondary Payer scenario with no questionnaire, or a primary remittance that has not posted yet, the claim should be held and flagged for a human, not dropped to the payer to find out.
How Foresight handles this
Foresight maintains an explicit payer-ordering sequence for coordination of benefits rather than inferring primacy at submission time, persists that coordination data so the order is durable across a patient's claims, and runs a pre-submission check that flags when primary, secondary, or tertiary coordination is ambiguous and holds the claim for review before it is constructed. The point is to move the decision to the front of the pipeline: surface the ambiguous cases while they are still cheap to fix, instead of discovering the wrong order two weeks later on a CO-22 remittance.
A practical checklist
- Capture all active coverage at intake, not just the first card, and record an explicit primary and secondary order.
- Run the Medicare Secondary Payer questionnaire for every Medicare patient, every time eligibility changes.
- Re-verify coordination of benefits for recurring patients on a cadence. Open enrollment and Medicaid redeterminations are predictable decay events.
- Do not submit a secondary claim until the primary remittance has posted and you can build a balanced 2320 loop from it.
- Separate the buckets: work CO-22 (wrong order) and OA-23 or MA04 (broken secondary) as different problems with different owners.
- Track coordination-of-benefits denials as a leading indicator of intake data quality, not a back-office cleanup task.
01What does CO-22 mean?
CO-22 means the payer believes another insurer is primary and should pay first per coordination of benefits. It is a sequencing denial, not a medical-necessity or coding denial. The service is covered, but the claim went to the wrong payer first or in the wrong order.
02What is the difference between CO-22 and OA-23?
CO-22 says the order is wrong: you billed a payer that is not primary. OA-23 appears on secondary claims and means the prior payer's payment and adjustment data was not carried correctly, so the secondary payer cannot reconcile. CO-22 is fixed by correcting payer order; OA-23 by rebuilding the secondary claim with accurate data.
03Why does Medicare deny with MA04?
MA04 means a secondary claim reached Medicare without the primary payer's identity or payment data. Medicare cannot calculate its secondary liability without knowing what the primary paid and adjusted, so it rejects until that information is on the claim.
04How do you prevent COB denials instead of working them?
Prevention happens at intake and at claim build. Capture and order all active coverage, run the Medicare Secondary Payer questionnaire on Medicare patients, re-verify recurring patients on a cadence, and check that the payer order is knowable and consistent before the claim is constructed. Hold ambiguous cases for review rather than submitting and hoping.
05Why are COB denials worse at specialty clinics?
Specialty patients carry dual coverage more often, claims are high-dollar enough that payers actively run coordination checks, and chronic patients return often enough that their coverage changes between visits. All three raise the rate at which the payer order is wrong or stale at submission.