The invoice nobody is refusing to pay
Most late invoices are not disputes. They are an email that went to the wrong person, an approval sitting in a queue, or a finance department that pays on the twenty eighth and always has. The money is not being withheld. It is being forgotten.
Which means the thing standing between you and being paid is usually a reminder, sent on time, by somebody who is not embarrassed to send it. You are embarrassed to send it. That is the whole problem. Chasing gets delayed because it feels rude, and the longer it is delayed the ruder it feels, and eventually you are asking about an invoice from two months ago and apologising for your own money.
An automation is not embarrassed. It sends on day one and day fourteen with the same even tone. That evenness is the actual product here, not the saved typing.
This lesson is about polite reminders and nothing more. It is not legal advice, and it is not debt recovery advice. Rules on late payment, interest, charges, statutory demands and what you may say to a debtor vary considerably by country and sometimes by sector. Before you automate anything beyond a courteous reminder, check what applies where you and your customer are based, and take proper advice for anything genuinely disputed or seriously overdue.
In plain English
- Ageing:
- How many days past the due date an invoice is. The number that decides which reminder goes out.
- Escalation:
- Reminders becoming firmer over time, in planned steps rather than in a sudden change of tone.
- Remittance:
- Confirmation from a payer that a payment has been made, and what it covers.
- Stop condition:
- The rule that halts the reminder sequence, such as payment received or a query raised.
A ladder, not a switch
Design the sequence before you write a word of it. Four rungs is plenty for most small businesses, and the tone should climb slowly enough that no single message is a shock.
BEFORE DUE, 3 days Friendly notice. Not a chase at all.
Purpose: catch the wrong recipient
before the invoice is even late.
DUE PLUS 3 Assume it was missed. Warm, brief,
no mention of lateness as a fault.
DUE PLUS 14 Direct. State the amount, the invoice
number and the original due date.
Ask a specific question: has this
been scheduled, and for when?
DUE PLUS 30 Formal. Same facts, shorter sentences,
no warmth added and none removed.
Ask them to confirm a payment date
or tell us what is blocking it.
This one a person writes or approves.
STOP THE SEQUENCE IMMEDIATELY IF
- payment or remittance arrives
- the customer replies at all, about anything
- the customer raises a query or dispute
- anyone on your team has spoken to them about it
The first rung is the one people never build and it is the most valuable. A note before the due date is not a chase, so it costs nothing socially, and it catches the single most common cause of late payment, which is the invoice sitting in the inbox of somebody who left in April.
Checkpoint
Escalate in planned steps, start before the due date, and stop the whole sequence the moment the customer replies about anything at all.
Tone that leaves the relationship intact
The instinct when writing a chaser is to soften it with apology. Do not. Apologising for asking implies you are not sure you are owed, and it makes the next reminder harder to send. Neutral and specific beats warm and vague.
Write a payment reminder. Under [90] words.
Invoice: [number], [amount], [currency]
Issued: [date] Due: [date] Days past due: [n]
Customer contact: [name and their role if known]
Stage: [before due / plus 3 / plus 14 / plus 30]
Tone by stage:
before due helpful heads up, no pressure at all
plus 3 assume it was missed, not withheld
plus 14 direct and factual, still courteous
plus 30 formal, plain, no warmth and no coldness
Rules:
- State the invoice number, the amount and the due date once.
- Ask exactly one question, and make it answerable in a line.
- Do not apologise for sending the reminder.
- Do not mention interest, charges, legal action, credit
ratings or collection agencies.
- Do not threaten to stop work or withhold anything.
- Do not guess why they have not paid.
That list of things not to mention is not squeamishness. Some of those statements carry legal weight in some places, and a sentence written by an automation is still a sentence you sent. Keep them out of the automated rungs entirely and handle them, if you ever need to, with advice and a person.
โ Weak prompt
Prompt
Write a strong follow up for an invoice that is 30 days overdue and make clear this is unacceptable.
Output
We note with concern that despite previous correspondence this invoice remains unpaid. Failure to settle within seven days may result in further action and additional charges being applied.
Vague menace, an implied threat about charges that may not be permitted where this customer is based, and a relationship damaged over what is very likely an approval sitting in a queue.
โ Good prompt
Prompt
Formal stage reminder, invoice HC-20418, 1240.00 GBP, due 14 March, 30 days past due. Under 90 words. State the facts once, ask one answerable question, no mention of interest, charges or legal action, no apology.
Output
Hello Dele, invoice HC-20418 for 1240.00 GBP was due on 14 March and is still showing as outstanding on our side. Could you confirm the date it is scheduled for payment, or let me know if something is holding it up? Happy to resend the invoice or send it to a different address if that helps.
Firm, factual, and easy to answer in one line. It gives them an exit that is not embarrassing, which is what actually gets invoices paid.
Timing, and the things that stop the clock
Send reminders in the morning of a working day, never on a Friday afternoon, and never on a public holiday in the customer's country. A chase that arrives when nobody can act on it just sits there getting older.
CHECK, EVERY TIME, BEFORE SENDING
- Is the invoice actually still unpaid right now?
Check the payment record, not yesterday's export.
- Has any reply arrived on this thread since the last rung?
- Has anyone on the team agreed different terms with them?
- Is today a working day where the customer is?
- Is this going to a person, or to an address that bounces?
IF ANY CHECK FAILS, HOLD AND FLAG FOR A HUMAN.
Do not send and correct afterwards. There is no correcting
a chaser sent to a customer who paid last Thursday.
Chasing someone who has already paid is the most expensive mistake in this whole lesson. It is also the easiest to make, because payment data is usually a day behind. Read the live record at the moment of sending, not a copy taken overnight.
Log every reminder against the invoice with its date and rung. When somebody finally asks what happened with this account, a plain list of five dated, courteous messages answers the question completely and takes no effort to produce.
๐ Quiz
Question 1 of 4Why is the reminder sent before the due date the most valuable rung on the ladder?