You shipped the feature, fixed the bugs, and answered the "quick question" that turned into a two-hour debugging session. The invoice went out on the first of the month. Thirty days later: nothing.
The most I have ever waited on was $4,800. The client answered every message within a day - "accounts is processing it", "the approver is on holiday", "next Friday, promise". What got it paid was not a longer or angrier email. It was the third email in a sequence I already had sitting in my drafts folder, sent on day 30, worded almost exactly like the one below. The money arrived in 48 hours.
If you freelance or run a small dev shop, chasing payment for finished work is one of the worst parts of the job. The fix is not a better apology for asking. It is a process: the same three emails, on the same days, every time.
Here they are, copy-paste.
Day 7: the polite nudge
At seven days past the due date, assume a boring explanation. The invoice was missed, routed to the wrong person, or stuck in an approval queue. Your goal is a response without friction.
Subject: Quick follow-up on invoice #[NUMBER]
Hi [CLIENT NAME],
I'm following up on invoice #[NUMBER] for [PROJECT/DELIVERABLE], which was due on [DUE DATE].
Could you confirm that it's been received and let me know when I can expect payment?
For reference, the outstanding amount is [AMOUNT].
Thanks,
[YOUR NAME]
Why this works: you identify the invoice, state the amount, and ask for one specific next step. No accusation, no essay.
Send it in the original invoice thread so the context travels with it. If they reply with a payment date, write it down. A promise in a casual email is easy to forget - yours and theirs.
Day 14: the firm follow-up
Two weeks late, be more direct. This message says the balance needs attention; it does not ask whether anyone saw your last email.
Subject: Payment overdue - invoice #[NUMBER]
Hi [CLIENT NAME],
Invoice #[NUMBER] for [AMOUNT] was due on [DUE DATE] and remains unpaid.
Please confirm the scheduled payment date by [RESPONSE DEADLINE].
If payment has already been processed, please disregard this reminder and let me know so I can update my records.
Thank you,
[YOUR NAME]
Why this works: it replaces a vague request with a clear action and a deadline, and it gives the client an easy out if payment is already moving.
Set the response deadline at two business days. If the answer is "waiting for approval," ask when approval is expected. If "accounting pays on Fridays," ask which Friday your invoice is scheduled for. Turn "we'll get to it" into something you can track.
Check your contract before this email. If it allows late fees, interest, or pausing work, know the terms before you invoke them. Never add fees the contract does not mention.
These templates are communication examples, not legal advice. Check your contract and applicable local law before adding late fees or taking collection action.
Day 30: the final notice
A month overdue changes the conversation. Stay polite, but do not send a third email that sounds like the first one.
Subject: Final payment notice - invoice #[NUMBER]
Hi [CLIENT NAME],
Invoice #[NUMBER] for [AMOUNT], originally due on [DUE DATE], remains outstanding despite my previous follow-ups.
Please arrange payment in full by [FINAL DEADLINE] or contact me by that date to confirm a concrete payment arrangement.
If the balance remains unpaid and I have not received an agreed resolution, I will consider the next steps available under our agreement and applicable law, which may include formal collection or recovery proceedings.
Please confirm receipt of this notice.
Regards,
[YOUR NAME]
Why this works: it is factual, it documents the history, and it sets an explicit deadline without threats you cannot carry out.
Only name actions you are genuinely prepared and legally entitled to take. Before formal recovery, review your agreement, preserve the invoices and correspondence, and check the rules in the relevant jurisdiction. And do not assume you can shut down a live service, revoke access, or withhold source code - your contract decides that, not your frustration.
What happens between the emails matters as much
- Keep a payment log. Invoice number, amount, due date, reminder dates, responses, promised dates. The day you have three late invoices, this log is the only thing keeping the story straight.
- Separate payment from new work. A client who has not paid asking for another feature is not an automatic yes. Review the agreement and discuss a pause or revised schedule.
- Make paying easy. Every email includes the invoice, the amount, payment instructions, and the reference their accounting needs. Every extra step is another week.
- Fix the next contract. Explicit payment terms, a defined invoicing schedule, a stated late-fee rule. For larger projects, milestone payments instead of one big invoice at the end.
- Do not let one client be your whole business. A great relationship is still a financial risk if one unpaid invoice stops you paying your own bills.
Build the system before you need it
The best time to decide how you handle late payment is before an invoice goes overdue. Set three calendar reminders for days 7, 14, and 30, save the scripts as templates, and when the day comes you fill in the brackets and send. You follow a process instead of writing an email while frustrated.
Your turn: what is worse - clients who ignore reminders, clients who keep promising "next week," or clients who dispute the invoice after the work is done? And what actually worked for you?
Written by the Change Brief team - we build practical, no-signup toolkits for freelancers.
AI assistance was used in drafting this article. The publisher reviewed and edited the content and takes responsibility for the final version.
Top comments (10)
The day 30 email working because it was already sitting in drafts is the whole lesson. Nobody writes a good escalation email while they are angry on day 30. They write a long one, or they wait another week. Having all three written before anything is late turns chasing payment from a mood into a schedule. The "which Friday" question is underrated too. "Accounting pays on Fridays" feels like an answer until you ask which one.
From a mood into a schedule - that is the whole lesson in one line. And yes: 'accounts pay on Fridays' survives for weeks as a non-answer until someone asks which one. Shortest useful question in the process.
The non-answer survives because nobody puts a date on the question. Asking "which Friday" works once; asking it with "if I don't hear by Thursday, the next email goes out Friday morning" is what makes it a process instead of a favor you're requesting.
That is the upgrade - 'which Friday' is a question, and 'if I don't hear by Thursday, the next email goes out Friday morning' is a system. The part people underestimate is what it does for the follow-up: you are not chasing anyone, you are executing a schedule they already saw. Tone matters though. It has to read like a calendar fact, not an ultimatum. Flat and boring is what makes it work.
"Executing a schedule they already saw" is the right frame, and it points at the part that makes flat possible: the schedule was visible from the first email. The day 7 nudge reads as a calendar fact because the invoice itself said net 30. Tone only becomes an ultimatum when the deadline shows up for the first time inside the chase.
Exactly - the deadline was never news, so the nudge never has to carry it. The failure mode I keep seeing is the quiet invoice: net 30 lives in a PDF nobody opens, so the day 31 email is the first time the client meets the number. Put the date in the email body, the proposal and the invoice, and the chase is just the calendar speaking.
The quiet invoice is the right name for it, and the three-place fix works because each surface reaches a different person. The champion reads the email, the approver reads the proposal, and whoever processes payment lives in the invoice. The date has to survive all three handoffs, because the person who finally pays was never in the conversation where it was agreed.
That is the sharpest framing of it - the date is not a reminder, it is the only context the payer gets. By the time the invoice reaches the payment queue, the relationship is out of the room and the invoice has to make the case alone. Anything that lives only in the email thread is invisible to the person who can actually send the money.
The day-30 email works, but what saved us most was never getting there: a deposit up front and milestones tied to delivery. Late payers usually show it in the first invoice, so that's when we tighten terms.
Prevention beats collection every time. The deposit does two jobs: it filters for clients who pay, and it changes the tone of every later conversation because money is already moving. And the first-invoice tell is real - the client who goes quiet on a small first invoice is showing you exactly who they will be at net 30.