Home About Experience Projects Case studies Resources Articles Briefs Playbook Tools FAQ How we start Security Get in touch

Finance automation

Automated Receivables Chasing That Stops When the Invoice Is Paid

Late payment is the normal condition in B2B, not the exception. Most small businesses chase manually, inconsistently, and only after the due date has already passed. Here is the ladder that works and the one check that makes it safe to automate.

Late payment is not an exception in business-to-business work. It is the normal condition, and the numbers are worse than most owners assume.

Atradius, a trade credit insurer, publishes an annual Payment Practices Barometer. Its 2025 North America edition found that 55 percent of all business-to-business invoiced sales in the United States were overdue, that only 52 percent of invoices were paid on time, and that 43 percent of the total value of credit sales was overdue.

Against that backdrop, most small businesses chase manually, inconsistently, and late.

THE LADDER, AND THE STEP EVERYONE SKIPS 7 days before confirm it is approved and scheduled Due date polite nudge +7 days direct, with the invoice +21 days a person calls +45 escalate The first step is the one that works, and the one almost nobody automates.
Figure 1: contact before the due date catches invoices stuck in an approval queue, while it is still an admin question rather than a payment dispute.

Why the first rung matters most

Every reminder ladder you will find online starts on the due date. That is a mistake, and it is the single most valuable change in this article.

A short, friendly message seven days before the due date confirming the invoice is approved and scheduled catches the largest single category of late payment: invoices sitting unapproved in somebody's queue. At that point it is an administrative question with a helpful answer. After the due date, the same conversation is a payment problem with an apology attached.

Most invoices are not late because the client will not pay. They are late because nobody on their side moved them along, and nobody on your side asked while asking was still easy.

How to build it

1. Get your ageing data accurate first

Every subsequent step depends on knowing, reliably, what is genuinely outstanding. If your ageing report includes invoices that were paid by transfer and never marked off, you are building a machine that will email clients about money they already sent.

2. Define the ladder and write it down

Seven days before due, on the due date, plus seven, plus twenty-one, plus forty-five. Fewer rungs than you think, each with a different tone and a different sender.

3. Write the messages so a human would recognise them

Automated does not have to mean robotic. Reference the invoice number, the amount, the actual date, and what you would like to happen. The early ones should read as helpful, because they are.

4. Build the reconciliation gate

This is the critical one. Before every send, re-check payment status at that moment, not at the moment the reminder was scheduled. An overnight payment that arrives between scheduling and sending is exactly the case that makes you look careless.

5. Escalate the channel, not just the volume

The later rungs should change medium rather than simply repeating. Chaser's 2026 accounts receivable report, based on a survey of over 300 finance professionals, found that combining SMS with email made businesses 49 percent more likely to be paid within two weeks. Treat that as directional, since Chaser sells receivables software.

6. Keep a person on the last rung

Automate up to the point where a relationship is at stake, then hand to a human with full context. Nobody should receive an automated legal-sounding message from a business they have worked with for three years.

THE GATE THAT PROTECTS THE RELATIONSHIP Reminder dueper the ladder Re-check payment status at send time, not at schedule time paid still open Cancel silently. Close the loop. Send, and log that it went. Chasing an invoice the client already paid is worse than not chasing at all. It says, in public, that you do not know what has been paid. Every reminder must re-check at the moment of sending.
Figure 2: the reconciliation check is not an optimisation. It is the thing that makes the automation safe to run.

Tools and what they cost

OptionWhat it costsHonest trade-off
Accounting software native reminders (Xero, QuickBooks)Included in your existing subscription.Free and immediate. Usually limited to fixed intervals after the due date, which means you cannot build the before-due rung that matters most.
Dedicated AR tools (Chaser, Satago, Upflow)Typically tens to low hundreds a month for small businesses.Purpose-built, with escalation ladders and reconciliation handled. You are paying monthly for something you may be able to script.
Apps Script against your accounting APIFree with Google Workspace.Full control over the ladder and the wording, and no per-message cost. You build and own the reconciliation logic, which is the hard part.
Connector platform (Zapier, Make)Billed per task or operation. A five-rung ladder across many invoices adds up quickly.Quick to a first version. Careful with the pricing model once your invoice volume grows.

What it is actually worth

The honest framing has three layers.

Independent context. Atradius, an insurer rather than a software vendor, reports 55 percent of US business-to-business invoiced sales overdue and 43 percent of credit sales value overdue in 2025. That is the size of the problem, from a source with no automation to sell.

Vendor-published effect, clearly labelled. Chaser's 2026 report found automation users 52 percent more likely to be paid within two weeks, and SMS plus email 49 percent more likely. Chaser sells accounts receivable automation, the sample is just over 300 self-selecting finance professionals, and I would not plan a business case on it. It is directionally useful and it is marketing.

The arithmetic that is actually yours. Take your current days sales outstanding, and your average outstanding balance. Every day you shave off DSO is roughly one day of that balance back in your account. That number is real, it is specific to you, and it does not require anyone else's statistic.

How it breaks

It chases paid invoices. The single worst failure, and the reason the reconciliation gate is not optional. One of these emails costs more goodwill than ten reminders earn you in cash.

The tone escalates faster than the relationship warrants. A good client who is habitually a week late does not need the same ladder as a new client who has gone silent. Segment, or at minimum exempt your top accounts from the automated later rungs.

Nobody handles the replies. Automated chasing generates responses, disputes and promises to pay. If those land in an unmonitored inbox you have automated the sending and abandoned the collecting.

How to tell whether it worked

Two numbers. Days sales outstanding, tracked monthly, which is the headline. And the share of invoices paid on or before the due date, which is the one the before-due reminder should move first and which will improve before DSO does.

Sources and honesty note. Overdue payment figures are from the Atradius Payment Practices Barometer 2025, North America edition; Atradius is a trade credit insurer, which gives it an interest in credit risk but not in selling automation software. The 49 percent and 52 percent figures are from Chaser's 2026 accounts receivable report, a survey of just over 300 finance professionals published by a company that sells receivables automation, and I have labelled it as such rather than presenting it as independent. Pricing is list price at time of writing.

Paul Prado Pacardo is a Senior Executive Assistant and Operations professional with over ten years supporting C-level leaders, and the solo founder of a multi-product software studio. Available for remote Chief of Staff, Operations, Senior Executive Assistant and Project Manager roles.