What Is the Difference Between CO-27 and PR-27 and Who Owes the Balance?
CO-27 and PR-27 look like the same denial. Both say coverage terminated, both land on a visit you already delivered, and in a high-volume posting queue they get handled identically, adjusted, written off, done.
How to Route 27-Code Denials So the Group Code Decides Who Pays
The goal is simple: every 27-code denial routed by its group code, PR to the patient and CO to appeal-or-adjust, never posted identically in a hurry. Here is what does that, move by move.
1. Read the Group Code Before the Reason Code
The reason code 27 tells you coverage terminated; the group code in front of it tells you who owes. Train the posting read to land on the two-letter prefix first, because that is the field that changes what you can legally do next. CO-27 and PR-27 look nearly identical on the remit, and a team scanning for the reason code alone will treat them the same. Reading the group code first is the single habit that keeps the whole downstream routing correct.
2. Route PR-27 to Patient Statements After Verifying the Denial
PR-27 means the coverage truly terminated and the patient is financially responsible, so this balance is billable, not a write-off. Verify the denial is accurate, confirm the termination is real and the visit fell after it, then route the balance to a patient statement with the supporting documentation. The write-off habit that treats every 27-code denial as a contractual adjustment is exactly where practices give away money patients legitimately owe, sometimes a full year of it before anyone notices.
3. Route CO-27 to Appeal-or-Adjust, Never to the Patient
CO-27 means your in-network agreement with the payer bars you from billing the patient for this denial, so the balance goes to appeal-or-adjust review, not to a patient statement. Billing a patient after a CO-27 is a compliance violation, not just a mistake, because you have contractually agreed to accept the payer's determination. Send CO-27 to review to confirm the termination and appeal if it is wrong, and write it off only when it is right, but keep it away from the patient every time.
4. Build the Split Into a Posting Rule and Audit It Monthly
Do not leave this to whoever is posting that day. Build a posting rule that separates 27-code denials by group code the moment they land, so PR-27 flows to patient billing and CO-27 flows to appeal-or-adjust automatically, and then audit the split monthly to catch anything miscoded or misrouted. The rule stops the identical-handling mistake at the source, and the monthly audit catches the exceptions before they turn into a year of write-offs or a batch of statements you have to recall.
5. Hand 27-Code Routing to a Dedicated Team
Practices that stop bleeding money on terminated-coverage denials do it by handing the routing to a dedicated team: remote specialists who read the group code, route PR and CO correctly, build the posting rule, and run the monthly audit, live in 1 to 2 weeks. The posting team goes back to the volume it can clear cleanly, a trained backup covers every gap, and the 27-code denial stops being the one that gets adjusted identically and quietly costs you. Below is what it sounds like when nobody owns this yet, in practice teams' own words.
Key Pain Points and Discussions by Providers
representative composite examples based on common workflow discussions
“We discovered we had written off a full year of PR-27 balances that were legitimately billable to patients, because our posting team adjusted every 27-code denial the same way. Nobody was reading the group code. It was real money we just handed back because CO and PR looked identical on the remit.” composite example: revenue cycle lead, multi-specialty group
“My posters scan for the reason code and miss the two letters in front of it. CO-27 and PR-27 land in the same bucket and get the same adjustment, and I do not find out until an audit shows we either wrote off billable balances or billed patients we were not allowed to.” composite example: billing manager, medical group
“Someone on my team billed a patient after a CO-27, and our contract says we cannot. That is not a rounding error, that is a compliance problem. The group code told us it was ours to eat and we sent a statement anyway, because nobody built a rule to separate the two.” composite example: practice administrator, primary care practice
“The fix for us was a posting rule, not a person. As long as it depended on whoever was posting that day remembering CO from PR, it broke constantly. Once the rule split them automatically and we audited it monthly, the write-offs and the wrong statements both stopped.” composite example: billing lead, multi-provider practice
“PR-27 is money on the table and CO-27 is a compliance line you cannot cross, and they are one character apart on the remittance. Until we started routing by the group code instead of the reason code, we were losing on both ends without realizing either one.” composite example: office manager, specialty practice
Our Answer
Here is what we actually do. A dedicated remote specialist reads the group code before the reason code on every 27-code denial and routes it by liability: PR-27 goes to a patient statement after the denial is verified and the termination confirmed, and CO-27 goes to appeal-or-adjust review and never to the patient, because a network contract bars billing them for that balance. They build the split into a posting rule so the routing happens automatically the moment the denial lands, and they run a monthly audit to catch anything miscoded or misrouted before it becomes a year of write-offs. Our teams include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, trained in US denial management and posting workflows, working inside the systems you already run, with approved AI tools assisting with first-pass and a human verifying every routing decision. This is our denial management paired with an AI-first workflow, in one paragraph.
Why This Keeps Happening
If the group code carries the answer, why do teams keep missing it? Because the two codes are nearly identical on the remit and volume rewards speed. The reason code 27 is the same on both, coverage terminated after the date of service, and the only thing that differs is the two-letter group code in front. A posting team clearing hundreds of lines scans for the reason and applies the same adjustment, and the CO-versus-PR distinction, the one thing that actually changes what is legal, gets lost in the pace. The X12 standard draws the line clearly; the posting queue is where it gets erased.
What makes the error expensive is that the two codes fail in opposite, both-costly directions. Under a CO group code you have a contractual obligation, your in-network agreement requires you to accept the payer's determination, so billing the patient is not just wrong, it is a compliance violation. Under a PR group code the patient is financially responsible and the balance is legitimately billable. Adjust them the same way and you either write off PR-27 money you could have collected or bill a patient on a CO-27 you were contractually barred from touching. Sorting that split correctly is exactly the judgment a disciplined denial management workflow is built to apply, and the terminated-coverage volume feeding it shrinks when the eligibility verification at the front end is tight.
And the loss compounds quietly because nothing flags it in the moment. A PR-27 written off looks the same in the system as a CO-27 written off, so the mistake does not surface until an audit, by which point it can be a year of billable balances given away or a batch of non-compliant statements already sent. The MGMA and HFMA both treat denial-posting accuracy as a core revenue-cycle control precisely because errors here do not announce themselves; they accumulate. The twelve seconds it takes to read the group code is the cheapest revenue-cycle control there is, and the identical-handling habit is one of the costliest ways to skip it.
Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:
| What you tried | What actually happened | Who ended up doing the work |
|---|---|---|
| Adjusted every 27-code denial identically | Wrote off a year of billable PR-27 balances that patients legitimately owed | The posting team, scanning for the reason code |
| Billed the patient on a CO-27 without checking the group code | Compliance violation, because the network contract barred billing the patient for that balance | A statement that never should have gone out |
| Left CO-versus-PR routing to whoever was posting that day | Broke constantly because it depended on memory, not a rule, with errors surfacing only at audit | Whoever happened to be in the queue |
| Gave 27-code routing to a dedicated remote specialist | Group code read first, PR routed to statements, CO to appeal-or-adjust, split built into a rule and audited monthly | Someone whose whole job it is |
The Solution
So what does "someone whose whole job it is" look like on a 27-code denial? The specialist reads the group code before the reason code, every time, because that two-letter prefix is what decides who owes. PR-27 they verify and route to a patient statement with documentation, since the coverage genuinely terminated and the patient is responsible. CO-27 they route to appeal-or-adjust and keep away from the patient entirely, because the network contract bars billing them for that balance. That disciplined split is exactly what a serious denial management workflow is built to deliver, line after line, at posting speed.
Then they take the routing out of anyone's memory and put it into a rule. The split gets built into posting so PR-27 flows to patient billing and CO-27 flows to appeal-or-adjust automatically the moment the denial lands, and a monthly audit catches anything miscoded or misrouted before it compounds. The year of quiet write-offs and the batch of non-compliant statements both stop, because the group code drives the routing instead of the pace of the queue. And the whole 27-code volume shrinks when lapses get caught earlier, which is why this pairs with tighter eligibility verification at intake.
Behind all of it, Approved AI tools may assist with the first pass and a trained human reviewer verifies. The workflow separates 27-code denials by group code the moment they post, routes PR and CO to their correct queues, and flags the exceptions for review; a person confirms the routing is right and owns the appeal-or-adjust decision on the CO side and the verification on the PR side. Every security control that protects the patient and claim data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving denial and patient-billing data through a routing workflow is only safe when the controls are real.
Who Actually Does This Work
Fair question: why would an outsourced team route your 27-code denials better than your own posters? Because reading the group code and routing by liability is their entire day, not one distinction lost in a queue of hundreds of lines. The people working your denials include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, all trained in US denial management and posting workflows. They read CO from PR on sight, they know billing a patient after a CO-27 is a compliance violation, and they know a PR-27 is billable money that should never be written off. That is not a distinction that survives being rushed; it needs someone whose whole job it is.
We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ team members, 24/7 coverage, and the AI-assisted plus human-verified workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at approximately 68% below equivalent in-house staffing costs. Trained backup coverage is included in the managed-service model.
And the security piece your compliance officer will ask about: Staffingly maintains active ISO/IEC 27001:2022 certification and operates under HIPAA-compliant controls and signed BAAs. SOC 2 Type II reporting and security controls apply according to the relevant entity, client environment, facility, device, and workflow. Venn Blue Border and related workstation restrictions are used where applicable. Staffingly maintains $5M in professional liability (E&O) and cyber insurance as part of its enterprise risk-management program; the full detail lives in our HIPAA and security posture.
Put the routine and the people together, and a specific list of things simply stops happening.
Ready to Route Your 27-Code Denials Correctly?
Evaluating the best insurance eligibility verification services? See how a dedicated remote team compares, then browse every pain point we solve.
How We Build a More Durable Process
A person alone is not the fix, and neither is a bot alone. The fix is a documented posting rule: split 27-code denials by group code the moment they land, route PR-27 to patient statements after verification and CO-27 to appeal-or-adjust review, keep CO away from the patient, and audit the split monthly, worked the same way every time. Before we take a single denial for a new practice, we chart your CO-27 and PR-27 volume by payer so we can see how many billable balances are being written off and whether any CO-27s reached a patient, and we build the rule against that, not against a generic template.
From there the routing becomes a living posting rule rather than a distinction one poster half-remembers. It records which group code sends a denial to patient billing and which sends it to appeal-or-adjust, how to verify a PR-27 before a statement goes out, why a CO-27 can never reach a patient, and the monthly audit that catches the exceptions. It is written down, kept current, and owned by the team. When your specialist is out, a trained backup works the same rule the same way, so a 27-code denial does not have to get mis-routed because one person was away.
That is the difference between auditing this year's write-offs after the fact and fixing the process for good, and it is what a dedicated denial management partner actually buys you. A staffer leaving used to mean the CO-versus-PR split broke and the write-offs crept back. Under this model the posting rule keeps running, the playbook stays, the backup steps in, and the 27-code denial stops being the one that quietly costs you on both ends.
The Whole Thing in Four Sentences
CO-27 and PR-27 share the same reason, coverage terminated after the date of service, but the group code decides who owes: CO is a contractual obligation that bars billing the patient, and PR is patient responsibility that is legitimately billable. Adjusting every 27-code denial identically, billing a patient on a CO-27, or leaving the routing to memory all fail the same way. The fix is to read the group code first, route PR-27 to patient statements and CO-27 to appeal-or-adjust, build the split into a posting rule, and audit it monthly. A multi-specialty group can use this workflow without exposing patient information or naming client organizations.
If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.
Ready to route your 27-code denials correctly? Start with a Two-Week Free Trial: your real CO-27 and PR-27 volume, dedicated specialists reading the group code and routing every balance by liability, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.
One Flat Weekly Rate. 45 Hours of Coverage.
No hourly meters, no setup fees, no security deposits, no long-term contracts. Two-Week Free Trial. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.
One dedicated remote specialist splitting your 27-code denials by group code and routing each balance correctly, single-location medical practice
5+ remote specialists running denial posting and management across a multi-provider group and several front desks
10+ remote specialists, multi-location medical group, MSO, or PE-backed platform posting and routing terminated-coverage denials across many payers and sites
45 hours of coverage at one flat weekly rate.
For a simple annual comparison, 40 hrs x 52 weeks = 2,080 hours. A Staffingly plan: 45 hrs x 52 weeks = 2,340 hours a year, that is 260 additional hours included in your flat rate. $399/week x 52 = $20,748 a year / 2,340 hours = $8.87 per hour.
Route Your 27-Code Denials Right This Month
You have seen the whole method. The trial lets you test it on your own terminated-coverage denials, with a tracker your team can watch every day.
Start My Two-Week Free TrialWant Us to Route Your 27-Code Denials Correctly?
Tell us your situation and we will map your CO-27 and PR-27 volume and where the balances are going wrong. A team member will follow up with next steps.
Frequently Asked Questions
Where the Claims on This Page Come From
Sources & References
- X12 Claim Adjustment Group Codes and Reason Codes. The standard definitions of group codes CO, contractual obligation, and PR, patient responsibility, and reason code 27, expenses incurred after coverage terminated. x12.org