What the aging report leaves out
The aging report is the oldest artefact in the revenue cycle and still the default way most operations decide what to work. It buckets outstanding balances by elapsed time and sorts them by amount. Everything a follow-up decision needs beyond those two facts, it leaves out.
Establish which date it is aging from
Before anything else, find out what clock your report starts. Date of service, date of submission and date of last activity produce three different reports from the same data, and plenty of operations have never checked which one theirs uses.
Aging from date of service folds your own filing delay into the payer's delay. A claim submitted three weeks late arrives in the sixty-day bucket at the same moment as one submitted the next day, and the two are in completely different positions. Aging from submission separates them but hides the filing delay entirely, which is its own problem: that delay is real and it comes off the filing deadline.
Neither choice is wrong. Using one while believing it is the other is.
Everything a bucket treats as identical
A claim denied on day twelve and a claim that has sat silently pending since day twelve appear in the same row at day forty-five. They need entirely different work. One has a stated reason and an appeal window already running. The other has no information attached to it at all, and the first task is to find out what state it is in.
The bucket also cannot distinguish:
- a claim nobody has touched from one touched four times
- a claim where the last touch produced movement from one where it produced nothing
- a balance the payer still owes from one that has moved to the guarantor
- a claim with a month before its filing deadline from one with a week
- a claim whose resolution is known and waiting from one where nobody knows what to do next
Every one of those changes what should happen this morning, and none of them is on the report.
Days elapsed points the wrong way
The most useful reframing costs nothing. An aging report counts up from a date in the past. The decision in front of you depends on counting down to a date in the future.
Filing deadlines vary by payer and by contract. A claim at seventy days against a payer with a one-year window is in a very different position from a claim at seventy days against a payer with a ninety-day one — and the aging report puts them in the same bucket and sorts them by balance. Days remaining, computed per payer, reorders the work in a way that days elapsed never will, and it is the sort that prevents the one loss that cannot be recovered afterwards.
Three dimensions to add
An aging report with three more columns stops being a summary and starts being a worklist:
- State. What the payer last said, in the payer's own terms: accepted, pending, denied with a reason, paid at an unexpected rate, or never acknowledged at all.
- Touch history. Whether it has been worked, how many times, and what the last touch produced. A claim touched three times with no change is a different problem from an untouched one and often needs a different person.
- Days remaining. Against the deadline that actually governs this claim, which for a secondary claim is frequently counted from the primary payer's remittance rather than from the date of service.
None of this means abandoning aging. Elapsed time is real, and the buckets are a reasonable summary for a client conversation. It is only as an instruction to a person about what to do next that the report is thin — and it is thin in a specific, fixable way. It describes the balance, and the work is decided by the claim.