The first late-payment message should assume a process problem, not bad intent. The invoice may be waiting for approval, missing a purchase order, or sitting in the wrong inbox. A useful reminder makes the amount, due date, invoice number, and next action easy to find—and gives the customer a simple way to report a problem.
The timing below is a starting point. Adapt it to the contract, relationship, amount, client payment cycle, and local law.
Before the due date: confirm receipt
Send this only when the invoice is material, the client is new, or delivery is uncertain.
Subject: Invoice [number] due [date]
Hi [name],
I’m checking that invoice [number] for [amount and currency], due [date], reached the right person. The invoice is [attached/linked here]. Please let me know if you need a purchase order, vendor form, or other detail to approve it.
Thanks, [name]
This message discovers exceptions while there is still time to fix them.
On the due date: make the action obvious
Subject: Invoice [number] is due today
Hi [name],
A quick reminder that invoice [number] for [amount and currency] is due today. You can review it at [link] and pay using [method/instructions]. If payment is already in progress, no action is needed beyond sharing the expected settlement date.
Thank you, [name]
Avoid saying “overdue” before the agreed deadline has passed.
Three to five days overdue: ask for a date
Subject: Payment date for overdue invoice [number]
Hi [name],
Our records show invoice [number] for [amount and currency] was due on [date] and remains outstanding. Could you confirm the payment date or tell me what is blocking approval? The invoice is available at [link].
Regards, [name]
A promised date is more useful than another vague acknowledgment. Record it and follow up against it. If the customer needs an online route, verify the invoice payment link and processor workflow before resending it.
Seven to fourteen days overdue: move to a person
Automation is less useful once a delay persists. Contact the buyer or accounts-payable owner directly.
Subject: Action required: invoice [number]
Hi [name],
Invoice [number], [amount and currency], has been outstanding since [due date]. Please confirm by [response date] whether payment is scheduled or whether there is a specific dispute we should resolve. Under our agreement, the next step is [accurate contractual step].
Regards, [name and contact details]
Only mention interest, fees, work suspension, or collection action if the agreement and applicable law support it. For one jurisdictional example, the UK government explains when a commercial payment becomes late and when statutory interest may apply in its late commercial payments guidance. That rule is not universal; check the law governing your contract.
When the customer disputes the invoice
Pause generic reminders. Ask the customer to identify the disputed line, reason, and supporting evidence. Confirm what is not disputed and whether that amount can be paid now. Keep the conversation separate from emotional judgments about the client.
Hi [name],
Thanks for flagging the issue with invoice [number]. I understand the disputed item is [item/reason]. I’ll review it against [quote/order/delivery evidence] and reply by [date]. Please confirm whether the undisputed amount of [amount] can proceed in the meantime.
How reminders work in Invoice Master
Premium organizations can configure a dunning policy with email stages scheduled by days after the due date. Each stage targets either the customer or the organization owner. An invoice can be active, paused, completed, or disabled in that sequence, and the collections queue supports individual or bulk actions.
That automation has deliberate boundaries:
- it sends configured emails; it does not calculate or add legal late fees;
- a usable recipient email is required for a customer reminder;
- paid, cancelled, or otherwise ineligible invoices should not continue through collection; and
- a dispute still requires a human decision about pausing and resolving the issue.
The strongest collections process begins before the invoice: verified billing details, a clear acceptance record, an agreed due date, and a payment route the customer can actually use. The pre-send invoice audit catches many of those defects before they become collection work. Reminders work best when they surface facts instead of escalating noise.