When should an RCM company outsource AR follow-up?
Outsource or co-manage AR follow-up when production capacity — not strategy — is the constraint: aging inventories rebuild faster than your team can work them, coverage is thin after turnover, or client growth outpaces hiring. Keep ownership of systems, SOPs, write-off authority, and client relationships; add specialists inside your environment with clear QA and reporting. Start with a scoped pilot on one aging slice or client book before expanding.
Capacity problem vs. process problem
Adding outside AR hands only helps if the bottleneck is hours and coverage. If your SOPs, payer playbooks, or denial root causes are broken, more touchers will mostly produce more of the same. Name the constraint before you staff around it.
- Capacity: process is sound, but claims age because there are not enough trained hours on the queue
- Process: the same denial reasons and rework loops repeat even when the queue is fully staffed
- Client mix: one specialty or payer book is drowning a team that still has slack elsewhere
- If process is the primary issue, fix playbooks and front-end leaks first — then add capacity
Trigger checklist: signals it is time to add AR capacity
You do not need every signal. Two or three sustained for more than a cycle usually means AR follow-up has become a capacity decision, not a temporary crunch.
AR over 90 keeps climbing
The 90+ bucket grows month over month even when the team is working full days — inventory is outrunning throughput.
Backlogs rebuild after every push
Weekend or month-end blitzes clear aging temporarily, then the same pile returns within weeks.
One resignation stalls a book
A single AR specialist leaving freezes a client or payer segment because coverage is too thin to cross-train.
Client SLAs are at risk
You are explaining aging and touch cadence to clients more often than you are expanding scope with them.
Hiring cannot keep pace with volume
You are turning away or delaying new client work because AR seats take too long to fill and ramp.
High-skill staff are stuck on statusing
Supervisors and senior billers spend their week on routine portal checks instead of escalations and complex appeals.
What to keep in-house
Co-managed AR works when the partner executes inside your rules — not when they become the decision-maker. Protect these functions even when production moves offshore or to a partner pod.
- System of record and admin access — least-privilege partner logins, you keep ownership
- Client relationship and commercial commitments — the partner supports your delivery, not your clients directly unless you design white-label that way
- Write-off authority, settlement decisions, and goodwill adjustments
- Payer escalation strategy and contract interpretation for edge cases
- SOP ownership and exception policy — partner follows your playbooks; you change the rules
- Final say on appeal strategy for high-dollar or sensitive accounts
How to pilot AR follow-up with a co-managed partner
A good pilot is narrow enough to judge quality in weeks, not quarters, and explicit enough that "it feels busy" is not the success metric.
- 01
Pick a bounded queue
One aging band (e.g. 61–120), one specialty, or one client book — not the entire AR inventory on day one.
- 02
Document touch rules
Define status cadence, notes format, when to call vs. portal, and what gets escalated back to your team.
- 03
Set access and QA
Least-privilege access, sample audits against your SOPs, and a named US contact for escalations.
- 04
Agree on reporting
Weekly volume worked, outcomes, aging movement, and open issues — using your KPI definitions.
- 05
Review and expand only if it holds
After the pilot window, decide to widen scope, adjust playbooks, or stop. Expansion should be earned.
Offshore, co-managed, or hire — choosing the path
"Outsource AR" is not one model. Match the path to how much control and visibility you need while you add capacity.
| Criteria | Hire in-house | Co-managed / offshore capacity | Full AR outsourcing | |
|---|---|---|---|---|
| Best when | Stable volume, time to ramp | Capacity gap now; keep systems & SOPs | You want to hand off ownership of the queue | |
| Control | Highest | High if work stays in your systems | Often lower / vendor-led | |
| Speed to capacity | Slowest | Faster with a scoped pilot | Fast, but transition-heavy | |
| Main risk | Hiring lag & turnover | Coordination & SOP clarity | Visibility and client trust |
Next steps for RCM operators
If the trigger checklist describes your queue, start with a capacity conversation scoped to AR — not a full back-office commitment. Salt HealthOps supports US RCM companies with co-managed AR follow-up inside your environment, under engagement models you can expand only when the pilot earns it.
RCM Company Support
How Salt works with US RCM operators.
Learn moreAR Follow-Up Services
Workflow scope for unpaid and aging claims.
Learn moreEngagement Models
Dedicated specialist, pod, or monthly support.
Learn moreRelated reading
Frequently asked questions
Should an RCM company fully outsource AR or use a co-managed model?
Most RCM companies should prefer co-managed capacity: partner specialists work inside your PM/EHR and payer portals under your SOPs, while you keep client ownership and decisions. Full outsourcing of AR can make sense only if you intentionally want a vendor-owned queue — which many client contracts and trust models do not allow.
What size backlog justifies a pilot?
There is no universal dollar threshold. A better test is whether aging and SLA risk are sustained after your team is already at full utilization, and whether a bounded slice (one aging band or client) can be measured cleanly for several weeks. If you cannot define that slice, clarify reporting before you add people.
Will offshore AR follow-up hurt client confidence?
It can if the work is opaque. It usually does not when clients see your brand, your systems, your SLAs, and your reporting — with production capacity added behind the scenes under HIPAA-aware, access-controlled workflows. Be explicit in your own client messaging about how quality and escalation work.
What should we measure in the first 30–60 days of a pilot?
Agree on definitions up front: accounts touched, touches per day, aging movement for the pilot slice, denial/appeal handoffs, QA sample results, and escalation volume. Avoid promising specific Days in AR or collection outcomes; judge whether the partner follows your SOPs and moves the inventory you assigned.