You know the scene. You open your invoicing tool for something else and there it is: an invoice twelve days past due. You think "I'll chase it tomorrow." Tomorrow brings a client call, a rush quote, a delivery problem. The invoice waits. Next week, it is still waiting.

The real cost of a reminder that never goes out

Every late payment you don't chase costs you three times. Time first: the longer the reminder waits, the longer it takes to write, because you have to rebuild the context, the history, what was already said or not. Cash second: the money exists, it is invoiced, it just sleeps in your receivables instead of funding your business. The relationship third: the longer the silence, the more unpleasant the follow-up becomes to send. Nobody started a company to play debt collector with their own customers.

Add those invoices up in your aging report, the table that sorts receivables by how late they are, and the total is almost always a surprise. Not because your clients are bad payers. Because the reminders never went out.

Why follow-ups don't happen (and why it's not your fault)

Laziness is not the cause. Accounts receivable follow-up is never urgent today: it can always go out tomorrow with no visible damage. So it loses, every single day, against the customer on the phone and the order that has to ship. That's mechanical. A task with no deadline always loses to the ones that make noise.

There is something more insidious. Every manual payment reminder email is a micro-decision: which client, what amount, how late, what history, which words. Too soft and you don't get paid. Too hard and you bruise a client you want to keep. That tone dilemma, multiplied by twenty invoices, wears people down. So the task gets postponed, and postponing is the most comfortable decision available.

Postponing a reminder is not a discipline problem. It's the rational response to a badly tooled task.

The problem is not you. It's the circuit: a repetitive, date-driven, tone-sensitive task left to the mental load of someone already saturated. Exactly the kind of process that belongs automated end to end, with a human approving instead of executing.

What AI actually does with an aging report

Automating overdue invoice reminders comes down to three verbs: sort, write in the right tone, pace. The human keeps the approval.

First verb: sort. The agent reads the aged receivables and classifies each invoice by how late it is. In my mechanism, four stages:

Second: write. For each invoice, the agent drafts a dunning email in the tone of its stage. Not a generic template with a first name injected. A text that knows the amount, the delay, the history. At day 3, something like "unless we're mistaken, this invoice probably slipped past your accounting." At day 45, more like "despite our two reminders left unanswered, we need a firm payment date." Those are style examples, not machine outputs, but the gap between them says what matters: the same tool does not speak the same way at day 3 and day 45. Same logic for a formal dunning letter when the stage calls for one.

The third, pace, is the most underrated. Late payment follow-up is a game of regularity, not intensity. A reminder that goes out at day 1, then day 15, then day 30 is healthier for the relationship than three months of silence followed by a furious email. The client knows where they stand. So do you.

The right reminder is not the harshest one. It's the one that leaves at the right moment, in the tone of that moment.

These reminders are one brick of something larger: AI-assisted sales administration, where the machine prepares and the human decides.

The demo: watch the agent sort and write

I could keep describing it. I put it online instead.

The invoice reminder demo runs this mechanism in front of you: a fictional aging report from a small company, the classification into four stages, then the reminder drafts, each in the tone of its stage. You read the emails, you watch the tone harden as the delay grows, and you see where the machine stops: at drafts. Nothing gets sent. In production, sending stays with a human.

Let me be plain about what you're looking at: the data is 100% fictional, companies, amounts and dates all invented. The mechanics are real. It's the same sorting engine and the same tone logic I wire into actual invoicing circuits.

The demo also shows a before/after time estimate, flagged on screen as an estimate. It rests on two assumptions: around 4.5 minutes to write one personalized reminder by hand, around 2 minutes to generate drafts for the whole report. Assumptions, not promises. The ratio between the two is hard to ignore though. And if you track DSO, the demo shows what a systematic cadence could claw back there too, flagged as an estimate as well.

A collections SaaS or a custom automation?

Fair question: dunning software exists, monthly subscription, similar promise. Here is how I frame the trade-off, including the cases where the SaaS wins.

Cost. A SaaS is paid monthly, forever. A custom automation is paid once, often the equivalent of a few years of subscription, then it's yours. But if you handle a heavy volume of unpaid invoices, need built-in legal recovery, and have nobody internally to own the topic, a specialized SaaS is entirely justified.

Tone. A vendor's templates sound like a vendor. A custom automation writes in your company's exact voice, and every email goes through your approval. In anonymous, high-volume B2C, honestly, templates are enough.

Integration. Custom plugs into the invoicing tool and mailbox you already run. A SaaS asks you to move your data into its world. And before either one: if your current invoicing tool already ships a decent reminder module, switch it on first. No reason to pay anyone, me included.

Adoption. One more tool means one more password, one more training session, one more tab nobody opens. With custom, the drafts land in the mailbox your team already lives in. On the other side, if your primary need is a turnkey reporting dashboard, a SaaS gives you one on day one.

My part in that decision fits in a short, fixed-price scoping: looking at your actual circuit and telling you which of these scenarios applies, including when the answer is "buy nothing."

Where to start

Not with a purchase. Not with a project. With a question: how much is sleeping in your aging report right now? If you can't answer in under a minute, that's already information. It usually means nobody owns the number, which means nobody owns the follow-up either.

The first step is a conversation about your real invoicing circuit: where invoices are born, who chases today, where it stalls. Thirty minutes is enough to know whether the topic is worth it for you. Write to me here, and if you'd rather watch the mechanics run first, the demo is open, no signup.

Your payment terms won't shorten themselves. The reminders, though, can write themselves.