Working the aging oldest-first spends the most effort on the claims least likely to pay, because claims are usually old for a reason. Triage by recoverability instead: filing and appeal deadlines first, then payer behavior, then balance, with age genuinely last.
Working the aging oldest-first feels like discipline. It is the opposite: it spends the most effort on the claims least likely to pay.
Why oldest-first underperforms
Claims are old for a reason. Some were denied and never worked. Some are past their filing window and are already dead. Some are behind a coverage problem that was never resolved and will not be resolved by a status call.
Meanwhile, claims at 45 days with a live deadline and a responsive payer are sitting untouched because they are not the oldest thing in the queue.
Triage by recoverability instead
- Deadline first. Anything approaching a filing or appeal limit outranks everything, regardless of age or balance. A missed window is a permanent loss.
- Then payer behavior. Some payers resolve on a single well-documented follow-up. Others require escalation. Effort should follow what actually works.
- Then balance. Within similar recoverability, chase the larger money.
- Then age. Genuinely last.
Build the queue from the denial reason
An aging report sorted by age tells you nothing about why a claim has not paid. The same report grouped by denial reason tells you what work each claim actually needs, and most of those groups have a single fix that clears many claims at once.
Eligibility denials need coverage research, not follow-up calls. Authorization denials need a retroactive request or an appeal. Coding denials need a corrected claim. Treating them as one undifferentiated queue is how staff spend a morning on status calls that change nothing.
What good looks like in numbers
A/R over 90 days is the standard alarm, and the useful version of it excludes credit balances and unrecoverable claims — otherwise the ratio flatters or frightens you for the wrong reasons.
Track the share of A/R that is past a filing deadline separately. It should be near zero, and if it is not, the problem is queue order rather than staffing.
The part most practices skip
Naming the unrecoverable portion explicitly. Some aged A/R cannot be collected — past filing, past appeal, no coverage. Leaving it in the aging inflates an asset that does not exist and buries the workable claims underneath it.
Writing it off is not giving up. It makes the remaining number true, and it makes the queue small enough to actually work.
Common questions
- What order should I work my A/R in?
- Deadline first, then payer behavior, then balance, then age. Anything approaching a filing or appeal limit outranks everything, because a missed window is a permanent loss.
- Why are my oldest claims not collecting?
- Claims are usually old for a reason — denied and never worked, past the filing window, or behind an unresolved coverage problem that a status call will not fix.
- Should I write off old A/R?
- Yes, once it is genuinely unrecoverable. Leaving it in the aging inflates an asset that does not exist and buries the workable claims underneath it.
- How do I know which claims are still workable?
- Check the filing and appeal deadline against the date of service, then the denial reason. A coverage problem needs resolving at the source; a status call will not move it.
- How often should A/R be worked?
- Continuously, in a queue sorted by recoverability rather than in a monthly sweep. Deadlines do not wait for a reporting cycle.
Denials Piling Up?
We handle the revenue cycle end to end — coding by certified coders, claim submission, denial management and appeals, and A/R follow-up, with six reported numbers every month.