It is the twelfth of the month. Someone has exported the outstanding list out of Tally, pasted it into a spreadsheet, and mailed it to four people with the subject line “Pending payments urgent”. The file has nine hundred rows. Two of them are from 2023. Nobody replies to the mail. Next month the same file goes out, slightly longer.
That is the normal fate of an invoice ageing report in a small Indian business. Not that it does not exist. It exists. It is just unreadable, unowned, and therefore harmless. Meanwhile the 90-plus column grows by one invoice a week, quietly, and nobody notices until a quarter ends and cash is short.
This is about making the ageing report small enough to read, structured enough to act on, and attached to named people who look at it on a fixed day.
Why nobody reads the ageing report you have
Three reasons, and they are all fixable.
The first is size. A report with nine hundred rows is not a report, it is a database dump. Nobody can hold nine hundred decisions in their head, so they make none.
The second is that it is sorted wrong. Most exports come out sorted by customer name or by invoice number. Neither of those is a priority. The only sort order that matters for collections is how old the money is, and after that, how much of it there is.
The third and worst reason is that the report has no owner. It goes to Accounts, Sales, the founder and one project manager. Four recipients means zero owners. Everyone assumes the person closest to the customer will handle it, and the person closest to the customer assumes Accounts is chasing because Accounts sent the mail.
So the invoice ageing report becomes a monthly ritual of information transfer with no decision attached. The number at the bottom right goes up. Everyone has seen it. Nothing happens.
Four buckets, and what each one actually means
Start by collapsing the report into four buckets, measured from the invoice due date and not the invoice date. This distinction matters. If your terms are thirty days net, an invoice raised on the first and due on the thirty-first is not overdue on the fifteenth. Ageing from the invoice date makes half your report look like a crisis and trains people to ignore it.
The four buckets:
- 0 to 30 days overdue. Administrative. The invoice is probably sitting in someone’s approval queue, or the GST details did not match, or the purchase order number is missing. Almost nothing here is a dispute. It is paperwork.
- 31 to 60 days overdue. Slipping. The customer has the invoice, has not objected to it, and has not paid. This is where a normal ninety-day payment culture and an actual problem look identical, which is exactly why this bucket needs attention rather than patience.
- 61 to 90 days overdue. At risk. By now there is usually a reason, and the reason is one of three things: a scope dispute, a cash problem at the customer’s end, or an internal contact who has left. All three need a different response, and all three need a human conversation rather than a reminder mail.
- 90-plus days overdue. Recovery. Treat this bucket differently from the other three. It is not a follow-up problem. It is a decision problem. Every line in here needs a written decision: escalate, settle at a reduced amount, put on a payment plan, or write off.
Four buckets is the right number because it maps to four different actions. Six buckets is precision without purpose. Two buckets, current and overdue, is too coarse to prioritise.
One more rule. Every line in the report carries the last contact date and a one-line status note. An ageing report without a last-contact column tells you the money is old. It does not tell you whether anyone has done anything about it, which is the only thing you actually want to know on a Monday morning.
One named owner per bucket
Here is the change that does most of the work: assign one person to each bucket, by name, and write it down where everyone can see it.
Not one person for all collections. Bucket owners, because the four buckets need four different skills.
- 0 to 30 goes to whoever raises the invoices. It is documentation chasing. The person who created the voucher is the person who can fix a wrong GSTIN or a missing PO reference in ten minutes.
- 31 to 60 goes to the account or relationship owner, usually someone in Sales. The customer still likes you at this stage. A call from a familiar voice works better than a reminder from an unfamiliar one.
- 61 to 90 goes to Accounts or a dedicated Recovery person. This is the bucket where you need someone comfortable asking an uncomfortable question and getting a date in writing.
- 90-plus goes to one senior person, and only one. A partner, the finance head, or the founder in a smaller firm. Decisions in this bucket cost money either way, so they belong to someone who can approve a settlement without a meeting.
BizvoraOne separates Accounts and Recovery as distinct roles for exactly this reason. They are not the same job. Accounts is concerned with whether the invoice is correct and recorded. Recovery is concerned with whether the money arrives. When one person carries both, Recovery loses, because reconciliation has a deadline and chasing does not.
Write the four names on a single line and pin it in the group. If a name has to change, change it and say so. What kills this system is quiet reassignment, where a person leaves and their bucket goes unowned for two months.
The fifteen-minute Monday ritual
Once a month is too slow. Ninety days is thirteen weeks, so a monthly review gives you three chances to catch an invoice before it enters the worst bucket. A weekly review gives you thirteen.
So: fifteen minutes, same time every Monday, four bucket owners plus whoever runs the meeting. Standing, on a call, on a shared screen, it does not matter. What matters is that it is short, fixed, and never skipped.
The agenda has four questions and nothing else:
- What moved into 90-plus this week? This is the first question, every week, without exception. If nothing moved in, say so out loud. If something did, the 90-plus owner takes it and says what the decision will be by next Monday.
- What moved out of each bucket? Collected, settled, or written off. Name the invoice and the amount. This is the only part of the meeting that feels good, so do not skip it.
- What is stuck with no contact in fourteen days? Sorted oldest contact first, not largest amount first. An invoice nobody has touched in a fortnight is the one that ages past ninety days.
- What needs a decision from someone not in this room? Usually a discount approval, a legal notice, or a hold on further work for that customer. Capture the name of the decision-maker and the date you need the answer.
Fifteen minutes is enough for this if the report is already sorted and the notes are already written. It is not enough if the meeting is where people first look at the data. Bucket owners update their own lines before Monday. That is the deal.
The outcome is not a longer list of tasks. It is a short list of promised dates, each with a name against it. What you chase next week is the promise, not the invoice.
What “actioned” means, precisely
Teams cheat on this without meaning to. Someone sends a WhatsApp message saying “Sir, kindly release payment” and marks the line as followed up. Nothing has happened.
Define actioned as all four of these:
- You spoke to a person, or received a written reply from one. A message that was delivered and not answered is not contact.
- You have a specific reason the invoice is unpaid, or a confirmation that it is scheduled.
- You have a date. Not “next week”, a date.
- The date and the reason are written on the invoice record, not in a private chat.
If any of the four is missing, the line stays open and appears again next Monday. This is also where the tone of your chasing matters, and there is a difference between persistence and nuisance. If you have not set one out yet, a follow-up cadence that keeps you persistent without being annoying is worth writing down before the Monday ritual starts.
The other common failure is upstream. Ageing reports go wrong when the invoice does not match what Sales actually sold, because scope changed and the books never heard about it. Those disputes surface in the 61 to 90 bucket as “customer says amount is wrong”, and they are expensive to unwind. Keeping your pipeline and your books pointing at the same version of the deal removes a good share of that bucket entirely.
When this does not apply
If your business is largely advance-paid, retail, or subscription-billed with auto-debit, you do not need four buckets and four owners. You need one person watching failed payments. Do not build a collections structure for a problem you do not have.
If you have fewer than about thirty open invoices at any time, run one bucket owner and a five-minute Monday check. The four-bucket split earns its keep when the report is long enough that priority is genuinely unclear.
And if a large share of your receivables sit with government or large-enterprise buyers on fixed payment cycles, ageing past ninety days is often structural rather than a collections failure. Report those separately. Mixing them into the same 90-plus column makes the bucket look permanent, and a bucket that looks permanent gets ignored.
What to do first
Do not redesign your accounting setup this week. Do one thing.
Pull the current outstanding list, sort it by days past due date, and split it into the four buckets. Then delete the columns you will not read. You need customer, invoice number, amount, days overdue, last contact date, and status note. That is six columns, and the report will fit on one screen.
Then write four names against four buckets and send that single line to the people concerned. Put fifteen minutes on Monday in everyone’s calendar and hold the first one this week, even if half the notes are missing. The first meeting is always poor. The third is useful.
If your vouchers already sit in the Accounting and Recovery module in BizvoraOne, the ageing view and the role-scoped dashboards will do the sorting for you, which means the Monday fifteen minutes goes on decisions rather than on building a spreadsheet. But the discipline comes first. A well-structured invoice ageing report that nobody owns is still just a file in someone’s inbox.
