An aging report read by bucket hides the story. Read by payer first, then by date of service rather than posting date, then split between insurance and patient responsibility, it names the specific breakdown causing the balance.
Most practices look at the aging as five columns of totals, note that the last one is bigger than they would like, and close it. The report contains far more than that, but not in the default view.
Read it by payer first
The aggregate is an average of very different behaviors. Split by payer and the picture usually resolves immediately: one or two payers account for most of the aged balance, and their reasons differ.
Aged workers compensation is often normal — those claims run on longer cycles. Aged commercial at the same age is a problem. The aggregate treats them identically and tells you nothing.
Then by date of service, not posting date
Date of service is what filing deadlines run from. An aging built on posting date can show a claim as young when its window is nearly closed, which is exactly the claim you most need to see.
Then split insurance from patient
They age for different reasons and require different work. Insurance A/R ages because something failed — a denial, a rejection, a coverage problem. Patient A/R ages because collection is slow, which is a different discipline with different tools.
Combined, they mask each other. A practice with healthy insurance A/R and a growing patient balance looks the same in aggregate as the reverse, and the fixes have nothing in common.
The three questions to ask each month
- Which payer holds the most aged balance, and why that one?
- What share of the over-90 bucket is still inside a filing or appeal window?
- How much of what is left is genuinely uncollectable and should be written off so the number stops lying?
Compare payers to each other, not to a benchmark
Your own payers under your own processes are the fairest comparison available. One payer aging materially worse than the others is a specific problem — a contract issue, a submission problem, or a payer genuinely slowing down.
That comparison is available in every practice and rarely made.
Watch the share past filing deadline
It should be close to zero. Anything else means claims are dying in the queue rather than being denied, which is a work-order problem rather than a payer problem.
This single figure is more actionable than the bucket totals it sits behind.
Review it with the people who work it
An aging read by the owner alone produces questions. Read alongside whoever works the queue, it produces explanations and a plan — and it surfaces the claims staff already know are hopeless but have no authority to write off.
Common questions
- How do I read an A/R aging report?
- By payer first, then by date of service rather than posting date, then splitting insurance from patient balances. Bucket totals alone tell you almost nothing actionable.
- Why use date of service instead of posting date?
- Because filing deadlines run from the date of service. An aging built on posting date can show a claim as young while its filing window is nearly closed.
- Why separate insurance from patient A/R?
- They behave differently and need different work. Blending them hides a growing patient balance problem behind adequate insurance performance.
- What questions should I ask of the aging each month?
- Which payer is worst and why, what share is past a filing deadline, and how much of the total is genuinely unrecoverable.
- Should unrecoverable claims stay in the aging?
- No. They inflate the asset and bury workable claims. Write them off so the remaining number is true and the queue is small enough to work.
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.