Dollar value and recovery probability are not the same thing. Health systems that outsource without scoring first are paying contingency fees on claims they could have kept.
For most health systems, accounts receivable outsourcing feels like a necessary hedge against an impossible workload. Payer complexity is up, staff bandwidth is down, denial rates keep climbing, and somewhere in the finance office, a decision was made (often years ago) to send everything below a certain dollar threshold to a vendor and move on.
It’s not a bad instinct. But it’s an expensive one. The problem isn’t outsourcing itself. It’s the outsourcing without intelligence.
The Dollar Threshold Trap
Here’s a scenario most RCM leaders recognize. A health system draws a line (say, $5,000), identifies a group of payers, looks at average adjudication lag, and automatically routes every claim below the threshold to a third-party vendor. High-dollar claims stay in-house. Low-dollar claims go out the door.
What that logic misses is that a dollar threshold and recovery probability are not the same thing. Bundled into that outgoing inventory are claims that are entirely winnable, ones your team could have overturned with the right visibility. They’re mixed in with genuine noise like aged-out accounts, duplicate submissions, and claims that are never going to pay. The vendor gets both the good and the bad, and you pay contingency fees on all of it.
You have no way of knowing which is which, because the decision to send them was never based on recoverability in the first place.
What A/R Scoring Actually Does
A/R scoring assigns a predictive recovery value to each claim before it leaves your system. It draws on the data you already generate including 837/835 transaction files, CARC and RARC codes, payer behavior patterns, denial reason history, service line, and claim attributes. This history is used in predictive models to identify which claims are likely to be paid.
The output isn’t a report, but a decision framework. High-score claims, those with strong recovery probability, can stay in-house or route to specialized vendors equipped to work them. Low-score claims go to cost-effective recovery workflows or get written off without burning staff hours or placement fees on a lost cause. Complex claims that look small on paper but carry real overturn potential get flagged, not buried. This is the difference between routing work by volume and routing it by value.
Health Systems Are Rethinking How They Outsource
Earlier this year, CommonSpirit Health announced it would spend nearly $2 billion to exit a long-standing revenue cycle outsourcing arrangement and bring core functions back in-house. The reasons cited were a desire for deeper integration with automation tools and closer alignment between financial operations and enterprise analytics.
CommonSpirit is an extreme example, but the instinct behind it isn’t. Health systems with the most mature revenue cycle operations aren’t asking “should we outsource?” They’re asking “what should we outsource, to whom, and based on what criteria?” Scoring is what makes that question answerable.
Three Decisions Scoring Makes Defensible
Stop paying contingency fees on claims your team should have worked. If a claim scores high on recovery probability and your team has the capacity to work it, sending it to a vendor is margin erosion. Scoring makes that visible before the placement, not after the fee.
Protect your write-off decisions. Premature write-offs are a persistent source of revenue leakage. When a claim hits a certain age and looks dormant, the temptation is to close it. Scoring lets you distinguish dormant-and-recoverable from dormant-and-done before you walk away from revenue that was still winnable.
Route complex claims correctly. A claim that looks small by dollar value may carry significant overturn potential based on payer history, denial pattern, and clinical context. Scoring surfaces that. Threshold-based routing buries it.
Move From Reactive to Proactive
The same intelligence that scores A/R for outsourcing decisions can flag claims at risk of denial before they’re submitted, shifting the work from clean-up to prevention. When post-bill prioritization draws on the same data informing pre-bill and concurrent risk, you stop treating denials as a downstream problem and start treating them as a system-wide signal.
Most revenue cycle teams are still operating in response mode. Scoring is what allows you to get in front of it.
See how Sift’s RevProtect Payments Intelligence Platform can help your team build smarter outsourcing decisions. Get in touch.
