Top

CO-22: May be covered by another payer per coordination of benefits

The payer believes another plan is primary and should pay first, so it will not process the claim until coordination of benefits is resolved.

What it means

A CO-22 is closer to a returned envelope with a forwarding address than to a denial. The payer has information suggesting another plan should pay first, and it is declining to adjudicate until the order is established. X12 defines code 22 as "This care may be covered by another payer per coordination of benefits" (X12). The hedge in "may be" is deliberate: nothing clinical has been judged and nothing has been priced.

Mechanically this fires when the payer's records show additional coverage or when its COB information is out of date. The fix is almost always about primary versus secondary order and getting the other payer's explanation of benefits on file, not about the clinical service itself. It is administrative, and it is fixed with information rather than argument.

How coordination of benefits works

Coordination of benefits is the set of rules that decide which plan pays first when a patient has more than one. The primary pays to its limit, then the secondary considers the balance. The order is set by rule, not by preference. For dependent children the birthday rule commonly applies; for Medicare alongside employer coverage it depends on employer size and the basis of entitlement.

What usually triggers it

Common triggers are two commercial plans, Medicare plus a commercial plan, a child covered by both parents, or an injury that suggests liability or workers' compensation coverage. In each case the payer holds the claim until the correct payer order is established.

Sources: X12 Claim Adjustment Reason Codes

Why it happens in behavioral health

Behavioral health patients frequently carry more than one plan, so CO-22 is common. Clients may have Medicaid alongside commercial coverage, a behavioral carve-out plus a medical plan, or coverage through a parent and a spouse. Any of these can flip which payer is primary for SUD and mental health services.

Residential and IOP episodes that span weeks are especially exposed because coverage can change mid-episode. Verify COB at intake and re-verify for long stays, then submit to the true primary first and bill the secondary with the primary EOB attached.

Why the same patient keeps generating it

The same patient keeps generating CO-22 because coverage changes and nobody asked. Jobs, marriages, divorces, birthdays and enrollment periods all move it. A record captured at intake eighteen months ago describes a situation that may no longer exist. Most patients do not know what coordination of benefits is. Someone covered under their own plan and a spouse's often has no idea which is primary. Asked "what insurance do you have," they hand over the card in their wallet, which may be either one.

Track it as its own rate

Track CO-22 separately as a coordination-of-benefits rate rather than inside the denial rate. A high CO-22 rate is a registration problem, not a coding or documentation problem, and it is solved by different people with different tools. Watched by intake source or by front-desk staff member it becomes actionable in a way an aggregate denial rate never is. The public data will not do this for you. In 2021, KFF classified 77% of in-network denials by HealthCare.gov marketplace plans as "all other reasons" beyond the named categories. That is a general healthcare baseline, and it does not say how often coordination of benefits was the reason. If you want that number you have to count it yourself.

Sources: KFF, Claims Denials and Appeals in ACA Marketplace Plans in 2021

How to fix it

  • Confirm which plan is actually primary using current eligibility and COB records.
  • If another payer is primary, bill that payer first and obtain its explanation of benefits.
  • Submit to this payer as secondary with the primary EOB attached.
  • If this payer's COB data is wrong, have the patient update coordination of benefits with the plan.
  • Ask the patient the specific question: whether they are covered under any other plan, including through a spouse, a parent, a former employer or Medicare. "Do you have insurance" produces the plan they carry the card for.
  • Send the secondary the primary's full adjudication detail (allowed, paid and adjusted amounts), not just the claim. Omitting it produces a fresh denial, usually CO-16 for missing information.
  • Update the patient record after resolving the order. This is the step most practices skip, and skipping it is why CO-22 recurs on the same patients.

How to prevent it

  • Capture all active coverage and COB order at intake and verify it before billing.
  • Re-verify coverage for long residential and IOP episodes that span coverage changes.
  • Flag dual-coverage patients so claims route to the correct primary automatically.
  • Ask "are you covered under any other health plan, including through a spouse or parent" at registration, not "what is your insurance."
  • Re-verify at the start of each plan year, after any gap in treatment, and whenever a claim comes back with anything suggesting other coverage.
  • Run eligibility against multiple payers at verification, not only the plan the patient named, so the second plan surfaces before the claim goes out.

How AI can help with CO-22

Automation helps CO-22 at verification, and specifically at discovering coverage the patient did not mention. That is the part a human cannot do by asking.

  • Coverage discovery across payers. Checking eligibility against multiple payers rather than only the plan the patient named surfaces the second plan before the claim goes out. A patient who forgot they are still on a spouse's plan is not being evasive. The system can find what they did not recall.
  • Primacy applied by rule. The birthday rule, Medicare secondary payer conditions and employer size are deterministic once the facts are known. Encoding them removes a category of judgment error that recurs constantly.
  • Sequencing the claims. Primary first, wait for adjudication, then secondary with the remittance attached. That is a workflow with a dependency, and dependencies are what workflow automation handles well.

Supabill automates benefits verification across payers, which is where this problem is actually solved. A CO-22 arriving on a remittance means the verification step did not happen or did not look far enough.

The honest limit: no verification system catches every plan. Coverage that was never registered anywhere your system can reach surfaces only when a payer tells you, and some patients genuinely cannot answer questions about their own coverage. You will still get some CO-22. The aim is turning it from a weekly item into an occasional one.

FAQ

Is CO-22 a denial?

Functionally it is a routing instruction. The payer is not refusing the service; it is declining to pay until the coordination of benefits order is established. Once billed in the right sequence, the claim usually pays normally.

Can I bill the patient for a CO-22 amount?

No. The CO group code makes it a contractual obligation, and the balance is not the patient's until the correct payer has adjudicated. Bill the primary first, then the secondary.

How do I know which payer is primary?

By rule rather than by preference. The birthday rule commonly governs dependent children, and Medicare primacy alongside employer coverage depends on employer size and the basis of entitlement. Verify rather than assume.

The patient says they only have one plan. Why did I get CO-22?

Because the payer has information suggesting otherwise, often from a coordination of benefits questionnaire the patient completed and forgot. Patients also frequently do not consider coverage through a spouse or a former employer to be theirs.

What do I send to the secondary payer?

The claim plus the primary payer's adjudication details: what was allowed, paid and adjusted. Omitting that detail is a common cause of a follow-up CO-16 for missing information.

How often should I re-verify coverage?

At minimum at the start of each plan year and after any gap in treatment. Coverage changes with employment, marital status and enrollment periods, and a record from eighteen months ago is not reliable.

What is the difference between CO-22 and CO-109?

CO-22 says another payer may be primary under coordination of benefits, so the claim needs to go to that payer first. CO-109 says this payer does not cover the service at all and it belongs with a different payer or contractor. One is about order, the other about ownership.

Should CO-22 count toward my denial rate?

Track it separately as a coordination-of-benefits rate. A high CO-22 rate is a registration problem, solved by different people than a coding or documentation denial, and mixing the two hides both.

What question should the front desk ask to prevent CO-22?

"Are you covered under any other health plan, including through a spouse, a parent, a former employer or Medicare?" Asking "what is your insurance" produces the card in the patient's wallet, which may be the secondary plan.

AI agents that run your billing.

Denials like CO-22 are rarely a one-off. They trace back upstream to eligibility, coding, documentation, or a payer rule that changed. Supabill's agents work the whole revenue cycle to stop them at the source. See our guide on why behavioral health denials keep rising, or book a demo.

Book a live demo