AR Aging Analysis: Catching Shortfalls Before the Bank Statement Arrives

AR aging analysis gets used the wrong way at most companies. The standard report shows invoices grouped by how many days they have been outstanding: current, 1-30, 31-60, 61-90, over 90. Someone reviews it, sends collection reminders to the overdue ones, and files the report. This is backward-looking analysis used for a backward-looking process.

The more useful way to run AR aging is forward: not just what customers owe today, but when you realistically expect to collect it, and what that means for your cash balance over the next 30 to 60 days. That combination, AR aging projected forward against your cash runway, is what gives you time to act before a shortfall becomes a constraint.

Why Backward-Looking AR Review Fails Growing Companies

When a company has three customers and issues 15 invoices a month, backward-looking AR review works fine. The controller knows each customer's payment habits by memory, can tell which ones are slow payers versus which ones are genuinely delinquent, and acts accordingly.

When that company grows to 40 customers and 200 invoices a month, the same approach produces a report that is large enough to be overwhelming but not specific enough to be actionable. The 90-day bucket might have four invoices in it, but are they from customers who are disputing the charges, customers who are going through their own cash crunch, or customers who are simply negligent payers who will clear in a week if someone calls them? The aging report does not distinguish, so the team applies the same collection workflow to all of them and waits.

The cash impact of that wait is invisible until it materializes. By the time a 90-day invoice shows up as a problem in the budget variance, the window to prevent it has already closed.

Building a Forward Projection from Aging Data

A forward AR projection starts with the same aging buckets but adds a collection probability to each. The probabilities do not need to be precise to be useful. A reasonable starting estimate for a B2B software company with net-30 terms might look like this:

• Current (not yet due): 95 percent collected within 45 days
• 1-30 days past due: 85 percent collected within 30 days, 10 percent within 60, 5 percent write-off risk
• 31-60 days past due: 65 percent collected within 30 days, 20 percent within 60, 15 percent requiring active intervention or write-off
• 61-90 days past due: 40 percent collected with intervention, 30 percent disputed or requiring escalation, 30 percent at risk
• Over 90 days: case-by-case judgment, no simple probability applies

Apply those probabilities to the current aging report and you get a projected cash inflow schedule: expected collections in weeks one through four, weeks five through eight, and beyond. Stack that schedule against your known cash outflows (payroll dates, vendor payments, rent, debt service) and you have a 30-to-60 day cash picture built from real data rather than the prior month's actuals.

This is not a precise forecast. The probabilities will be wrong in individual cases. But it does not need to be precise to be useful. If the analysis shows a likely gap of $180,000 in week five because three large invoices are in the 31-60 bucket and one major vendor payment lands that week, you have roughly four weeks to address it. That four-week window is the entire value of the analysis.

The 30-Day Action Window

What can you actually do with a 30-day warning that you cannot do with a five-day warning? Quite a lot, depending on the gap size and your relationship with the parties involved.

On the collections side: you can make a personal call to the three or four customers whose invoices are driving the projected shortfall, before they are technically delinquent, to confirm payment timing and address any disputes early. Large customers often have their own payment processing cycles that your standard net-30 terms do not account for. A direct conversation four weeks out can result in a payment that nets-30 in reality rather than nets-45 or nets-60.

On the payables side: you can look at the vendor payments due in the same week and identify any that could be extended without damaging the relationship. Most vendors with whom you have a track record of on-time payment will accommodate a 10-to-15 day extension if you ask in advance rather than after missing the payment date.

On the balance side: if the gap is large enough that neither collections acceleration nor payables extension closes it, a 30-day window gives you time to draw on a revolving credit facility (if you have one), have a conversation with your bank about a short-term bridge, or make a deliberate decision to defer a planned spend category. None of those options are available when the shortfall is visible only five days before it hits.

Where This Analysis Breaks Down

We are not saying forward AR projection eliminates cash surprises. It does not. The projections depend on customer behavior that is not fully predictable. A customer that has always paid in 30 days can suddenly take 90 days during their own year-end freeze. A large invoice in a healthy aging bucket can be disputed after the projection was run, removing the expected cash entirely.

The analysis also depends on having clean, current AR data. If your accounts receivable aging is built from ledger entries that are two weeks out of date because reconciliation has not run, the projection is starting from a picture that does not reflect the current state. Payments that came in last week are not in the system yet. Invoices that were disputed and credited off last week still show as outstanding. The forward projection can only be as good as the data going into it.

This is the operational dependency that matters most: forward AR analysis is a useful tool for teams whose AR data is current, and a misleading one for teams whose AR data is a month behind. The mechanics of the analysis are straightforward. Getting the data current enough to trust the output is the harder part, and it is the prerequisite rather than the afterthought.

Integrating It Into a Regular Rhythm

The most effective way to run forward AR analysis is as a weekly review, not a monthly one. A monthly view gives you one chance per cycle to catch a gap; a weekly view gives you four. The time investment is not proportionally larger: once the model is built, updating it each week takes 20 to 30 minutes if the AR data is current.

The output of the weekly review is a single decision: is there anything in the next 30 days that requires action this week? If the answer is no, file it and move on. If the answer is yes, that specific item should be on someone's action list before the end of the day, not added to a general collections backlog that gets worked whenever there is time.

The goal is not to perfectly predict cash flow. The goal is to see shortfalls early enough that the response options are meaningful rather than desperate. Four weeks of lead time makes most shortfalls manageable. Four days makes most of them crises.