US Medical Billing
A/R & Follow-Up

What an A/R Aging Bucket Hides

An A/R aging report answers exactly one question: how long has this been outstanding. It is then asked what is at risk, who is late, what to work, and how much will be collected — and it cannot answer any of those without being cut by something other than time.

Updated 8 min read

On this page

Key takeaways

The buckets are a convention

The familiar column widths are inherited from general accounting practice, not from anything in healthcare. No standard adopts them, no payer's behavior changes at their boundaries, and nothing happens to a claim when it crosses one except that it appears in a different column of a report.

That is worth saying because the boundaries acquire a moral quality they have not earned. A practice comes to treat one column as acceptable and the next as failure, and then manages toward the report. The useful boundaries are the ones that mean something for the practice's own payers — a threshold set where that payer's claims have usually finalized, and a threshold set where a filing or appeal window starts to be at risk. Both of those are derived from the practice's own data and from its contracts, and neither is likely to land on a round number.

Keep the conventional report if the ledger needs it

Which date the clock starts from is a choice

Before any bucket means anything, something has to define day zero, and there is more than one defensible answer. Each produces a different report from the same underlying accounts, and a practice comparing its aging to anyone else's — or to its own, across a system change — is often comparing two different measurements.

Three common start points for the aging clock, and what each measures.
Three common start points for the aging clock, and what each measures.
Clock starts atWhat the report then measuresWhat it obscures
Date of serviceTotal elapsed time from the encounter — the patient's-eye view, and the one that includes the practice's own delay in billing.Whether the delay is the payer's or the practice's. A charge that took two weeks to bill starts life two weeks aged.
Bill or submission dateHow long the claim has been with the payer — the follow-up view, and the one that isolates payer time.The billing lag entirely. A practice with a charge-capture problem can show a healthy aging report.
Last activity on the accountHow long since anything happened — useful for finding accounts nobody has touched.Total exposure. An account touched last week looks new however long it has actually been open.

None of the three is wrong; using one and describing it as another is. The billing-lag question the first two separate has its own measure in charge lag, which is worth reading beside the aging rather than inside it.

Re-aging is the one that produces a wrong answer, not a partial one

What one bucket mixes together

A single aging column is a population defined by one attribute — elapsed time — and populations defined by one attribute are heterogeneous in every other. Three of those mixtures matter enough to separate before the report is used for anything.

Payers with different normal speeds
Two claims in the same column can be one that is unremarkable for its payer and one that is badly overdue for its own. Cutting the aging by payer is the single change that converts the report from a description into a signal, because it lets each payer be compared to its own behavior rather than to a shared boundary.
Reasons that require different actions
Age says nothing about why an account is open. A claim in process, a claim the payer has no record of, a claim awaiting an attachment, and a claim finalized to a balance nobody posted are four different jobs sitting in one column. Age finds them; only status decides which is which.
Insurance A/R and patient A/R
These are two different books with different collection mechanics, different aging behavior, and different meanings for the same number of days. Reported together, movement in one masks the other — and the patient side ages differently by design, because a statement cycle is a sequence rather than a wait.

“Over 90” is a mixture, not a finding

Age is not a test of collectibility

The most consequential misreading of an aging report is that the old columns are the uncollectible ones. Age is correlated with difficulty and is not the criterion — and the clearest written statement of what the criterion actually is sits in a place worth borrowing carefully.

Medicare's rules on provider bad debts (opens in a new tab) set out what makes a debt allowable, and the criteria are about effort and judgment rather than about time: the provider must be able to establish that reasonable collection efforts were made, similar to the effort put forth to collect comparable amounts from non-Medicare patients; the debt must have been actually uncollectible when claimed worthless; and sound business judgment must have established that there was no likelihood of recovery at any time in the future. Elapsed time appears nowhere in that list.

Read that as a description, not as a rule you are under

The practical version: an aged account is a candidate for a decision, and the decision is either that it is still worth working or that it is not. Both are dispositions, both need a reason recorded, and neither follows automatically from the column the account is sitting in. Designing an A/R follow-up process covers the process that makes those decisions rather than letting a queue make them by default.

Three cuts that make the report usable

None of the above argues for abandoning aging. It argues for adding the dimensions that make an aged account actionable, and there are three that do most of the work.

  1. By payer, always

    So each payer's aging is read against its own normal behavior rather than a shared boundary. This is the cut that turns the report from a description of the book into a signal about a payer, and it is usually one grouping away.
  2. Insurance separately from patient

    Two books, two mechanics. Reported as one number, a good month on one side hides a bad month on the other, and neither trend is legible.
  3. By time remaining, not only time elapsed

    The question an aged claim actually raises is how long is left — to a filing window, to an appeal window, to the point where recovery stops being realistic. A view sorted by remaining time puts the recoverable-but-nearly-lost accounts at the top, which is where a follow-up process needs them, and no aging bucket will ever surface them.

Work the shape, not the number

Common questions

What are the standard A/R aging buckets?

There is no standard, and that is the point of this article rather than an evasion. The familiar column widths come from general accounting practice; nothing in healthcare adopts them, and no payer's behavior changes at their boundaries. Keep the conventional view if the ledger or a lender reads it, and build the operational view on boundaries that mean something for your own payers — where that payer's claims usually finalize, and where a filing or appeal window starts to be at risk.

Should aging run from the date of service or the date we billed?

Both are defensible and they measure different things. From date of service you get total elapsed time, including your own billing delay; from the bill date you get payer time in isolation. The error is not choosing one — it is using one and describing it as the other, which is how a practice with a charge-capture problem ends up reading a healthy aging report. Whichever you use, keep the billing lag visible separately.

Our oldest bucket keeps growing. What does that tell us?

On its own, almost nothing, because that bucket is a mixture: genuinely stuck claims, genuinely uncollectible ones, patient balances on payment plans, and anything the system re-aged incorrectly, in unknown proportions. Split it by payer, by reason, and by insurance versus patient before drawing a conclusion. Growth concentrated in one payer is a payer signal; growth spread evenly is usually a capacity or process signal.

Can we write off everything past a certain age?

Age is not the test, and a policy of that shape converts a judgment into a default. The clearest federal statement of what makes a receivable uncollectible turns on reasonable collection efforts that can be established, the debt being actually uncollectible when treated as worthless, and sound business judgment that there is no likelihood of recovery — none of which is elapsed time. A threshold can reasonably decide when an account gets a decision; it should not be the decision.

Authoritative sources

Ready to improve your revenue cycle?

Tell us about your practice and we’ll tell you where we would start.