Accounts receivable: read it by age, don't rebuild it
Every week, someone rebuilds the receivables list by hand from two tools. The aging grid that replaces that spreadsheet, and what it should show in one minute.

By Jérôme Knops
Published November 6, 2026 · 4 min read

Reading your accounts receivable in one minute takes three numbers: the total outstanding, its breakdown by age, and the names of the clients who weigh the most in it. Most businesses have these three numbers somewhere, but never in the same place or on the same date: someone rebuilds them by hand, usually on Monday morning, so they mean something before Tuesday's meeting.
What a receivables view should answer in one minute
A business owner looking at accounts receivable wants four answers, not a fifty-line spreadsheet:
- How much is outstanding right now, in total?
- What share is still within normal terms, and what share isn't?
- Which two or three clients account for most of what's overdue?
- Is it improving or getting worse compared with last month?
As long as the balance is rebuilt by hand, those four answers only exist once a week, and they are already a little stale by the time anyone reads them: a payment received on Tuesday is still counted as overdue until the next export.
The aging grid
Classifying by age turns a list of invoices into a decision. Each bracket calls for a different action, and mixing them up is what wastes the most time.
| Age | What it means | The action |
|---|---|---|
| 0 to 30 days | Within normal terms | Leave it alone |
| 30 to 60 days | First delay | A written reminder, the same wording for everyone |
| 60 to 90 days | A settled delay | A phone call, not one more email |
| Over 90 days | Real risk | An owner's call: a commercial gesture, formal notice, or a provision |
The classic trap is treating all four rows the same way: chasing a hundred-and-twenty-day invoice by email achieves nothing, and calling about a fifteen-day invoice annoys a good client for no reason. The grid mainly stops you from confusing an invoice that just went out with one that will probably never get paid without a call from the owner.
Why the hand-built spreadsheet lies a little
Take a fifteen-person finishing trades contractor, invoicing around forty regular clients. On an ordinary Monday, its receivables sit around €180,000: a cautious assumption to illustrate the calculation, not a real figure.
That number is accurate on Monday morning, at the moment of the export. Over the next four days, a salesperson keeps granting payment extensions over the phone, a client pays by bank transfer that nobody reconciles right away, an invoice goes out late because the sign-off sheet wasn't signed yet. Monday's spreadsheet doesn't move: it stays the reference until the following Monday.
If fifteen percent of that balance sits beyond ninety days without anyone noticing before the quarterly review, that's €27,000 left without a timely decision, simply because the number that would have flagged it only existed once a week, already stale the next day.
What changes with an application built for the business
The receivables balance lives continuously in the application, because it comes from the same data as the invoice: as soon as an invoice is issued, it enters the balance; as soon as a payment is reconciled, whether from the bank or from the accountant's return, it leaves it. Nobody re-keys a line to keep the number right.
The aging classification happens on its own, as of today's date rather than the date of the last export. An owner opens the screen and sees the total, the share past sixty days, and the two or three clients carrying the most overdue amount. When a client crosses a threshold, an alert shows up on the right person's daily list, without waiting for the weekly meeting.
What an up-to-date balance doesn't replace
An accurate number doesn't decide anything on its own. Knowing that a client is past ninety days doesn't say whether to call firmly or give them two more weeks because they have ordered every month for ten years. That decision stays commercial, and it always belongs to a person, never to an automatic rule.
Accounts receivable: the key takeaways
A readable receivables view fits in four numbers: the total, the overdue share, the clients who weigh the most, and the trend. Classifying by age turns a list of invoices into different actions, from a simple reminder to the owner's own call.
Rebuilding that spreadsheet by hand every week only keeps the number accurate one day in five. Having it live from the same data as invoicing keeps it accurate every day, without adding a task for anyone. For the follow-up itself once the bracket is identified, the three-step grid for chasing an unpaid invoice takes over, and to understand what delays the invoice before it even enters the balance, the time between finishing the job and invoicing rounds out the topic.

Founder and CTO of Edenio
Jérôme Knops is the founder of Edenio, where he designs and builds custom business applications for construction, supply chain and distribution companies. He runs the scoping meetings, writes the code, and stays the person you talk to once the tool is in production.
See all their articles
Jérôme Knops
