How Do You Improve Patient Collections When Revenue Cycle Management Software Only Chases Payers?

Patient responsibility is the share of a visit the payer hands back to the patient. It includes the deductible, coinsurance and copayment reported under group code PR on the remittance. We think the problem is simple. Practices chase that money with tools built to chase payers.

Here's what usually happens. The front desk collects a copay, the payer's remittance arrives weeks later with a different number, and the difference sits in a claim status nobody owns.

We'll walk through the four checkpoints that decide patient collections and the five numbers we'd review every week. We'll also cover where the money leaks, what the No Surprises Act asks for self-pay patients, and when a spreadsheet stops being enough.

This is an operations guide, not legal advice.

Patient Collections Improve When Patient Responsibility Has Four Owned Checkpoints

Patient collections improve when we stop treating patient responsibility as leftover claim balance and give it four checkpoints, each with one owner and one deadline. Most practices already run some patient collections process. The money leaks in the gaps between the steps.

The American College of Foot and Ankle Surgeons (ACFAS) cites McKinsey & Co. research that physicians recover only about 50% of what's owed once a patient leaves the office. That is why we put the first two checkpoints before the patient walks out.

1. An Estimate Before the Visit

We build the estimate from the eligibility response, including deductible remaining, coinsurance percentage and copay for the visit type. For scheduled procedures, we send patient payment estimates at least three business days ahead, so the patient can plan.

The estimate is only as good as the benefits data behind it. That is why we pair this step with the eligibility workflow we described in the front-desk eligibility post.

2. A Check-In Collection Against a Written Policy

At check-in we collect the copay, any prior balance and a deposit toward the estimated deductible for procedures. ACFAS recommends posting the payment policy at check-in and having new patients sign it at their first visit.

Point of service collections work when the front desk isn't improvising. We give staff one script and one rule for what to collect.

3. The 835 Posted Within Two Business Days

The electronic remittance advice, the ASC X12 835, is where the payer states the real patient responsibility. We post it within two business days, and we compare the PR amount against the estimate for every visit.

That comparison is the step most practices skip. Without it, nobody learns the estimate was wrong until the patient calls.

4. A Clean Balance Before the First Statement

Before a patient statement goes out, we settle the visit. We apply any check-in payment, refund or move any credit, and charge a card on file only where the patient consented. Then the statement shows one number the patient can trust.

Pro tip: Give each checkpoint a named owner, not a team. When the 835 posting belongs to "billing", it belongs to nobody on a busy Monday.

Why Revenue Cycle Management Software Treats Patient Responsibility as a Claim Status

Most revenue cycle management software is organized around the claim, so patient responsibility appears as a status on a claim rather than as a balance with its own life. That design is sensible for payer work. It leaves the patient side with no single record.

• What the Claim-Centered Workflow Gets Right

The claim is the right unit for payer follow-up. Tebra's help center shows the pattern clearly. Staff transfer a claim balance to patient responsibility, then send patient statements in batches.

When statements go out, Tebra's documentation says claims move to a "Pending patient" status, with text, email and mailed delivery options. That is solid tooling for sending bills.

• Where the Claim-Centered Workflow Stops

The claim status tells us a bill went out. For example, it doesn't tell us the estimate was $140 low, the patient paid $60 at check-in, and a $40 credit sits on another visit. We have to assemble that picture ourselves.

Point tools fill parts of the gap. Here is how we read the categories we checked on 26 September 2026.

Tool category	Example we read	What it does well	Where it stops for patient collections
Practice management and billing	Tebra PM help center	Transfers balances to the patient, batches statements, sends text and email reminders	Organizes patient responsibility by claim, and the pages we read showed no estimate-to-835 comparison
Patient estimation	Waystar Patient Estimation	Builds estimates from benefit data before the visit	Waystar reports that 87% of its estimates land within a client-accepted range, so the practice still has to measure its own misses
Collections analytics	Experian Health	Scores accounts by propensity to pay and segments outreach	Works on balances already owed, after the leaks upstream have happened
Check-in and payments	Kyruus Health	Shows copays and balances at check-in and stores a card on file	Collects what the system says is due, even when that number is stale

We don't think any of these tools is the problem. The gap is that no single record ties the estimate, the check-in payment, the 835 and the statement together.

Five Patient Responsibility Numbers We Would Review Every Week

Most guides to patient collections in medical billing stop at tactics. We'd review five numbers every week instead.

Each one can be computed from data a practice already has, including the schedule, the eligibility log, the payment ledger and the 835 files. Together they show where patient responsibility is collected, where it is misjudged and where it stalls.

Say you run a four-location dermatology group seeing about 600 visits a week. This hypothetical example shows how each number reads.

1. Point-of-Service Capture Rate

This is the dollars collected at check-in divided by the patient responsibility known at check-in. "Known" means copays, prior balances and the estimated deductible portion, not the final 835 amount.

In our hypothetical group, the front desk knew about $21,000 of patient responsibility last week and collected $13,650. That is a 65% capture rate. We read it by location first, because one site at 40% usually explains the whole gap.

2. Estimate Variance per Visit

This is the 835 PR amount minus the estimate, per visit. We track the share of visits where the miss exceeds $50 in either direction, and the total dollars of those misses.

A high share of large misses means the estimate logic or the benefits data is wrong. A consistent underestimate is the worse failure, because the patient gets a surprise bill and trust drops.

3. Days From 835 to First Patient Statement

This is the calendar days between the 835 posting date and the first patient statement for that visit. We compute it from the remittance date and the statement batch log.

If this number runs past two weeks, the patient has half-forgotten the visit by the time the bill arrives. We'd treat that delay as a process problem before a software problem.

4. Open Patient Credit Balances

This is the total of patient credit balances, usually created when check-in collection exceeded the final patient responsibility. We track the dollar total and the oldest credit.

Credits matter twice. They are money the practice owes back, and they distort every aging report until someone resolves them.

5. Patient Balance Aging by Status

This is open patient responsibility grouped by status, not only by age. We use four buckets, which are posted but not yet billed, statement sent, on a payment plan and referred to an agency.

A large "posted but not yet billed" bucket points back at number 3. A large agency bucket means the upstream checkpoints failed weeks ago, and those balances tend to end as bad debt.

Number	Formula	Data source	What a bad reading means
Point-of-service capture rate	Collected at check-in ÷ known patient responsibility at check-in	Payment ledger, check-in log	Front-desk script or policy is not being followed
Estimate variance per visit	835 PR amount minus estimate	835 files, estimate log	Benefits data or estimate logic is wrong
Days from 835 to first statement	Statement date minus 835 posting date	835 files, statement batch log	Posting or statement batching is late
Open patient credit balances	Sum of patient credits, plus age of oldest	Payment ledger	Check-in overcollection is not being resolved
Patient balance aging by status	Open patient responsibility by status bucket	Ledger, statement log, agency file	Balances are stalling at a specific handoff

Pro tip: Start with estimate variance. We'd pick it first because it separates a front-desk problem from a benefits-data problem, and it needs only two files.

Where Patient Collections Leak Between the Estimate and the Statement

Patient collections leak at a few repeatable handoffs, and most of them happen before the first patient statement is ever printed. Each leak changes patient responsibility after someone has already quoted or collected it.

Deductibles are why this matters more each year. The KFF 2025 Employer Health Benefits Survey found that 33% of covered workers are in a high-deductible health plan with a savings option. It also found that 34% face a single-coverage deductible of $2,000 or more.

KFF put the average single-coverage deductible at $1,886 in 2025. For covered workers at firms with 10 to 199 employees, the share with a $2,000-plus deductible was 53%.

• Leaks Before the Visit

The first set of leaks comes from stale or partial data at the front end. The estimate is built on benefits that changed, or on a deductible the patient partly met at another provider.

An AAFP FPM article noted that collection ratios often drop in January during "deductible season". We plan for that reset rather than treating January as a surprise.

• Leaks After the 835

The second set comes after the remittance arrives. A secondary payer never gets billed, a credit sits unapplied, or a statement is suppressed because a card is on file but never charged.

Leak	Where it starts	What it does to patient responsibility	Who we'd make own it
Stale benefits in the estimate	Eligibility check	Estimate misses the real amount	Front-desk lead
Deductible reset in January	Plan year change	Underestimates for early-year visits	Front-desk lead
Secondary coverage not billed	Registration	Patient billed for what a second payer owes	Billing lead
Check-in overcollection	Point of service	Creates patient credit balances	Billing lead
Statement held for card on file	Statement batch	Balance ages with no bill and no charge	Billing lead
Balance sent to agency too early	Collections policy	Converts recoverable money into bad debt	Practice manager

What the No Surprises Act Asks of Self-Pay Patient Responsibility

For uninsured or self-pay patients, the No Surprises Act turns the estimate into a requirement. CMS says a provider must give a good faith estimate of expected charges when the patient requests one or schedules at least three business days ahead.

We treat this as the self-pay version of checkpoint one, with firm deadlines.

• When a Good Faith Estimate Is Owed

According to CMS guidance on good faith estimates, the timing depends on how far ahead care is scheduled.

Scheduled ahead	Good faith estimate due
0 to 2 business days	Not required
3 to 9 business days	Within 1 business day
10 or more business days	Within 3 business days
Patient asks before scheduling	Within 3 business days

• What Happens When the Bill Runs $400 Over

CMS's dispute page says a patient can start a dispute when a provider charged at least $400 more than its good faith estimate. The bill has to be dated within the last 120 calendar days.

We track estimate variance for self-pay visits separately for that reason. A self-pay miss is a patient responsibility problem and a compliance exposure at the same time.

Pro tip: Store every good faith estimate against the visit record, not in a shared inbox. A dispute is far easier to answer when the estimate sits one click from the bill.

When a Spreadsheet Is Enough and When Patient Responsibility Needs Its Own Layer

A spreadsheet is enough for patient collections at one location with one practice management system (PMS). A dedicated layer starts to pay once patient responsibility spans several locations, several systems or several estimate sources.

We'd make the call on volume, locations and how long the weekly numbers take to assemble by hand.

• Stay on a Spreadsheet

One location, one system and fewer than about 300 visits a week is spreadsheet territory in our view. Export the week's 835 PR amounts and estimates, compute the five numbers and review them in 30 minutes.

• Add a Point Tool

If estimate variance is the main problem, an estimation tool is usually the cheapest fix. If check-in capture is the problem, a check-in and payments tool with card-on-file consent often pays for itself.

• Build a Read Layer Over the PMS

When the five numbers take a staff member most of a day each week, or when locations run different systems, we'd build a layer. It reads the schedule, eligibility log, ledger and 835 files, and it keeps one patient responsibility record per visit.

It doesn't replace the practice management system. It gives the billing lead one queue of exceptions instead of four reports.

Situation	Our default	Why
One location, one PMS, low volume	Spreadsheet	The five numbers take minutes to compute
Estimate misses drive most complaints	Estimation tool	Fixes the input, not the reporting
Check-in capture is low across sites	Check-in and payments tool	Fixes the moment of collection
Several locations or systems, hours of manual reporting	Custom read layer	Only a joined record answers the weekly questions

We built software for Borderless that covers scheduling, messaging, billing, payments and reporting for a dermatology practice.

Building is the wrong move when the real issue is a front desk without a script. We'd fix the script first and measure again.

Start With Last Week's Twenty Visits and One Column

We'd start small this week. Pull twenty visits from last week, put the estimate next to the 835 PR amount and the check-in payment, and add one column for the gap.

That single table shows where patient responsibility is slipping, before anyone buys or builds anything. Your revenue cycle management software will keep working the payer side well.

The patient side needs its own record, its own owners and five numbers reviewed weekly. When that record has to span locations and systems, it becomes the kind of layer Better Software builds with the operators who run the work.

Frequently Asked Questions

What is the 7 7 7 rule for collections?

It refers to Regulation F, 12 CFR 1006.14(b)(2). A debt collector is presumed compliant if it calls a person about a debt no more than seven times in seven days. The same presumption requires no call within seven days after a phone conversation about that debt. We ask any agency working our patient responsibility balances how it tracks this.

Who is responsible for collecting patient payments?

The patient, or the guarantor on the account, owes the patient responsibility once the payer adjudicates the claim. Inside the practice, we give each step one named owner. The front desk owns check-in collection, the billing lead owns posting and statements, and the practice manager owns agency referrals.

How to calculate AR days in RCM?

We divide total accounts receivable by average daily charges, usually the last 90 days of charges divided by 90. We also split patient responsibility out of that total, because patient and payer balances age differently. A 2009 AAFP FPM article put normal total AR near 100% to 120% of monthly charges.

What is a good collection ratio?

It depends on the ratio. A 2009 AAFP FPM article called a gross collections-to-charges ratio of 50% to 80% typical in family medicine, and inflated fee schedules pull it lower. We prefer net collections against allowed amounts, with patient responsibility tracked apart from payer dollars.

How is RCM different from medical billing?

Medical billing builds and submits claims and posts payments. Revenue cycle management covers the whole path, from scheduling and eligibility through coding, billing, denials and patient responsibility collection. We look for the biggest gaps at the handoffs between those stages, not inside any single one.