PR-96 Denial Code: 2026 Patient-Billing Compliance & Resolution Guide

A patient calls the practice complaining about a bill they didn’t expect. The PR-96 denial showed up on the remittance, the front desk billed the balance, and now the patient’s threatening to file a complaint. The PR group code said patient responsibility , so why is this a problem?

The pr 96 denial code shifts non-covered charges to the patient, but only when valid pre-service notice exists. For Medicare patients, that means a properly signed ABN before the service was rendered. Without it, the PR-96 amount can’t legally be collected, no matter what the group code says.

Initial denial rates hit 11.8% in 2024, and PR-96 sits among the most operationally misunderstood codes in the denial management stack. X12 maintains the official CARC 96 definition under External Code List 139, and CMS Transmittal 13666 (March 25, 2026) governs the current update cadence.

This guide covers what PR-96 actually means, the four-way group code framework that determines who pays, the ABN compliance rules every Medicare biller must follow, and the 4-path resolution decision tree for handling PR-96 correctly.

Quick Answer: What Is the PR-96 Denial Code?

The PR-96 denial code is the combination of Claim Adjustment Group Code PR (Patient Responsibility) and Claim Adjustment Reason Code 96, which X12 defines as “Non-covered charge(s)” with the rule that “at least one Remark Code must be provided that is not an ALERT.” The PR group code shifts financial responsibility to the patient, but only when valid pre-service notice (an ABN for Medicare patients or equivalent waiver for commercial payers) has been documented. Without proper notice, billing the patient becomes a compliance violation despite the PR group code.

What Is the PR-96 Denial Code? Official X12 + CMS Authority Definition

The pr 96 denial code sits at the intersection of X12 transaction standards and CMS compliance rules. Most billers search for the pr 96 denial code description because the ERA shows an adjustment without enough context to resolve it correctly. Here’s the authority framework behind what you’re seeing.

The X12 Definition (CARC 96 Verbatim + RARC Requirement)

X12, the standards body that maintains all Claim Adjustment Reason Codes under HIPAA, defines CARC 96 as “Non-covered charge(s).” The official rule attached to the code is non-negotiable: “At least one Remark Code must be provided (NCPDP Reject Reason Code or Remittance Advice Remark Code that is not an ALERT).”

You’ll find the active pr 96 denial code description on the X12 CARC official list. The CARC 96 claim adjustment reason code itself has been stable since last modified July 1, 2017, but remains active and current.

The X12 External Code List 139 (CARC list) was last modified November 1, 2025. The X12 ECL 411 (RARC list, maintained by CMS) was last modified March 4, 2026.

An ERA showing PR-96 without a RARC attached doesn’t meet the X12 835 transaction standard. Billers can contact the payer and request the specific RARC before doing any resolution work. The X12 claim adjustment reason code framework is HIPAA-mandated , payers can’t opt out of it.

Why CMS Calls It “PR-96”: Group Code PR Explained

Group Code PR stands for Patient Responsibility, one of five Claim Adjustment Group Codes defined by X12 (alongside CO, OA, PI, and CR). When a payer assigns PR-96 to a claim line, the payer is communicating two things at once: the service is non-covered (CARC 96), and the patient bears financial responsibility for the balance (Group Code PR).

CMS states the rule plainly in the Medicare Claims Processing Manual: Medicare beneficiaries may be billed only when Group Code PR is used with an adjustment. That rule is what makes the pr 96 denial code operationally different from CO-96, PI-96, and OA-96.

The denial code pr 96 specifically signals patient responsibility. But Group Code PR is the necessary condition for patient billing, not the sufficient condition. ABN and notice requirements are the second layer. Practices managing high PR-96 volume need denial management services that triage compliance status before any patient statement goes out.

The 2026 CARC/RARC Update Cadence (CMS Transmittal 13666)

CMS Transmittal 13666 (Change Request 14410), dated March 25, 2026, establishes that contractors update CARC and RARC code lists three times per year, approximately March 1, July 1, and November 1. The CARC and RARC code sets are living code lists, not static references.

See the CMS Transmittal 13666 for the full implementation language. The practical implication for billers: the RARC pairings on a carc 96 denial today may not match the RARC pairings six months from now.

The CAQH CORE v3.10.0 update (Section 13) is the most recent cross-industry refinement of CARC/RARC pairing logic, with a May 1, 2026 compliance deadline. Practices that don’t update their ERA mapping logic against these cadences route denial code 96 claims through outdated workflows.

Why “Denial Code” Is Slightly Misleading

Here’s the thing. PR-96 is technically a Claim Adjustment Reason Code, not a denial code. CARCs explain why a payer adjusted a claim from the billed amount. Sometimes the adjustment is a denial, sometimes a coordination offset, sometimes a contractual write-off, sometimes a non-covered charge.

The industry calls all CARCs “denial codes” colloquially because they trigger the same rework workflow operationally. Throughout this guide, we’ll use both “PR-96 denial code” (matching how billers search) and the technically accurate framing.

The pr 96 denial isn’t necessarily a flat rejection. It’s a reclassification of who owes what. And code 96 can land with any of four group codes, each pointing to a completely different resolution path.

How PR-96 Appears on the 835 Electronic Remittance Advice

Payers transmit the pr96 denial code through the X12 835 Health Care Claim Payment/Advice transaction (version 005010X221A1), the HIPAA-mandated electronic remittance format. The adjustment lives in the CAS segment, short for Claim Adjustment Segment, at the service line level. Understanding the 835 structure is what separates billers who resolve PR-96 correctly from those who route it to the wrong queue.

The CAS Segment: Where PR-96 Lives on the ERA

The exact CAS segment notation: CAS*PR*96*[adjusted dollar amount]~. Each CAS segment carries three required elements: the Group Code (PR), the Reason Code (96), and the monetary value. Your billing system parses these elements to auto-post adjustments and route denials through the 835 transaction.

If your billing system has PR-96 configured to auto-route to patient billing without checking for ABN status, that configuration creates compliance exposure on every affected claim. The 835 doesn’t know whether the ABN exists. Your workflow has to check before any auto-post result triggers a patient statement.

The same CAS segment carries CO-96 denials with the notation CAS*CO*96*[amount]~. Our CO-96 denial code guide walks through the contractual write-off side of the same reason code.

CARC vs RARC: Why “PR-96 Remark Code” Is a Category Confusion

PR-96 is a Claim Adjustment Reason Code (CARC), not a Remittance Advice Remark Code (RARC). The two serve different functions on the 835. CARCs explain the primary reason a payer adjusted a claim from the billed amount.

RARCs supplement CARCs with additional detail and appear in the LQ segment at the service line level or the MIA/MOA segments at the claim level.

This answers the “96 remark code” search query: the question itself contains a category error. The 96 remark code terminology is a category confusion. OA-96, PR-96, and CO-96 are all CARCs, not remark codes.

The Group Code (PR) tells you who’s financially responsible. The CARC (96) tells you the reason category: non-covered charges. The RARC (N425, N130, M38/M39, etc.) tells you the actual operational reason and the resolution path.

Working denial code pr 96 from the CARC alone is like trying to repair a car without knowing what’s broken. The RARC is the diagnostic.

The Code Trio Framework: Group Code + CARC + RARC

Here’s what most billing teams miss. PR-96 is never enough information by itself. The complete remittance signal is what we call the Code Trio: Group Code + CARC + RARC. Every PR-96 denial code resolution decision depends on reading all three together.

The Group Code (PR) tells you who’s financially responsible. The CARC (96) tells you the reason category: non-covered charges. The RARC (N425, N130, M38/M39, etc.) tells you the actual operational reason and the resolution path. Working denial code pr 96 from the CARC alone is like trying to repair a car without knowing what’s broken. The RARC is the diagnostic.

The X12 standard makes this explicit: CARC 96 “requires at least one Remark Code that is not an ALERT.” That’s not a recommendation. It’s a transaction-standard requirement. An ERA showing PR-96 without a RARC fails the 835 standard, and your team can request the missing RARC from the payer before taking any other action.

PR-96 vs CO-96 vs PI-96 vs OA-96: The Four-Way Group Code Framework

What usually happens when a biller sees code 96 on a remittance? They check the dollar amount, route it to write-off, and move on. That’s the right move for CO-96. It’s a compliance violation for PR-96 when a signed ABN exists.

And it’s the wrong move entirely when the denial should have been appealed. The group code framework is what separates all four scenarios.

The Five Group Code Framework (Why Group Code Matters Most)

X12 defines five Claim Adjustment Group Codes: PR (Patient Responsibility), CO (Contractual Obligation), PI (Payer Initiated Reduction), OA (Other Adjustment), and CR (Correction and Reversal). The Group Code prefix tells you who absorbs the dollar amount. The Reason Code that follows tells you why.

For Reason Code 96 (Non-covered charges), four group code variants exist operationally, including PR-96, CO-96, PI-96, and OA-96, and the prefix changes everything about your resolution path.

Our CO-96 denial code framework guide walks through this same group code logic from the contractual obligation side. It’s the canonical authority piece on the CO-96 variant. The X12 Claim Adjustment Group Codes list provides the authoritative definitions for all five codes.

PR-96: Patient Responsibility (When Compliance Allows)

PR-96 is the variant where financial responsibility shifts to the patient, but the shift is conditional. The PR group code is the necessary condition for patient billing, not the sufficient condition. The sufficient condition is documented pre-service notice: an Advance Beneficiary Notice (ABN) for Medicare patients or an equivalent waiver for commercial payers.

Is pr 96 patient responsibility? Yes, conditionally. Without that documentation, billing the patient becomes a compliance violation despite the PR group code. The full ABN framework lives in Section 7. Operational rule: never transfer a pr 96 patient responsibility amount to a patient statement without confirming notice exists in the patient’s record.

PR-96 follows the same conditional patient-billing framework as our PR-27 denial code guide for coverage termination. Both are PR-prefix codes that require specific compliance conditions before billing.

CO-96: Contractual Obligation (Provider Write-Off)

CO-96 means the same reason, non-covered charges, but the CO group code locks responsibility to the provider as a contractual write-off. Patient billing is a contract violation for commercial payers and a compliance violation for Medicare.

The issue is that both PR-96 and CO-96 share Reason Code 96, so they look nearly identical on the ERA surface. The group code is the only thing that distinguishes them.

The CO-96 denial means the provider absorbs the loss. The co 96 denial code locks the dollars to provider write-off, regardless of whether the patient was informed.

Our complete CO-96 denial code guide covers the contractual obligation side at depth, including the ABN exception that converts CO-96 to PR-96 in specific Medicare scenarios. Critical operational distinction: if you bill the patient for co96 thinking it’s PR-96, you’ve created compliance exposure that can escalate quickly.

PI-96: Payer Initiated Reduction

PI-96 means the payer initiated a 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.

Less common than PR-96 or CO-96, but the pi 96 denial code is increasingly seen on Medicare Advantage adjudications. The pi-96 denial code resolution requires reviewing the payer’s internal payment policy, not the patient’s benefit document.

OA-96: Other Adjustment

OA-96 appears most often in coordination-of-benefits situations, crossover claims between Medicare and Medicaid, or government program payment adjustments. The OA group code doesn’t point clearly to provider or patient. Context determines responsibility. The oa 96 denial code requires reading the accompanying RARC more carefully than the other variants.

The oa-96 denial code accompanies situations where the adjustment falls outside contractual, patient-responsibility, or payer-initiated categories.

The Single Most Critical Distinction in All of RCM

PR-96 vs CO-96 is the most misunderstood and most compliance-critical distinction in medical billing. Getting it wrong with a Medicare patient can trigger a contract violation. Getting it wrong with a commercial patient can trigger a payer audit.

CMS states the rule plainly in the Medicare Claims Processing Manual: beneficiaries may be billed only when Group Code PR is used with an adjustment.

CO-96 is a write-off. The PR-96 denial code is patient-billable when valid pre-service notice exists. Billing a patient for a CO-96 denial without converting to PR-96 through valid ABN/notice is a contract violation for commercial payers and a compliance violation for Medicare.

The same group code logic applies to other reason codes. Our CO-45 denial code (PR-45 framework) covers the parallel PR-45 vs CO-45 distinction for fee schedule adjustments, where the same compliance pattern applies.

And our CO-22 denial code guide walks through the four-way framework for reason code 22, applying the same group code logic to the COB context. The denial code co 96 is always a write-off. pr96 is always conditional on pre-service documentation.

Statutory vs Benefit Exclusion: The Distinction That Determines Your Resolution Path

PR-96 surfaces under two operationally distinct frameworks: statutory exclusions (services excluded by law) and benefit exclusions (services excluded by plan contract). The two follow different liability rules, require different documentation paths, and trigger different appeal strategies. Treating them as the same pr 96 denial code type sends your team down the wrong workflow.

The Two Frameworks Behind Every PR-96

Statutory exclusions for Medicare are governed by §1862(a)(1)(A) of the Social Security Act. Benefit exclusions are governed by the patient’s plan contract, the Summary Plan Description for ERISA plans, or the policy document for individual market plans. The same CPT code can trigger PR-96 under either framework.

The non-covered charges classification looks identical on the ERA. The resolution path is completely different.

Without distinguishing which framework applies, your team will miss appeals on benefit-excluded services that were incorrectly categorized, or spend time appealing statutorily excluded services where no coverage exists by law. These pr 96 denial code non-covered charges require different first steps, different documentation, and different escalation paths.

Statutory Exclusions: §1862(a)(1)(A) and the Medicare Framework

Section 1862(a)(1)(A) of the Social Security Act (codified at 42 U.S.C. 1395y(a)(1)(A)) excludes from Medicare coverage “items or services which are not reasonable and necessary for the diagnosis or treatment of illness or injury or to improve the functioning of a malformed body member.” This is the federal statute behind every Medicare PR-96 statutory exclusion denial.

Statutorily excluded services include cosmetic surgery (with limited reconstructive exceptions), routine physical exams (with limited preventive exceptions), routine dental services, hearing aids, and several other categories. CMS publishes the comprehensive list in the MLN Booklet “Items & Services Not Covered Under Medicare” (most recent edition: September 2025).

See the CMS Items & Services Not Covered Under Medicare Booklet for the full list. The Medicare-specific resolution path for statutorily excluded services involves the GY modifier, covered in Section 7.

Benefit Exclusions: Plan Contract Language

Benefit exclusions are different. The service may be statutorily covered by Medicare or a commercial plan in general, but the specific patient’s plan contract excludes it. Think of cosmetic procedures excluded under a commercial plan’s specific benefit document, frequency limitations on physical therapy beyond covered visits, or out-of-network services where the plan only covers in-network care.

Here’s where it gets specific: benefit exclusions require the patient’s specific plan documents, not the generic federal statute, to determine coverage.

Resolution path for benefit exclusions: pull the Summary Plan Description (SPD) or benefit document, identify the specific exclusion language, and decide whether to appeal (if the exclusion is misapplied) or proceed with patient billing (if the exclusion is correctly applied and notice exists). Benefit exclusions sometimes overlap with medical necessity determinations.

Our CO-50 medical necessity guide covers the adjacent compliance framework where coverage and clinical necessity intersect.

Why This Distinction Changes Your Workflow

For statutorily excluded services billed to Medicare: GY modifier pathway, ABN may be voluntary (NEMB applies), patient billing legitimate. For statutorily excluded services in a Medicare-as-secondary scenario: still need GY, but resolution depends on what the secondary plan covers.

For benefit-excluded services on commercial plans: resolution requires the SPD review, not the federal statute. Mixing the two frameworks in workflow design creates compliance risk and missed appeals. The pr 96 denial code resolution path starts by answering one question: is this a statutory exclusion or a plan-contract benefit exclusion?

ABN Compliance: When PR-96 Is Actually Patient-Billable

This is the most compliance-dense section in this entire guide. The ABN framework is what converts PR-96 from a payer-side adjustment into a legally collectible patient balance. Skip it and you’ve created OIG audit exposure with every patient statement you send.

The ABN Form CMS-R-131: The Only Legal Bridge for Medicare

For Medicare patients, the Advance Beneficiary Notice of Noncoverage (ABN), Form CMS-R-131, is the legal document that determines whether PR-96 is collectible. CMS designed the ABN as a pre-service notice that tells the patient: Medicare may not pay for this service, and you may be financially responsible.

A signed ABN before the service shifts liability to the patient and authorizes PR-96 billing. Without it, the loss is a provider write-off.

The CMS ABN page (Form CMS-R-131) contains the current form version, instructions, and required language. Form CMS-R-131 must name the specific service being delivered, the estimated cost, and the reason Medicare may not pay. The patient must sign the ABN before the service is rendered.

A signed ABN after the fact isn’t enforceable. Timing is dispositive. Practices that build ABN intake into their insurance eligibility verification workflow catch PR-96 triggers before the service is rendered, turning compliance risk into recoverable revenue.

Mandatory ABN vs Voluntary ABN (NEMB Form CMS-20007)

CMS distinguishes two types of ABN requirements: mandatory ABN and voluntary ABN. Mandatory ABNs are required when Medicare may deny a service as not reasonable and necessary, typically for services where coverage depends on documented medical necessity.

Voluntary ABNs (issued through the NEMB form, CMS-20007) apply when the service is statutorily excluded from Medicare entirely, though the NEMB is no longer required and many practices still issue it as a patient communication best practice.

The mandatory ABN protects the provider’s right to bill the patient when Medicare denies. The voluntary ABN/NEMB serves as transparent patient communication for statutorily excluded services where the GY modifier pathway applies. Both serve compliance functions, but the underlying legal frameworks differ.

The Four Medicare Modifiers: GA, GY, GZ, KX

Four Medicare modifiers govern PR-96 liability outcomes, and the modifier selection happens before claim submission. Per the CMS Medicare Claims Processing Manual:

GA = “Waiver of Liability Statement Issued, as Required by Payer Policy.” ABN required, beneficiary liable. Use when you obtained an ABN before the service.

GY = “Item or Service Statutorily Excluded or Does Not Meet the Definition of Any Medicare Benefit.” Beneficiary liable. Use for statutorily excluded services where Medicare can’t cover by law.

GZ = “Item or Service Expected to Be Denied as Not Reasonable and Necessary.” No ABN given, provider liable. Use when the service may be denied and no ABN was obtained , provider absorbs the loss.

KX = “Requirements specified in the medical policy have been met.” Use when documentation supports medical necessity per LCD/NCD requirements.

The modifier you append determines whether PR-96 or CO-96 lands on your remittance. GA + valid ABN = PR-96 (patient-billable). GZ (no ABN) = CO-96 (provider write-off). GY modifier = PR-96 with statutory exclusion framework (patient-billable, NEMB recommended for transparency). KX = supports medical necessity, helps prevent denial entirely.

See the FCSO Medicare PR-96 statutory exclusion guidance for the full Medicare-specific modifier framework.

ABN Timing Is Non-Negotiable

An ABN signed after the service is delivered does not change the liability that attached the moment the service was rendered without notice. CMS treats post-service ABNs as void for liability purposes.

Here’s where it gets non-negotiable: if your team is signing ABNs after the appointment, you have a compliance gap. Front desk training should make ABN timing the first checklist item for any service with potential PR-96 risk. An audit that surfaces post-service ABNs signals systemic process failure, not individual error.

Commercial Payer Equivalents

For commercial payers, the equivalent legal function is the Financial Responsibility Form or Patient Responsibility Acknowledgment. BCBS, UHC, Aetna, Cigna, and Humana each have variations of pre-service notice requirements. Build both Medicare ABN and commercial equivalents into standard intake workflow for any service with known coverage uncertainty.

The legal framework differs but the operational rule is identical: pre-service signed acknowledgment before billing the patient. Our PR-27 patient responsibility guide covers the parallel coverage-termination compliance framework. Both PR-prefix codes require specific documentation before patient billing.

When Billing the Patient Becomes a Compliance Violation

Billing a patient for PR-96 without valid ABN/notice creates compliance exposure. For Medicare patients specifically, this can constitute a Medicare billing violation under the provider participation agreement. For commercial patients, it triggers patient complaints, payer audits, and potential contractual breaches.

Practices that systematically bill PR-96 without ABN verification create OIG audit exposure. The False Claims Act exposure is real. Improper patient billing of non-covered services has been an OIG enforcement focus. Here’s the operational rule: if no ABN/notice exists, the PR-96 amount is a write-off regardless of what the group code says.

Is pr 96 patient responsibility? Yes , but only conditionally, and only when the compliance framework is in place before the service is rendered.—

How to Resolve a PR-96 Denial: The 4-Path Decision Tree

Before you touch the resolution workflow, ask one question: did the payer apply PR-96 because the service is actually non-covered with valid pre-service notice on file, or because something upstream broke down? The first scenario goes to Path B. The second routes through Paths A, C, or D.

Reading the Code Trio (Group Code + CARC + RARC) at this stage saves your team 30 or more minutes per claim downstream. That single triage step is your pr 96 denial code resolution starting point.

Path A: Write Off (Provider Absorbs)

Write off when:

• The denial came in as PR-96 but no ABN or pre-service notice was obtained
• The patient is Medicaid-enrolled and federal balance billing prohibitions apply
• The payer contract explicitly prohibits patient billing for non-covered services
• The denial should have been CO-96 and the PR group code was payer error

Path A operational rule: if you can’t produce a signed pre-service notice and the patient isn’t Medicaid-eligible, billing the patient creates compliance exposure. The PR-96 amount becomes a provider write-off regardless of what the group code says.

Sometimes what looks like PR-96 traces back to incomplete claim information that should have triggered CO-16 denial code routing. Verify the Code Trio before writing off.

Path B: Bill the Patient (PR-96 Legitimately Patient Billable)

Bill the patient when:

• The denial is confirmed PR-96 with valid pre-service notice (ABN for Medicare, equivalent waiver for commercial)
• Statutory exclusion applies and GY modifier was correctly used
• The patient was informed in advance and signed acknowledgment of financial responsibility
• The PR-96 amount represents a benefit exclusion the patient acknowledged before service

Path B operational rule: pull the signed ABN or financial responsibility form. Confirm the form names the specific service and date. Confirm the patient signed before the service was rendered. Issue the patient statement with clear language explaining the non-covered service and the prior notice. This is the pr 96 denial code reimbursement path when the compliance framework is intact.

Path C: Appeal (Payer Determination Is Wrong)

Appeal when the payer’s PR-96 determination is factually incorrect. Most PR-96 denials don’t warrant appeal. They resolve through Path A (write off) or Path B (bill patient). Appeal only when you have evidence the payer’s coverage interpretation is wrong.

Appeal triggers: the service should be covered under the patient’s specific plan terms; the denial was issued in error (wrong plan code, incorrect eligibility lookup); a prior authorization was obtained but wasn’t linked to the claim correctly; plan benefits or coverage policy supports payment.

Appeal timing: most payers allow 30 to 180 days from denial date. Medicare: 120 days for Redetermination, 180 days for Reconsideration. 2026 ALJ threshold: $200 per Federal Register CY 2026 AIC Adjustment. Tracking PR-96 appeal windows alongside the CO-29 timely filing framework keeps recoverable revenue from aging out.

Path D: Refund (Miscategorization Discovered Post-Billing)

Path D applies when your team has already collected a PR-96 amount from the patient and subsequent review reveals the collection was improper. This happens when ABN compliance was assumed but later discovered to be invalid, when the denial should have been CO-96, or when state Medicaid balance billing rules prohibit the collection.

Process refund to the patient with documentation of the corrected categorization. Notify the payer of the corrected classification if it affects future adjudication. Document the audit trail to protect against OIG and state regulatory exposure. Update front-end workflow to prevent recurrence.

Practices that systematically catch miscategorized PR-96 patient billings need denial management services that audit pre-statement before patient charges go out.

Decision Matrix Reference Table

The 10 Real Causes of PR-96 Denials

Most PR-96 cause lists conflate operational triggers with root causes. The 10 causes below split into three categories: benefit-design exclusions, eligibility and coverage gaps, and coding and documentation failures. Some causes look identical on the remit but require completely different fixes. The RARC tells you which cause applies.

That’s why you should never work pr 96 denial code reason from the CARC alone.

Cause 1: Benefit Plan Exclusion

The plan simply doesn’t cover the service. Cosmetic procedures, experimental treatments, alternative therapies, certain DME items, and specific behavioral health services land here regularly. RARC N425 or N130 typically accompanies. No coding correction will resolve it because the service itself is what’s excluded, not how it was billed.

Cause 2: Statutory Exclusion (Medicare-Specific)

Items or services excluded by federal law under §1862(a)(1)(A). Cosmetic surgery, routine dental, hearing aids, eyeglasses without cataract surgery context. RARC N425 typically accompanies. GY modifier pathway applies. Patient billing is legitimate with NEMB documentation.

Cause 3: 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 most commonly affected. The RARC will reference authorization specifically, commonly N115 or payer-specific auth language. Front-end prior authorization tracking eliminates this cause entirely.

Cause 4: Out-of-Network Provider Without Notice

Patient used an out-of-network provider without knowing the plan doesn’t include out-of-network benefits. The service itself may be valid. The coverage isn’t there. Common pattern with Medicare Advantage plans, HMO plans, and narrow-network commercial plans.

Cause 5: Frequency Limitations Exceeded

Patient already hit the annual limit for a service. Second or third occurrence flagged as non-covered. Common with chiropractic visits, physical therapy sessions, certain labs, and behavioral health sessions. The plan covers the service, but not at this frequency for this patient.

Cause 6: Plan Type Mismatch (HMO/PPO/EPO/HDHP)

Front desk verified eligibility but didn’t confirm plan type. HMO plans are stricter about referral and prior auth than PPO plans. EPO plans don’t cover out-of-network at all. HDHP plans have higher patient cost-sharing. PR-96 surfaces when the workflow assumed PPO behavior on an HMO claim.

Cause 7: Coverage Lapsed or Plan Changed Mid-Year

Patient’s insurance lapsed or rolled into a new plan with different benefits between visits. Treatment-course assumptions about coverage create exposure. Real-time eligibility checks on date of service catch this. Registration-only checks miss it. The eligibility verification process at the date-of-service level catches mid-year coverage changes that registration-only checks miss.

Cause 8: Incorrect CPT/ICD-10 Combination

Diagnosis (ICD-10) and procedure (CPT) codes must align to demonstrate medical necessity. Mismatch triggers automatic PR-96 routing on services that should have been covered. Coding review at scrub stage catches this before submission.

Cause 9: Bundling Errors That Got Reclassified

NCCI PTP bundling errors sometimes route as PR-96 instead of CO-97 when the secondary code gets categorized as plan-excluded rather than bundled. The fix is usually code restructuring with appropriate modifiers. Practices with high CO-97 bundling denials volume often see corresponding PR-96 spikes when the secondary procedure gets reclassified as non-covered rather than bundled.

Cause 10: Authorization Requirements Changed Without Notification

Authorization requirements update mid-year, and changes don’t come with provider notification. A service that didn’t need auth in 2024 may require it in 2026 under updated payer policy. The first indication is often a PR-96 denial. Medical necessity determination changes cascade across multiple denial codes. Our CO-50 medical necessity guide covers the LCD-driven side of this same dynamic.

Specialty-Specific PR-96 Patterns: Where Non-Covered Denials Hit Hardest

PR-96 isn’t distributed evenly across specialties. Eight specialties account for the majority of non-covered charge volume, and each has its own operational trigger pattern, typical RARC pairing, and resolution path.

Behavioral Health

Behavioral health plans frequently have separate benefit structures from medical benefits. Session limits (typically 20 to 50 outpatient sessions per year), provider type restrictions (LCSW vs LMFT vs psychologist), and prior auth thresholds for ongoing therapy cause PR-96 more than in most other specialties.

Aetna, Cigna, and BCBS commercial plans show particular variation here. The RARC commonly references benefit limits or prior auth. Pull the specific session count and verify against the plan benefit summary.

Durable Medical Equipment (DME)

Non-covered HCPCS codes are common in DME billing. Many commercial plans exclude specific equipment categories outright. Medicare statutorily excludes certain comfort items (diapers, shower chairs) entirely. The DME-specific PR-96 pattern involves missing the wound modifier (A1, A2, A3, etc.) on surgical dressings.

Without the modifier, the claim denies as non-covered even when the wound type is policy-covered. The reopening process can add the modifier post-submission for Medicare DME claims.

Cardiology

Diagnostic services ordered as part of routine cardiac workup sometimes fall outside preventive coverage tiers and land in non-covered territory, particularly under high-deductible plans. Cardiac imaging codes have payer-specific frequency limitations. Stress testing, echocardiograms, and cardiac CT scans often require prior authorization that varies by payer.

PR-96 on cardiology claims frequently traces to either the frequency limit or the prior auth gap.

Dental and Oral Surgery

Medically necessary dental services billed to medical insurance face PR-96 frequently because coverage language is often ambiguous across medical and dental plan lines. Oral surgery procedures (extractions related to medical conditions, biopsy of oral lesions, treatment of jaw fractures) sit in the gray zone.

Resolution usually requires medical necessity documentation and explicit payer policy review. Many medical plans cover these services but require specific coding patterns and documentation.

Anesthesiology

When the surgeon is in-network but the anesthesiologist isn’t, the anesthesiology claim sometimes returns PR-96 due to out-of-network provisions. The No Surprises Act limits patient billing in this scenario for emergency and certain non-emergency situations. But the federal protections don’t eliminate PR-96 generation, just collection rights. Anesthesiology billing teams must check NSA applicability before any patient billing decision.

Chiropractic

Chiropractic services under Medicare are limited to spinal manipulation only. Other chiropractic services (massage, acupuncture, nutritional counseling) are statutorily excluded. PR-96 with GY modifier signals the statutory exclusion pathway. Commercial plans often cap chiropractic visits at 12 to 30 per year, after which subsequent visits return PR-96 for frequency limitation.

Track the patient’s used-visit count against the plan limit before each appointment.

Physical Therapy

PT services hit PR-96 most commonly through frequency limits and prior authorization gaps. Many commercial plans cover 20 to 30 PT visits per condition. Subsequent visits without re-authorization return non-covered. The Medicare KX modifier becomes relevant once therapy thresholds are exceeded. KX signals that documentation supports continued medical necessity.

Practices billing PT without tracking visit counts against plan limits accumulate PR-96 volume that’s largely preventable.

Ophthalmology

Routine vision exams are excluded from most medical plans (covered separately under vision benefits), and routine refraction is statutorily excluded from Medicare. PR-96 on ophthalmology claims often traces to billing routine vision services to medical insurance instead of vision benefits.

Diabetic retinal screenings sit in the covered category but require specific diagnosis pairing. Verify whether the visit was routine or diagnostic before claim submission. Specialty-specific PR-96 patterns are best handled by medical billing services that understand the payer-policy nuances unique to each specialty.

Payer-Specific PR-96 Patterns: Medicare, Medicaid, BCBS, and Commercial

PR-96 patterns vary significantly by payer. The operational rules, appeal windows, and compliance frameworks differ across Medicare, Medicaid, and commercial plans. Here’s how each major payer applies CARC 96 and what resolution looks like in practice.

Medicare PR-96: Statutory Exclusion + Overutilization + ABN Compliance

Per FCSO Medicare guidance dated February 16, 2026, PR-96 on Medicare claims is received when the service billed is statutorily excluded from coverage under Medicare. Payment cannot be made under Part A or Part B. The recommended path is the GY modifier (statutorily excluded or does not meet Medicare benefit definition) on the affected line item.

Medicare regions sometimes issue PR-96 for overutilization scenarios that historically were CO-57. Since PR group code transfers liability, secondary payer or patient billing becomes the path. Critical operational rule: confirm overutilization triggered the denial rather than coding error before transferring liability.

ABN documentation determines whether the PR-96 amount is collectible from the patient. See FCSO Medicare PR-96 statutory exclusion guidance for the full FCSO framework. Medicare 835s commonly carry both CO-253 Medicare adjudication adjustments and PR-96 in the same remittance.

Medicare Advantage PR-96: OIG Oversight Active in 2026

Medicare Advantage Organizations (MAOs) issue PR-96 denials at higher rates than Original Medicare, and OIG Report OEI-09-18-00260 (2022) found that MAOs reversed many denials on appeal, indicating systematic denial errors. MAO denials remain subject to ongoing OIG monitoring through 2026.

The practical implication: MAO PR-96 denials warrant closer scrutiny than commercial PR-96 denials. Appeal rates for MAO denials are higher because the underlying denial pattern is more error-prone. The 2026 CMS-0057-F transparency provisions (Section 13) directly affect how MAOs must communicate prior auth and coverage decisions. Document patterns of repeat denials by specific MAO for compliance escalation.

Medicaid PR-96: Federal Balance Billing Prohibitions

Medicaid operates as the payer of last resort under federal law, and balance billing Medicaid beneficiaries is prohibited under 42 C.F.R. § 447.15. PR-96 on Medicaid claims cannot transfer to patient billing in most circumstances. Path A (provider write-off) is the default.

State Medicaid programs vary in how they format CARC 96 on remittances, but the federal balance billing prohibition is uniform. Dual-eligible patients (Medicare + Medicaid) have additional protections. Resolution requires confirming the patient’s Medicaid enrollment status and applicable state-specific rules.

BCBS PR-96: BlueCard and Plan-Specific Variations

BCBS plans use the BlueCard program for inter-plan coordination, but PR-96 patterns vary significantly by Blue plan and state. Preventive services and behavioral health benefits show particular variation across BCBS entities. BlueCard PR-96 denials sometimes route through home plan vs host plan logic incorrectly. Verify the plan-specific COB sequencing.

Resolution: contact BCBS provider relations for plan-specific coverage policies before assuming PR-96 is correct.

UHC, Aetna, Cigna, Humana: Commercial Payer Patterns

UnitedHealthcare: PR-96 commonly involves prior auth gaps and out-of-network coverage. Provider portal updates faster than phone calls. Aetna: PR-96 frequently pairs with N130 RARC. Behavioral health and frequency limit denials are common. Cigna: PR-96 patterns concentrate around preventive service billing and specialty pharmacy. Plan-specific benefit summary is critical.

Humana: PR-96 with statutory exclusion language common on Medicare Advantage products. GY modifier pathway applies. Resolution path across all four: pull the patient’s specific benefit document, verify the exclusion language, and confirm pre-service notice if billing the patient.

Practices managing PR-96 across multiple commercial payers benefit from systematic revenue cycle management workflows that triage by payer-specific patterns.

CY 2026 Medicare Appeal Thresholds

For Calendar Year 2026 Medicare appeals filed on or after January 1, 2026, the Administrative Law Judge (ALJ) hearing threshold is $200 per the Federal Register CY 2026 AIC Adjustment, up from $190 in CY 2025. The Federal District Court threshold is $1,960, up from $1,900.

For PR-96 appeals where the disputed amount falls below $200, redetermination through the MAC (Level 1) and reconsideration through the QIC (Level 2) are the available paths before reaching the ALJ threshold. Aggregate small-dollar PR-96 disputes within the same payer to clear the threshold when appropriate.—

Companion RARCs That Appear with PR-96: The Code Trio Decoded

The RARC is what converts a generic PR-96 from “non-covered charges” into an actionable resolution path. Seven RARCs account for the majority of PR-96 pairings. Knowing each one tells you exactly what happened and what to do next.

N425: Statutorily Excluded Service(s)

RARC N425, “Statutorily excluded service(s),” is the most common companion RARC on Medicare PR-96 denials for services excluded by federal law. When you see PR-96 + n425, the Medicare program cannot cover the service under Part A or Part B regardless of medical necessity. GY modifier pathway applies. NEMB documentation supports patient transparency. Patient billing legitimate.

N130: Consult Plan Benefit Documents

RARC N130, “Consult plan benefit documents/guidelines for information about restrictions of this service,” appears most frequently on commercial payer PR-96 denials when the service is excluded by plan contract rather than federal statute.

Resolution requires pulling the patient’s specific Summary Plan Description or benefit document to verify the exclusion language and decide whether to appeal or proceed with patient billing. N130 is the RARC that points you to the benefit exclusion framework from Section 6.

M38 and M39: The ABN Compliance RARCs

M38 and M39 are the RARCs that specifically address ABN compliance outcomes, and most billing teams never see them documented. M38 means the patient is liable due to proper written notice (the ABN was valid). M39 means the patient is not liable because the notice didn’t comply (the ABN was invalid or improperly executed).

M39 is the audit signal. When M39 appears, the practice’s ABN process has compliance gaps. M38 confirms the ABN process worked correctly. Track M38 vs M39 frequency by patient registration team to identify training gaps. Tracking RARC patterns across denial codes follows the same framework documented in our CO-29 RARC framework guide.

N56: Procedure Code Not Correct/Valid

RARC N56, “Procedure code billed is not correct/valid for the services billed or the date of service billed,” appears when the PR-96 denial traces to a coding error rather than a benefit exclusion. Resolution: correct the CPT/HCPCS code or date of service logic and resubmit as a corrected claim.

This is a Path A to corrected resubmission scenario, not a write-off.

N115: Local Coverage Determination Decision

RARC N115, “This decision was based on a Local Coverage Determination (LCD),” appears on Medicare PR-96 denials where a MAC LCD determined the service didn’t meet medical necessity criteria. Pull the LCD, confirm the diagnosis and indications support coverage, and either correct and resubmit or appeal with medical necessity documentation.

Our CO-50 with N115 guide covers the LCD-based denial framework at depth. The same RARC framework applies to PR-96 + N115 patterns.

N431: Not Covered with This Procedure

RARC N431, “Not covered with this procedure,” typically signals a code combination rule, including bundling, add-on, or combo edits. Validate code pairing rules against NCCI. Rebill with the correct primary/add-on structure or remove the invalid line.

M51 and MA130: Documentation Issues

M51 means “Missing/incomplete/invalid procedure code.” Correct the code element and resubmit. MA130 means “Your claim contains incomplete and/or invalid information.” Review all flagged fields per the payer’s specific clarification and resubmit. Both signal data integrity issues, not coverage exclusions. Path A (write off) doesn’t apply. Correct and resubmit.

How to Prevent PR-96 Denials + The 2026 Compliance Calendar

PR-96 is largely preventable. Most denials trace to front-end failures that a systematic verification protocol would catch before any claim goes out. Three 2026 compliance updates make this prevention work more urgent than it was in 2025.

Front-End Prevention: The 6-Point Verification Protocol

Run this protocol on every patient encounter, not just new patients:

Our PR-27 patient responsibility guide is the canonical PR-prefix authority piece on the site.

For the parallel CO-45 fee schedule framework that applies the same group code logic to a different reason code, see our complete guide.

Practices with systematic insurance eligibility verification protocols catch PR-96 triggers before claims go out.

ABN Intake Workflow Standards

ABN must be signed before the service is rendered. Post-service signatures are void. Form CMS-R-131 must specify the service, the estimated cost, and the reason Medicare may not pay. Voluntary ABN/NEMB is recommended for statutorily excluded services for patient transparency. Audit ABN execution quarterly to identify training gaps in registration teams.

CAQH CORE v3.10.0: May 1, 2026 Deadline

CAQH CORE published updated Code Combinations in February 2026, version 3.10.0, with a payer compliance deadline of May 1, 2026. This update affects how payers must communicate CARC and RARC combinations in the 835 transaction, including PR-96 pairings.

Mapping logic that worked correctly in 2025 may route denials incorrectly after May 1, 2026. Verify your practice management system and clearinghouse have updated ERA mapping to reflect the new CAQH CORE v3.10.0 combinations. Our CO-96 CAQH CORE v3.10.0 framework guide covers the same v3.10.0 update from the contractual write-off side.

The v3.10.0 changes apply identically to both PR-96 and CO-96 pairings.

CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F)

The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) requires impacted payers, including Medicare Advantage, Medicaid, CHIP, and federally facilitated marketplace QHPs, to implement operational PA transparency provisions by January 1, 2026 and the FHIR Prior Authorization API by January 1, 2027. See the CMS Interoperability and Prior Authorization Final Rule for full implementation timelines.

The 2026 PA transparency provisions improve coverage data flow between providers and payers, which should reduce PR-96 incidence over time. Through 2026, prior auth gaps remain a primary PR-96 driver.

WISeR Prior Authorization Model

Under the WISeR Prior Authorization Model (effective July 1, 2025), CMS finalized PA requirements for select services under the Wasteful and Inappropriate Services Reduction model. This affects which services may generate PR-96 denials due to missing or unverified prior authorization. Track WISeR-affected services in your prior auth workflow.

Run quarterly reviews of the WISeR-applicable code list against your specialty’s billing patterns. PR-96 prevention is one piece of the broader 2026-2027 compliance calendar. The ICD-11 transition covers another major piece practices need on their radar.

Related Codes and the “96” Disambiguation

Not every “96” search in medical billing refers to CARC 96. Multiple code systems use the number 96 for unrelated purposes. Here’s the quick reference that prevents routing errors.

Related CARC Cluster

Our complete CO-96 (the sister code) guide covers the contractual write-off framework that mirrors PR-96’s patient billing framework.

PR-97 vs CO-97: Bundling Adjacent Codes

CARC 97: “The benefit for this service is included in the payment/allowance for another service/procedure that has already been adjudicated.” PR-97 (rare) vs CO-97 (common) , most “97” denials are CO-97 because bundling is a contractual issue, not patient liability.

Resolution differs entirely from PR-96: bundling fixes (modifier review, code restructuring) rather than coverage analysis. Our CO-97 bundling guide covers the bundling resolution framework that’s distinct from PR-96 coverage analysis.

Modifier 96: A Different Code Entirely

CPT Modifier 96 = “Behavioral Health Treatment, Services and Supplies.” Appended to behavioral health procedure codes, not a denial code. Some search engines bundle Modifier 96 with CARC 96 due to numerical similarity. They have nothing operationally in common.

ICD-10 Z96: Not a Denial Code

Z96 = “Presence of other functional implants” in ICD-10-CM. A diagnosis code, not a denial code. Appears in search bundles due to “96” pattern matching but is entirely unrelated to PR-96.

The PR-Prefix Cluster

PR-1: Deductible amount. PR-2: Coinsurance amount. PR-3: Copay amount. PR-21: This service may be covered under premium payment. PR-27: Expenses incurred after coverage terminated. PR-200: This service may be covered under another insurance plan. All share the PR group code (patient responsibility) but represent different reasons for patient liability. Same compliance framework: documented pre-service notice required for billing.

Our PR-27 patient responsibility guide is the canonical PR-prefix authority piece on the site. For the parallel CO-45 fee schedule framework that applies the same group code logic to a different reason code, see our complete guide.

Frequently Asked Questions: PR-96 Denial Code

What does the PR-96 denial code mean?

The PR-96 denial code combines Group Code PR (Patient Responsibility) and Claim Adjustment Reason Code 96, which X12 defines as “Non-covered charge(s).” The PR group code shifts financial responsibility to the patient, but only when valid pre-service notice (an ABN for Medicare or equivalent waiver for commercial) has been documented. Without notice, billing the patient creates compliance risk.

What is the difference between PR-96 and CO-96?

Both share Reason Code 96 (Non-covered charges) but differ by Group Code. PR-96 (Patient Responsibility) shifts the balance to the patient when valid pre-service notice exists. CO-96 (Contractual Obligation) requires provider write-off and prohibits patient billing. Billing a patient for CO-96 creates a contract violation for commercial payers and a compliance violation for Medicare.

Can I bill the patient for PR-96 without an ABN?

No, not for Medicare patients. CMS requires a properly executed ABN (Form CMS-R-131) signed before the service to legally collect a non-covered amount from a Medicare beneficiary. Without it, the PR-96 amount becomes a provider write-off regardless of the PR group code. Commercial patients require equivalent pre-service waivers.

When is the GY modifier used with PR-96?

The GY modifier is appended when billing a service that’s statutorily excluded from Medicare, meaning the service isn’t a Medicare benefit by federal law. GY signals “Item or Service Statutorily Excluded or Does Not Meet the Definition of Any Medicare Benefit.” The patient is liable for these services, with NEMB documentation recommended for transparency.

What is N425 RARC and how does it relate to PR-96?

RARC N425, “Statutorily excluded service(s),” is the most common companion RARC on Medicare PR-96 denials for services excluded by federal law. When you see PR-96 + N425, the GY modifier pathway applies, and the patient is legitimately billable with proper documentation.

Is PR-96 always patient responsibility?

Conceptually yes: the PR group code signals patient responsibility. Operationally no: the patient is only billable when valid pre-service notice (ABN for Medicare, equivalent waiver for commercial) is documented. Without proper notice, the PR-96 amount becomes a provider write-off despite the PR group code.

What is a 96 non-covered denial?

A 96 non-covered denial is any CARC 96 denial, the X12 Claim Adjustment Reason Code for “Non-covered charge(s).” The Group Code prefix (PR/CO/PI/OA) determines who absorbs the cost. PR-96 routes to the patient; CO-96 routes to provider write-off; PI-96 and OA-96 follow payer-policy or coordination logic.

How long do I have to appeal a PR-96 denial?

Appeal timelines vary by payer. Medicare appeals must be filed within 120 days for Redetermination (Level 1) and 180 days for Reconsideration (Level 2). Commercial payers typically allow 30 to 180 days. The CY 2026 ALJ threshold is $200. File as early as possible rather than waiting for the deadline.

What is modifier 96 used for?

CPT Modifier 96 is “Behavioral Health Treatment, Services and Supplies,” appended to behavioral health procedure codes. It’s completely unrelated to CARC 96. Modifier 96 is a CPT modifier on the claim before submission. CARC 96 appears on the remittance after claim processing.

What does code 96 mean in medical billing?

In medical billing, “code 96” most commonly refers to Claim Adjustment Reason Code 96 (CARC 96) meaning “Non-covered charge(s).” It’s part of the X12 standard used in the 835 ERA. The Group Code prefix (PR-96, CO-96, PI-96, or OA-96) determines who is financially responsible for the adjusted amount.