How to Chase Late Payments Without Losing the Customer

The work is done. The money is not here.

Ninety-two percent of businesses report invoices being paid after the due date. Seventeen percent are waiting more than thirty days past due. Somewhere between "invoice sent" and "payment received" sits a task nobody in a small company wants: asking a customer you like, and want to keep, for money they already owe you.

So it gets postponed. Then it gets done badly, in a burst, when the bank balance forces it. Forty percent of businesses spend six or more hours a week on receivables admin, and most of those hours are spent reconstructing who owes what rather than actually chasing.

The awkwardness is the whole problem. Not the process, not the software. This is a guide to removing the awkwardness, first by making the chase mechanical and predictable, then by handing the mechanical part to something that does not find it unpleasant.

Why invoices are actually late

Before writing a single reminder, sort your overdue list into four buckets. They need completely different treatment and most businesses send the same email to all four.

• It never arrived. Sent to a person who left, caught by a spam filter, or missing a PO number so the customer's system rejected it. Extremely common and instantly fixable.
• It is stuck in an approval queue. Someone has to code it, someone else has to approve it, and neither has your invoice at the top of their pile. Nobody has decided not to pay you.
• The customer is managing their own cash. You are on a list of who gets paid this week, and the ones who chase consistently are higher on it. This is not personal and it is entirely responsive to your follow-up discipline.
• There is a dispute nobody told you about. Quantity, price, damage, a missing delivery note. Silence here is not stalling, it is a problem waiting to be found.

The first two are administrative and account for a large share of what looks like bad payment behaviour. Both are solved by contacting the right person early, not by firmer language later.

The escalation ladder

Fixed dates, escalating firmness, always the invoice attached, always the amount and reference in the first line. Adjust the days to your terms; keep the shape.

When	Channel	Tone	Purpose
Due date minus 3	Email	Courtesy	Confirm it arrived and is approved
Due date	Email	Neutral	On-record marker that terms are live
Day 7	Email + second channel	Friendly, direct	Reach a person, not an inbox
Day 14	Second channel, then call	Firm, specific	Get a date, not a feeling
Day 30	Email, named sender	Formal	State consequences, offer a plan
Day 45+	Human decision	—	Stop supply, plan, or escalate

Two details do most of the work.

Ask for a date, not for payment. "Can you confirm which week this will be paid?" gets a reply that "please arrange payment" does not, and a stated date is a commitment you can hold someone to at day 21.

Use a second channel from day 7. Email-only chasing is the default and it underperforms; adding SMS or WhatsApp produces a substantial relative improvement in getting paid within two weeks. In practice that is because email reaches an accounts inbox and a message reaches the person who can push the button. For a lot of small businesses, WhatsApp is already the channel the customer uses for orders and questions, which makes a payment nudge there normal rather than aggressive.

What to actually say

Short, dated, specific, no apologising for asking. Three that carry most of the sequence:

Day minus 3, email:

Invoice 1042, EUR 3,480, is due Friday 21st. Just checking it reached the right person and there is nothing you need from us to get it approved. PDF attached again for convenience.

Day 7, second channel:

Hi Marta, invoice 1042 (EUR 3,480) was due on the 21st and is showing as unpaid our end. Could you let me know which week it is scheduled for? Happy to resend anything you need.

Day 30, email, from a named person:

Invoice 1042, EUR 3,480, is now 30 days overdue. Our terms are 30 days net and we have not had a payment date despite reminders on the 18th, 28th and 4th. Please confirm payment by the 20th, or let me know if a payment plan would be easier. New orders are on hold until this clears.

Notice what is missing: no "just following up", no "sorry to bother you", no threat that will not be carried out. If new orders are not really going on hold, do not write that they are; a bluff called once removes the last rung of your ladder permanently.

Automating the boring 90 percent

Nothing above requires judgment except the dispute handling and the day-45 decision. Everything else is scheduling, attaching, reading replies and record-keeping, which is exactly what an agent does better than a busy owner. Businesses using receivables automation are meaningfully more likely to be paid within two weeks of due date, and the mechanism is unglamorous: the messages actually go out, on the day, every time.

A working setup does five things:

1. Watches aging in the accounting system. Invoice raised, due date, payment received. Xero, QuickBooks, Holded, Sage or a mid-2000s ERP that only exports a nightly CSV, it does not matter much; the aging report is the trigger.
2. Sends the ladder in your voice, on the right channel. Email with the PDF for the record, WhatsApp or SMS for the nudge, both logged against the invoice.
3. Reads the replies. "Paid on Tuesday" becomes a tracked promise with a follow-up on Wednesday. "We never got the delivery note" stops the sequence and raises a dispute. An out-of-office finds the covering contact.
4. Stops the moment money lands. The single most relationship-damaging failure in automated chasing is a reminder sent the day after payment. Reconciliation against the bank or accounting feed has to be part of the loop, not a weekly job.
5. Escalates to a human on purpose. Disputes, payment plans, your three largest accounts, anything over a threshold you set. That gate is the human-in-the-loop step, and it is what keeps this from feeling like a robot dunning your customers.

Because it runs on the channels your customers already use, this is the same machinery as any other follow-up that keeps getting dropped, pointed at the one that costs you cash. The mechanics of the pipeline in more depth are in accounts receivable automation, and it sits alongside the rest of the finance stack described in AI agents for finance teams.

Measure DSO, not activity

The vanity metric is reminders sent. The real one is days sales outstanding: the average days between raising an invoice and having the money.

Take a baseline over the last full quarter before you change anything, then watch three numbers monthly:

• DSO. The headline. Expect movement within one full payment cycle, not in week two.
• Percentage of invoices with a first contact before the due date. This is the discipline metric, and it is the one that predicts the DSO improvement.
• Percentage of overdue value in dispute. If this rises when you start chasing properly, that is good news badly disguised: those disputes existed, they were just invisible.

Do not accept a projected percentage from anyone, including us. Measure your own baseline first; the method is in calculating automation ROI. The same discipline applies at month-end close, where unreconciled receivables are usually the thing holding the whole close open.

Start with the oldest invoice you have been avoiding

There is one on your aging report right now that you have quietly decided not to think about. It is probably in the "stuck in an approval queue" or "nobody told you about the dispute" bucket, and one message today resolves the question either way.

Then make the ladder automatic, so the next one never gets old enough to be uncomfortable.

Oido runs receivables follow-up across email and WhatsApp from your existing accounting data, tracks promises, stops on payment, and hands disputes to a person. See how it works for small teams, or tell us what your aging report looks like.