Most clients pay late because the invoice gets lost in their inbox, not because they\'re refusing to pay. A simple four-email cadence — before the due date, on the due date, at 7 days past due, and at 30 days — gets the vast majority of invoices paid without burning the relationship. Templates below, with the timing.
Done in seconds. No sign-up required.
The order matters more than the wording. A pre-due-date reminder is friendly and resolves most forgotten invoices before they become "overdue." A reminder on the actual due date is a routine nudge, not an accusation. The two follow-ups after — at 7 days and 30 days — escalate in tone but stay professional. Going from polite to firm to final over a month is normal business practice; going from silent to legal letter in a week is not.
The hard part isn\'t writing the emails. It\'s remembering to send each one at the right time. Most freelancers send the first one, forget the rest, and the unpaid invoices quietly stack up. Set a reminder for each stage when you first send the invoice — that\'s the system.
Subject: Invoice #1042 — due Friday, May 15
Hi [Client first name],
Quick reminder that invoice #1042 for $2,400 is due this Friday. Payment details are on the original invoice (attached for convenience), or let me know if you need them resent.
Thanks,
[Your name]
Three sentences. No apology, no preamble, no "just checking in." A pre-due reminder is the most useful one in the cadence because it\'s zero-confrontation — the invoice isn\'t late yet, so the client can\'t feel accused.
When to send: 3 to 5 days before the due date.
Subject: Invoice #1042 — due today
Hi [Client first name],
Just a note that invoice #1042 for $2,400 is due today. If payment has already been sent, please disregard. If not, I\'d appreciate it being processed by end of day.
Thanks,
[Your name]
The "if payment has already been sent, please disregard" line is important — it acknowledges that bank processing takes time and protects the relationship if the client paid yesterday.
When to send: the morning of the due date.
Subject: Invoice #1042 — 7 days past due
Hi [Client first name],
Following up on invoice #1042 for $2,400, which was due on May 15 and is now 7 days past due. Could you confirm when payment will be made?
If there\'s an issue with the invoice or with internal processing on your end, let me know and we\'ll work it out.
Thanks,
[Your name]
The tone shifts here from "reminder" to "request for a status update." Asking a direct question — "when will payment be made?" — forces a response. The second paragraph gives the client an honorable exit if something\'s actually wrong (lost invoice, approval bottleneck, dispute).
When to send: 7 days past the due date. If your contract includes a late fee, mention it here.
Subject: Final notice: invoice #1042 — 30 days past due
Hi [Client first name],
Invoice #1042 for $2,400 is now 30 days past due. This is my final email reminder before I escalate.
Please process payment by [date 7 days out]. If I haven\'t received payment or a written response with a payment plan by then, the invoice will go to collections and a 1.5% monthly late fee will apply per our original terms.
I\'d much rather resolve this directly. Let me know how you\'d like to proceed.
[Your name]
The "Hi [Client]" drops the warmth — you\'re now in a transactional posture. Naming the consequence (collections, late fee) and a specific deadline makes the email actionable rather than vague. The closing line keeps the door open in case the client genuinely intends to resolve it.
When to send: 30 days past the due date. After this, switch to phone or registered letter.
The templates are easy. The hard part is sending them on time, every time, for every invoice. The freelancer who sends invoice #1 with a perfect 4-email cadence and then sends invoice #12 with only the first reminder is the freelancer with $4,000 in unpaid invoices three months from now.
Solve it with a reminder for yourself the moment you send the invoice. One reminder set to fire 3 days before the due date (your cue to send email 1). One on the due date (email 2). One at 7 days past (email 3). One at 30 days past (email 4). You don\'t need a CRM. A simple invoice payment reminder per stage handles it.
If you\'re also the one paying invoices — most freelancers and small business owners are — the same reminder system works for both sides. See the invoice tracking guide for the dual-direction setup.
Three to five days before the due date, not after. A pre-due-date nudge is friendly, easy to send, and resolves most "I forgot" cases without any awkwardness. Sending only after the due date turns every reminder into a confrontation.
Four is the standard cadence: one before the due date, one on the due date, one at 7 days past due, and one at 30 days past due. After 30 days, switch to phone calls or a final-notice letter before involving a collections agency.
Keep it short, factual, and free of accusations. Lead with the invoice details — number, amount, due date — then ask one direct question. "Could you confirm when payment will be made?" lands better than "You have not paid." Tone follows length: short messages read as professional, long messages read as anxious.
Only if the late fee was in your original contract or invoice terms. Surprising a client with a late fee they never agreed to damages the relationship without recovering the money. If your terms include one, mention it on the second reminder and apply it on the third.
Include the invoice number and due date. "Invoice #1042 — due May 15" is better than "Friendly reminder." Specific subject lines get opened. Generic ones get ignored.
Set a reminder for yourself the moment you send the invoice. One reminder at day -3 (pre-due), one at day +7, one at day +30. Without a system, follow-ups get sent inconsistently or not at all — and the invoices that fall through the cracks are usually the smaller ones you don't want to chase but do want to be paid.
Set a reminder for each stage when you send the invoice. Email lands a few days before — you send the template. That's the cadence.
Create Follow-Up ReminderLast modified: