Your AR aging report is a billing error log. Are you reading it that way?

Home care accounts receivable aging is one of the most-looked-at reports in any billing operation and one of the least-used. Most agency owners and administrators open the report, glance at the 90-plus column, and either feel relieved or feel sick. What they rarely do is treat the report as a map of what went wrong and when.

That is the shift that separates billing operations that recover most of their earned revenue from the ones that silently write off dollars every year in claims that aged past recovery. The AR aging report is a time-stamped record of every billing error in your last three months. If you know what each bucket means operationally — not just financially — you can use it to find the problems while there is still time to fix them.

What each aging bucket is actually measuring

Most AR aging reports in home care billing systems break outstanding claims into four buckets: current (0-30 days), 31-60 days, 61-90 days, and 90-plus days. Each one represents a different kind of operational situation, not just a different age.

0 to 30 days: normal processing lag

Claims in the current bucket are mostly just in transit. Medicaid and most managed-care payers run processing cycles that range from a few days to a few weeks depending on claim type, submission method, and payer. A clean claim submitted via EDI will often clear inside two weeks. A claim that hit a payer-side edit and needed manual review may sit in this bucket for the full 30 days before payment or denial arrives.

The current bucket deserves a quick scan but not alarm. What you are looking for here is any claim that should have cleared already — a payer that typically pays in 10 days and a claim that is already 25 days outstanding is worth a status check, but it is not yet a recovery situation.

31 to 60 days: where fixable problems first appear

This is the most important bucket for catching problems before they become permanent. Claims that have aged into the 31-60 range without payment have almost certainly received a denial or rejection that has not been addressed. The claim did not just get slow — something happened to it.

The most common reasons a home care claim lands in this bucket: an authorization mismatch that triggered a denial, an EVV data gap that caused a payer-side rejection, a service code or modifier error, or a coordination-of-benefits issue where the payer is waiting on primary insurance information. All of these are fixable. None of them require writing off the revenue. But they require action now, not next month.

The agencies that keep this bucket clean have a standing workflow: every claim that moves from current into 31-60 gets a denial code pulled, a correction path identified, and a resubmission date set — all within the same week it moves.

61 to 90 days: the window is closing

A claim that has reached 61-90 days without resolution has a problem that was not caught in the 31-60 bucket. That means a denial arrived and was either not worked, not worked correctly, or the first resubmission also denied and no one followed up. At this point, the claim still has a realistic recovery path — most payer appeal windows run 120 days from denial date, so there is usually time — but that path requires focused attention, not passive resubmission.

For authorization-related denials in this bucket, the question is whether a retroactive authorization is still available from the payer. For EVV-related denials, the question is whether the visit record can still be corrected and whether the payer's resubmission window is still open. For timely filing denials — where the claim simply did not go out within the payer's submission window — the revenue is likely gone and the claim should be written off rather than worked. Understanding which denial type you are dealing with changes everything about the action required.

90-plus days: a decision list, not a queue

The 90-plus bucket should not be treated as a backlog to work through on rotation. Every claim in this bucket needs a specific status: actively being appealed, waiting on retroactive authorization, in a formal payer dispute, or confirmed as uncollectible and ready for write-off. The difference between those statuses matters because the action required is completely different.

A claim being actively appealed needs a follow-up date and someone responsible. A claim confirmed as uncollectible needs to be written off cleanly so it stops inflating the AR balance and distorting the denial rate, which makes the report harder to read accurately for everyone else.

Reading the distribution as a diagnostic signal

The most useful thing you can do with an AR aging report is not to total the columns. It is to read the distribution of claims across the buckets as a signal about what kind of billing problems you have and how long they have been building.

If the 31-60 bucket is growing week over week, something is happening systematically to clean claims that is causing them to deny. That usually points to a recent change: a new payer requirement, an authorization process that got disrupted, an EVV implementation gap, or a service code update the agency has not caught yet. The pattern across claims — same denial code, same payer, same service type — tells you where to look.

If the 90-plus bucket contains claims spread across many payers, the problem is internal process, not payer-specific. Denials are being received and not worked. That is a workflow gap — either no one is pulling denial queues regularly, or the denial-to-resubmission process is slower than the appeal windows require.

If the 90-plus bucket is concentrated in one payer, there is a payer-specific issue. Either that payer has requirements your billing process is not meeting, or there is a contract or credentialing issue that is causing systematic denials. All of those require different fixes, but identifying the payer concentration is what makes them findable.

If the current bucket is unusually large, check whether claims are actually going out. A billing queue that is not being submitted, a clearinghouse connectivity issue, or a submission schedule that nobody verified after a billing system change — all of these can make the current bucket balloon while nothing is actually being paid.

The payer mix problem that distorts the report

One of the most common mistakes in reading home care AR aging is treating all payers the same. Medicaid fee-for-service has different processing timelines than managed-care Medicaid. Some managed-care organizations run faster cycles than others. A large balance in the 31-60 bucket for a payer that consistently pays in 45 days is less alarming than the same balance for a payer that typically pays in 14.

The agencies with the clearest view of their AR know their expected payment timelines by payer and use them as the baseline. When a payer that usually pays in 12 days has claims at 40 days, that is a specific signal — not just a number in a bucket.

Most home care billing systems can produce AR aging reports filtered by payer. If yours can, run that view alongside the aggregate. The payer-specific view tells you whether a growing bucket reflects a process problem, a payer-specific issue, or normal variation in the mix.

What unapplied payments do to the report

There is a category of AR inflation that has nothing to do with denial management: unapplied payments. These are payments the payer sent that were not correctly matched to the outstanding claim in the billing system. The claim shows as unpaid. The payment is sitting in a suspense account or posted to the wrong line. The AR report overstates what is actually owed.

Unapplied payments accumulate when ERA auto-posting fails, when payers send checks that require manual posting, or when billing system migrations disrupt the payment-to-claim matching logic. They are most common right after a payer changes their remittance format or after a billing system upgrade.

The way to find them is to compare what the payer reports as paid — which you can usually verify through the payer's portal — against what the billing system shows as received for the same remittance period. Any gap between those two numbers is either a posting error or a payment the payer says they sent that has not cleared. Both require investigation, not write-off.

Building a weekly AR review into the billing cycle

The agencies with the healthiest AR aging ratios do not run a review once a month. They run a focused scan every week — not a full audit, but a quick check that answers specific questions before the billing cycle closes.

The weekly review looks for three things: any claim that moved from 31-60 to 61-90 since last week and has no action assigned; any claim in the 90-plus bucket where the appeal deadline is within the next two weeks; and any payer where the total balance has grown significantly without a corresponding increase in recent submissions. Those three checks take 20 minutes and prevent most of the situations that turn fixable denials into permanent write-offs.

For a fuller picture of the billing gaps that feed the AR aging report in the first place — unbilled hours, EVV gaps, rate mismatches — the overview of where home-care margin leaks covers each category. For specifics on how claim denials work and what the recovery path looks like, the piece on home-care claim denials walks through the most common denial types and what each one requires to fix.