Notes on payer behavior
CO-26 denial code: the service came before coverage started
Denial code CO-26 is the payer saying: "Expenses incurred prior to coverage." In short: The payer's start date for the plan is after the date of service. Recoverable when that start date is wrong or the coverage was made retroactive; otherwise the visit belongs to a prior plan or to the patient.
What the payer is asserting
The patient's coverage under this plan hadn't started yet on the date of service, so the plan owes nothing. It's the mirror image of CO-27, where coverage ended before the visit. The same group-code point applies: if the patient truly had no coverage, the normal report is PR-26, patient responsibility. A CO-26 puts the write-off on the practice, and that's worth questioning before anyone posts it. PR vs CO, and who actually owes.
Where it usually comes from
- A new job or a waiting period. The patient showed a new card, but the employer plan's effective date is the first of next month.
- A new or changed plan. Marketplace and employer plans often start on the first of a month. A visit in the gap lands on the old plan, or on nobody.
- A dependent added late. A spouse or child added after the visit, with the enrollment not yet in the payer's file.
- COBRA. A patient who lost job-based coverage can elect COBRA after the fact, and the U.S. Department of Labor says COBRA coverage is retroactive to the day job-based coverage ended once it's elected and paid. A visit in that window can turn from uncovered to covered.
- The payer's file is simply wrong. Enrollment dates get keyed wrong and corrected later. The payer won't reprocess on its own.
Three checks before anything else
- The eligibility response from the visit. If it showed the plan active on the date of service, you have a dispute about the payer's own data, and the screenshot or the eligibility response is the evidence.
- The prior plan. Ask the patient what covered them before the new plan. The claim may be payable there, inside that payer's filing window. Sending a claim to the right payer, and the window that matters.
- A pending COBRA election or enrollment fix. If either is in motion, hold the claim and resubmit once coverage is in the payer's file, rather than billing the patient now.
Is it recoverable?
From this payer, yes, when the start date is wrong or coverage is made retroactive. From another payer, yes, when the patient had other coverage that day. From the patient, yes, when there truly was no coverage, once the group code is PR or the payer confirms patient liability in writing. The costly outcome is the quiet one: a CO-26 posted as a contractual write-off, and nobody billed.
Source: the code descriptions on this page are quoted from the X12 Claim Adjustment Reason Code list, the standard code set every payer remittance uses.
Questions people ask about CO-26
What does denial code CO-26 mean?
The payer says the date of service came before the patient's coverage under the plan began, so the plan owes nothing on the claim.
What's the difference between CO-26 and CO-27?
CO-26 means the service came before coverage started; CO-27 means it came after coverage ended. Both are eligibility-date denials, and both are worth checking against the eligibility response from the visit.
Can I bill the patient for a CO-26 denial?
If the patient truly had no coverage that day, yes, and the group code should be PR rather than CO. Check for a prior plan, a COBRA election or a backdated enrollment first.
Can a CO-26 be reversed later?
Yes, if the payer corrects the start date or the coverage is made retroactive, for example through a COBRA election. Ask the payer to reprocess the claim once the corrected coverage is in its file.