In short: Remind only when the ledger still shows an amount due and the invoice is not on hold. Refresh the balance before release. A timeout after a successful send must not send the same stage again.
An overdue reminder is useful only when the amount is still due and the recipient is the right one. Build it on the receivables ledger, not on a spreadsheet copied last month. Paid, disputed and credited invoices need a stop rule that runs before any message is released.
This is not debt collection and it is not legal process. It is also not invoice approval. Approval decides whether you accept a supplier’s bill. This page is about money your customer still appears to owe you.
The ledger is the authority
Store the reminder against an invoice id and a customer id that exist in the accounting system. Keep due date, currency, open balance and the internal owner. Do not key the workflow off a forwarded PDF’s filename. If two systems disagree, the ledger wins and the other list is the thing you repair. System integration is the work of making that read reliable. A stale export is how a paid invoice gets chased.
IRAS expects GST-registered businesses to keep records, including tax invoices, for at least five years from the end of the accounting period. The reminder log is not that tax invoice. Keep the log long enough to explain what you sent. Do not confuse it with the GST record. Details are in the retention guide.
Refresh, then hold
Before a message is released, read the open balance again. Selection in the morning is not release in the afternoon.
Pause, for a named reviewer, when any of these are true:
- the invoice is marked disputed;
- a payment plan is in force;
- a credit note is unallocated and would change the balance;
- the customer record is suspended;
- the balance read failed.
A hold stops every later stage, not only the next email. Clearing it is a deliberate act.
Stages are a business rule
Write the stages down: for example a first operational reminder, a second to the account owner, and an internal escalation that does not go to the customer until a person sends it. The gaps between stages are your policy. Do not copy a sequence from a template and call it standard.
Keep the message operational. Do not add a promotion to a collection notice without a separate review. Bank instructions inside the template are dangerous. A change to the account you ask the customer to pay is the same class of control as a supplier bank-detail change: independent check, not a quick edit in the template.
Draft, then a person releases
Start with drafts. A person checks the recipient, the attachment, the amount and the payment instruction. Customer contacts can be personal data even in a business relationship; the PDPC’s Key Concepts guidelines distinguish business contact information by purpose and context, and they still expect reasonable protection for personal data you do hold. Send the reminder to the address your customer master says is the billing contact. Do not scrape a new address out of an old email and assume it is authorised.
One stage, one send
Give each reminder an event key: invoice id plus stage. Record that the stage was sent before you consider the action complete. If the mail system accepts the message and the workflow then times out, a retry must see the event key and stop. Microsoft’s error-handling guidance describes retries and run-after branches. A retry is safe only when the send itself is idempotent. The maintenance problem of “the write succeeded but the acknowledgement was lost” is the same shape as in the failed-run guide.
Do not report a promised improvement in days-sales-outstanding. You can count the wrong reminders, the disputes still open and how long the ledger read lagged. Those are quality measures. They are not a collection-rate claim.
Tests
- The customer pays between selection and release. The fresh balance suppresses the draft.
- A partial credit note reduces the balance. The draft shows the new balance or it does not send.
- Dispatch succeeds and the flow times out before it logs the send. The retry does not send stage one again.
Illustrative scenario, not a client engagement: a scheduled reminder is about to draft itself when a payment lands. The balance read returns zero and the draft is dropped. On another invoice the accounting connection times out. That item waits for a person. It is not treated as unpaid merely because the read failed.
This guide is not legal advice and not a debt-collection procedure. FYAdvisers is not a law firm. To design the hold and the balance check, use the contact form or WhatsApp +65 9071 3976 (chat).
Frequently asked questions
When is the balance treated as fresh enough to send?
Immediately before release, from the accounting ledger, not from the list that was selected that morning. If the ledger cannot be read, the item waits. It is not treated as unpaid by default.
How does a dispute stop every later stage?
The invoice carries a hold set by a named person, with a reason. Selection for stage two or three checks that hold. Clearing the hold is also a named action, so a reminder does not resume by accident.
Who approves the wording and the recipient rules?
The business does, in a template with a version. The first releases should be drafts a person sends. Bank details in the template are a controlled field. A change to them is a supplier-master problem, not a wording tweak.
Should the workflow threaten legal action?
No. Operational reminders are not a debt-recovery process and not legal advice. Escalation to a lawyer or a collector is a human decision outside this workflow.
