Skip to content
AcademyBy ··6 min read

AR ageing report: read the numbers that matter

Use an AR ageing report to prioritise overdue invoices, find disputes early and make a realistic weekly collections plan.

Accounts receivable ageing buckets from current to 90 days overdue
Photo by Mikhail Nilov on Pexels

An accounts receivable ageing report groups unpaid invoices by how far they are from their due date. It is the page to open before an average metric, because it names the balances and customers behind the number. A thin 90+ bucket can be more urgent than a much larger current bucket, particularly for a small business that cannot afford a surprise.

Quick answer. accounts receivable aging report is most useful when it produces one decision for this week, not another report to admire.

Use buckets to choose work

Keep current, 1–30, 31–60, 61–90 and 90+ days separate. Then sort each bucket by balance and promise date. A £20,000 invoice at 61 days with no reply deserves a named owner today. A £200 invoice at day 10 may simply need the purchase-order number resent. The report tells you where to look; judgement decides the next move.

Separate disputes from slow payment

A disputed invoice should not disappear into a generic overdue bucket. Mark the reason, person responsible and next resolution date. The finance task may be a credit note, proof of delivery or a corrected VAT field, not another reminder. Keeping that distinction protects the relationship and makes the collections queue honest.

Make it a short meeting

Review ageing for 15 minutes every week. Read the biggest changes, agree actions and record promised payment dates. No long deck required. The point is to prevent invoices becoming archaeological finds in somebody’s inbox.

Start with the record, not the assumption

Before acting on accounts receivable aging report, pull the small set of records that would let another person reach the same conclusion: the original agreement or policy, the invoice or transaction history, the current balance, and the dated messages that explain what has happened. Put them in chronological order. This sounds prosaic, but it prevents the common failure mode where a tidy-looking dashboard hides a missing credit note, a changed contact, or a promise already made by someone else. Keep the raw figure alongside the definition used to create it. If a number is based on a period, write down the start and end dates. If a term starts after acceptance rather than on an invoice date, record that too. The point is not to create paperwork for its own sake. It is to make the next action fair, explainable and easy to revisit when a customer, colleague or adviser asks how you got there.

Work through use buckets to choose work

Treat the first pass as a controlled check rather than a grand clean-up. Choose a recent, representative slice of work: perhaps ten open invoices, one customer account, or the last ninety days of credit sales. Reconcile the total against the system of record, then inspect the exceptions one by one. A useful note names the owner, the last contact, the stated obstacle and the next date to review it. That level of detail beats a vague label such as “follow up”. It also reveals whether the problem is operational: an invoice sent to the wrong portal, an absent purchase-order number, a query that nobody acknowledged, or a reminder that was drafted but never delivered. Once those facts are visible, use accounts receivable aging report to choose one proportionate next step. Do not change a whole policy because of one awkward case; correct the cause, then see whether the pattern repeats.

Use separate disputes from slow payment to decide what changes

A practical decision should have an owner and a deadline. For example, if the evidence shows that invoices routinely become stuck before approval, the fix may be a pre-due check asking whether a portal upload, purchase order or supplier form is missing. If the evidence shows a genuine commercial disagreement, pause the disputed part and keep the undisputed amount visible. If the data is sound and there has simply been no response, move to the next documented message in the sequence. Keep the wording calm and specific: invoice number, amount, due date, payment route and a clear reply date. It is tempting to make an exception feel like a negotiation about the relationship. Usually it is better to make the process predictable, then reserve human judgement for the cases that really warrant it. That leaves customers knowing what to expect and gives the team a defensible record of what happened.

A realistic monthly check

Imagine a small services business reviewing its ledger on the first working Monday. One invoice is a few days beyond terms because the buyer’s accounts-payable contact has changed. Another is older, but the customer has made a recorded part payment and agreed a date for the rest. A third is large enough that the founder wants to approve any firmer wording. These are three different jobs, even though all three appear as overdue. The first needs a corrected contact and a short reminder. The second needs a diary entry and a check on the promised date. The third needs a factual handover containing the agreement, delivery evidence and previous messages. This is why an ageing number, template or software feature is only useful when it turns into a visible queue. The queue gives people a way to act without guessing, while still leaving space for an exception that deserves care.

Make make it a short meeting repeatable

Set a cadence that is modest enough to keep. A weekly review of new exceptions and a monthly review of the headline measure will usually tell a small team more than a frantic quarter-end scramble. Save a brief note on what changed: a corrected term, a recovered payment, a disputed invoice, a customer who needed a different route, or a rule that created needless noise. Review that note with the person who owns sales or delivery as well as finance. Collections, cash flow and customer experience overlap; handing the issue to a single inbox can make a recurring process failure look like an individual debt. The related guides on payment terms, DSO and escalation are useful cross-checks when you want to test the surrounding process rather than chase one balance harder.

  1. Check the source record. Confirm the amount, dates, terms and contact before a message or calculation is created.
  2. Classify the exception. Separate missing administration, a real dispute, a promised payment and a silent overdue balance.
  3. Choose the smallest sensible step. Make payment or a useful reply easy, and keep consequential escalation with an accountable person.
  4. Record the outcome. Save what changed and when it will next be reviewed, so the next colleague does not need to reconstruct the story.
Illustrative prioritisation view.
BucketQuestionTypical next action
CurrentWas it received?Pre-due check
1–30Is there a payment date?Friendly reminder
31–60Is anything disputed?Owner call
61+Do we escalate?Formal review

A practical next move

Use a fixed weekly export or dashboard view. If the 60+ total grows two weeks running, investigate the cause before it becomes a write-off conversation.

Questions people ask

What is an AR ageing report?

A list of unpaid receivables grouped by the number of days before or after their due date.

Which ageing bucket is most risky?

Usually the oldest unpaid and undisputed balances, but value, customer context and collectability matter too.

How often should I review it?

Weekly works for many small teams; higher-volume books may need daily exception review.

Sources and limits

This guide is general operational information, not tax or legal advice. Check the contract, the governing jurisdiction and your accountant before relying on a debt, fee or tax treatment. Useful primary references: IRS Publication 334, SBA cash-flow guidance, NIST API protection guidance.

See your own buckets without building a spreadsheet first.

Generate an ageing report

Stop doing this by hand

Duebay runs the escalation described here on a schedule: import your open invoices, and every overdue one gets chased from friendly nudge to final notice without you writing another email.