Designing Overdue-Invoice Reminders People Don't Hate
Nobody likes chasing money. Freelancers put it off because it feels awkward, and clients dislike being chased, especially when they've already paid. When I built follow-ups into InvoiceAgent, the goal was reminders that go out reliably without ever feeling aggressive, and without ever being wrong.
Here's how they work.
Two reminders, no more
The schedule is deliberately short:
- First reminder: three days after the due date
- Final reminder: four days after that
export const DEFAULT_FIRST_FOLLOW_UP_DELAY_DAYS = 3;
export const FINAL_FOLLOW_UP_DELAY_GAP_DAYS = 4;
export function getClientFollowUpStages(firstFollowUpDelayDays?: number | null) {
const first = resolveFirstFollowUpDelayDays(firstFollowUpDelayDays);
return [
{ stage: "OVERDUE_1", offsetDays: first },
{ stage: "OVERDUE_FINAL", offsetDays: first + FINAL_FOLLOW_UP_DELAY_GAP_DAYS },
];
}
Why three days? A payment made on the due date can take a day or two to arrive, so a reminder on day one often chases money that's already on its way. Three days gives transfers time to land. You can change the first delay per invoice, and the final reminder always follows four days later.
Why only two? After two polite emails, the problem usually isn't that the client forgot. It needs a conversation, and that should come from you, not from software.
Reminders are sent in your local time
Each reminder is scheduled at the same hour as the original invoice, in your time zone, starting from the due date (or the send date, if there's no due date). A reminder that turns up at 3am looks automated in the worst way.
The wording
The emails are short, specific and written in the first person, because they come from you:
Hi {recipientName},
Following up on invoice {invoiceNumber} for {amountDue}, which was due on {dueDate}.
It is now {daysOverdue} day(s) overdue. I have attached the invoice again here for convenience.
Kind regards, {senderName}
And the final one:
This is a final reminder about invoice {invoiceNumber} for {amountDue}, originally due on {dueDate}.
It is now {daysOverdue} day(s) overdue. Please let me know if payment is already in motion or if anything is blocking it.
A few choices are deliberate:
- Facts, not feelings. The invoice number, the amount, the due date and how many days have passed. No "just checking in!" and no guilt.
- The invoice is attached again, so the client doesn't have to search their inbox.
- "Final" doesn't threaten anything. It asks whether payment is already in motion or whether something is blocking it. That gives the client an easy, face-saving reply, which is usually all that's needed.
- You're copied in on every reminder, so you always know what your client received.
Reminders are optional per invoice. When you set one up, you choose the first delay, and the form previews the exact date and time each reminder will go out. The wording itself is fixed: the short, factual templates above.
Partial payments
If a client pays part of an invoice, the reminder asks for what's still owed, not the original total:
export function outstandingBalanceCents(invoice, fallbackTotal = 0) {
if (invoice.status === "PAID") return 0;
return Math.max(0, (invoice.convertedTotalCents ?? fallbackTotal) - invoice.amountPaidCents);
}
Asking someone who has paid 80% for the full amount is a good way to sour a relationship.
Never chase someone who has already paid
This is the part that took the most care. The worst possible reminder is one sent to a client who paid an hour ago. So before any reminder goes out, InvoiceAgent checks several times:
- Claim the reminder by switching it from
PENDINGtoPROCESSINGin a single conditional update. If two workers pick up the same reminder, only one wins, so a client can never get the same email twice. - Check the invoice is still unpaid and that follow-ups haven't been paused or turned off.
- Check the bank. If the invoice has a Wise payment reference, look for the payment before going any further.
- Render the PDF, which can take a moment.
- Check again just before sending. If a payment arrived while the PDF was rendering, or the balance is now zero, cancel the reminder.
- If the payment state is uncertain, for example a balance that changed mid-send or a bank check that's more than 30 seconds old, don't guess. Put the reminder back in the queue and try again on the next run.
if (!latest || latest.status !== "SENT" || latest.followUpPausedAt ||
outstandingBalanceCents(latest, totals.convertedTotalCents) === 0) {
// Paid, paused or cancelled while we were working: don't send.
await cancelReminder(reminder.id);
return { status: "canceled" };
}
The rule behind all of this is simple: when in doubt, wait. A reminder that goes out a few minutes late costs nothing. One that goes out wrongly costs trust.
Marking an invoice as paid, or recording the payment that clears it, cancels anything still pending.
What I'd suggest if you're building something similar
- Keep the sequence short and the gaps generous.
- Put the facts in the email: amount, due date, days overdue and the invoice itself.
- Give the final reminder an easy way out ("is anything blocking it?") instead of a threat.
- Check payment status as late as possible, and make sending idempotent.
- Treat "not sure" as "not yet".