Every month, practices across the country write off revenue they didn’t have to lose. The CO-96 denial code is sitting behind a significant portion of that number. Initial denial rates hit 11.8% in 2024, up 2.55% year-over-year, and according to a 2025 MDaudit report, the average medical necessity denial now costs $450 per claim, a 70% jump from the prior year. For a non-covered charges denial code, that’s money that often doesn’t come back.
If you’re looking at a stack of CO-96 denials right now, you already know the code exists. What you need is a clear explanation of why it keeps showing up, who actually owes the money, and what your team should do about it.
Quick Clarification: What Does “Code 96” Mean?
In medical billing, code 96 refers specifically to Claim Adjustment Reason Code (CARC) 96, which means “Non-Covered Charges.” This is a standardized code used across payers in revenue cycle management. It’s not the same as police radio code 10-96 (mental health call) or banking Response Code 96 (system error). If you searched “code 96” and landed here, this is the medical billing definition.
This guide covers what the CO-96 denial code actually means on your EOB, why it keeps coming back, and exactly what your team should do about it, including the Medicare-specific rules most billing departments get wrong.
What Is the CO-96 Denial Code? The Official Definition
The CO-96 denial code means the billed service is not covered under the patient’s insurance plan, and the provider is contractually obligated to absorb the cost as a write-off. It’s part of the standardized claim adjustment reason code system that tells providers exactly why a payer reduced or denied a payment. When Group Code CO appears with CARC 96, the provider cannot bill the patient for that amount.
X12 maintains the official CARC list, and CARC 96 has been in active use since January 1, 1995. The current definition, last modified July 1, 2017, reads: “Non-covered charge(s). At least one Remark Code must be provided (NCPDP Reject Reason Code or Remittance Advice Remark Code that is not an ALERT).” (X12 CARC List, Last Modified July 1, 2017)
In plain terms, that means the payer is telling you the service isn’t covered, and they’re required to tell you specifically why through an accompanying remark code.
The CO group code is where the financial consequence lives. CO stands for Contractual Obligation, meaning the provider agreed by contract to write off this amount. It’s not a negotiation. It’s not a request. The provider absorbs it unless a valid Advance Beneficiary Notice or equivalent waiver was signed before the service was provided.
CMS is direct about this for Medicare: beneficiaries cannot be billed when Group Code CO appears on the remittance advice. (CMS Medicare Claims Processing Manual, Chapter 1) That rule doesn’t have exceptions for billing staff who didn’t know, or for services where documentation looked solid.
Here’s something most billing departments don’t know. The CO-96 denial code description requires at least one accompanying remittance advice remark code by X12 standard. If your ERA shows CO-96 with no RARC attached, the payer hasn’t met the X12 835 transaction standard. You can contact them and request the specific remark code before you do anything else. That’s not aggressive. That’s the payer’s obligation under the standard.
On the 835 transaction, CARC 96 appears in the CAS segment within Loop 2110 Service Payment Information, alongside the RARC that specifies the exact reason for the denial.
CO-96, PR-96, PI-96, and OA-96: What Each Prefix Actually Means
The number 96 tells you the problem: non-covered charge. The letters before it tell you who pays for it. That’s the part most billing teams miss, and it’s the part that determines everything about what you do next.
Here’s how all four variants compare:
| Code | Full Name | Who Is Responsible | Can Patient Be Billed | Common Scenario |
| CO-96 | Contractual Obligation | Provider writes off | No (except with valid ABN) | Service excluded per provider-payer contract |
| PR-96 | Patient Responsibility | Patient | Yes | Statutory exclusion or non-benefit category where patient was notified |
| PI-96 | Payer Initiated Reduction | Payer adjusts | Depends on payer contract | Payer applies internal policy reduction unrelated to patient benefit limitations |
| OA-96 | Other Adjustment | Varies | Depends on context | Secondary insurance coordination, crossover claims, government program adjustments |
CO-96: When you’re contracted with a payer and they send CO-96, your contract already settled this. You write off the amount. CMS reinforces this for Medicare specifically: beneficiaries cannot be billed when Group Code CO appears on the remittance advice.
PR-96 denial code: This is where liability shifts to the patient. The PR-96 denial code means the provider can bill the patient directly. It shows up most often when a service is statutorily excluded but the patient was properly notified beforehand, or when the patient actively chose a non-covered service. Getting CO-96 and PR-96 mixed up isn’t just a billing error. It’s a compliance problem that can cost a practice far more than the original denial.
PI-96 denial code: The payer initiated a payment reduction based on its own internal policies, not a coverage exclusion in the member’s benefit plan. The service may technically be covered. What’s changed is how the payer is applying its internal payment rules. When you see the PI-96 denial code, review the payer’s internal payment policy, not the patient’s benefit document.
OA-96 denial code: This one appears most often in coordination-of-benefits situations, crossover claims between Medicare and Medicaid, or government program payment adjustments. The OA-96 denial code doesn’t point clearly to the provider or the patient. The claim adjustment reason code alone won’t tell you enough. Look carefully at the remittance advice remark codes that come with it, because the resolution path depends entirely on the specific scenario.
One factual clarification worth making here: CO-96 does not indicate that the patient’s coverage was inactive or lapsed. Lapsed or terminated coverage generates CO-27. CO-96 means the service itself is non-covered under an active plan. These two codes lead to completely different resolution workflows, and confusing them wastes real time.
When CO-96 Is the Provider’s Loss and When the Patient Owes
CO-96 is generally not patient responsibility. The CO group code signals a contractual obligation, which means the provider agreed in the payer contract to write this amount off. That agreement was made before the service ever took place.
CMS makes this explicit for Medicare: beneficiaries cannot be billed when Group Code CO appears on the remittance advice. (CMS Medicare Claims Processing Manual, Chapter 1) That’s not a guideline with room for interpretation. It’s a billing rule with compliance consequences.
The Advance Beneficiary Notice exception is the only real path to patient billing. Before providing a service that Medicare may deny as non-covered, a provider can have the patient sign an Advance Beneficiary Notice. That document, signed before the service, explains that Medicare may not pay and that the patient agrees to be financially responsible if it doesn’t. When a valid ABN is in place and Medicare denies with PR-96, the patient can be billed.
The timing matters. An ABN signed after the service is provided doesn’t change anything. The liability already attached to the provider when the service was rendered without a waiver in place. You can’t go back.
For commercial payers, the rules follow the same basic structure. In-network contracts typically treat CO-group adjustments as write-offs, the same way Medicare does. But payer contracts vary. Before making any patient billing decision on a commercial CO-96 denial, check the specific contract terms.
Here’s where the stakes get real. If a provider receives CO-96 and bills the patient anyway without a valid prior waiver, that’s a contract violation for commercial payers and a compliance violation for Medicare. It’s not just a billing mistake. It’s the kind of error that draws audits.
If your team is uncertain whether CO-96 charges can be passed to patients in specific situations, that question has compliance implications worth getting right. Our denial management team works through these exact scenarios daily.
When CO-96 Is the Provider’s Loss and When the Patient Owes
CO-96 is generally not patient responsibility. The CO group code signals a contractual obligation, which means the provider agreed in the payer contract to absorb this amount as a write-off. That agreement was made before the service ever took place.
CMS Medicare Claims Processing Manual, Chapter 1 confirms this directly: beneficiaries cannot be billed when Group Code CO appears on the remittance advice. That’s not a guideline open to interpretation. It’s a billing rule with compliance consequences attached.
The Advance Beneficiary Notice is the only legitimate exception. Before providing a service that Medicare may deny as non-covered, a provider can have the patient sign an Advance Beneficiary Notice explaining the potential financial responsibility. That document shifts liability. When a valid ABN is in place and the claim denies, Medicare typically assigns PR-96 rather than CO-96, and the patient can be billed.
Timing matters here more than most billing teams realize. An Advance Beneficiary Notice signed after the service was already provided doesn’t change the liability that attached the moment the service was rendered without a waiver. You can’t fix that retroactively.
For commercial payers, in-network contracts typically treat CO-group adjustments as write-offs the same way Medicare does. That said, contract language varies between payers. Before making any patient billing decision on a commercial CO-96 denial, review the specific contract terms rather than assuming the rule is universal.
Here’s the bottom line: CO-96 is a write-off. The PR-96 denial code is patient-billable. Billing a patient for a CO-96 denial without a valid prior waiver is a contract violation for commercial payers and a compliance violation for Medicare. The cost of getting that wrong is almost always higher than the original denied amount.
If your team is uncertain whether CO-96 charges can be passed to patients in specific situations, that question has compliance implications worth getting right. Our denial management team works through these exact scenarios daily.
Why the Remark Code Matters More Than the Denial Code for CO-96
CO-96 is the headline. The RARC is the story. CARC 96 tells you the category of the problem: non-covered charge. What it doesn’t tell you is what kind of non-covered charge it is, or what you’re supposed to do about it. That’s entirely the RARC’s job.
Without reading the remittance advice remark code first, you can’t know whether the fix is a coding correction, a policy lookup, an authorization request, or a straight write-off. Acting before you check it is like opening a claim and guessing.
The Official RARC Codes That Pair with CO-96 on Your ERA
Here’s something worth knowing that no competitor article mentions. Per X12’s 835 transaction standard, CARC 96 requires at least one accompanying remark code on every ERA. If your explanation of benefits shows CO-96 with no RARC attached, the payer hasn’t met that standard. You can contact them and request the specific RARC before you do any resolution work. That’s not aggressive. That’s the payer’s obligation under X12.
Noridian and other Medicare Administrative Contractors publish guidance on how these RARC pairings work in practice. The table below maps the most common 96 remark code pairings you’ll see with CARC 96 on your ERA.
| RARC Code | Official X12/Noridian Description | What It Means in Plain Language | Immediate Action |
| N130 | “Consult plan benefit documents/guidelines for information about restrictions for this service.” | The payer is pointing you to the member’s benefit documents for the specific exclusion. | Pull the plan’s benefit summary or local coverage determination and identify the specific coverage restriction. |
| N425 | “Statutorily excluded service(s).” | The service is excluded by statute, typically Medicare law, not just payer policy. | Verify if ABN was obtained. If not and Group Code is CO, write off. If PR, bill patient. |
| N431 | “Not covered with this procedure.” | The procedure code combination doesn’t fit the payer’s coverage policy. | Review CPT selection and payer policy for this specific code combination. |
| N569 | “Not covered when performed for the reported diagnosis.” | The ICD-10 code doesn’t support coverage for this procedure under payer policy. | Review Dx-to-procedure medical necessity mapping and LCD if Medicare. |
| N180 | “Item or service does not meet the criteria for the category under which it was billed.” | The billing category is wrong for what was actually provided. | Review HCPCS or CPT category selection and resubmit under the correct code. |
| N115 | “This decision was based on a Local Coverage Determination (LCD).” | A Medicare Administrative Contractor has published an LCD that excludes this service in this scenario. | Pull the specific LCD from the MAC website and review coverage criteria. |
Every resolution path for a CO-96 denial starts with that RARC column. Resubmission, appeal, write-off: the right call depends entirely on which remark code is sitting next to the denial. Reading CO-96 alone and jumping to a fix is like trying to repair a car without knowing what’s broken. The RARC is the diagnostic. Everything else follows from it.
What Changed for CO-96 in 2026: The CAQH CORE Update
CAQH CORE published updated Code Combinations in February 2026, version 3.10.0, with a compliance deadline of May 1, 2026. If that name isn’t familiar, here’s the short version: CAQH CORE is the operating rules authoring entity designated by HHS under the ACA for HIPAA-mandated administrative transactions. When CAQH CORE updates its guidance, health plans are required to comply. This isn’t optional.
The v3.10.0 update pushes payers toward more uniform CARC/RARC combinations for common denial scenarios, including CO-96 denial code pairings. For billing teams, that has a specific practical consequence: denial analytics tools and ERA mapping systems need to be verified against the updated combinations before that May 2026 deadline. Mapping logic that worked correctly in 2025 may route denials incorrectly after the update takes effect.
This is the kind of change that slips through quietly if your practice management system vendor doesn’t flag it. Worth a direct conversation with them before May.
Three things your team should check right now:
- Confirm your practice management system vendor has updated ERA mapping to CAQH CORE v3.10.0
- Verify that your denial worklist routing rules reflect the updated code combinations
- Review any CO-96 denials that arrived after February 2026 to ensure they’re being categorized correctly under the new combination logic
Ten Reasons Your Claims Are Coming Back with CO-96
Most billing teams assume the CO-96 denial code is a coding problem. The data says otherwise. Front-end process gaps drive the majority of non-covered charges denials, which means the fix usually lives upstream from the coder’s desk.
Services Excluded from the Patient’s Plan
Some services simply aren’t in the patient’s benefit document. Cosmetic procedures, experimental treatments, alternative therapies, and certain DME items fall into this category regularly. RARC N425 or N130 typically accompanies this cause. No coding correction will resolve it because the service itself is what’s excluded, not how it was billed.
Missing or Expired Prior Authorization
Prior authorization was required but never obtained, or the authorization expired before the service date. Specialty referrals, high-cost imaging, and surgical procedures are the most common scenarios. RARC N431 sometimes appears here when the payer’s system interprets the authorization gap as a coverage mismatch rather than an administrative miss.
Medical Necessity Not Established
The payer’s system cross-references the CPT code against the ICD-10 diagnosis to determine whether clinical criteria are met. When the documentation or coding doesn’t demonstrate medical necessity, the service gets treated as non-covered. RARC N569, “not covered when performed for the reported diagnosis,” is the most frequent RARC pairing for this cause.
Incorrect CPT, HCPCS, or ICD-10 Coding
The procedure was likely covered, but the wrong CPT code made it look non-covered to the payer’s system. A covered service billed under a code the payer doesn’t recognize for that diagnosis will generate CO-96 automatically. This is the most recoverable cause because a corrected claim with the right code often resolves the denial without a formal appeal.
Missing or Incorrect Modifiers
For Medicare claims, modifiers GA, GY, and GZ communicate ABN status and determine liability designation before a claim is even processed. Missing one of these on a service where the Advance Beneficiary Notice was obtained can flip the group code from PR to CO. For behavioral health billing, modifiers 96 and 97 distinguish habilitative from rehabilitative services, which carry different coverage rules under many commercial plans.
Out-of-Network Provider Issues
Coverage restrictions apply when the rendering provider is out-of-network for the patient’s specific plan. Some plans reduce payment. Others apply CO-96 or PR-96 to the full claim. Group practices see this frequently when one provider is in-network and a covering colleague who sees the same patient isn’t.
Benefit Exhaustion and Plan Limitations
Physical therapy capped at 30 visits, mental health sessions limited to 20 per year, chiropractic restricted per quarter. When those limits are exhausted and another claim goes out anyway, CO-96 follows. This isn’t a coding failure. It’s a benefit tracking failure, and the claim was submitted without confirming remaining visits.
Pre-Existing Condition Exclusions
Short-term health plans and certain grandfathered plans still carry pre-existing condition exclusions. When a patient’s plan excludes coverage tied to a specific condition and the claim covers services treating that condition, the denial reason code CO-96 appears regardless of how accurately the claim was coded.
Coordination of Benefits Errors
Claims must go to the primary payer first when a patient carries two insurance plans. If the secondary payer receives the claim without the primary payer’s EOB attached, or if the wrong carrier is billed as primary, CO-96 can result from the secondary carrier’s perspective. Crossover claims between Medicare and Medicaid generate OA-96 in this same scenario.
Front-End Verification Gaps
Here’s the cause behind most repeat CO-96 patterns: eligibility verification confirmed the patient had active coverage, but nobody checked whether the specific service being provided that day was actually covered under that patient’s plan. Confirming coverage status and confirming service-level benefit detail are two different checks. Practices that skip the second one keep seeing the same non-covered services denial code cycle through their denial reports month after month.
If more than one of these causes sounds familiar from your denial reports, the pattern usually points back to a front-end workflow gap. Our AR Follow-Up team has seen this before. Here is how we approach it.
CO-96 and PR-96 in Medicare Billing: What Providers Need to Know
How Medicare Communicates Liability Through Group Codes
Medicare denial code 96 works the same way as it does with commercial payers at the code level, but the liability rules are stricter. When Medicare processes a claim and determines a service is non-covered, it assigns a group code based on who is financially responsible. CO means the provider absorbs the cost. PR means the beneficiary owes.
The number 96 appears under both group codes. That’s what creates the confusion. CARC 96 doesn’t determine liability. The group code prefix does. CMS Medicare Claims Processing Manual, Chapter 1 confirms this directly: beneficiaries cannot be billed when Group Code CO appears on the remittance advice.
ABN Modifiers and What They Mean for CO-96 vs. PR-96
The modifier appended to a Medicare claim at the time of billing is what determines which group code the Medicare denial code 96 lands under. Most billing professionals don’t realize the modifier decision made before the service is provided is what controls patient liability after the denial arrives.
| Modifier | Full Name | When Used | Group Code Result | CARC | RARC |
| TO | Waiver of Liability on File | ABN signed before service | PR | 96 | N425 |
| GY | Statutorily Excluded or Non-Medicare Benefit | Service is never covered by Medicare | PR | 96 | N425 |
| GZ | Expected Denial, No ABN | Likely non-covered, no waiver obtained | CO | 96 | N425 |
igned beforehand. When GZ is appended, or when no modifier is used and Medicare denies with CO-96, the provider absorbs the write-off. The modifier choice at billing determines patient liability. (Source: CMS Medicare Claims Processing Manual, Chapter 1; CMS ABN Transmittal guidance.)
Statutory Exclusions Under Medicare and How CO-96 Applies
Statutory exclusions are different from coverage limitations or local coverage determination restrictions. Congress excluded these services from Medicare by law, which means perfect documentation and accurate coding won’t change the outcome.
Palmetto GBA, the Medicare Administrative Contractor for Jurisdiction M Part B, publishes specific CO-96 scenarios in its official provider guidance, including ambulance transportation to a funeral home, services provided to incarcerated patients, and routine dental, vision, and hearing examinations. When Medicare denies a non-covered services denial code with RARC N425 for any of these services, no appeal will overturn it.
The practical question at that point isn’t how to fight the denial. It’s whether a valid ABN was obtained before the service, which would shift the denial to PR-96 and allow patient billing. If no ABN was in place, write the charge off.
How to Fix a CO-96 Denial: A Decision-Based Resolution Guide
Not every CO-96 denial resolves the same way. The RARC you identified earlier determines which branch of this guide applies to your specific denial. If you skipped straight to this section, go back and check the remark code first. That two-minute step prevents hours of misdirected work.
Step 1: Read the Full ERA as a Three-Part Statement
The ERA gives you three pieces of information at once: the group code tells you who is liable, CARC 96 tells you the category is non-covered, and the RARC tells you the specific reason. Most billing teams read only the CARC and start working. Reading all three together takes roughly 30 additional seconds and completely changes the resolution path.
On the 835 transaction, CO-96 appears in the CAS segment of Loop 2110. The RARC follows in the MOA or MIA segment. Pull both before touching the claim.
Step 2: Identify Your Root Cause Category
Based on the RARC, assign the denial to one of four categories before taking any other action:
- Category A, Coding Error (RARC N431 or N569): correct and resubmit
- Category B, Authorization Gap (RARC N130 with authorization-related context): pursue retroactive authorization or appeal
- Category C, Genuine Plan Exclusion (RARC N425): determine CO vs. PR liability, then write off or bill patient
- Category D, Payer Processing Error (no clear clinical or coding basis): build an appeal file
That categorization tells you exactly which step below applies to your denial.
Step 3: If the Cause Is a Coding Error, Correct and Resubmit
Category A denials are the most recoverable. Check the CPT code against the ICD-10 using the payer’s local coverage determination or coverage policy. Verify that all required modifiers are present before resubmitting. Resubmit as a corrected claim using claim frequency code 7, which designates it as a replacement of a prior claim. Confirm the payer’s timely filing limit first. Most commercial payers allow 90 to 180 days from the date of service, though this varies by contract.
Step 4: If the Cause Is Missing Authorization, Pursue Retroactive or Appeal
Call the payer before building an appeal. Some payers will grant retroactive prior authorization when the service was medically necessary and the omission was administrative rather than a clinical decision. If retroactive authorization isn’t available, a formal appeal is the only path forward. The appeal letter should include the clinical basis for the service, supporting notes from the treating provider, and a clear explanation of why authorization wasn’t obtained in advance.
If you’re at Step 4 and the appeal file is building faster than your team can manage, that’s exactly what our denial management service is built for. Here is how One O Seven RCM handles CO-96 appeals.
Step 5: If the Cause Is a Genuine Plan Exclusion, Determine Liability
When RARC N425 confirms a statutory or contractual exclusion, the question isn’t how to overturn it. The question is who owes the money. Check the group code. CO means write off the amount. PR means the patient can be billed, but only when proper advance notice was given before the service. For Medicare, writing off a CO-group exclusion isn’t optional. It’s a compliance requirement.
Step 6: If the Cause Is a Payer Error, Build Your Appeal File
Payer errors happen more often than payers acknowledge. A CO-96 denial can land on a covered service when the payer’s system misapplies its own medical policy, flags the provider’s network status incorrectly, or fails to update a benefit period reset. These are worth appealing. The appeal file should include the member’s benefit document showing coverage, the provider’s in-network agreement confirmation, clinical documentation supporting the service, and a one-page letter citing the specific policy section that covers the billed code. For most commercial payers, internal appeals must be filed within 180 days of the denial date.
Step 7: Document and Track Every CO-96 for Pattern Prevention
One CO-96 denial is a billing event. Ten denials for the same service from the same payer is a workflow problem that needs a process fix, not a claim-by-claim response. Log every resolved denial with the root cause category, RARC, payer name, service type, and resolution outcome. That log becomes your CO-96 pattern report. When the pattern becomes visible, you’re not correcting claims anymore. You’re fixing the workflow that keeps generating them.
CO-96 Denials by Payer: What Changes Across Medicare, Medicaid, and Commercial Plans
The CARC 96 definition is standardized by X12, so the code means the same thing regardless of which payer sends it. What changes is how each payer applies it, what their coverage policies exclude, and what the resolution process looks like on their end. Using a Medicare resolution approach on a BCBS denial wastes time and often misses the actual fix.
CO-96 in Blue Cross Blue Shield (BCBS) Claims
BCBS is a federation of independent plans, which means CO-96 behavior can differ between BCBS Alabama and BCBS Texas. Across plans, the most common triggers are services requiring prior authorization that weren’t pre-approved, exclusions specific to individual or employer-sponsored benefit packages, and out-of-network provider claims where the plan’s out-of-network benefit is limited or absent.
BCBS plans pair CO-96 with remark code N130 more often than N425. That distinction matters because N130 points you to the member’s benefit documents rather than a statutory exclusion, which means an appeal may be viable if the exclusion language is ambiguous. Verify the specific appeal window on the denial notice itself, as BCBS plan deadlines typically range from 90 to 180 days but vary by plan.
CO-96 in UnitedHealthcare Claims
CO-96 in UnitedHealthcare claims most often appears for services requiring prior authorization under UHC’s clinical coverage guidelines, services billed under codes that UHC’s bundling policies don’t allow separately, and specialty services where UHC’s medical policy restricts coverage to specific clinical indications. The UHC provider portal is the fastest diagnostic tool here. When CO-96 arrives on a UHC claim, pulling the Coverage Summary Plan Document through the portal identifies the specific exclusion language faster than calling the payer directly.
CO-96 in Medicaid Claims
Medicaid CO-96 denials are state-specific because each state’s Medicaid program sets its own benefit structure within federal parameters. Common triggers include optional benefits that have been eliminated in state budget cycles, services requiring prior authorization under managed care contracts, and claims submitted to the wrong managed care organization after a patient switched plans mid-year.
Verifying active Medicaid status isn’t enough. The patient’s current managed care plan and specific benefit package need to be confirmed at the time of service, because two managed care organizations operating in the same state can have meaningfully different non-covered services denial code outcomes for the same procedure.
CO-96 in Skilled Nursing Facility (SNF) Billing
CO-96 in SNF billing most often appears when services provided to a Medicare Part A SNF patient fall outside the scope of the covered condition requiring the SNF stay. Medicare’s SNF benefit covers services tied directly to the patient’s plan of care for that condition. Ancillary services unrelated to that condition, or any services provided after the benefit period has exhausted, are denied with CO-96.
Every service billed under the SNF benefit needs MDS documentation support. When CO-96 appears on an SNF claim, the first review should be the patient’s plan of care and MDS to confirm whether the billed service was within the scope of the covered condition. If it wasn’t, the write-off is appropriate. If it was, that documentation becomes the foundation of the appeal.
How to Prevent CO-96 Denials Before the Claim Is Submitted
By the time CO-96 lands on your ERA, the service has already been provided. At that point, the options are resubmit, appeal, or write off. Shifting that work to before the claim is generated is where the real recovery rate improvement lives. Even two or three of these strategies applied consistently will reduce CO-96 frequency more than any appeal process refinement.
Service-Level Benefit Verification (Not Just Eligibility Confirmation)
There’s a meaningful difference between confirming a patient has active coverage and confirming that the specific service being provided today is covered under that patient’s plan. Basic eligibility verification tells you coverage is active. That’s it.
Service-level verification confirms whether the specific CPT code is covered under the plan, whether visit limits have been exhausted, whether the rendering provider is in-network for that patient’s specific plan tier, and whether prior authorization is required for that service. Tools that return real-time benefit detail, not just an eligibility status flag, catch the non-covered charges denial code before the claim is ever generated. That’s the verification gap driving most repeat CO-96 patterns.
Prior Authorization Management Before High-Risk Services
The problem isn’t that billing teams don’t know authorization is required. The problem is that authorization requirements change, and those changes don’t come with a notification. A service that didn’t need authorization in 2024 may require prior authorization in 2026 under an updated payer policy, and the first indication is often a denial.
Assign one person on the billing team to own authorization management specifically. That person should review the top 20 CPT codes billed by the practice against each major payer’s clinical coverage guidelines on a quarterly basis. When a new requirement appears, the workflow update should happen before the first affected claim goes out.
Coding Accuracy and LCD Alignment
For Medicare claims, every CPT code should be checked against the applicable local coverage determination before submission. LCDs define exactly which ICD-10 codes support medical necessity for a given procedure. A billed diagnosis that isn’t in the LCD’s covered indications list will generate CO-96 regardless of how accurate the clinical documentation is.
The MAC’s website publishes LCDs by jurisdiction. Bookmarking the relevant MAC and checking it when a new procedure or diagnosis combination enters the billing workflow takes minutes and prevents claims that have no path to payment.
Staff Training on Payer Policy Changes
Payer medical policies update several times per year. Most billing teams learn about those changes after receiving a denial, which is the most expensive possible way to find out. Schedule quarterly payer policy reviews as a standing agenda item, prioritizing the top three or four payers by claim volume. When a policy change affects a commonly billed service, the coding and authorization workflow needs to be updated before the next claim goes out, not after the first denial arrives.
Claim Scrubbing and Pre-Submission Audits
A claim scrubber running against payer-specific edits catches code combination errors, missing modifiers, and authorization flag warnings before the claim leaves the practice. Not every scrubber checks against payer-specific policies. Verify that your clearinghouse or practice management system scrubs against each payer’s edit library, not just generic coding rules. A scrubber catching CO-96 denial code triggers at the pre-submission stage recovers its cost quickly in avoided denial work.
| Prevention Strategy | Timing | Frequency | Impact Level |
| Service-level benefit verification | Pre-service | Every patient visit | Critical |
| Prior authorization confirmation | Pre-service | Every applicable service | Critical |
| LCD alignment check | Pre-submission | Per new CPT/ICD-10 combination | High |
| Payer policy review | Pre-policy change | Quarterly | High |
| Claim scrubbing | Pre-submission | Every claim | High |
If your team is spending more time resolving CO-96 denials than preventing them, that ratio is worth fixing. Our revenue cycle management service builds prevention into the front end so denials arrive less often.
CO-96 Compared to Related Denial Codes: A Quick Reference
CO-96 and CO-27 land in the same denial queue but require completely different resolution workflows. CO-96 means the service isn’t covered under the patient’s active plan. CO-27 means coverage wasn’t active on the date of service at all. Sending a CO-27 denial through a denial code 96 resolution process wastes time and produces no result.
| Denial Code | Description | Key Difference from CO-96 |
| CO-96 | Non-covered charge (contractual) | Provider write-off unless valid ABN obtained beforehand |
| PR-96 | Non-covered charge (patient responsibility) | Patient can be billed directly |
| CO-97 | Payment included in allowance for another service | Bundling issue, not a coverage exclusion |
| CO-27 | Expenses incurred after coverage terminated | Coverage was lapsed, not a non-covered service under an active plan |
| CO-204 | Not covered under patient’s current benefit plan | More specific than 96; plan benefit explicitly excludes this service |
| CO-16 | Claim missing information or has submission errors | Correctable billing error, not a coverage issue |
| CO-50 | Not deemed medically necessary | Medical necessity denial with a different appeal pathway |
CO-97 deserves a separate look when it appears on the same remittance as CO-96. That combination often signals an unbundling issue rather than two independent coverage problems, and appealing them separately without reviewing the service relationship first typically doesn’t resolve either one.
CO-96 Denial Code: Frequently Asked Questions
What is the CO-96 denial code?
CO-96 is a Claim Adjustment Reason Code that means “Non-Covered Charges.” It tells you the insurance company has determined the billed service isn’t included in the patient’s benefit plan or doesn’t meet plan criteria. The “CO” prefix means the provider is contractually obligated to absorb the cost and cannot bill the patient unless a valid waiver was signed before the service was provided.
What is the difference between CO-96 and PR-96?
CO-96 and PR-96 use the same code number but carry opposite financial outcomes. CO-96 means the provider must write off the charge. PR-96 means the patient is responsible and can be billed directly. Mixing these two up is one of the more costly compliance errors in medical billing. The group code prefix, not the number 96, is what determines who pays.
Can a provider bill the patient for a CO-96 denial?
Generally, no. CO-96 carries the Contractual Obligation group code, which means the provider agreed by contract not to bill the patient for this amount. For Medicare, CMS is explicit: beneficiaries cannot be billed when Group Code CO appears on the remittance advice. The exception is when a valid Advance Beneficiary Notice was signed by the patient before the service was provided, which can shift the denial to PR-96.
What is PR-96 on an EOB?
PR-96 on an Explanation of Benefits means Patient Responsibility, Non-Covered Charges. The insurance company has reviewed the claim, determined the service isn’t covered under the patient’s plan, and assigned liability to the patient. Unlike CO-96, the provider can bill the patient directly for PR-96 amounts. Before billing, verify the coding was accurate, because a PR-96 caused by a billing error still shouldn’t be collected from the patient.
What remark codes pair with CO-96?
The most common RARCs with CO-96 are N130 (consult plan benefit documents), N425 (statutorily excluded service), N431 (not covered with this procedure), N569 (not covered for the reported diagnosis), N180 (does not meet criteria for the category billed), and N115 (based on a Local Coverage Determination). The RARC identifies the specific reason for the denial. CO-96 without a RARC violates the X12 835 standard, and the provider can request one from the payer before beginning any resolution work.
How do I resolve a CO-96 denial?
Start by reading all three parts of the ERA together: the group code (CO or PR), CARC 96, and the accompanying RARC. The RARC tells you which resolution path applies. N431 or N569 means correct the coding and resubmit. N425 means determine whether an ABN was signed, then write off or bill the patient accordingly. N130 means pull the benefit documents and assess whether an appeal is viable before taking any further action.
What is the difference between CO-96 and CO-27?
CO-96 means the service isn’t covered under the patient’s active plan. CO-27 means the patient’s insurance wasn’t active on the date of service. These require entirely different resolution workflows: CO-96 is a coverage exclusion problem, and CO-27 is an eligibility timing problem. Some sources incorrectly state that CO-96 indicates inactive coverage. That’s not accurate. Inactive coverage generates CO-27, not CO-96.
What is the difference between CO-96 and CO-97?
CO-96 means the charge is non-covered under the patient’s plan. CO-97 means the service is considered included in the payment for another service already billed on the same claim. CO-96 is a coverage problem. CO-97 is a bundling problem. When both appear on the same remittance, review the services for inappropriate unbundling before appealing either denial separately, because the underlying issue may be the same for both.
What is CO-96 in Medicare billing?
In Medicare billing, CO-96 most often appears for services statutorily excluded from Medicare coverage, such as routine dental, vision, and hearing exams, or services provided outside the scope of a covered condition. Medicare uses the CO vs. PR group code to communicate liability: CO means the provider absorbs the cost, and PR means the beneficiary owes. The modifier appended to the claim, whether GA, GY, or GZ, typically determines which group code Medicare assigns.
What is the golden rule in medical billing as it relates to CO-96?
Read all three parts of the denial before taking any action: group code, CARC, and RARC. The group code tells you who pays. The CARC tells you the category. The RARC tells you exactly why. Acting on CO-96 without reading the RARC first is like trying to repair equipment without knowing what’s broken. The RARC is the diagnostic. Every resolution decision for this denial flows from it.
What is the PI-96 denial code?
PI-96 means Payer Initiated Reduction for a non-covered charge. The payer is applying a unilateral payment reduction based on its own internal policies rather than a coverage exclusion in the patient’s benefit plan. Unlike CO-96, where the service is excluded entirely, PI-96 may apply to a service that’s generally covered but is being reduced by the payer for administrative reasons. Review the accompanying RARC and the payer’s payment policy to determine whether an appeal is appropriate.
What is the OA-96 denial code?
OA-96 means Other Adjustment for a non-covered charge. It appears most often in coordination of benefits scenarios, crossover claims between Medicare and Medicaid, and government program payment adjustments. The OA group code doesn’t assign liability to either the provider or the patient the way CO and PR do. Resolution depends entirely on the specific scenario and the accompanying RARC, so review the full remittance context before taking any action.
What does CARC 96 require by X12 standard?
By X12 standard, CARC 96 requires at least one accompanying Remark Code, either an NCPDP Reject Reason Code or a Remittance Advice Remark Code that is not an ALERT. If a payer sends CO-96 without a RARC attached, the ERA doesn’t meet the X12 835 transaction standard. In that case, the provider can contact the payer and request the specific RARC before beginning any resolution or appeal work.
What is the CAQH CORE update for CO-96 in 2026?
CAQH CORE published updated Code Combinations in February 2026, version 3.10.0, with a compliance deadline of May 1, 2026. This update affects how payers must communicate CARC and RARC combinations in the 835 transaction, including CO-96 pairings. Revenue cycle teams should verify that their practice management system and clearinghouse have updated ERA mapping to reflect the new CAQH CORE v3.10.0 combinations before the May 2026 deadline.
How long do I have to appeal a CO-96 denial?
Appeal timelines vary by payer and state. For Medicare, the standard windows are Redetermination within 120 days of the denial notice and Reconsideration within 180 days of the Redetermination decision. For commercial payers, internal appeals are typically required within 90 to 180 days of the denial date, though some payers set shorter windows. Always check the specific deadline printed on the denial notice itself. Filing one day late means the denial stands regardless of its merit.
Managing CO-96 Denials Is a Workflow Problem, Not a Billing Problem
Most recurring CO-96 denials are front-end workflow failures, not coding errors. The pattern in denial reports almost always traces back to the same gap: eligibility verification confirmed active coverage, but nobody checked whether the specific service being provided that day was actually covered under that patient’s plan. By the time the EOB arrives, correcting that missed step takes three to five times longer than catching it before the service was provided.
One O Seven RCM works inside this problem every day across multiple specialties and payer types. Not every denial is preventable. But recurring denials almost always point back to a workflow gap that can be identified and fixed, and that distinction changes what you do next.
If CO-96 keeps appearing in your denial reports and the volume isn’t decreasing month over month, that pattern is worth a conversation. See how One O Seven RCM handles full-cycle denial management, including CO-96 prevention, resolution, and pattern tracking.
