CO-26 Denial Code: What "Expenses Incurred Prior to Coverage" Actually Means and How to Fix It

By Dr. Zain Vally  |  Updated September 2026  |  Medical Billing Denials

A CO-26 denial tells you one thing: the date of service on the claim falls outside the patient's active coverage window with that payer. The payer is saying the patient was not covered on the day you provided care, so the payer has zero liability.

That last part matters. The "CO" group code shifts financial responsibility to the provider, not the patient. If the payer had used PR-26 instead, the patient would owe the balance.

CO-26 means neither party should have billed that payer in the first place.

This page breaks down why CO-26 fires, how it differs from PR-26, and the exact steps to recover the revenue.

CO-26 vs. PR-26: Who Pays?

Both codes use CARC 26 ("expenses incurred prior to coverage"). The difference is the group code in front of it, and that group code determines who absorbs the cost.

When your team sees CO-26, the reflex should be to check which payer actually covered the patient on that service date. Billing the patient is not the answer here.

Five Scenarios That Trigger CO-26

1. Coverage Had Not Started Yet

The patient's plan has an effective date after the service date. This is common with new hires whose group coverage starts on the first of the following month. A March 22 visit billed to a plan effective April 1 returns CO-26.

2. Retroactive Termination

An employer terminates the employee's coverage retroactively, sometimes weeks or months before the service date. The eligibility check at the time of service may have returned "active," but the payer's records were updated after the fact. This is one of the most frustrating versions of CO-26 because the practice did verify.

According to a 2024 MGMA poll, 19% of practices reported at least one retroactive termination denial per month. Re-verifying within 72 hours of the service date is the only reliable defense.

3. Wrong Payer Billed

The patient switched insurers between visits, and the old payer ID is still on file. The previous payer correctly denies with CO-26 because the patient's coverage with them ended before the service date. The fix is straightforward: identify the current payer and rebill.

4. COBRA Gap

COBRA continuation coverage is retroactive once elected, but there is a 60-day election window. During that window, claims submitted to the prior group plan will deny as CO-26. If the patient elects COBRA and the premium is paid, the claim can be resubmitted with the COBRA payer ID and the effective date will cover the service retroactively.

5. Marketplace Effective-Date Confusion

ACA marketplace plans purchased between the 1st and 15th of the month take effect the first of the following month. Plans purchased after the 15th take effect the first of the month after that.

A patient who enrolled on January 18 does not have coverage until March 1. Any January or February service billed to that plan returns CO-26.

The Eligibility Verification Failure Behind Most CO-26 Denials

In my experience working denial queues for multi-location groups, CO-26 almost always traces back to one of three verification gaps:

No verification at all. The front desk collected the insurance card and entered it into the PM system without running a real-time eligibility check. A card from a terminated plan looks identical to an active one.

Verification ran too early. Eligibility was checked at scheduling (sometimes weeks before the visit) rather than within 48 to 72 hours of the service date. Retroactive terminations, job changes, and plan switches happen in that gap.

Retroactive change after a valid check. This is the scenario above: the 271 returned "active," but the payer updated the record after the fact. Documenting the verification date and response gives you grounds for an appeal when the payer's own system confirmed coverage at the time.

A multi-location practice running four or more sites should be checking eligibility automatically through the clearinghouse integration, not manually through the payer portal. Manual checks do not scale, and they do not create the audit trail you need when a payer's retroactive update contradicts your verification.

Five-Step Fix Sequence for CO-26

Worked Example: Maria Torres, DOS March 3

Preventing CO-26 Before It Hits Your Queue

Run real-time eligibility within 72 hours of every appointment. Not at scheduling, and not from the card. Use your clearinghouse's automated 270/271 integration, with the response feeding directly into your PM system so the front desk sees a flag if coverage is inactive.

Document every verification. Save the 271 response with a timestamp. If the payer retroactively terminates coverage after your check returned "active," that timestamped response is your appeal evidence.

Flag new patients and insurance changes. When a patient reports a new insurance card, run eligibility immediately and confirm the effective date before the visit happens. A card does not mean active coverage.

For groups running multiple locations, centralizing eligibility verification through a single clearinghouse integration eliminates the inconsistency of each site running its own process. Our clients using automated batch eligibility checks the evening before each day's schedule see CO-26 denial rates drop below 0.5% of total claims.

Related Denial Codes

• PR-26: Same CARC, but patient-responsible. The patient's coverage lapsed due to non-payment or voluntary termination. You can bill the patient for the balance.
• CO-22: "This care may be covered by another payer per coordination of benefits." Often appears alongside coverage-gap denials when COB order is wrong.
• CO-29: "The time limit for filing has expired." If you catch a CO-26 late and the correct payer's timely filing window has closed, the rebill will return CO-29.

Frequently Asked Questions