Follow up professionally, with the right invoice details.

Start with the position today

A copied reminder can be wrong even when the original invoice was correct. The customer may have made a part payment, received a credit or raised a question since the last check. Before preparing a message, compare the remaining balance, due date and current state with the accounting record. Record when that information was checked. An imported spreadsheet is a snapshot, so it needs a fresh check before dispatch rather than being treated as a live payment feed.

In the shared example, EX-101 was issued for £1,200 and has an applied payment of £300. Its remaining balance is £900 as of 3 October 2026. A reminder asking for £1,200 would ignore money already recorded. A message about the £900 should still pause if the customer reports another payment until the accounting record can be checked.

Make the sender and next step clear

Use an authorised business sender, a working reply address and the contact responsible for the customer's invoices. Include the invoice reference, due date, currency and remaining balance. Give a safe route to an invoice copy or an existing approved payment page where that route has been verified. Avoid including unrelated customer records or asking the recipient to follow new bank details embedded in a reminder.

Tone can differ for a long-standing customer, a first invoice or a customer who regularly needs a purchase-order reference. Agree those differences in advance. A polite message should make it easy to respond, including when the customer cannot pay yet. A more forceful tone does not solve missing documents or an incorrect recipient. Those cases need a person to correct the cause.

Agree timing before repeating messages

A sequence might include a before-due note, a first overdue reminder and a later request for a response. This is an illustrative pattern, not a legal timetable or a proven optimum. Set intervals to suit agreed terms, customer groups and the business's existing process. Define working days, quiet hours, maximum attempts and an owner to review unanswered cases. Check whether the accounting software already sends reminders so two systems do not contact the same customer independently.

In the proposed workflow, reaching the attempt limit creates a review task rather than an endless sequence. An owner can decide whether to call, supply information or pause. Approval of a schedule does not remove the need to check the invoice state at each planned send. If the balance or contact has changed, the draft needs another review.

Three different messages for three situations

Before due: ‘A note that invoice EX-104 for £800 is due on 10 October. Please let us know if you need a copy or a purchase-order reference.’ First overdue: ‘Our record shows £900 remaining on EX-101, due on 18 September. Could you confirm the payment position, or let us know if anything needs clarification?’ Both explain the record without assuming that silence means refusal to pay.

Response request: ‘We have not yet received an update about EX-101. Please reply with the payment position or the question we need to resolve.’ These are examples to adapt, not messages ready for automatic use. The templates guide includes fuller wording and placeholders. Editing the public preview changes only the text on your screen; it does not alter a customer record, create a sending schedule or contact anyone.

Know when to stop—and when to combine

Pause routine reminders when a reply arrives, an invoice is disputed, a payment is claimed, a contact is wrong or source information is stale. Stop when the invoice is verified as settled, voided or otherwise excluded. A promise to pay can change the next review date, but it does not reduce the balance. EX-102 remains £650 outstanding while its dispute is investigated; the dispute requires an owner rather than a stronger reminder.

For customers with several open invoices, consider one authorised message listing the relevant references instead of several competing sequences. Keep each currency separate and leave disputed or restricted items out of routine wording. Agree who reviews the combined message and how replies are linked back to individual invoices. Discuss your current reminder process to identify the rules, contacts and checks a future pilot would need.

Explore the example