Aging Report Triage: Work Only the Claims That Can Still Pay

Every practice management system can print an aging report: every unpaid balance, sorted into columns by how long it has been unpaid. The report is easy to run and miserable to use, because it arrives as a flat list of every problem the practice has ever had, oldest failures mixed in with claims that are three weeks old and perfectly fine. Faced with two hundred rows, most owners either start at the top and burn an afternoon on the first twelve, or close the report and promise themselves a catch-up week that never comes. The fix is not more follow-up time. It is triage: deciding, before touching a single claim, which rows can still turn into money and which are already lost.

A to-do list implies every item deserves doing. An aging report makes no such promise. It is an inventory of outstanding balances in every possible state: claims a payer is still processing on a normal schedule, claims stuck behind a fixable error, claims denied and waiting on an appeal that has a deadline, patient balances nobody has invoiced, and balances so old or so small that collecting them would cost more than they are worth. Treating those as one queue means the order you work them is the order the report happens to print them — which is to say, random with respect to recoverable dollars.

Working accounts receivable well is therefore a sorting problem before it is an effort problem. A solo owner with ninety minutes a week can outperform a practice that "works the report" for a full day, if the ninety minutes land exclusively on claims where action changes the outcome. The three cuts below are how you find those claims.

The first cut is age, because age is where the deadlines live. Payer contracts set timely filing limits — a date after which a claim that was never submitted, or needs to be corrected and resubmitted, will be denied for lateness no matter how legitimate the service was. Denied claims carry appeal windows that close the same way. Medicare fee-for-service makes both concrete: claims must reach the contractor within one calendar year of the date of service, and a request for redetermination — the first level of appeal — must be filed within 120 days of receiving the remittance advice. Commercial and Medicaid limits differ by contract and state, and many are far shorter than Medicare’s. Age tells you which claims are approaching a cliff.

The second cut is payer, because unpaid claims cluster. When ten claims sit unpaid at the same payer with the same denial code, that is not ten problems; it is one problem expressed ten times — a lapsed authorization workflow, a credentialing gap, an eligibility check that stopped happening. Grouping by payer turns two hundred rows into a handful of patterns, and fixing the pattern collects the whole cluster at once. It also changes the phone math: one call to one payer representative can cover every claim in the batch, where row-by-row work would have made ten calls.

The third cut is dollars, and it is the one practices resist. Every claim costs roughly the same amount of staff time to chase — pulling the claim, checking status, calling, documenting, resubmitting. That cost does not scale down for small balances. A practice that spends twenty minutes of front-desk time pursuing an $18 copay is paying more to collect the balance than the balance is worth, while a $600 evaluation claim ages toward its filing limit unworked. Sorting each age-and-payer group by balance, descending, is the last cut: within any batch, the expensive claims get the attention first.

Run this as a standing weekly block, not a quarterly cleanup. Weekly matters for a structural reason: most of the deadlines in the previous section are measured in days, and a report reviewed monthly can silently carry a claim across its appeal window between reviews. The steps assume a report you can filter and sort; if your system can only print a static PDF, exporting to a spreadsheet first is worth the two minutes.

1. 01

   Pull the report and clear the noise first

   Export insurance and patient receivables, then remove what does not belong in follow-up at all: balances already paid but not yet posted, credits, and claims submitted within the payer’s normal processing time that show no error status. For Medicare, a clean electronic claim is not even payable until day 14, so a two-week-old claim with no rejection is not a problem — it is a claim. Filtering the current bucket out typically removes a third of the rows before any real work starts.

2. 02

   Flag everything approaching a deadline

   Before sorting by anything else, mark claims within roughly 60 days of a filing limit and denials within reach of an appeal window that is still open. These outrank every other row regardless of balance, because for them this week is different from next week. A $40 claim at month eleven of a twelve-month filing limit dies if it waits; a $400 claim at day 45 does not. This is the only step where small balances jump the queue.

3. 03

   Group the remainder by payer, then by reason

   Collapse the surviving rows into payer clusters, and within each payer cluster into the reason the money is stuck: no response, rejected at the clearinghouse, denied with a code, pended for records. Each cluster is one work item. Ten claims pended for the same documentation request are one records submission; ten claims denied for eligibility are one enrollment-date problem to resolve before touching any individual claim.

4. 04

   Order clusters by recoverable dollars

   Total each cluster’s balance and work the list in descending order. This is where the effort-to-value math gets enforced: a cluster worth $2,100 across nine claims gets the first phone call, and the $37 single-claim cluster gets whatever time is left, if any. Recoverable dollars — not row count, not age alone — decide the order once deadline risk is handled.

5. 05

   Work each cluster once, and document the exit

   For each cluster, take one action that moves every claim in it: a corrected batch resubmission, one payer call covering the full claim list (note the reference number), one records package, one appeal. Log what was done and the follow-up date the payer committed to, then stop. Chasing the same cluster twice in a week feels productive and changes nothing; the payer’s own clock has to run.

6. 06

   Decide the bottom of the report on purpose

   Whatever survives every cut — too old to file, appeal window closed, cost to collect above the balance — gets a decision, not another week on the report. Write it off with a reason code (timely filing, uncollectible small balance, appeal exhausted), and tally the reasons monthly. The write-off log is the practice’s most honest process-improvement document: every entry names the upstream failure that created it.

The 30-day columns on the report are not urgency levels — the deadline flags and clusters above set urgency. The buckets are diagnostic. Each one, read against how claims are supposed to move, points at a different kind of breakdown.

Three conditions end a claim’s life as a receivable. The filing limit has passed on a claim that was never successfully submitted, and no exception applies — Medicare, for instance, recognizes only narrow ones, such as contractor error or retroactive entitlement. The final available appeal has been decided or its window has closed. Or the balance is small enough that the staff time to pursue it costs more than it will return. A balance in any of these states is not an asset; it is a row of guilt on a report, and it makes every future triage session slower.

Losing it well means two things. First, the write-off is recorded with a reason, because an adjustment without a reason code is indistinguishable from money that leaked. Second, the reasons get read. A month of write-offs coded to timely filing is a follow-up cadence problem. A pile coded to uncollectible small balances is a time-of-service collection problem. A cluster coded to appeal exhausted on one denial type is a documentation problem that the denial-management workflow should be catching upstream. The write-off log converts dead claims into a to-do list for the living ones.

Triage decides what to do with the receivables you have; the front end decides how many you get. The three habits that shrink next quarter’s report are already covered in their own guides: verifying eligibility before the first visit so claims stop dying of enrollment surprises, posting every EOB promptly so the report reflects reality instead of unposted payments, and watching the cash-flow signals that tell you receivables are aging before the report does. A practice that does those three things finds its weekly triage getting shorter on its own — which is the only A/R metric that feels like anything.