Payment reminder email: what to write at each stage

A payment reminder email is the most-used and least-thought-about message in a small business. Most are either too apologetic to prompt action or too aggressive for a customer who simply has not processed the invoice yet. The useful version is neither: short, factual, with everything the recipient needs to pay without replying to ask.

Assume good faith for a long time. The overwhelming majority of late invoices are late because of something mundane — the invoice went to the wrong inbox, a purchase order reference is missing, the approver is away, the payment run is on Thursday. Every early reminder should be written as though that is what happened, because it usually is.

What every reminder must contain

• The invoice number and date, in the subject line as well as the body.
• The amount and the currency.
• The due date, and — after it passes — how many days overdue.
• The invoice attached again. Never make someone search their inbox for it.
• How to pay: bank details or the payment method agreed. Repeating this in every reminder removes a whole round trip.
• A single clear request with a date: "could you confirm the payment date by Friday" beats "please advise".
• A named human to reply to, with a direct phone number by the second reminder.
• A line inviting them to tell you if something is wrong with the invoice — which is how disputes surface before they become silence.

Never send a reminder without checking it is actually unpaid, and that the invoice went to the right address in the first place. Chasing a customer who paid last week costs more goodwill than the invoice is worth, and it teaches them to ignore your reminders.

The sequence, stage by stage

1. A few days before due: a courtesy note confirming the invoice is with the right person and the date is expected. Friendly, no pressure — this one prevents most lateness.
2. Day one overdue: short and factual. State that it appears unpaid, restate the details, attach it, ask for a payment date.
3. Day seven: same facts, plus a direct phone number and an explicit question — is there anything blocking payment. Call the same day if you can.
4. Day fourteen to twenty-one: address it to a named person with authority, note the previous attempts with their dates, state what happens next and when.
5. Day thirty: formal in tone, referencing your terms and any interest or recovery costs you are entitled to claim, with a firm deadline before escalation.
6. Final notice: state precisely what will happen and on what date — a formal demand, collections, or a legal route — and then do it. A threatened step that never arrives destroys every future reminder you send.
7. At every stage, log what was sent and any reply against the invoice, so anyone can pick up the thread.

Tone: firm, never rude

Escalate formality, not aggression. The early messages can be warm; the later ones should become shorter, more precise and more procedural — dates, amounts, references, next steps. Sarcasm, capital letters and moral language all reduce the chance of payment, because they hand the recipient an easier subject to react to than the invoice. Write every reminder as though it might be read aloud in a dispute, because occasionally it is.

In Ettex Mail, the messages you send repeatedly can live as reusable replies next to the inbox, so the six stages above become six saved texts you personalise in a line rather than rewrite each time. Scheduled send lets you write the batch on Friday and deliver on Monday morning, per-address signatures keep the branding right when reminders come from a billing mailbox on your own domain, and follow-ups stop a thread from being forgotten. The invoices themselves — numbers, amounts, due dates and statuses from draft through paid — sit in Ettex Invoices, and if you send a longer designed statement, Ettex Docs holds the master.

To be clear about the boundary: Ettex does not send payment reminders automatically. There is no dunning engine that watches due dates and mails on day one, day seven and day thirty, and no link between an invoice going overdue and an email being sent. The templates and the scheduling are there; deciding who gets reminded this week is a task on someone's calendar.

Chasing works better with the whole picture attached. A statement of account lists every invoice, credit and payment on a customer's ledger, which settles most "we already paid that" replies in one message.

What makes reminders fail

• Sent to the person who commissioned the work rather than the one who processes payments.
• No invoice attached, so acting on the email requires finding a document.
• Vague requests — "please advise" — that can be answered by doing nothing.
• Apologising for chasing, which signals the deadline is negotiable.
• Jumping from friendly to threatening with nothing in between, usually after a long silence on your side.
• Threats that are never carried out, after which every later message is discounted.
• No record of what was sent when, so the fourth reminder repeats the second and nobody can show a history.
• Reminders only by email, when one phone call would have found the actual blockage in two minutes.

A payment reminder email is a piece of administration, not a confrontation. Attach the invoice, repeat the details, ask one question with a date, escalate formality on a schedule — and pick up the phone before the tone hardens.