Client hasn’t paid the invoice: the reminder emails

The invoice is past due and you’ve rewritten the reminder four times without sending it. Below is a three-step sequence you can send as it stands: a neutral nudge at day three, a firmer one at day ten with the line that pauses work, and the day-twenty-one message that names what happens next.

These three emails are site content rather than kit scripts. The $12 kit covers the scope and price side of client work, the fourteen reply scripts, the change order template and the proposal clauses. Payment chasing sits next to it, so the sequence is here for free.

Before you write anything, check three things

Most overdue invoices are not a client refusing to pay. They are an invoice that never reached the person who pays things. Spend two minutes on this before you draft, because it changes which email you send.

• Did it go to the right address? Larger clients have an accounts inbox, and an invoice sent to your day-to-day contact frequently sits in their personal email for a month.
• Does it have everything their system needs? A missing PO number, cost centre, or supplier reference will bounce an invoice out of an approval queue silently, and nobody will tell you.
• What did you actually agree? Net 30 from the invoice date and net 30 from month end are three weeks apart. Check before you call something late.

Then send the first email on the third working day past due. Waiting two weeks because it feels awkward makes it much more awkward, and it lets the client learn that your dates are approximate.

Day 3: the neutral nudge

Everything about this one is deliberately low temperature. It contains no “just checking,” no apology, and no suggestion that anything is wrong, because at day three nothing is. Ending with a question about what you can do keeps the exchange practical, and it usually produces the actual answer: send it to accounts, add a PO, the approver is on leave until Thursday.

Day 10: the firm one, with the pause line

The pause is announced before it happens, with a date attached, and the same paragraph says you’d rather not use it. That combination is what lets the message be firm without being hostile. A pause the client finds out about by noticing a missed deadline reads as retaliation. A pause they were warned about on a specific date reads as a policy, and it usually gets the invoice paid two days before the date arrives.

“A payment date I can rely on is enough” is worth keeping. Cash-flow trouble is common and clients hide it badly. Offering to accept a date instead of the money gives them a way to be honest with you, and a client who says “the 5th, when our own invoice clears” and then pays on the 5th is not a problem client.

If you do pause, pause. Say it in one line on the day, keep it to the milestone you named, and don’t take the work back up until the payment clears. The same rule the kit applies to unsigned change orders applies here: the first time you pause and stay paused, the next invoice gets paid on time.

Day 21: the decision email

Only name a consequence you will actually carry out, and only one that exists in your agreement. A late fee you never wrote into the contract, mentioned for effect and then quietly dropped, teaches the client that your last email in any sequence is the one to ignore. If your contract has no late-fee clause, the honest consequence is a final notice and no further work, which is plenty.

The closing question is doing real work. Silence at three weeks is often embarrassment: a client whose own money hasn’t arrived, a company being acquired, a contact who was made redundant and whose inbox nobody is reading. Asking rather than accusing gets you that information, and once you have it you can decide whether to offer a payment plan or stop.

What to change so it doesn’t happen again

• Invoice on milestones, not at the end. A project split across two or three invoices caps what any one silence can cost you.
• Put the payment terms where they get read. Due date, late-fee percentage, and the pause policy belong in the same section as the price, not in fine print underneath it.
• Ask for the accounts email at kickoff, along with any PO requirement. It takes one sentence and removes the most common cause of a late invoice.
• Keep the reminders on a calendar, at day 3, day 10 and day 21. Deciding when to chase in the moment is how invoices drift to sixty days.

One thing worth noticing across all three emails: none of them apologise for sending an invoice, and none of them explain your circumstances. State the number, the date, and what you need to happen next. Everything added beyond that turns a bill into a request for a favour.

The fourteen reply scripts, the change order template and the six proposal clauses that keep scope and price agreed in writing are in the $12 kit. The reminder emails above are free to copy.