An unpaid invoice is rarely a conflict; it is usually an inbox problem wearing a conflict's clothes. The chase sequence that works treats the client as forgetful rather than hostile, states the same facts in every email, and hardens its tone on a fixed calendar. This guide builds that sequence beat by beat, from the friendly reminder on the due date to a final notice that stays professional.
Assume Good Faith, State the Facts

The chase begins by assuming the invoice was missed rather than ignored, because the polite-reminder tone recovers most late payments and the aggressive tone burns clients who simply forgot. Payments-platform templates and receivables guidance agree on the opening stance: friendly, factual, specific. Good faith lasts exactly as long as the client's replies do; silence is information, not an insult to be answered with volume. Every email in the sequence, whatever its tone, leads with the same facts block, so the client's second read is easier than their first. Chasing is not confrontation; it is customer service for your own cash flow.
The Three-Beat Escalation
The chase runs three beats: a friendly reminder on the due date, a firm follow-up seven days late, and a final notice at thirty days late, with the tone hardening at each beat while the facts stay identical.
- Beat one, day 0: a friendly reminder on the due date itself, treating the invoice as probably missed.
- Beat two, day 7: a firm follow-up that names the days overdue and offers a call.
- Beat three, day 30: a final notice that states the consequence you can actually carry out.
Every beat resends the invoice copy; never assume the first attachment survived. Calendar the beats the day you send the invoice, not when you notice the silence, because the discipline of the dates is what keeps the tone decisions out of the emotional weather of your bank balance.
The Facts Block on Every Send
Every chase email carries the same facts block, invoice number, amount, issue date, due date, days overdue and payment link, because a chase the client must decode is a chase they defer.
- Invoice number and reference exactly as printed on the document.
- Amount outstanding, matching the attached copy to the cent, including GST treatment.
- Issue date and due date, so the timeline is visible without opening anything.
- Days overdue, stated plainly: this invoice is now 7 days past due.
- Payment link or transfer details, one click or one copy-paste from done.
Assemble the block once when the invoice goes out and paste it into every beat. The facts block is the spine of the sequence; the tone changes around it, never instead of it.
The Three Beats Compared
The beats differ in subject line, opening stance and what they add: the reminder adds nothing, the firm follow-up adds a phone-call warning, and the final notice adds the consequence you can actually carry out.
| Beat | Subject line | Opening stance | What it adds |
| Friendly reminder (day 0) | Invoice 2041 due today | Probably missed, no problem | Nothing; facts block and link only |
| Firm follow-up (day 7) | Invoice 2041 — 7 days overdue | Still unpaid, action requested | A call offer and a direct question about blockers |
| Final notice (day 30) | Final notice: Invoice 2041 | Formal, calm, dated | The stated consequence: work suspension or referral, only if true |
Only threaten consequences, suspension or referral, that you will execute. A final notice with an empty threat is a bluff, and clients who call bluffs renegotiate everything afterwards.
Paid, Disputed or Final
The sequence ends three ways: payment gets a one-line thank-you receipt, a dispute moves the thread from chasing to resolution with evidence, and silence at final notice moves the account to your escalation policy. The receipt matters more than it looks; it closes the loop warmly and trains the client that paying you produces a clean, immediate ending. A dispute gets a reply that asks for the specific objection in writing, resolves it with delivery evidence, and restarts the clock with a corrected invoice if amounts change. Late fees are charged only if the invoice or contract states them. The ending of a chase, more than its middle, decides whether the next invoice starts from trust or from a lawyer's template.
Cash-Flow Writing as a Business Register
Quotes, invoices, chases and receipts form one transactional register where dates and numbers are the persuasion, and small-group practice with correction keeps that register firm and polite at once. iWorld Learning's Business English small-group classes mark exactly this payment and transactional writing in three-to-six-person classes, so the firm-but-warm tone survives contact with a genuinely late client. Track days-sales-outstanding per client; the pattern names the problem clients before the next project does.
Frequently Asked Questions
Should I call the client between chase emails?
Call after the firm follow-up goes unanswered for three days, and open the call by offering to fix payment problems, not by demanding explanations.
Can I add a late fee in the chase email?
Only if the invoice or contract already states one; a fee invented in the chase converts a payment problem into a trust problem.
What if the client says the invoice is disputed?
Pause the chase thread, ask for the specific objection in writing, resolve it with evidence, then restart the clock with a corrected invoice if amounts change.