Start from the terms, not the template
Before writing any reminder, collect the facts the reminders depend on: invoice date, due date, payment methods, any agreed late fees or interest, and who the client contact is. If those facts are inconsistent between invoices, fix that first — automation will repeat inconsistency faithfully.
Most invoicing tools, including Stripe, can send reminders natively; Stripe documents its options for automatic collection and reminders. A custom workflow is only needed when your invoicing, CRM and communication tools need to be coordinated, or when you want reminders to stop based on something the invoicing tool doesn't know about.
A sensible reminder sequence
| Stage | Timing (example) | Tone and content |
|---|---|---|
| Invoice sent | On issue | Amount, due date, how to pay, who to ask |
| Due soon | A few days before due | Friendly heads-up, same details, link to pay |
| Due today | Due date | Short, factual |
| Overdue | Some days after due | Polite; ask if there's a problem; offer a contact |
| Escalation | Later | Handed to a person — no more automated messages |
Keep the timings in a configuration your bookkeeper can change. The right spacing depends on your clients and terms; there is no universal answer.
Conditions that must stop a reminder
- The invoice is paid, partly paid, voided or credited.
- The client has disputed the invoice or raised a query.
- A payment plan has been agreed.
- The client contact has changed or the email bounced.
- A person has paused reminders for that client.
The first condition depends on accurate payment status. If payments arrive by bank transfer and are reconciled weekly, reminders may fire for invoices that were paid days ago. Either reconcile before reminders go out, or soften the wording ("if you've already paid, thank you — please ignore this").
Writing reminders people respond to
- Put the amount, invoice number and due date in the first lines.
- Include a direct payment link if you have one.
- Offer a route for questions. Many late payments are queries in disguise — wrong PO number, wrong contact, missing detail.
- Stay factual. Avoid threats or invented consequences.
- Don't add marketing to payment messages.
Where a person takes over
Automated reminders should end. After the last automated stage, create a task for a named person to call or email personally. Decisions about pausing work, applying fees, offering plans or involving collections are business decisions with relationship and legal implications; keep them human.
Before you switch it on
Run test invoices to your own address and confirm: reminders stop as soon as an invoice is marked paid; disputed invoices are skipped; a paused client receives nothing; and every message shows the correct amount and currency. Record the test results in your automation runbook.
Questions
Can a reminder include a late fee?
Only if the late fee is in the terms the client agreed to and the applicable rules where you operate allow it. A reminder is not the place to introduce new terms.
What if the client has already paid?
The reminder should check invoice status at the moment it sends. If payments are reconciled manually, delays between payment and status update are the most common cause of embarrassing reminders.
Sources and further reading
- automatic collection and reminders docs.stripe.com
Official documentation changes. Check the current version before you rely on a rule, limit or setting.
Next step
Start with one workflow worth fixing.
Bring the real steps, the tools you already use and the place the handoff gets stuck. We review feasibility, access and approval points before quoting — no instant integration promise.
See Business Automations for what we scope, or prepare a custom quote brief.