How to follow up on an unpaid invoice without losing the client: four messages and a cutoff

A client once paid the VALORAE group nineteen days late, and I wrote about the editor side of that week in paying editors on the date you agreed.

That post covered who absorbs the gap.

This one covers the other half: the messages that go to the client, and when.

Because here is the complication. My first instinct with a late invoice was to wait, so I would not look desperate. Waiting is the expensive option.

A client who hears nothing on the due date learns that the date was soft. Every invoice after that one gets paid a little later, and you trained them to do it.

Day minus 3: the reminder nobody minds

The first message goes out before the invoice is late.

It is one line. The invoice number, the amount, the due date, and the link to pay. No apology and no small talk.

This message is not a chase. It is a service. Finance teams lose invoices in shared inboxes, and the person who approved your work is often not the person who pays it.

Let the tool send this one. Stripe's page on customer emails, which I read on 17 October 2026, says you can turn on reminders for unpaid recurring invoices and choose whether Stripe sends them before, when, or after the invoice is due. The same page says you can resend a one-off invoice from the dashboard or the API.

Whatever you invoice with, look for the same switch. A reminder that goes out by default is one you never have to feel awkward about.

Day 1: the note that assumes good faith

The day after the due date, send a short message from your own address.

"Hi, invoice 104 was due yesterday. Can you confirm it is in the payment run? Link attached."

That is the whole message. It assumes a process problem, because most of the time it is one.

Two rules here. Send it to the person who signs off the work and copy the billing contact if you have one. And ask a question that needs an answer, because "just checking in" invites silence.

If you never collected a billing contact, that is the gap to close next time. When I wrote up the onboarding process I put the signature and the first invoice ahead of kickoff for this reason. Payment logistics are easiest to sort out before anyone owes anybody anything.

Day 7: the direct one

A week late, the tone changes. Not the warmth. The precision.

Attach the invoice again. State the amount, the original due date, and how many days it is now overdue. Then ask for one of two things: a payment date, or a call today to sort out whatever is blocking it.

Some clients go quiet because something is wrong with the work and they have not said so. The day 7 message gives them a way to say it. A complaint about the work is a solvable problem. A silent client is not.

So if they raise a problem, separate it from the money. Fix the deliverable that is wrong, and keep the rest of the invoice due. Do not let one disputed video hold an entire month hostage.

And keep it about the invoice. Not about the relationship, not about how hard your team worked, not about your own cash flow. Your cash flow is not their problem. That is what the reserve is for.

Day 14: pause the next thing

Two weeks late with no date and no reply, stop starting new work.

This is the contrarian line, and it is short: keep delivering, stop starting.

Anything already in progress gets finished and handed over, because withholding half-done work turns a billing problem into a fight about ownership. But nothing new goes into the queue until the invoice has a date on it.

Say it plainly. "We will finish this week's batch as planned. New work for next month is on hold until invoice 104 is settled or scheduled. Happy to talk today."

That sentence is not a threat. It is the scope you already agreed, enforced on schedule.

I put the same idea another way in saying no to a client request: a boundary only works when it is written down before you need it. If your agreement says work pauses on overdue invoices, the day 14 message points at a clause instead of inventing one.

If it does not say that yet, add it to the next contract. Do not invent it in the middle of a late payment.

Day 30: the cutoff, in writing

A month late, you send the last chasing message you will write.

It names a final date. It lists what is owed, what has been delivered, and what happens on that date: the engagement ends, the handover goes out, and any remaining balance is handled as a closed account.

Then you do the thing you said.

Stripe's invoicing overview, read 17 October 2026, describes an uncollectible status for an invoice where the customer is unlikely to pay, and says you would normally treat it as bad debt in your accounting process. Most invoicing tools have an equivalent. Using it is not giving up. It is closing the file so it stops occupying your week.

Ending the engagement cleanly matters more than the balance. I wrote how to fire a client with this case in mind: hand everything back, list open invoices once, and keep the reason short.

I will be honest about the limit. Chasing a balance past this point usually means formal collection or legal steps, and those depend on where you and the client are. I am not the right person to advise on that. Someone qualified where you work is.

Day 31: fix the calendar, not the client

Every late invoice is a lesson about your terms, not your client.

Three changes do most of the work.

Take payment before the work starts, or at least have the first invoice scheduled before kickoff. Stagger client due dates across the month so one late payer does not land on the same day as your editors' pay. And put the pause clause in the agreement, so the day 14 message is a reference rather than a negotiation.

Across the VALORAE group, the cash rule I care about most runs the other way: editors get paid on the date we agreed, whatever any client does. That only works if chasing is a schedule, not a feeling.

Editors on the other side of this deal with the same problem from below. VALORAE Cast wrote the version for them in six edits deep and still unpaid, and the advice there matches this one: stop delivering new work and send one dated invoice.

It is useful to read the editor's version. It shows you how your own day 14 message lands.

The short version

• Send a reminder before the due date, automatically.
• Follow up the day after it is due, with a question that needs an answer.
• At day 7, attach the invoice and ask for a payment date or a call.
• At day 14, keep delivering what is in progress and stop starting new work.
• At day 30, name a final date in writing and keep to it.
• Write the pause clause into the next agreement.
• Pay your editors on time regardless.

More operator notes like this live at tgsidd.com.