A reminder schedule that works without souring the relationship

Chasing an invoice feels like a nerve problem, so people try to solve it with nerve. It is a scheduling problem, and the reason it consumes so much emotional energy is that most freelancers re-decide each chase from scratch (whether to send it, when, how apologetic to be) instead of deciding once and letting a fixed cadence run.

A schedule set in advance also removes the thing that actually damages relationships. Chases sent at random intervals, in a tone that tracks how annoyed you happen to be that morning, read as personal. Chases that arrive on the same rhythm for every client read as process, and nobody resents process.

The chasing is unpaid work, and it is a lot of it

In a 2022 survey of New York freelancers run as campaign research by the Freelancers Union with the Authors Guild, the Graphic Artists Guild and several other trade bodies, 76% of respondents said they spend one to two hours a week chasing payment. Treat that number carefully: it is one state, four years ago, the sample size was not published, and the organizations running it were campaigning for legislation at the time. It is not a measurement of freelancers generally.

It is still the right order of magnitude to plan against, and the arithmetic is worth doing on your own numbers rather than theirs. As an illustration, an hour and a half a week is 78 hours a year. At an effective hourly rate of €60 that is €4,680 of your capacity spent on collection, which is more than most freelancers spend on software, insurance and accountancy combined. If you have never worked out what your own hour is worth after all the unbilled time, the effective hourly rate calculator will give you the figure to multiply by.

The point of a schedule is not to make chasing pleasant. It is to cut those hours by removing the decision, and to make the chases that do happen land earlier, when they still work.

The cadence

Six touches. The first one arrives before anything is late, which is the step most people skip and the one that prevents the rest.

Three things change as you move down that table, and they change in a deliberate order.

Channel escalates before tone does. Steps one to three stay on the original email thread, because a reply in an existing thread carries the invoice, the date and the original approval with it. Step four starts a new thread with a new subject line, because a long thread gets collapsed and skimmed. Step five moves to the phone, which is the largest single jump in effectiveness available and the one people avoid longest.

The audience widens before the language hardens. At day seven you copy the project contact, not to embarrass anyone but because they are the person with an internal interest in the work continuing. At day 30 the notice reaches someone senior to them. You never widen the audience and harden the tone in the same step; doing both at once is what turns a collection into a conflict.

What is attached changes as you go. Early steps reference the invoice. Day seven re-attaches it, because the most common honest answer at day seven is that it was never entered. Day 14 attaches a statement of account if more than one invoice is open. Day 30 attaches a formal PDF.

Before the due date is the step that pays for itself

A note three working days before the due date is not a chase, and framing it as one is why people leave it out. It is a systems check that catches the two defects that generate most late payments: the invoice never reached accounts payable, and the invoice reached them and was rejected without anyone telling you.

Both of those are recoverable in three days and expensive at thirty.

Subject: RE: Invoice 2026-041 — [Project name]

Hi [name],

Invoice 2026-041 (€4,200) falls due on Thursday 20 August.
Could you confirm it's in the system and scheduled for that run?

If anything's missing on it (PO reference, entity name, anything
your side needs), send it back and I'll reissue today.

Thanks,
[Name]

Line by line: the subject line stays on the original thread so the invoice travels with the message. The amount and date appear in the first sentence because the recipient may handle a hundred of these a week and should not have to open an attachment to know what you want. "Confirm it's in the system and scheduled" asks a question they can answer in four words, which is why it gets answered — "when will this be paid" often cannot be answered by the person reading it. The second paragraph is the whole point of the email: it offers to fix a rejection before the rejection costs you a full payment cycle. There is no apology anywhere, and there is nothing to apologize for.

Cut the second paragraph if you have worked with this client's finance team for years and their process is known good. Keep it for every new client, indefinitely.

Day seven is where the tone changes, once

By day seven the polite assumptions have been tested. The invoice is either stuck, disputed, or deprioritized, and all three respond to the same message: a restatement of the facts with a specific date attached.

Subject: Overdue: invoice 2026-041, €4,200, due 20 August

Hi [name],

Invoice 2026-041 for €4,200 was due on 20 August and is now seven
days overdue. I've attached it again here.

Payment terms on the signed agreement are 14 days from issue.
Could you let me know the payment date, or tell me what's holding
it up so I can resolve it?

If it's easier, the invoice can be paid by card or bank transfer
on this link: [link]

[Name]

The new subject line carries the amount and the word "overdue," because it may be forwarded to someone who has never seen the thread and needs the facts in the preview pane. The first sentence states three facts and no feelings. Referring to the signed agreement rather than to "my terms" moves the conversation from your preference to a document both parties signed. The ask is deliberately double: give me a date, or tell me the obstacle. A single ask is easy to leave unanswered; a fork is harder.

The payment link matters more than it looks. Every step you remove between deciding to pay and paying moves the invoice up the queue, which is the practical case for sending invoices that can be paid by card, SEPA or bank transfer from the document itself rather than as a PDF with account details at the bottom.

If drafting these under pressure is what stops you sending them, the free payment reminder generator will produce a subject line and body from the invoice number, due date, amount and the tone you pick, in the browser and without a signup.

Automation helps, but only the part that is genuinely mechanical

Nearly every invoicing tool now sends automatic reminders on a schedule. The differences that matter are whether the reminder knows what else that client owes, whether it stops firing when a payment lands, and whether it goes to accounts payable rather than to whoever the invoice was addressed to. Those are the failure modes that produce the embarrassing chase for money that arrived yesterday, and they are the substance of the Bonsai alternative comparison rather than the count of reminder templates.

Automate steps one to four. Do not automate steps five and six. A phone call and a formal notice are decisions, and a system that makes them for you will eventually make one you would not have made.

Where the schedule stops

At day 30 the reminder is no longer a reminder. It becomes a written notice that states what you are entitled to, and in the EU and the UK that entitlement exists automatically — under Directive 2011/7/EU interest on a late B2B payment runs without any reminder being necessary, and the fixed recovery compensation under Article 6 applies on top of it. Your emails are not what create the claim. They are what evidence you gave the client a fair chance to avoid it.

What that notice must contain, the current statutory rates, and the harder second version of the letter are in how to write an overdue payment letter that gets paid. What comes after it, by jurisdiction, is in the escalation ladder when a client stops paying.

Before you build the schedule, though, it is worth checking whether you need it as often as you do. Most repeat late payment traces to a defect in routing, invoice content or timing rather than to client behavior, and those are listed in seven reasons clients pay late. The whole prevention system sits in the freelancer's guide to getting paid on time.

Three changes to make this week

Write the cadence down as six rows with dates, once, and apply it to every open invoice regardless of how the client makes you feel.

Add the pre-due check to every invoice you send from now on. It is the only step that prevents late payment rather than responding to it.

Draft both templates today, while nothing is overdue and your tone is neutral. The version you write when you are owed €4,200 and angry is never the version you should send.

Worklyn's The Polite Chase drafts each step of that cadence against the real invoice and waits for your approval before anything goes out, so the schedule runs whether or not you feel like running it.