What do you say when a customer breaks a promise to pay?

Quote the promise and the date it was made, state that it has passed, and ask what changed. Do not restate the invoice from the beginning — the strength of your position is entirely in their own words, and repeating the balance makes it a routine reminder they have already learned to ignore. Ask for a new date and treat a second miss as a different kind of problem from the first.

Should you believe a second promised date?

Believe it enough to wait for it, and not enough to stop preparing. Confirm it in writing with an amount attached, note that it is the second date given, and decide in advance what you will do if it also passes — which for most businesses means pausing further work rather than an immediate escalation. What you should not do is keep granting extensions without ever naming a consequence.

Customer missed a promised payment date — follow-up template

They gave you a date and it has passed. The email that works quotes their commitment rather than restating the invoice.

Two weeks overdue
Firm tone
They promised and missed the date

The email

Subject

Invoice [Invoice number] — the [Promised date] payment did not arrive

Body

Hi [Customer name],

On [Date of their email] you told me invoice [Invoice number] for [Amount] would be paid on [Promised date]. That date has passed and the payment has not arrived.

I held off chasing on the strength of that, so before I do anything else: what changed?

If it was a process problem — a run missed, an approval outstanding — tell me and give me the new date. If the position has changed and it cannot be paid as agreed, I would rather know that now than find out by waiting again.

I need an answer by [Date].

Regards,
[Your name]
[Your business]

Fill in before you send

[Customer name]
[Date of their email]
[Invoice number]
[Amount]
[Promised date]
[Date]
[Your name]
[Your business]

When to send this

One or two working days after a promised date passes with no payment and no explanation.
When the promise is in writing and you can quote the date it was made.
When you did in fact stop chasing because of the promise — the email says so, and it should be true.

When not to send this

The wrong reminder at the wrong moment costs more than no reminder at all.

The morning after the promised date, on a payment that was promised for that date.: Instead: Give it a working day or two. Bank transfers initiated on the promised date frequently land the next day, and chasing a payment that is already in flight undoes all the credit you earned by waiting.
When the 'promise' was actually 'I will try to get it out this month' or 'soon'.: Instead: Use the one-week email that asks for a date. Quoting a vague sentence back as if it were a commitment lets them dispute your account of the conversation, and the argument moves from their unpaid invoice to your characterisation of it.
When they have already written to say the date has slipped and given you a new one.: Instead: Hold to the new date instead, and note that this is the second. Chasing over an explanation you were already given is how a customer who is communicating stops communicating.

Not certain this is the reply you got?

This template assumes they promised and missed the date. Replies rarely say so in those words, and picking the wrong one is how a dispute gets chased or a kept promise gets nagged. Paste what they actually sent and the decoder will tell you which situation it is — and therefore which email belongs here.

Decode the reply you were sent

Notes on this one

'What changed?' outperforms every other question here. It cannot be answered with silence without the silence itself becoming an answer, and it lets a customer whose circumstances have genuinely worsened tell you so without having to volunteer bad news from scratch.

Track the promise, not the invoice age, after this point. A second broken date is a much stronger signal than another week of lateness, and it is usually the moment to move to the firm 30-day email whatever the calendar says.

Questions this comes with

What do you say when a customer breaks a promise to pay?: Quote the promise and the date it was made, state that it has passed, and ask what changed. Do not restate the invoice from the beginning — the strength of your position is entirely in their own words, and repeating the balance makes it a routine reminder they have already learned to ignore. Ask for a new date and treat a second miss as a different kind of problem from the first.
Should you believe a second promised date?: Believe it enough to wait for it, and not enough to stop preparing. Confirm it in writing with an amount attached, note that it is the second date given, and decide in advance what you will do if it also passes — which for most businesses means pausing further work rather than an immediate escalation. What you should not do is keep granting extensions without ever naming a consequence.

All 19 reminder templates

Collectly does this across every invoice, on its own

You just picked the email to send on one invoice. Collectly does the same thing continuously for every unpaid invoice you have — reads the replies, works out why each one is unpaid, estimates when it will land, and drafts the follow-up for you to approve.

With 15 rules it cannot talk its way around

A paid or written-off invoice is never chased again. Follow-ups are switched off permanently, not deferred.
A disputed invoice stops automated chasing entirely and goes to a person to resolve.
A promise to pay on a date pauses reminders until that date has passed. Collectly checks back the day after, not on the day.
At least three days between reminders on the same invoice, so re-running the analysis cannot turn into nagging. A resent or corrected invoice the customer has just asked for is not a reminder, and still waits for your approval.

Try it on your invoices See how it works

Want the full template pack in one email?

All of them in one message you can keep. Both offers are opt-in, and you confirm by email before anything is sent.

More free tools on the tools index.