Skip to main content
rcm.today

Operated by AdvancedCare USA Inc., which sells revenue cycle software and services. Our formulas and sources are published so you can check them.

Denial code CO-22 — this care may be covered by another payer (COB)

CO-22 is a coordination-of-benefits signal: the payer believes another plan should pay first. Fix the primary/secondary order before resubmitting the same claim to the same payer.

Last reviewed against published HFMA, CMS, MGMA, Premier, and related primary sources linked on this page on .

What CO-22 means

CO-22 (group code CO = contractual obligation) means the payer is adjusting the claim because another payer may be responsible under coordination of benefits. The most common real cause is outdated or incomplete other-insurance information at registration. First action: verify active coverages and primary-payer order for the date of service, then bill the correct primary — do not simply rebill the same payer with no COB change.

What the code actually says

X12’s short description for reason code 22 is: “This care may be covered by another payer per coordination of benefits.” (X12 CARC (opens in a new tab), as of this page’s last review).

COB is the set of rules that decide which plan pays first when a patient has more than one. For Medicare beneficiaries with other coverage, CMS’s Medicare Secondary Payer rules describe common situations (working aged, GHP, liability, no-fault, workers’ compensation, and others) in the MSP manual chapter on MSP situations (opens in a new tab) (as of that manual publication). Commercial plans apply their own COB provisions and often require an other-payer paid amount on secondary claims.

CO-22 is not a final statement that this payer will never pay — it is a stop until primary liability is resolved. Remark codes may name the other payer type or the missing COB data (X12 RARC (opens in a new tab)).

Most common causes and where they originate

  • Patient has active commercial primary; Medicare billed first incorrectly

    Where it originates
    Registration / MSP questionnaire
    How to confirm on the remit
    CO-22 with MSP or other-insurance RARC
    Prevention owner
    Registration + MSP process

  • Dual commercial plans; birthday rule or subscriber order wrong

    Where it originates
    Registration
    How to confirm on the remit
    CO-22; portal shows other carrier
    Prevention owner
    Front desk

  • Workers’ comp / auto / liability should be primary

    Where it originates
    Intake + case type
    How to confirm on the remit
    Remark on accident, WC, or liability
    Prevention owner
    Intake + billing specialty desk

  • Other coverage terminated but payer file still shows it

    Where it originates
    Eligibility
    How to confirm on the remit
    Patient insists single coverage; payer COB file stale
    Prevention owner
    Billing + patient COB update

  • Secondary billed without primary EOB / payment info

    Where it originates
    Secondary billing
    How to confirm on the remit
    CO-22 or COB information RARC on secondary
    Prevention owner
    Billing ops

  • Divorce / dependent coverage order incorrect

    Where it originates
    Registration
    How to confirm on the remit
    Dependent on two plans; order disputed
    Prevention owner
    Registration

Operational framing for ambulatory billing. Always confirm COB against payer responses for the date of service — not against last year’s registration screenshot.

Working the denial, in order

  1. Step 1

    Read RARCs and payer COB messages

    Capture which other payer the remittance implies. Portal messages and eligibility COB segments often name the primary carrier.

  2. Step 2

    Re-run eligibility and MSP / other-insurance questions for the DOS

    For Medicare, walk the MSP questionnaire scenarios in light of [CMS MSP guidance](https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/msp105c03.pdf). For commercial, pull both carriers’ eligibility COB.

  3. Step 3

    Establish primary and bill primary to conclusion

    Do not appeal CO-22 as if it were a medical-necessity denial. Obtain the primary determination (pay, deny, or patient liability) first.

  4. Step 4

    Bill secondary with primary adjudication data

    Include payer paid amount, adjustments, and patient liability as the secondary requires. Missing primary data often produces another COB rejection.

  5. Step 5

    If both payers refuse primary, escalate with evidence

    Use written COB determinations. Formal Medicare appeals, when applicable, follow [MLN006562](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf). Track timely-filing on each plan separately.

  6. Step 6

    Update the permanent coverage record

    A worked CO-22 that leaves registration data wrong will recur on the next visit. Measure labour via [cost to collect](/cost-to-collect).

Before you resubmit

  • All active coverages for the DOS are listed with subscriber IDsIncluding Medicare, Medicaid, commercial, and accident riders when relevant.
  • Primary payer decision is documented (EOB or denial)Secondary claims need primary adjudication data.
  • MSP questionnaire answers match the billing order for Medicare patientsWorking aged, disability GHP, ESRD, liability, no-fault, WC checked as applicable.
  • Accident-related claims have the correct casualty carrier billed first when requiredDo not force medical primary when liability/no-fault is primary under the plan rules.
  • Timely-filing deadlines for each payer are calendarisedPrimary delays can burn secondary clocks — escalate early.
  • Patient is not balance-billed while COB is unresolved unless policy allowsConfirm financial policy and state rules.
  • Registration system updated so the next claim inherits the fixWorkqueue closed only after master data change.

Preventing it upstream

CO-22 prevention is almost entirely registration and eligibility.

  1. Require full other-insurance capture at scheduling and check-in, not only the card the patient hands over first.
  2. For Medicare, complete MSP screening whenever coverage or employment status changes (CMS MSP (opens in a new tab)).
  3. Automate eligibility COB segment review before first claim.
  4. Create a COB workqueue SLA measured in days, not in appeal letters — delay is what kills secondary timely filing.

Management frame: denials hub. Labour model: cost to collect.

How this code differs from ones it gets confused with

CO-22 vs [CO-109](/denials/co-109). CO-22 says another payer may be primary under COB rules while this payer might still have secondary liability. CO-109 says this payer/contractor is not the correct entity for the claim at all — re-route, do not just reorder COB fields on the same plan.

CO-22 vs [OA-23](/denials/oa-23). OA-23 reports the impact of a prior payer’s adjudication on this remittance (common on secondary claims). It is an adjustment explanation, not the same as “we refuse primary because of COB.”

CO-22 vs [CO-16](/denials/co-16). You may see information-style remarks when COB loops are incomplete. If the root issue is other-payer order, treat it as COB work, not as a generic missing-modifier fix.

These two pages should be cross-trained: CO-109 and CO-22 are the usual wrong-payer / COB pair.

Common questions

What does the CO-22 denial code description actually mean?
X12 describes reason 22 as care that may be covered by another payer per coordination of benefits. The payer is pointing at COB order or other-insurance responsibility, not at medical necessity or a bundled procedure.
Does CO-22 mean this insurance will never pay?
Not necessarily. Many CO-22s resolve by billing the true primary first and then this plan as secondary. Some resolve when outdated other-coverage is removed from the payer’s COB file.
How do Medicare Secondary Payer rules relate to CO-22?
When Medicare is billed but another payer is primary under MSP, remittances often surface COB-related adjustments. CMS MSP manual materials describe the situations in which Medicare is secondary. Always match the questionnaire and evidence to the date of service.
Should I appeal CO-22 immediately?
Usually no. Investigate coverage order and bill the correct primary first. Appeal when you have written proof this payer is primary and it still refuses after correct billing.

Sources

  1. X12 Claim Adjustment Reason Codes (CARC) (opens in a new tab) — X12
  2. X12 Remittance Advice Remark Codes (RARC) (opens in a new tab) — X12
  3. CMS Medicare Secondary Payer Manual, Chapter 3 (MSP situations) (opens in a new tab) — Centers for Medicare & Medicaid Services
  4. CMS MLN006562 — Medicare Parts A & B Appeals Process (opens in a new tab) — Centers for Medicare & Medicaid Services
  5. CMS Medicare Claims Processing Manual (Pub. 100-04) (opens in a new tab) — Centers for Medicare & Medicaid Services
  6. Premier: claims adjudication costs providers $25.7 billion (opens in a new tab) — Premier Inc.

Last reviewed against published HFMA, CMS, MGMA, Premier, and related primary sources linked on this page on .

Every benchmark and formula on this page is sourced and dated above. Where a figure is a range, the range is the honest answer, not a hedge. If you think something here is wrong or out of date, tell us — corrections are logged and dated.

Denial Code CO-22: Coordination of Benefits | rcm.today