A collection email need not sound aggressive to be firm. It should let the recipient act without hunting for number, balance, attachment or bank details. Replace every bracket and reconcile the balance before sending.
Prepare these fields first
- [Contact name] and correct entity.
- [Invoice number].
- [Total] and [open balance].
- [Due date].
- [Attachment or secure link].
- [Payment instructions].
- [Requested action] and [reply date].
1. Before due date and on the first overdue day
Template 1 — pre-due check
Subject: Invoice [number] — due [date]
Hello [name], we are checking that invoice [number] for [amount], attached, has entered your approval process. It falls due on [date]. Please confirm receipt and tell us today if any document is missing. Thank you.
Template 2 — first reminder
Subject: Due date reached — invoice [number]
Hello [name], unless we have missed a receipt, the [balance] balance on invoice [number], due [date], remains open. Please share the expected transfer date or its reference if already sent. The invoice and payment details are attached.
“Unless we have missed” is not weak; it protects against unallocated cash. Keep the facts exact and ask for a dated answer.
2. Broken promise and a disputed invoice
Template 3 — missed promise
Subject: Follow-up on payment expected [date]
Hello [name], in our [date] conversation, [amount] was expected on [promised date]. We cannot identify it today. Please confirm a new firm date by [time/date] or send the transfer advice.
Template 4 — dispute detail
Subject: Invoice [number] — detail needed on your query
Hello [name], we have recorded your point about [reason]. To investigate, please identify the affected lines/quantities and attach [order, photo, acceptance]. Any undisputed [amount] remains to be handled under the agreement where applicable. We will respond by [date].
A dispute email should neither reject the issue automatically nor admit an unverified fault. It opens a small process with evidence, owner and deadline.
3. Final operational reminder before formal review
Template 5 — approved escalation
Subject: Final operational reminder — invoice [number], balance [amount]
Hello [name], despite our messages of [dates], the [amount] balance due [date] remains open and no documented dispute is recorded. Please pay or propose a precise written plan by [date/time]. Without a response, the file will go to [internal role/adviser] to review appropriate next steps. This email does not prejudge the route selected.
- Approve this escalation level.
- Attach the correct invoice and statement.
- Remove unnecessary recipients.
- Claim no unvalidated charge.
- Provide a response channel.
- Archive delivery evidence.
- Create the next task immediately.
Do not write “court tomorrow” where nobody has reviewed the file. Credibility comes from a real, proportionate next step.
Templates do not replace verification
Adapt language, entity, amount, due date and context. Delete every field that was not replaced before sending.
4. Personalise without breaking control
BelloPOS can provide number, date, payments and balance. The team adds context: missing order, contact absence, partial delivery or promise. Lock financial fields to the source and leave tone and relationship wording editable.
| Field | Source | Control |
|---|---|---|
| Number/balance | Invoicing | Automated or verified copy |
| Due date | Contract/invoice | Approved calculation |
| Contact | Customer record | Restricted and current |
| Next step | Credit policy | Human approval |
Always recheck subject and attachment. Sending another customer’s invoice is both a collection failure and a confidentiality incident.
Mistakes to avoid
- Leaving a bracket in the email.
- Attaching the wrong invoice.
- Disclosing debt to a third party.
- Typing over the balance.
- Promising unapproved action.
- Claiming invented charges.
Frequently asked questions
What subject line gets a response?
Use a factual subject with number and action, not angry capitals: “Invoice F-123 — due 15 October.”
Should I attach the invoice?
Yes where the channel and recipient are verified; avoid public links and double-check it belongs to that customer.
Can I send reminders on WhatsApp?
Only in line with the relationship, consent and privacy policy. Confirm through a channel that preserves useful evidence.
When should I use the final template?
After reconciliation, documented reminders and internal approval for a genuine formal review.
Can BelloPOS fill these templates?
Invoice and payment data can feed your process, but retain human approval before any message is sent.
What to take away
A strong reminder email is short, exact, actionable and traceable; its tone progresses, but its facts never drift.
Sources
The figures and rules quoted above come from these pages, read on the date given in the article.
- Ministry of Economy and Finance, Law 69-21 on payment deadlines
- Moroccan Tax Administration, Circular 734 on payment deadlines
Turn the templates into a procedure
Choose locked fields, approval levels and the next task created after every send.
Read next
Other practical guides on the same subject: