CO 22 denial code: you billed the wrong payer first

By Kathryn Thompson, RCM Expert, Supa

TL;DR: CO 22 means the payer believes another plan should pay first under coordination of benefits. It is a routing instruction rather than a refusal. The claim usually pays once it goes to the right payer in the right order, and the recurring version of this problem is almost always stale insurance data.

Key takeaways

• X12 defines code 22 as care that may be covered by another payer per coordination of benefits.
• The claim was not judged unnecessary or non covered. It was sent to the wrong payer first.
• Repeat CO 22 on the same patient means your insurance record is out of date.
• Patients frequently do not know which of their plans is primary.
• Asking the right question at registration prevents most of this.

A claim comes back CO 22 and the natural reaction is to treat it as a denial. It is closer to a returned envelope with a forwarding address.

The service is fine. The order was wrong.

What does the CO 22 denial code mean?

X12 defines code 22 as "This care may be covered by another payer per coordination of benefits," with a start date of January 1, 1995 and a last modification in 2007 (X12).

The hedge in that wording is deliberate. It says may be covered, because the payer is not always certain. It has information suggesting another plan exists and it is declining to pay until the order is established.

What is coordination of benefits? The rules determining which plan pays first when a patient has more than one. The primary plan pays to its limit, then the secondary considers the balance.

The most common triggers are a patient with two commercial plans, a patient with both Medicare and a commercial plan, a child covered by both parents, or a case where an injury suggests liability or workers compensation coverage.

Notice this is not a clinical determination and not a pricing one. It is administrative, and it is fixable with information rather than argument.

How do you resolve a CO 22?

Establish the correct order, then rebill in that order. The order is determined by rules rather than by preference, and neither you nor the patient gets to choose.

The working sequence:

1. Contact the patient and ask specifically. Not "do you have insurance," which produces the plan they carry the card for. Ask whether they are covered under any other plan, including through a spouse, a parent, a former employer, or Medicare.
2. Determine primacy by rule. For dependent children, the birthday rule commonly applies. For Medicare alongside employer coverage, it depends on employer size and the basis of Medicare entitlement. These rules are specific and worth having written down.
3. Bill the primary and wait for adjudication. The secondary needs the primary's determination before it can process.
4. Bill the secondary with the primary remittance attached. Missing this detail generates a fresh denial, frequently CO 16 for missing information.
5. Update the record. This is the step that prevents the next one.

Step five is the one practices skip, and skipping it is why CO 22 recurs on the same patients. Our guide to reading an EOB and ERA covers pulling the primary's adjudication detail you will need for the secondary claim.

Why does the same patient keep generating this?

Because insurance changes and nobody asked. Coverage shifts with jobs, marriages, divorces, birthdays, and enrollment periods, and a record captured at intake eighteen months ago describes a situation that may no longer exist.

There is also a genuine knowledge problem on the patient side. Most people do not know what coordination of benefits is, and a patient covered by their own plan and a spouse's often has no idea which is primary. When you ask "what insurance do you have," they give you the card in their wallet, which may be either one.

That makes the question you ask more important than the frequency with which you ask it. "Are you covered under any other health plan, including through a spouse or parent" produces different answers from "what is your insurance."

Three points where re-verification pays for itself: at the start of each plan year, after any gap in treatment, and whenever a claim comes back with anything suggesting other coverage.

For practices working with clients across multiple coverage situations, our guide to in network versus out of network in behavioral health covers the related question of how coverage status shapes what you collect.

[Image: A simple flow showing a claim bouncing back from the secondary payer, then routing to the primary, adjudicating, and returning to the secondary with the remittance attached, editorial process diagram, accent teal - alt='Resolving CO 22 means establishing the payer order and billing in sequence']

Should CO 22 count as a denial?

Not in a way that drives your denial reduction work, because the fix is a data fix rather than a claims fix.

Grouping CO 22 with clinical denials distorts the picture. A practice with a high CO 22 rate does not have a coding problem or a documentation problem. It has a registration problem, and those are solved by different people using different tools.

Track it separately as a coordination of benefits rate and you get a metric that points at its own remedy. Watch it by intake source or by front desk staff member and it becomes actionable in a way an aggregate denial rate never is.

Worth remembering that KFF classified the great majority of marketplace denials, 77%, as "all other reasons" beyond the named categories (KFF). Administrative denials like this one sit inside that large undifferentiated bucket, which is part of why the industry conversation focuses on medical necessity while most actual denial volume is procedural.

Where automation actually helps with CO 22

At verification, and specifically at discovering coverage the patient did not mention. That is the part humans 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, and the system can find what they did not recall.

Primacy applied by rule. 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 will surface 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 recurring weekly item into an occasional one.

Want other coverage found before you bill rather than after? Book a demo.

FAQ

Q: Is CO 22 a denial?

A: 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.

Q: Can I bill the patient for a CO 22 amount?

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

Q: How do I know which payer is primary?

A: 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.

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

A: 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.

Q: What do I send to the secondary payer?

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

Q: How often should I re-verify coverage?

A: 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.