Triage aged AR by expected recovery, not by date

The leak

The standard aging report sorts by date in 30-day buckets. 0 to 30, 31 to 60, 61 to 90, 91+. Your team works the top of the bucket first because that is how the screen is sorted. Whether the claim at the top is worth $42 or $1,200 is invisible until the biller clicks in.

The result: people-hours are not allocated to highest-yield claims. The $42 cash-pay collection takes the same biller minutes as the $1,200 BCBS appeal. The bucket fills faster than you can drain it because nothing about the worklist tells you what to skip.

The agent

The triage agent scores every aged claim across three dimensions:

1. Payer-specific overturn rate for the CARC code on the denial.
2. Dollar amount of the claim.
3. Days remaining in the appeal window.

It returns a ranked list of claims to work today, where the next click is always the highest-expected-recovery claim in your aging report. Claims with poor odds (out-of-window, low dollar, low historical overturn) are flagged for batch-close instead of consuming a biller’s attention.

Before / after

	Today	With NxtPivot
Worklist sort	Date	Expected recovery
Visibility into dollar at risk	Click-in	At-a-glance
Out-of-window claims	Mixed in	Auto-batched
Recovery per biller-hour	Baseline	3 to 5x

The math

If your team currently works 80 aged claims per day with an average recovered value of $90 per worked claim, that is $7,200 a day at full attention.

If the ranked queue lifts average recovered value to $260 (highest-yield-first), the same 80 claims a day becomes $20,800. Same headcount, same hours, ~3x the recovered revenue on the aged book.

The triage agent does not change your win rate per claim. It changes which claims your team spends time on.

Where to start

Pull last quarter’s worked-claim log. Sort by recovered value descending. If the top decile of claims contributed > 50% of recovered revenue (it almost always does), the leak is real. The fix is the queue, not the team.