Why a sequence beats a single strong email
Every reminder you send teaches the buyer what to expect from you. If you stay friendly forever, they learn that nothing changes when they ignore you. If you go nuclear on day +1, they learn that you panic — and they often disengage internally rather than respond. A predictable sequence does the opposite: each step is a small, expected escalation, so the buyer's accounts payable team can route it through their own process without drama.
Step 1 — Friendly nudge (day +1 to +3)
Short, warm, low-friction. Re-attach the invoice or include the share link. Ask if there is anything to clarify. This stage clears the majority of overdue invoices that are just lost in an inbox.
Step 2 — Personal follow-up (day +7 to +10)
Switch from automated to personal. A short note from the actual person who did the work has a much higher response rate than another templated email. Ask for a specific date the buyer expects to pay, not a general acknowledgement.
Step 3 — Firm reminder (day +14 to +21)
Now structural: amount owed, original due date, days overdue, late-fee policy if disclosed, and a clear request for a confirmed payment date in writing. Pause any new work for the same customer until the overdue invoice is resolved. Continuing to deliver into a non-paying customer is the single most common way small businesses end up with five-figure write-offs.
Step 4 — Final notice (day +30 to +45)
Names the deadline and the next step. After the deadline passes, the in-house cadence is over and the next action is external — collections, small-claims court, or a documented write-off. Send from a real named person and keep timestamps of every reply.
Worked example
An agency carries a £4,500 invoice past its 30-day terms. Day +2 a friendly nudge is sent automatically — no reply. Day +9 the project lead emails personally — buyer says the contract owner is on leave. Day +18 a firm reminder lands, copying the buyer's finance address; payment is scheduled within four days. The final-notice stage is never needed because each step landed at the right calendar point. That is what 'good escalation' actually looks like.