An aging report nobody acts on is a report you do not need. Which cut turns it into a list of actions, what to take out of it, and how often to look.
Key takeaways
- A report that does not end in a list of names to call is not a collections report.
- Sorting by age alone floats old small debts to the top and hides large fresh ones.
- The cut that works combines amount, age, and what has already been done.
- Disputed debt is not overdue debt, so it does not belong on the same list.
- The right cadence is weekly, because monthly finds out too late.
An aging report exists in almost every system, and most businesses look at it once a month, nod, and close it. The problem is not the report but the cut: a table sorting debt into day ranges says what the position is and does not say what to do tomorrow morning.
Why the standard report does not work
The classic report splits into 30, 60, 90 and over. It is accounting-correct and operationally useless, for two reasons. The first: it is sorted by age, so at the top of the list sits a 340-shekel debt from two years ago that nobody will collect, while a 40,000 debt that went overdue last week sits tenth.
The second: it does not know what has already been done. A customer who received three reminders and one who received none look identical in the table, so the action derived from them will be identical - which is exactly why the report produces the same reminders resent to the same people.
The cut that turns it into a task list
| The cut | What it surfaces | The action |
|---|---|---|
| Debt above a material amount, over 14 days late | Few rows, most of the money | A phone call today |
| Overdue debt untouched for 10 days | Things falling between chairs | A first or second reminder |
| A customer with more than one overdue invoice | A pattern, not an incident | A conversation about conduct, not about an invoice |
| Debt over 90 days with no response | Stuck files | A decision: escalate or take off the list |
| Disputed debt | Noise | Remove from the report, manage separately |
The rule behind the table: every row in the report has to answer who does what tomorrow. If no action follows from a row, it should not be there.
Why disputed debt comes out
This is the change that makes the biggest difference and is also the least intuitive. An invoice the customer disputes - a wrong amount, a service not delivered, a credit that was promised - is not a collections problem but an open sales or service problem, and sending a reminder about it does harm: it signals that nobody listened, and it will not be paid anyway.
What works is a separate status. The debt stays in the accounting record, leaves the action list, and gets an owner and a target date for resolving the dispute. Once the dispute is closed it returns to the list - and a reminder about it is then entirely reasonable.
What using it looks like in practice
- Once a week, on the same day, run the report on the defined cut.
- Go down the rows and assign an action to each one.
- Update the last-contact date on every row handled.
- Mark disputed debts and move them to the second list.
- At the end of the pass, count how many rows entered and how many left since last week.
Step 3 is the condition for all the rest. Without a last-contact date, next week's report will be identical to this week's, and there will be no way to know whether you worked or merely looked.
What the report is missing to be usable
Beyond the cut, three fields are absent from nearly every standard aging report, and adding them is what separates a table from a working tool:
- Last contact date - when this customer was last spoken to about the debt.
- Type of last contact - an automated reminder, a personal email, or a call.
- Open promise - if the customer named a date, what that date is.
- Status - current, overdue, disputed, on an arrangement.
- Owner - who is responsible for this customer in collections.
- Amount on an arrangement against amount open - where there is a payment plan, the total row misleads.
The third field produces the quickest result. A customer who promised to pay on Wednesday and did not is the easiest call in the world - there is a reason, there is a date, and there is no need to rehearse what the debt is. Without that field the same call starts from scratch every time.
What matters is not adding all of them at once. The first two alone produce most of the improvement, and each extra field costs time to fill - and a field nobody fills is worse than a field that does not exist.
The two numbers worth more than the report
Beyond the list itself, two numbers say whether collection is improving. The first is the average days from invoice issue to payment - not the average of open debt, but of what actually got paid this month.
The second is the share of debt over 60 days out of total open debt. It matters more than the absolute figure because it measures quality rather than volume: a growing business will see open debt grow even when everything is fine, and that ratio will stay flat. When the ratio climbs, something in the process has broken - usually well before cash flow feels it. The full background on generating the actions themselves is in an orderly receivables collection workflow.
What to do with old debt that will not be collected?
How long to keep trying is a business decision, and how a bad debt is handled in the books is a question for the accountant. What is purely operational is that the decision be made explicitly: a debt nobody intends to collect and which never leaves the list contaminates every future report and produces a standing sense of failure.
The simple procedure: once a quarter go through everything over 90 days and decide on each row - escalate, reach an arrangement, or take it off the action list. Three options, one decision, and then the report is clean.
Sources
Frequently asked questions
How often should you look at the report?
Weekly for the action list, monthly for the two numbers. Monthly alone is too late: a debt going overdue at the start of the month is handled only four weeks later, and that is exactly the window in which a reminder still works easily.
Should the report be run by customer or by invoice?
Both, for different uses. The action list works by customer - because you call a person, not an invoice - and the check of what exactly is open happens by invoice, inside the call.
What counts as a "material amount"?
It varies between businesses, and a practical definition is the amount that would make you stop what you are doing to pick up the phone. If there is no such amount, the first cut in the table is redundant and you can work by age alone.
Are automated reminders worth it?
For small, fresh debts, yes - that is exactly where automation saves time without harming the relationship. For large or old debts, an automated reminder replaces a conversation that needs to happen, so it postpones the resolution.
Keep reading
Related service
Dashboards
One screen with the few numbers that actually change a decision.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.