What Is the PR-95 Denial Code?

Code text and status verified 17 September 2026. CARC 95 is the standardized X12 code payers use to communicate a single message: a required step in the plan's coverage process was not followed. The service may have been medically necessary, correctly coded, and well documented — but a required administrative step was missed before the claim adjudicated, so the payer is refusing payment as billed. The official description is published by X12 in External Code List 139 at x12.org; the wording on this page is ours.

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. X12 publishes exactly four — CO, OA, PI and PR — and publishes their labels only, not any rule about what a provider may collect:

• PR-95 (Patient Responsibility). The payer has assigned the unpaid amount to the member, on the basis that the member failed a plan rule they were obligated to follow — most commonly going out-of-network without authorization, or not obtaining a required primary-care referral. It is the payer's allocation, and it is the precondition for billing the patient, but it is not the whole test.
• CO-95 (Contractual Obligation). The payer has assigned the amount to the provider under the participation contract — most commonly where the provider was responsible for obtaining prior authorization and did not. 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 — and both directions of the mistake are expensive. Writing off a PR balance by habit surrenders money the payer has explicitly allocated to the member; billing a patient for a CO-95 that was your own authorization failure is a contract violation.

CARC 95 is usually accompanied by a Remittance Advice Remark Code (RARC) that names the specific step 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 account for the recurring 95 denials on most worklists. 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. On plans that place the referral duty on the member this denies as PR-95 and the amount flows to the member — but the duty is set by the plan product, not by the code, so read the plan's own referral rule rather than assuming. 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 treated as a member-responsibility failure and denies PR-95. (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 — inpatient admission notification and maternity pre-registration are the usual examples. The windows are set plan by plan, so take the number from the plan's own document rather than from a general rule; missing the 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 step was missed; the group code tells you which side of the contract the payer has assigned the amount to.

A 95 denial splits into two cases, and almost all wasted effort comes from working the wrong one. Answer the branch question first: was the required step actually met?

Branch A — the rule WAS met. This is an appeal or a corrected claim, never a retro-auth request. Evidence required, in order of weight:

• the referral record for the date of service, showing the referring PCP, the referral number, the referred-to provider or specialty, the authorized visit count and the valid-from/valid-to dates;
• the authorization record, showing the auth number, the approved CPT/HCPCS codes, the approved units or visits, the rendering provider and facility, and the approved date range;
• the eligibility record for the exact date of service, showing the plan product and its referral/network rule;
• the 837 as transmitted, showing where the reference number was carried.

If the auth or referral exists and simply never reached the claim, resubmit a corrected claim — not a new claim, which risks a duplicate denial under CARC 18 — with the number in the correct segment (loop 2300 REF with qualifier G1 for the prior-authorization number on the 837 professional claim). If the auth exists and the claim carried it, the denial is a payer linkage error and the appeal argues exactly that, with the auth record and the transmitted claim attached side by side.

Branch B — the rule was NOT met. Now the question is whether an exception applies. Evidence required:

• for a retroactive authorization: the clinical note establishing urgency or emergent presentation, the eligibility record if the member's coverage was granted retroactively, and the date and reference of the utilization-management call;
• for a good-cause appeal: documentation of why the step could not be completed in advance — emergent presentation, retroactive eligibility, or coverage the member reported incorrectly at registration.

Retro-authorization windows and qualifying reasons are set by each payer and by your contract — they are short, they vary, and there is no industry-wide number worth quoting. Read the payer's utilization-management policy for the plan in question before promising a practice it can be recovered.

Then route the balance. If the denial stands and the group code is genuinely PR, the amount may become a patient balance — after confirming it is not a No Surprises Act protected situation, confirming the patient is not a Medicaid beneficiary (see the payer notes below), and giving 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: every trigger listed above is checkable before the visit. Our prior authorization process guide walks the end-to-end workflow that prevents the no-auth version of this denial, and recurring volume is what prior authorization services exist to absorb.

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. The descriptions below are ours; X12 publishes the official text at x12.org.

The fastest way to tell them apart: CO-197 means no authorization existed. CO-15 is retired — X12's published code list records reason code 15 with a stop date of 1 May 2018, so it must not appear on current remittance advice; if you are seeing it, you are reading a historical denial or a stale mapping table in your PM system or clearinghouse. Use CO-197 for authorization-absent denials. PR-95 means a plan rule was not followed, and when the group code is PR the payer has put the amount on the member. 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 potentially 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 step 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. The summaries below are ours; the official remark text is published with the code list at x12.org (checked 17 September 2026).

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 step 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. Step-therapy denials are common on commercial drug and procedure pathways. Confirm the specific plan's referral and network rules at eligibility verification — they differ by product within the same carrier, which is why a rule that held for one member of a carrier's book may not hold for the next.

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 organization-determination and reconsideration 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 prior-authorization requirements only for selected services and supplier types, so true 95 'plan step 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 beneficiary can be billed for a service Medicare does not cover.

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. The balance-billing restriction here is federal, not a state-by-state guess: under 42 CFR 447.15 a state plan must limit participation to providers who accept, as payment in full, the amounts paid by the Medicaid agency plus any deductible, coinsurance or copayment the plan requires the individual to pay (checked 17 September 2026). For an enrolled member and a covered service, that is what your participation turns on — so treat a Medicaid 95 denial as a front-end authorization problem to prevent, not a patient balance to pursue, and take any question about a service the program does not cover at all to your state's own rules and your provider agreement.

The universal rule across payers: a PR group code is necessary but not sufficient to bill the patient. Confirm the payer type, the plan product's own rule, the No Surprises Act status, and any Medicaid restriction 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 descriptions are ours; X12 publishes the official text at x12.org.

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 the contract, NSA and Medicaid checks are 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 step was met (or good cause existed for the lapse) and the payer denied 95 anyway, the appeal has to put the proof in front of the reviewer. Adapt the paragraph below, attach the evidence listed in Branch A above, and submit as a corrected claim or formal appeal per the payer's process.

> Re: Appeal of Denial — CARC 95 (required plan step reported as 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 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 a 95 appeal has to contain: the primary-source proof — the referral or auth record, the eligibility record for the exact date of service, and, when arguing good cause, a clinical note documenting why the step could not be completed in advance (emergent care, retroactive eligibility, coverage the member reported incorrectly). An appeal with neither proof of compliance nor a good-cause argument has nothing for the reviewer to act on. When the requirement genuinely was not met and no exception applies, do not appeal: correct the front-end process and, if the group code is PR and the contract, NSA and Medicaid checks are 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.