Unpaid Invoice Follow Up: How to Chase Late Payments Without Losing the Client

This article first appeared on Invoala.

The short answer

An unpaid invoice follow up works when it lands on a schedule, restates the exact facts (invoice number, amount, due date, days late), and asks for one specific thing. Chase at day 1 after the due date, again around day 7, again around day 14, then escalate — by phone or a formal demand — around day 30. Write down your terms before the work starts, keep the paper trail in one place, and every follow up becomes a copy-and-send job instead of a confrontation. Late payment is usually a process problem, not a character problem: the invoice never reached the right inbox, the payer's payment run is monthly, or the amount is disputed and nobody said so.

Photo by Wesley Tingey on Unsplash

How to Write a Payment Follow Up Email That Works

A payment follow up email should be short, factual, and easy to act on. The temptation is to write three paragraphs explaining how disappointed you are. Resist it — long emails get skimmed and postponed.

Use this structure:

• Subject line that names the document. "Invoice #1042 — $2,400 — due 12 March" beats "Quick question". It's findable and it tells the reader this isn't a chat.
• One line of context. "Sending a friendly reminder about the invoice below."
• The facts as a small block. Invoice number, amount, issue date, due date, days overdue, payment details.
• One clear ask. "Could you confirm the payment date?" or "Could you let me know if anything is missing for this to be approved?" Vague asks get vague replies.
• A warm close with no threat. The first reminder is housekeeping. Most late payments respond to it.

Practical details that make a difference: attach the original PDF again (people genuinely can't find it), reply in the same thread as the original invoice so the history stays together, and keep the tone identical whether it's day 2 or day 12. If your invoice was generated as an A4 PDF from a free invoice generator, the layout, totals and payment details are already consistent, so you can paste the same figures into every follow up without re-typing numbers.

Example: Chasing a $2,400 invoice that's 21 days late

Say you invoice a client $2,400 for a website build with 8% sales tax, on net-14 terms.

• Subtotal: $2,400.00
• Sales tax at 8%: $192.00
• Total due: $2,592.00
• Issued: 1 March. Due: 15 March.
• Payment received: nothing. Today is 5 April — 21 days past the due date.

At this point you've sent a reminder on 16 March and another on 22 March. The third email is where you shift from reminding to resolving, and it should read roughly like this:

Two things are doing the work here: the real number in the subject line, and the two-option question. Option 1 gets you a date. Option 2 gets the hidden problem out into the open, which is where most stalled invoices actually live.

Then add simple interest or a late fee only if your contract or invoice already states it — and if it does, quote the exact clause and the exact figure. Whether you can charge late payment interest at all, and how much, depends on your jurisdiction and on what your contract says, so check the official source for your country rather than copying a rate from a blog.

Photo by SumUp on Unsplash

Late Payment: What to Say in a Second Reminder

The second reminder is the one people put off, usually because it feels rude to repeat themselves. It isn't. What reads as rude is silence for six weeks followed by a demand letter.

For a second reminder, change one thing: move the ask from "please pay" to "please confirm a date", and add a consequence you're actually willing to carry out. Examples of honest consequences:

• "I'll pause work on the next milestone until this clears."
• "From 1 May I'll add the late fee set out in clause 6 of our agreement."
• "If I haven't heard back by Friday I'll give you a call to sort it out."

Don't threaten legal action you won't take, and don't invent fees your contract doesn't mention. If you're unsure what your agreement allows, describe the situation plainly and say you'll follow up formally — then check the rules that apply where you are.

If you're juggling more than a few invoices, the harder problem isn't wording, it's remembering who is at day 7 and who is at day 30. That's a tracking problem, not a writing problem. Keeping a simple list of paid, due and overdue invoices — which is what invoice payment tracking is for — means the second reminder goes out because it's on the list, not because you happened to remember.

How Invoala helps you follow up on unpaid invoices

Invoala is a free invoice generator with no sign-up and no watermark, so the mechanical parts of this process take a couple of minutes rather than an afternoon:

1. Get the invoice right first. Fill in the invoice generator form — client details, line items, tax, payment terms — and download an A4-accurate PDF. A clean, correctly formatted invoice with a clear due date removes the most common excuse for late payment.
2. Add your payment terms to the document, not just the email. Due date, accepted payment methods, and any late fee clause belong on the invoice itself, where they're visible 30 days later when someone finally opens it.
3. Send it and keep the PDF. Because nothing is watermarked and you don't need an account, the same file you sent is the file you re-attach to reminder two and reminder three. No version confusion.
4. Use reminders instead of memory. Invoala's automated payment reminders handle the "when do I chase?" part of the sequence, so the day-1, day-7 and day-14 nudges go out consistently.
5. Track the state of each invoice. Mark what's paid, due or overdue so escalation to a phone call happens on schedule.

If you'd rather start from a layout than a blank form, there are free downloadable invoice templates you can work from, and a walkthrough of the step-by-step invoice creation process if you want the full picture. For freelance-specific terms — deposits, kill fees, net-30 vs net-14 — there's a dedicated guide to invoicing for freelancers.

How to Make an Invoice for Web Development Work

Web development invoices are unusually prone to late payment because the deliverables are invisible. Nobody can hold your API refactor in their hand, so approval gets fuzzy and payment stalls.

What helps:

• Invoice by milestone, not by month. "Milestone 2: checkout flow" is verifiable. "April development" is arguable.
• Name the deliverable and the acceptance date. If the client had a week to raise issues and didn't, say so on the invoice.
• Break out third-party costs separately. Domains, hosting, licenses and plugin fees are pass-through costs and should be visible as their own lines, not buried in a rate.
• List revisions included. Two rounds included, then hourly, keeps scope disputes off the payment thread.
• Put the environment and handover in the description if payment is tied to it. "Final payment releases repository access and production credentials" is descriptive, not aggressive — and it needs to be in the contract too.

Use whatever unit your client agreed to: hourly, fixed milestone, or a retainer drawn down in days. A generated PDF that itemises each of those clearly does a lot of the arguing for you.

Writing Invoices for Landscaping Jobs and Deposits

Landscaping money is usually split: a deposit up front, then a balance on completion, often with materials bought before the first day on site. Get those three moments onto paper.

• Deposit invoice, issued before work starts. State the deposit as a percentage or a fixed figure, state what it covers (materials, scheduling, plant hire), and state whether it's refundable. Whether a deposit must be refundable, and under what consumer rules, depends on your jurisdiction and the type of customer.
• Progress invoice for materials or long jobs. If a job runs across several weeks, invoice at agreed intervals rather than carrying all the cost yourself.
• Final invoice on completion. Reference the deposit already paid and show the outstanding balance clearly, so the client isn't doing mental arithmetic and stalling.

Two practical habits: take photos of the finished work with timestamps, and put the job address and a one-line scope on the invoice. "Front and rear garden clearance, 14 Elm Road" is much harder to dispute than "landscaping services" — and if it ever has to be escalated, that description is your evidence. For recurring maintenance contracts, net-14 terms with a fixed monthly amount typically beat per-visit invoicing, in most cases, depending on how your customers prefer to be billed.

How to Create an Invoice Without Software

You don't need accounting software to issue a professional invoice. You need five things on one page:

1. The word "Invoice" plus a unique invoice number you never reuse.
2. Your business name and contact details, and the client's legal or trading name.
3. Line items: description, quantity, unit price, and line total.
4. Totals: subtotal, tax if applicable, anything already paid, and the total due.
5. Payment details and the due date, stated explicitly.

Then the practical choices: a spreadsheet or word processor works, but page-size and margin settings are the usual failure point — an invoice that spills onto a second page or prints half off the edge looks careless and slows approval. Generating a properly sized A4 PDF avoids that entirely. If you do keep your own template, save it as a PDF rather than a document file, since PDFs render identically on the client's machine and can't be edited by accident.

What you must check locally: whether a tax identification number, VAT/GST number, or a specific tax label is legally required on your invoices. That varies by country and by whether you're registered, so confirm it with the official tax authority where you operate rather than relying on a template alone.This isn't legal or tax advice — it's a description of the general rule that invoices should identify the parties, the work, the amount and the deadline.

The follow-up calendar, in one line each

Day 0: invoice issued with a due date and your payment terms on it. Day 1 after due date: friendly reminder, facts only. Day 7: second reminder asking for a payment date. Day 14: firmer reminder naming the consequence you'll actually apply. Day 30: phone call or formal written demand, with a full paper trail of every previous message. Beyond that, it depends on the amount, your contract and your jurisdiction — and for anything substantial, it's worth checking what your local rules and, if needed, a qualified professional say about recovering the debt.

---

Originally published at Unpaid Invoice Follow Up: How to Chase Late Payments Without Losing the Client. More guides at Invoala.