By Andy Schachtel, CEO of Sourcefit | Global Talent and Elevated Outsourcing
Key Takeaways
- Days in A/R is a symptom metric. The days hide in specific places: unbilled claims, untouched payer follow-up queues, unworked denials, credit balances, and self-pay balances nobody calls about.
- Benchmark honestly: overall days in A/R around the mid-30s to mid-40s is typical for well-run organizations depending on payer mix, but the more actionable numbers are A/R over 90 days and touch rates on aging claims.
- Most A/R aging is a capacity problem disguised as a process problem. Claims age because no one touches them, and no one touches them because follow-up staffing never matches claim volume.
- Dedicated offshore follow-up teams attack the backlog economically: systematic worklists, payer-specific playbooks, and enough hands to touch every claim on schedule instead of triaging the loudest ones.
The Metric Everyone Watches and Few Decompose
The direct answer to “how do we reduce days in A/R” is: find out where the days actually accumulate, because the average on the dashboard is hiding a distribution. An organization with 48 days in A/R almost never has every claim paying in 48 days. It has a healthy core paying in 25 and a stagnant tail sitting at 120-plus, and the tail is where the money goes to die. Claims over 90 days collect at sharply declining rates, and past timely-filing limits they collect at zero.
We run A/R follow-up operations for US providers, and the diagnostic pattern is remarkably consistent. When days in A/R creep upward, leadership tends to look for a process flaw. What we usually find instead is arithmetic: the follow-up team can work a fixed number of accounts per day, claim volume grew, and the difference has been quietly aging into the tail for months.
Where the Days Hide
Decompose the pipeline and the culprits show themselves.
Unbilled and discharged-not-final-billed. Days accumulate before a claim ever leaves the building: documentation gaps, coding queues, and edit rejections that bounce claims into worklists. Every day here is pure, silent aging.
Payer processing you never verify. Clean claims mostly pay on cycle. The failures are claims that were never received, suspended for information, or quietly denied, and each sits invisible until someone checks status. The difference between checking at day 45 and day 21 is three weeks of age on every problem claim.
Denials nobody works. A denial unworked is a claim aging at maximum speed. Appeal windows expire while the denial sits in a queue, converting recoverable revenue into write-offs, the failure chain we detailed in why US hospitals are losing millions to claim denials.
Self-pay after insurance. Deductible-era balances shift real money to patients, and patient balances age faster than any payer class when statements are the only outreach. Estimates, payment plans, and actual phone calls change the curve.
Credit balances and small balances. Overpayments awaiting resolution and small balances judged too minor to work both inflate A/R and distort the picture, and both yield to systematic batch processing.
Benchmarks That Drive Action
| Metric | Healthy Range (typical) | Why It Is Actionable |
| Days in A/R (overall) | Mid-30s to mid-40s, payer-mix dependent | The headline, but only a symptom |
| A/R over 90 days | Under 15 to 20% of total A/R | Measures the tail where collectibility dies |
| First-pass clean claim rate | 95%+ | Every rejection restarts the clock |
| Days from service to bill | Under 4 to 5 days | The controllable head of the pipeline |
| Follow-up touch cadence | Every open claim touched per payer-appropriate cycle | The capacity number almost nobody tracks |
| Denial overturn and appeal timeliness | Appeals filed well inside payer windows | Converts aging denials into cash |
The touch-cadence line is the one we push clients to adopt, because it converts A/R management from an outcome you observe into an input you control. Define the follow-up interval per payer class, then staff to actually meet it at your claim volume. When touch cadence is met, days in A/R falls as a consequence. When it is not, no amount of dashboard attention will fix the trend.
The Compression Playbook
Sequence matters. Start at the head of the pipeline: push service-to-bill days down with charge capture discipline and edit-queue ownership, and lift the clean-claim rate with the front-end verification rigor we described in how offshore eligibility teams reduce claim rejections. Every claim that goes out later or bounces back restarts the clock you are trying to compress.
Then attack the tail with a segmented blitz. Rank the over-90 inventory by collectible value and timely-filing urgency, not by age alone, and work it with dedicated capacity rather than skimming it between new claims. Organizations that split “current” follow-up from “backlog recovery” into separate teams see both improve, because the backlog stops cannibalizing the cadence that prevents the next backlog.
Institutionalize the cadence with payer playbooks: status-check timing, portal versus call strategies, escalation paths, and reconsideration tactics per payer. Follow-up is craft, and documented craft scales while tribal knowledge does not.
Finally, automate the checkable and reserve humans for the fixable. Claim status APIs and RPA can confirm receipt and payment cycles at scale; trained analysts belong on the claims where something is wrong, the pattern we outlined in AI and automation in healthcare RCM. The blend raises effective touch capacity without raising cost linearly.
Why Offshore Capacity Changes This Equation
A/R follow-up is the purest capacity function in the revenue cycle: outcomes scale almost linearly with qualified hands on worklists. That is why it responds so well to the offshore model. At 50 to 65 percent below onshore role costs, an organization can afford enough analysts to meet touch cadence on every claim, current and backlog, instead of triaging. Teams work US payer hours where phone work demands it and process portal and documentation work around the clock, so worklists advance every day. And under a transparent cost-plus model, the business case is straightforward arithmetic: the incremental collections from a worked tail against the monthly cost of the team working it, an ROI structure we laid out in the ROI of offshore revenue cycle management. It runs under HIPAA business associate agreements with certified controls, ISO 27001 and SOC 2 among them.
Frequently Asked Questions
What is a good days in A/R number?
For most physician and outpatient organizations, the mid-30s to mid-40s is a defensible range, with payer mix moving the target: heavy Medicare tends lower, heavy workers’ comp or litigation-adjacent volume higher. Track your trend against your own baseline and pair the average with A/R over 90 days, which tells you whether the number is healthy or merely averaged.
How fast can days in A/R realistically improve?
Front-end fixes show up within one to two billing cycles. A dedicated backlog blitz typically produces visible cash within 60 to 90 days, with the over-90 percentage falling steadily as the tail gets worked. Expect the overall days metric to improve for two to three quarters as the one-time backlog recovery and the new steady-state cadence both take hold.
Should we write off old A/R or work it?
Segment before deciding. Rank the aged inventory by collectible value, payer, and timely-filing status. A meaningful share is usually still recoverable with focused effort, appeals inside windows, resubmissions, corrected claims, while some is genuinely dead and should be written off cleanly so the metric reflects reality. Working the recoverable tail is typically self-funding several times over.
Is it better to fix processes or add follow-up capacity?
Both, in that order of diagnosis but often in parallel execution. Process fixes at the front end stop manufacturing new aged claims; capacity clears what exists and holds the cadence. The most common mistake is pursuing process perfection while the tail keeps aging past filing limits, which converts a fixable problem into a permanent write-off.
How do offshore A/R teams coordinate with our in-house staff?
Through clean queue ownership. The offshore team typically owns status checks, documented follow-up, portal work, and standard appeals, while in-house staff keep the exceptions that need clinical input or payer relationships. Shared worklists, payer playbooks, and a weekly operations review keep both sides aligned, and every action lands in your system under your audit trail.
To learn more about how SourceCycle builds A/R follow-up teams that touch every claim on schedule, visit sourcecycle.com or contact our team for a consultation.
