PR-27 Denial Code: What It Means and When You Can Actually Fight It
Seeing PR-27 on a remittance tends to end the conversation before it starts. Coverage ended before the service date, the patient owes it, move on. That’s true often enough that it’s become the default response, but it’s also wrong often enough that treating every PR-27 that way quietly costs practices real, recoverable revenue.
The honest version of this code has two tracks. Some PR-27 denials are exactly what they appear to be: the patient genuinely had no coverage on the date of service, and the balance is theirs. Others are the payer applying a termination date after the fact, sometimes months later, to a claim that was legitimate when the service was actually provided. Telling those two situations apart comes down to one specific piece of evidence, and most billing content barely mentions it.
What PR-27 Actually Means
PR-27 combines two X12 components. The group code, PR, stands for Patient Responsibility, meaning the payer has determined the financial liability for this charge legally falls on the patient rather than the provider or the payer. The reason code, CARC 27, is officially defined as “expenses incurred after coverage terminated.” Put together, the payer is stating that on the date of service, according to their records, the patient’s policy was no longer active.
That last phrase, according to their records, is the entire crux of this code. The payer’s eligibility file at the moment they adjudicate the claim is what generates PR-27. If that file is accurate and reflects the coverage status that actually existed on the date of service, the denial is legitimate. If that file has since been updated with a backdated termination that didn’t exist when the service happened, the denial is contestable.
When PR-27 Is Genuinely the Patient's Responsibility
Several everyday scenarios produce a legitimate PR-27, and these are worth recognizing quickly so effort goes where it matters.
Employment change. The patient lost job-based coverage and the new plan hadn’t started yet when the service occurred.
Non-payment of premium. The patient stopped paying premiums and the payer terminated coverage effective on or before the date of service, with no applicable grace period remaining.
Aging out of a parent’s plan. A dependent exceeded the age limit for coverage under a parent’s policy.
Plan switch during open enrollment. The patient moved to a new carrier, and the claim was submitted to the previous carrier for a date after the new plan’s effective date.
In these cases, verifying the termination date against the patient’s actual coverage history confirms the denial is correct, and the appropriate next step is a straightforward conversation with the patient about the balance, not an appeal.
When PR-27 Is Actually Reversible
This is the part that gets far too little attention across the field, and it’s where real revenue sits.
Retroactive termination
A payer sometimes discovers a coverage-ending event, non-payment, employer notification delay, plan exit, weeks or months after it happened, and then applies the termination date retroactively. If you delivered care and verified active coverage before the payer’s system reflected any problem, the claim was legitimate at the time of service even though it now shows PR-27. The date the payer discovered the issue is not the date the coverage question existed.
ACA marketplace grace periods
For Marketplace plans with Advance Premium Tax Credits, federal rules require a three-month grace period after a missed premium payment before coverage can terminate. During the first month of that window, the payer is required to pay claims normally. During months two and three, claims may be pended rather than paid outright, and the remark codes attached to a claim in this window (commonly referencing the grace period) tell you which stage applies. A PR-27 that ignores an active grace period is a payer processing error, not a legitimate denial.
Medicare Advantage disenrollment
This is a currently relevant driver worth knowing about specifically because of how many patients are affected by plan exits and disenrollments happening across the Medicare Advantage market right now. A beneficiary who enrolled in an MA plan is no longer covered under traditional Medicare for the same period, so a claim billed to original Medicare after an MA enrollment took effect returns as a coverage-timing denial. The fix isn’t an appeal, it’s identifying the correct current plan and rebilling the right payer. The reverse also happens: retroactive MA disenrollments can restore traditional Medicare eligibility for dates that were previously billed to the wrong plan.
Wrong plan or wrong member ID
Occasionally the patient had valid coverage the entire time, but the claim was routed to an expired member ID or the wrong plan within a family policy. The coverage exists. The claim just went to the wrong place.
The One Piece of Evidence That Decides the Outcome
Across every reversible scenario above, the deciding factor is the same: can you show what the patient’s eligibility status actually was on the date of service, not what it looks like today.
This means re-running an eligibility check is not enough by itself if you run it today and use that as your evidence. A same-day check tells you nothing about coverage status weeks or months ago. What actually supports an appeal is a timestamped record from the date of service itself: a saved 270/271 eligibility transaction log, a payer portal screenshot with a visible date and time, or a phone verification reference number logged at check-in.
Practices that save this documentation at every visit, not just when a problem is suspected, are the ones who can actually contest a retroactive termination months later. Practices that verify eligibility and then discard the record are stuck with no way to prove what they already confirmed.
CO-27: The Same Reason Code, Different Liability
CARC 27 can also appear with the CO group code instead of PR, and the difference matters as much as it does with the other paired codes in this series.
CO-27 means the same underlying issue, expenses incurred after coverage terminated, but the contractual obligation prefix means the provider absorbs the balance rather than the patient. This typically shows up when the provider’s own agreement with the payer, or a specific verification failure the provider was responsible for, prevents shifting the cost to the patient. A common trigger is submitting a claim well after a policy lapsed when the provider’s own eligibility verification process should have caught the issue before the service was rendered, particularly under payer contracts that place that verification burden on the provider.
Practically: if your team verified eligibility properly and documented it, and the payer later applies a retroactive term date anyway, PR-27 with an appeal is the likely path. If the verification step was skipped entirely and the claim went out on outdated information the provider should have caught, CO-27 is more likely, and the responsibility sits with the practice’s own process rather than the patient.
How to Work a PR-27 Denial
1. Pull the date of service, not today’s date, and check it against the patient’s coverage history.This single step resolves the legitimate cases immediately.
2. Look for retroactive termination signals.A gap between when the termination was applied and when the service occurred is the flag to watch for.
3. Retrieve your eligibility documentation from the date of service.This is the appeal, or the confirmation there isn’t one.
4. Check for Medicare Advantage enrollment activity if the patient is Medicare-eligible and the denial timing lines up with open enrollment or disenrollment periods.
5. Verify demographic and plan routing details before assuming the denial reflects an actual coverage gap. A wrong member ID or misrouted family plan claim looks identical to a real termination until you check.
6. If the denial is legitimate, communicate with the patient promptly rather than letting the balance age silently. Surprise bills months later collect far worse than a prompt, clear conversation.
7. If retroactive termination applies, file the appeal with the timestamped eligibility record attached, not a same-day re-verification.
What a Retroactive Termination Appeal Actually Needs
Winning a retroactive termination appeal is less about persuasive writing and more about assembling the right documents in the right order. Payers process these appeals against a specific standard: was coverage active according to information available at the time of service, regardless of what the file shows now.
The appeal should include the original claim details, the specific dates in question, and the eligibility documentation from the date of service itself. If that documentation is a saved 270/271 response, include the transaction timestamp and the response confirming active coverage, not just a summary of what it said. If it’s a portal screenshot, the visible date and time stamp matter as much as the coverage status shown. A phone verification is the weakest form of evidence unless it was logged with a reference number and the name of the representative at the time, which is exactly why building that habit into check-in scripts pays off later.
State plainly in the appeal that the retroactive termination date postdates the service, and that coverage was confirmed active through the payer’s own system at the time care was provided. Payers see enough of these to have an internal process for handling them, and a clean, evidence-first submission moves faster than one built around explaining the situation in narrative form without the underlying proof attached.
Timing matters too. Most payers have an appeal filing window measured from the denial date, not the date of service, so a retroactive termination discovered months after the fact can still be appealable if the appeal itself goes in promptly once the denial appears.
Payer-Specific Patterns Worth Knowing
PR-27 behaves somewhat differently depending on the payer type, and knowing the pattern for your specific payer mix saves time.
Commercial payers generally follow employer group reporting timelines, which means retroactive terminations tend to cluster around open enrollment periods and mid-year employment changes. Claims submitted in the weeks immediately following either event carry a higher chance of hitting a retroactive term date that hadn’t been reported yet at the time of service.
Medicaid programs vary significantly by state in how they handle retroactive eligibility changes, and some states have rules protecting providers who verified eligibility in good faith even when a beneficiary’s status later changes. Checking your specific state’s provider manual on this point is worth the time for any practice with meaningful Medicaid volume.
Medicare Advantage plans see PR-27 activity concentrated around enrollment period boundaries, and disenrollment activity in a given plan year can be tracked at a portfolio level. A practice noticing a rising pattern of MA-related PR-27 denials from one specific plan may be looking at that plan’s broader market exit rather than an isolated patient issue, which changes how the front desk should be screening Medicare patients at check-in going forward.
Preventing PR-27 Before It Happens
Real-time eligibility verification at check-in, not the day before or the week before, catches the majority of preventable PR-27 situations, since it reflects the payer’s records as close to the actual date of service as possible. For a fuller explanation of how that verification process works, see our guide to insurance eligibility verification. The habit worth building on top of that process is saving the confirmation, not just checking it, so that if a payer applies a retroactive change later, the practice isn’t left with no way to demonstrate what was true at the time.
What does PR-27 denial code mean?
It means the payer's records show the patient's coverage had terminated before the date of service, and the PR group code assigns the resulting balance to the patient rather than the provider.
Is PR-27 always the patient's responsibility?
Not always. If the termination was applied retroactively after the service was performed and coverage was verified as active at the time, the denial can often be appealed successfully with proof of eligibility on the actual date of service.
What's the difference between PR-27 and CO-27?
Same underlying reason code, different liability. PR-27 shifts the balance to the patient. CO-27 means the provider absorbs it, typically when a verification failure the provider was responsible for is involved rather than a genuine, undetectable coverage gap.
What is retroactive coverage termination?
It's when a payer discovers a coverage-ending event, such as non-payment or an employer notification delay, after the fact and applies a termination date to a period that had already passed, sometimes affecting claims for services performed while coverage still appeared active.
How do I prove a PR-27 denial should be reversed?
With a timestamped eligibility record from the actual date of service, such as a saved 270/271 transaction log or a dated payer portal screenshot. A same-day re-verification does not prove what coverage status was in the past.
What is the ACA grace period and how does it affect PR-27?
Marketplace plans with premium tax credits are required to provide a three-month grace period after a missed payment before coverage terminates. Claims during the first month must be paid normally, and a PR-27 issued during an active grace period may reflect a payer processing error rather than a legitimate denial.
How does Medicare Advantage disenrollment cause PR-27 denials?
A beneficiary enrolled in a Medicare Advantage plan is not covered under original Medicare for the same period. Claims billed to original Medicare after MA enrollment took effect return as a coverage-timing denial, and the fix is identifying the correct current plan and rebilling it.
What is PR-26 and how is it different from PR-27?
PR-26 applies when expenses were incurred before coverage began, the mirror scenario to PR-27, which applies to expenses incurred after coverage ended.
