What Is the PR-95 Denial Code?

Updated June 2026. CARC 95 is the standardized X12 code payers use to communicate a single message: 'Plan procedures not followed.' The service may have been medically necessary, correctly coded, and well documented — but a required administrative step in the plan's coverage workflow was missed before the claim adjudicated, so the payer is refusing payment as billed.

The word that matters most on a 95 denial is the group code printed in front of it on the 835 ERA or the EOB:

• PR-95 (Patient Responsibility). The payer is saying the member failed to follow a plan rule they were obligated to follow — most commonly going out-of-network without authorization, or not obtaining a required primary-care referral — and is assigning the unpaid balance to the patient. A PR group code is the payer's signal that you may bill the patient for this amount.
• CO-95 (Contractual Obligation). The payer is saying the provider failed to follow a plan rule under the participation contract — most commonly not obtaining prior authorization for a service the provider was responsible for authorizing. A CO group code is a provider write-off that cannot be billed to the patient.

The same reason code (95) can land as either PR or CO depending on whose responsibility the missed step was. This is the single most important distinction on a 95 denial, because it determines who absorbs the cost. In our denial audits we typically see practices treat every 95 as a write-off out of habit, surrendering real, billable PR balances — and, just as often, balance-billing patients on CO-95 denials that were the practice's own authorization failure, which is a contract violation.

CARC 95 almost never travels alone. It is usually paired with a Remittance Advice Remark Code (RARC) that names the specific procedure that was missed. See the RARC decoder table below to translate the remark and route the denial correctly. For the broader code family, our full CARC denial codes list maps the relationship between 95 and adjacent reason codes.

Five operational gaps produce the overwhelming majority of CARC 95 denials. Knowing which one fired tells you immediately whether the denial is appealable and who owns the balance.

1. Missing PCP referral (HMO / POS plans). The plan required a referral from the member's primary care physician before a specialist visit or procedure, and no referral was on file at the date of service. This is the classic PR-95 scenario on HMO plans — the member was responsible for securing the referral, so the balance flows to patient responsibility. Common on pediatrics, dermatology, cardiology, and any specialist receiving HMO/POS referrals.
2. No prior authorization obtained. The service required pre-authorization and none was secured before delivery. Whether this lands as PR or CO depends on whose duty it was: if the provider contract makes the rendering provider responsible for obtaining auth, it denies CO-95 (write-off); if the member chose a service or provider outside the authorized pathway, it can deny PR-95. Note that a pure 'auth absent' denial frequently arrives as CO-197 rather than 95 — the two overlap and need to be distinguished (see the comparison table below).
3. Out-of-network without approval. The member saw an out-of-network provider on a plan that required in-network use or pre-approval for OON care. On HMO and many POS/EPO plans, OON care without authorization is a member-responsibility failure — it denies PR-95, and the balance is generally the patient's. (The No Surprises Act limits balance billing for certain emergency and ancillary OON situations; verify before billing the patient.)
4. Step therapy / 'fail first' protocol skipped. The plan required the patient to try and fail a preferred, lower-cost treatment before covering the requested one, and that step was bypassed. Common in pain management, rheumatology, gastroenterology, and any drug-or-procedure pathway governed by a step-therapy policy.
5. Notification / pre-cert timeframe missed. Some plans require notification within a set window (for example, inpatient admission notification within 24–48 hours, or maternity pre-registration by a certain week). Missing the notification window even when the service was otherwise covered triggers a 95 denial citing the procedural lapse.

The practical takeaway: read the RARC paired with the 95 and the group code together. The RARC tells you which procedure was missed; the group code tells you who owes the balance.

Work a 95 denial in this order. The early steps frequently overturn the denial entirely and keep the balance off the patient.

1. Confirm the group code and read the RARC. PR-95 vs CO-95 changes everything downstream. Pull the RARC (N640, N210, N130, N428, etc.) to identify the exact rule the payer says was missed before you do anything else.
2. Verify whether the rule was actually met. Pull the referral, authorization, or eligibility record for the date of service. A large share of 95 denials are payer error — the auth existed but wasn't linked to the claim, the referral was on file under a different member ID, or the auth number was transposed. If the requirement was met, this is an appeal with proof attached, not a retro-auth.
3. Submit a corrected claim with the authorization/referral number. When a valid auth or referral exists but never made it onto the original claim, resubmit a corrected claim (not a new claim — that risks a duplicate CARC 18 denial) with the auth number in the correct loop/segment (2300 REF for the prior-auth number on the 837). This resolves a meaningful share of 95 denials with no appeal needed.
4. Request retroactive (retro) authorization. When no auth was obtained but the service was clearly medically necessary, request a retro-auth from the payer. Most payers allow retro-auth only within a short window (commonly 24–72 hours to a few business days post-service, but it varies by payer — verify your contract) and only for limited reasons (urgent/emergent care, retroactive member eligibility, provider unaware of a new auth requirement). A granted retro-auth lets you resubmit and get paid. Document the clinical urgency in the request.
5. Appeal with a medical-necessity and good-cause argument. If retro-auth is denied or unavailable, file a formal appeal arguing (a) the service was medically necessary, (b) good cause existed for the procedural lapse (emergent presentation, member misrepresented coverage, retroactive eligibility), and (c) any applicable state prompt-pay or continuity-of-care protection. Attach the clinical documentation and the eligibility record.
6. Route the balance correctly only after the above. If the denial stands and the group code is genuinely PR, the balance may be billed to the patient — but only after confirming it is not a No Surprises Act protected situation and only with proper patient notification. If the group code is CO, write it off and feed the root cause back into your front-end authorization workflow so it does not recur.

Prevention beats appeal here: a clean front-end eligibility and authorization process eliminates most 95 denials before the claim is ever submitted. Our prior authorization process guide walks the end-to-end workflow that prevents the no-auth version of this denial.

Three reason codes cluster around the same family of problems — referrals, authorizations, and pre-certs — and worklist teams routinely confuse them. They have different root causes, different group codes, and different fixes. Use this table to route each correctly.

The fastest way to tell them apart: CO-197 means no authorization existed. CO-15 means an authorization existed but is wrong or missing from the claim. PR-95 means a plan rule was not followed and, when the group code is PR, the patient is on the hook. If your EOB shows 95 with a PR group code, do not lump it in with your CO-197 auth-absent write-offs — it is a different denial with a billable balance. For the auth-absent variant, see our companion CO-197 breakdown; for the deeper code relationships, the CARC denial codes list is the master reference.

CARC 95 is a category-level code — it tells you a plan procedure was missed but not which one. The paired Remittance Advice Remark Code (RARC) narrows it down. Decode the RARC first; it determines whether you chase a referral, an authorization, or a network exception.

If the RARC points to a referral or authorization that does exist, the denial is a payer linkage error — fix it with a corrected claim carrying the correct reference number. If the RARC confirms the rule was genuinely not met, move to the retro-auth and appeal path. Always reconcile the RARC against your front-end auth/eligibility record before deciding the denial is final.

How a 95 denial behaves — and whether the patient can be billed — varies sharply by payer type.

Commercial (HMO / POS / EPO). This is where PR-95 lives. HMO referral rules and EPO/POS network requirements are member obligations on most plans, so OON-without-approval and missing-referral denials commonly land as PR-95 with a billable balance. Step-therapy denials are common on commercial drug and procedure pathways. Always confirm the specific plan's referral and network rules at eligibility verification — they differ by product within the same carrier.

Medicare Advantage (Part C). MA plans impose their own prior-auth and network rules and issue 95-family denials when those are skipped. MA retro-auth and appeal rights are governed by CMS rules; members have strong organization-determination and reconsideration appeal rights, and continuity-of-care protections may apply. Out-of-network MA denials are not automatically patient-billable — check the plan's OON benefit and any emergency/urgent exceptions before assigning PR.

Traditional Medicare (Part A/B). Fee-for-service Medicare generally does not require referrals and has limited prior-auth requirements (select services/DME), so true 95 'plan procedures not followed' denials are less common than on managed care. When they do appear, they usually relate to a specific notification or documentation requirement; an ABN may be needed before the patient can be billed for a non-covered service.

Medicaid and Medicaid MCOs. Medicaid fee-for-service and managed-care plans require referrals and prior authorizations for many services, and skipping them triggers 95 denials. Critically, in most states Medicaid members cannot be balance-billed for covered services even when a plan procedure was missed — the loss typically falls on the provider, not the patient. Treat Medicaid 95 denials as a front-end authorization problem to prevent, not a patient balance to pursue, unless your state's rules and the plan contract clearly allow otherwise.

The universal rule across payers: a PR group code is necessary but not sufficient to bill the patient. Confirm the payer type, the No Surprises Act status, and any Medicaid balance-billing prohibition before sending a statement.

A 95 denial worklist overlaps with several neighboring codes. Knowing which signal the same root cause (referral/auth/network) versus a different problem speeds the work-down.

The operational discipline: tag every 95 by group code (PR vs CO) and by RARC at intake, then route referral/network failures to the patient-statement path (only when PR and NSA-clear) and authorization failures to the retro-auth-and-appeal path. Codes like CO-50 and CO-96 belong in a separate medical-necessity worklist — do not let them dilute your authorization queue. For the full reason-code map, keep the CARC denial codes list open, and route the prevention work through structured denial management services.

When the rule was met (or good cause existed for the lapse) and the payer denied 95 anyway, a tight appeal overturns a large share of these denials. Adapt the paragraph below, attach the proof, and submit as a corrected claim or formal appeal per the payer's process.

> Re: Appeal of Denial — CARC 95 (Plan Procedures Not Followed) > Member: [Name] | ID: [Member ID] | Claim #: [Claim Number] | DOS: [Date of Service] > > We are appealing the denial of claim [Claim Number], denied under CARC 95 ("Plan procedures not followed") with remark code [RARC]. The required plan procedure was satisfied for this date of service. [Choose: A valid referral (#[Referral Number]) from the member's PCP [PCP Name] was on file prior to the service / Prior authorization #[Auth Number] was approved on [date] for the billed services / The service was rendered as an emergent/urgent presentation qualifying for the plan's retroactive-authorization and good-cause exception.] Supporting documentation is attached: [referral/authorization record, eligibility verification for the DOS, clinical note establishing medical necessity and urgency]. We respectfully request reprocessing and payment of this claim under the member's benefits. Please contact our office at [phone] with any questions.

What makes a 95 appeal succeed: attach the primary-source proof — the referral or auth record, the eligibility screenshot for the exact date of service, and, when arguing good cause, a clinical note documenting why the procedural step could not be completed in advance (emergent care, retroactive eligibility, member-supplied coverage error). A 95 appeal without attached proof of the rule being met — or good cause for the lapse — will not reverse. When the requirement genuinely was not met and no good-cause exception applies, do not appeal; correct the front-end process and, if the group code is PR and the situation is NSA-clear, route the balance to the patient. If your team lacks the bandwidth to run referral verification, retro-auth, and appeals at volume, our prior authorization services and denial management services own this workflow end to end.