What Is the CO-22 Denial Code?

CO-22 is the standardized X12 code a payer uses to communicate: 'We are not paying this claim — at least not yet — because we believe another insurance plan should pay first under coordination-of-benefits rules.' The official X12 CARC 22 definition is 'This care may be covered by another payer per coordination of benefits.'

The two-character prefix is a Group Code, and on this denial it is almost always CO (Contractual Obligation), occasionally OA (Other Adjustment). CO means the adjusted dollar amount is the provider's responsibility under the payer contract and cannot be balance-billed to the patient. CO-22 is not telling you the patient owes money — it is telling you the claim is in the wrong queue.

Unlike bundling denials (CARC 97) or medical-necessity denials (CARC 50), CO-22 is not about how the service was coded or documented. It is an eligibility and payer-sequencing problem. The clinical claim may be perfectly clean; it simply went to the wrong payer first, or the payer's record of which plan is primary is out of date.

Three situations produce the overwhelming majority of CO-22 denials:

1. The patient has two or more active plans and the claim was submitted to the secondary (or tertiary) plan first instead of the primary.
2. Medicare Secondary Payer (MSP) applies — the patient has active group health coverage through an employer that, by federal rule, must pay before Medicare (e.g., an actively-working patient 65+ on a large-employer group plan, or coverage related to a workers' comp, no-fault, or liability claim).
3. The payer's coordination-of-benefits record is stale. The patient may genuinely have only one active plan now, but the payer's COB file still shows a terminated or never-existent secondary plan, so it kicks the claim back pending COB confirmation.

In our denial audits we typically see CO-22 spike whenever a patient population skews older (Medicare/commercial overlap), pediatric (both-parents dual coverage), or Medicaid-eligible (Medicaid as payer of last resort) — and almost always the root cause is an eligibility step that was skipped or a COB record nobody updated.

CO-22 has a small, well-defined set of root causes. Categorizing each denial by cause is what makes the worklist fast.

1. Coordination-of-benefits record not updated with the payer. The single most common cause. The insurer's COB file shows the patient has other coverage (often coverage that has since terminated), so it pends every claim with CO-22 until the patient calls the plan's COB department to confirm which plan is primary. The provider cannot fix this directly — the patient must contact the payer's COB line — but the practice triggers and tracks the call.

2. Dual coverage billed in the wrong order. The patient has two active plans and the claim went to the secondary first. Common with: a child covered under both parents (the birthday rule decides primacy — the parent whose birthday falls earlier in the calendar year is primary); a working spouse covered under their own employer plan plus a partner's plan; or a retiree with both a commercial retiree plan and Medicare.

3. Medicare Secondary Payer (MSP). Federal MSP rules require certain other payers to pay before Medicare: a Group Health Plan for actively-working beneficiaries 65+ at employers with 20+ employees; a Large Group Health Plan for disabled beneficiaries at employers with 100+ employees; no-fault/auto, liability, and workers' compensation for related care; and the first 30 months of Medicare entitlement for End-Stage Renal Disease when a group plan exists. Billing Medicare first in any of these cases produces CO-22.

4. Medicaid as payer of last resort. By federal law Medicaid pays last. If a Medicaid patient also has Medicare or commercial coverage and Medicaid was billed first, expect CO-22 (or a state-specific equivalent) directing you to the primary payer.

5. Stale or wrong insurance on file at registration. The patient changed jobs, aged into Medicare, added or dropped a spouse's plan, or the front desk entered the secondary as primary. The claim is technically clean but addressed to the wrong payer.

6. Accident/injury claims (third-party liability). Care arising from an auto accident, work injury, or liability event may be the responsibility of a no-fault carrier, workers' comp, or liability settlement before the health plan pays. The health plan denies CO-22 pending the liability determination.

The fix for CO-22 is procedural, not clinical. Work it in this order:

Step 1 — Re-verify eligibility for ALL of the patient's plans. Run an eligibility check (270/271) on every plan on file, not just the one that denied. The goal is to establish, with the payers' own data, which plan is primary today. Capture the effective and termination dates of each plan. This single step resolves most CO-22 denials because it tells you definitively whether you billed the wrong payer or whether the payer's COB record is simply stale.

Step 2 — Confirm the correct primary payer and the rule that decides it. Apply the right ordering rule: for dependents, the birthday rule; for active workers 65+, MSP; for Medicaid patients with any other coverage, Medicaid pays last; for accident-related care, the liability/no-fault/workers'-comp carrier first. Document which rule applies — your appeal or resubmission will reference it.

Step 3a — If you billed the wrong payer: submit the claim to the correct primary payer. Once the primary adjudicates, bill the secondary payer and attach the primary's EOB or ERA (835) showing what the primary paid, allowed, and left as patient responsibility. The secondary cannot process a coordinated claim without the primary's remittance.

Step 3b — If the COB record is stale (you billed the correct/only payer): the patient must call the payer's coordination-of-benefits department to confirm they have no other active coverage (or to state the correct order). Provide the patient a short script and the payer's COB phone number. After the patient updates the COB record, resubmit the original claim. There is no modifier or coding change — the claim was correct; the payer's file was wrong.

Step 4 — For Medicare MSP: if Medicare denied CO-22 because a group health plan is primary, bill the group plan first, then submit the Medicare claim with the primary's EOB. If Medicare's MSP record is wrong (e.g., the employer coverage already terminated), the patient or provider contacts the Benefits Coordination & Recovery Center (BCRC) to correct Medicare's MSP file before resubmitting.

Step 5 — Track the COB-confirmation loop. CO-22 caused by a stale COB record can recur on every subsequent claim until the patient actually completes the payer call. Flag the patient account so the front desk re-confirms COB status at the next visit. See the copy-paste COB-update request template later in this guide.

Several adjacent codes get mixed up with CO-22 because they all touch coordination of benefits. They mean different things and have different fixes. Use this table to triage:

The key distinction: CO-22 says 'someone else is primary — find them and bill them first.' CO-23/OA-23 is the secondary payer's bookkeeping line that records the primary's adjudication impact — it usually means coordination is working, not failing. Treat a CO-23/OA-23 zero-dollar line as informational unless it leaves a balance unaccounted for. Treat CO-22 as an action item: re-sequence the payers.

CO-22 frequently arrives with one or more Remittance Advice Remark Codes (RARCs) that pinpoint exactly which coordination problem the payer hit. Decode the RARC before you call — it tells you who needs to do what.

Read the RARC first. If you see MA04, N4, or N479, the message is unambiguous: the secondary payer wants the primary's EOB attached — there is nothing to appeal, just resubmit with the attachment. If you see N245, MA92, or MA130, the other-coverage data on the claim itself is wrong or incomplete and must be corrected. If you see N130, the payer is pointing you to its own COB benefit rules to confirm sequencing. For the broader denial-code reference, see our CARC denial codes list and our explainer on the related bundling code, the 97 denial code.

Coordination of benefits is governed by different rule sets depending on the payer, and the resolution path differs.

Medicare (Medicare Secondary Payer). MSP is federal law, not a contract term, and it is enforced strictly. Medicare is secondary when: the patient is an active worker 65+ covered by a Group Health Plan at an employer with 20+ employees; a disabled beneficiary covered by a Large Group Health Plan at an employer with 100+ employees; the care relates to a no-fault/auto, liability, or workers'-compensation claim; or, for the first 30 months of ESRD-based entitlement, a group health plan exists. To bill Medicare correctly as secondary, you must report the primary payer's payment information on the claim. If Medicare's MSP record is wrong (the primary coverage already ended), the patient or provider contacts the Benefits Coordination & Recovery Center (BCRC) to update Medicare's file before resubmitting. Medicare publishes the full MSP framework on cms.gov.

Medicaid (payer of last resort). Federal law requires Medicaid to pay after all other available coverage. If a Medicaid member also has Medicare or commercial insurance, that coverage is primary and Medicaid is billed last, with the primary EOB attached. Many state Medicaid programs (and their managed-care plans) have their own COB-denial codes and 'cost-avoidance' rules that look like CO-22; the fix is the same — bill the primary first. Verify the patient's other coverage through the state's eligibility portal, because Medicaid's third-party-liability file is frequently more current than the practice's record. See our Medicaid glossary entry for how Medicaid coordinates with other payers.

Commercial plans. Two commercial plans coordinate using NAIC model COB rules: the birthday rule for dependent children, the employee/subscriber-vs-dependent rule (your own plan is primary over a plan where you are a dependent), and active-vs-retiree/COBRA tiebreakers. Commercial payers will pend CO-22 until their COB department confirms which plan is primary — and they require the member, not the provider, to make that confirmation call. Build the patient COB call into your workflow, because the practice cannot resolve a commercial COB hold on the patient's behalf.

Across all three, the controllable lever is the same: two-payer eligibility verification at the front desk and a COB record that is actually current. That is the prevention layer.

Most CO-22 denials caused by a stale COB record require the patient to call their plan, because payers will not update coordination of benefits on a provider's word alone. Hand the patient this script, then resubmit with the cover note below.

Patient script — give this to the patient (or call with consent):

> 'Hello, I'm calling about my coordination of benefits. My member ID is [ID] and my date of birth is [DOB]. My medical provider's claim was denied because your records show I may have other insurance. I want to confirm my current coverage: [I have only this plan / my primary plan is ___ and this is my secondary plan]. Please update your coordination-of-benefits record so my provider's claim dated [date of service] can be processed, and please give me a reference number for this call.'

Record the COB reference number the payer provides — it goes on the resubmission.

Resubmission cover note (for a secondary claim — when you are sending the primary EOB):

> 'Re: Claim [claim #], patient [name], DOB [DOB], member ID [ID], DOS [date]. This claim was denied CO-22 (coordination of benefits). [Primary payer name] is the patient's primary payer per [birthday rule / MSP / patient confirmation]. The primary payer's EOB/ERA is attached, showing allowed amount $[X], paid $[X], and remaining balance $[X]. Please process this claim as secondary and coordinate benefits accordingly. Patient COB confirmation reference: [number].'

Resubmission note (for a stale-COB record — when the denied payer IS primary/only):

> 'Re: Claim [claim #], patient [name], DOB [DOB], member ID [ID], DOS [date]. This claim was denied CO-22 (coordination of benefits) in error. The patient has confirmed with your coordination-of-benefits department on [date] (reference [number]) that [this is the only active plan / this plan is primary]. Please reprocess the original claim. No coding change is required.'

Keep the appeal/resubmission factual and short. CO-22 is resolved by correct payer order and the right attachment, not by argument. If your team lacks the bandwidth to run the eligibility re-checks, the patient COB calls, and the secondary resubmissions on every CO-22, outsourced denial management services and insurance eligibility verification services can own the loop end to end.

CO-22 is one of the most preventable denial categories because it is created upstream, at registration, not in coding. A practice running clean on CO-22 does five things consistently:

1. Verify eligibility on every plan, not just the first one. When a patient presents two insurance cards, run a 270/271 eligibility check on both and capture effective/termination dates. Single-payer verification is the most common upstream cause of CO-22 — the front desk verified one plan and never checked whether a second plan was primary.

2. Ask the coordination-of-benefits question at intake. Train registration to ask directly: 'Do you have any other health insurance, including through a spouse, a parent, Medicare, Medicaid, or an auto/work injury claim?' Capture the answer in the patient record and re-ask at every visit for high-risk populations (65+, pediatric, Medicaid-eligible).

3. Apply the ordering rules at registration. Encode the birthday rule for dependents, MSP for active workers 65+, and Medicaid-pays-last in your front-desk workflow so the correct primary is set before the claim is created — not discovered after a denial.

4. Flag patients with a known stale-COB history. If a patient triggered a CO-22 because of a stale payer record, flag the account so the next visit re-confirms the patient completed the payer COB call. Otherwise CO-22 recurs on every claim.

5. Track CO-22 as its own denial category with a root-cause tag. Tag each CO-22 by cause (wrong order / stale COB / MSP / Medicaid-last / liability) so the team can see whether the volume is a front-desk eligibility gap (fixable with training) or a payer COB-file problem (fixable only by the patient call). CO-22 belongs on your eligibility-related denial dashboard alongside other front-end denials, because it is a leading indicator of clean-claim-rate erosion. For how front-end accuracy ties to overall AR, see how to reduce claim denials.

Practices that operationalize two-payer eligibility verification and a maintained COB record typically eliminate the large majority of CO-22 denials, because the root cause — wrong payer order — never reaches the clearinghouse. The denials that remain are stale-payer-file issues that resolve with a single patient COB call.