Stop Doing Collections From Memory: Automating Your Receivables

Ask most business owners who owes them money and they will name the two customers they are currently annoyed with. Ask about the other eleven and the room goes quiet. That is collections from memory, and it produces the same result everywhere: the loud invoices get chased, and the quiet ones get old.

The customers who never argue are the ones costing you

Memory chases by emotion, not by exposure. The buyer who disputed a line item is top of mind. The one who said "it's with finance" back in July, politely, and has said nothing since, is not, and their ₦1,800,000 has been sitting in your 90-day bucket ever since. Nothing about that customer creates a reminder, so nothing reminds you.

The second failure is timing. Chasing when you remember means chasing at random: sometimes on day three, sometimes on day sixty-two. Invoices are most collectable in the first two weeks after the due date, while the work is fresh and the buyer still feels the obligation. Miss that window and you are negotiating with someone who has mentally closed the job.

What to automate

Automate anything that is a rule rather than a judgement. Four things carry most of the weight.

1. Reminder schedules, before and after the due date. A note three days before the due date is not chasing, it is service, and it catches the invoices that were simply forgotten or never approved. After the date, a fixed cadence at roughly day 3, day 10 and day 21 does the work. Our reminder email templates cover what those should actually say.
2. Aging that recalculates itself. A spreadsheet ages only on the day you update it, which is why the numbers in it are always a bit optimistic. Aging should move on its own overnight, so an invoice crossing into the 60-day bucket becomes visible without you noticing it first. Start with what an aging report is if you have never used one.
3. A prioritised chase list. Ten minutes on the ₦3,000,000 invoice at day 45 is worth more than an hour on the ₦120,000 one at day 5. Sorting by amount and by risk is arithmetic, and arithmetic is exactly what you should not be doing from memory at 9pm.
4. Escalation triggers. Decide once what happens at 30, 60 and 90 days: the tone hardens, the call replaces the email, the account goes on stop. Written down in advance, escalation is policy. Decided in the moment, it is a mood, and it lands unevenly across customers.

Automation is not there to be clever. It is there to make sure the boring, repetitive, easily-forgotten steps happen on the day they should, to every customer, including the ones you like.

What to keep human

The difficult conversation is yours. When a customer is genuinely struggling, or angry, or has gone silent, no sequence of emails will fix it. A phone call from a person will, or at least it will tell you the truth, which is what you actually need before you decide whether to keep supplying them.

The payment plan is yours too. Splitting ₦4,000,000 into four monthly payments is a commercial decision with real risk in it, and it depends on things a tool cannot see: how much you need the customer next year, whether their business is actually recovering, whether they have honoured a plan before.

So is the relationship. Your biggest customer should never feel like they are being processed. Automation should handle the routine so that when you do pick up the phone, you are calling about something that matters, not about an invoice that was only ever waiting on a PO number.

Where automation does not help

It will not make a broke customer solvent. Reminders can move a payment forward in a queue, but if there is no money in the account, a perfect eight-step sequence changes nothing. Recognising that early and moving to a plan or to recovery is worth more than another email.

It will not rescue a 180-day invoice. By then the work is a memory and the goodwill is gone. Automation is a defence against invoices getting old, not a cure once they have.

And it will not fix terms you should never have agreed to. If you are on Net 60 with a customer who then takes another 30 days, the problem sits upstream of collections, in what you agreed to before the job started. No reminder schedule can undo that.

Letting the system remember

Arvalox is built to hold the part you should not be holding in your head: it ages every invoice automatically, ranks who to chase first by amount and risk, and sends AI-assisted reminders before and after the due date so the quiet customers get the same steady follow-up as the loud ones. What it deliberately does not do is take the hard call off your desk. That one is still yours, and it should be.