Skip to content
EligibilityCARC

CO-26 denial code

Expenses incurred prior to coverage

The service predates the coverage effective date.

How to fix it

Verify the actual effective date. If the patient had different coverage on the date of service, bill that payer.

How to prevent it

Verify coverage for the specific date of service rather than for today. Effective dates move retroactively more often than expected.

In practice

A patient presents in the first week of January with a new insurance card. Eligibility is checked, the payer confirms coverage, and the claim is submitted. It returns CO-26: expenses incurred prior to coverage.

The card was genuine and the coverage is real. The effective date is the fifteenth, not the first, and the eligibility response confirmed that the policy exists rather than that it was active on the date of service.

The recovery is to identify who covered the patient on the actual date of service — often the prior plan, still active through a transition — and bill there. If nobody did, the balance is patient responsibility, and the conversation is easier held in January than in March.

What sits behind it

CO-26 concentrates around two moments in the year: January, when plan changes take effect, and any month following a job change. Both are periods when a patient reasonably believes they are covered and is technically correct, just not yet.

The verification failure is specific and worth naming. Checking whether a patient has coverage is a different question from checking whether coverage was active on a given date, and many eligibility workflows answer the first while appearing to answer the second. For a service delivered today the difference is invisible; for one delivered near an effective date it is the whole claim.

CO-26 and CO-27 are mirror images — one is service before coverage began, the other after it ended — and they share a root cause. Both come from verifying the patient rather than verifying the date, and both are prevented by the same change in what the front desk actually checks.

Related codes

Terms used here — Eligibility Verification · Coordination of Benefits · Patient Responsibility

How we handle it — Eligibility Verification · Denial Management · Patient Collections

Primary sources

The rules behind CO-26, at the bodies that publish them.

Every denial code with a guide

Liability and workers comp

Looking for a different code? Search all 190 CARC and RARC codes

Questions about CO-26

CO-26 means the service predates the coverage effective date; CO-27 means it came after coverage terminated. They are mirror images of the same failure — verifying that a patient has coverage rather than verifying that coverage was active on the date of service.

Only where the effective date on file is wrong, which does happen when enrolment is processed retroactively. Confirm the actual effective date with the payer first; where the date is correct there is no appeal, only a different payer or the patient.

Usually the prior plan, if the patient was in a transition and the old coverage was still active on that date. Where no coverage existed, the balance is patient responsibility — a conversation much easier to have close to the visit than months later.

Verify eligibility for the specific date of service, not just current coverage, and pay particular attention in January and after any job change. Most eligibility workflows confirm that a policy exists, which is a different question.

Find out what your denials are costing you

A free billing audit reviews your denial rate, AR aging and clean claim rate against industry benchmarks. Takes about two minutes to request. No sales pitch.

No setup fees · You pay when we collect · Pricing from 3% of net collections