How to automate invoicing and payment reminders for freelancers

Getting paid is a process, not a personality test. The invoice has to be right, the client has to know how to pay, and someone has to notice when they do not. Automation is good at the noticing. It is bad at the relationship, which is why this template stops and hands the thread back to you.

This is written for freelancers in the UK, and it is usable in the US if you swap the tax rules for your own. It is not tax advice. I am not quoting interest rates or tool prices. Both go stale. The official pages are linked so you can check them on the day you send.

If invoicing is one item on a longer list of chores, it also appears in ten tasks you can automate this week. The stack around it is in AI tools for freelancers.

Use the accounting tool before you build a workflow

FreeAgent, Xero, QuickFile and Stripe Invoicing can all raise an invoice, and several of them can email a reminder. Their pages: FreeAgent, Xero, QuickFile and Stripe Invoicing. Spend twenty minutes in the product you already pay for. If its reminder is clear and you can edit the words, use it. Building a parallel chaser in Zapier is how clients get two emails on the same morning.

Build your own sequence only when the product will not do the thing you need. Common gaps: you want a draft instead of a send, you want to stop automatically when a client replies, or you want a payment link the accounting tool does not include. Those are fair reasons. “I felt like using Make” is not.

A spreadsheet can run this if you are small. Columns that matter: invoice number, client name, email, issue date, due date, amount, currency, status (draft, sent, paid, query), and the date of the last reminder. Status is the field the automation is allowed to trust. If you forget to mark an invoice paid, the robot will chase a client who has paid. That is the failure mode to design for. Reconcile the sheet, or the accounting tool, before you widen the schedule.

What to put on the invoice

For UK invoices, start with the government’s own list and follow it for your situation: invoices, what they must include. In ordinary language, a freelancer’s invoice usually needs a unique number, the date, your name and address, the customer’s name and address, a description of the work, the amount, and the payment terms. VAT registration adds further lines, including your VAT number and the VAT amount. If you are not registered, do not invent VAT.

Payment terms belong on the invoice in words and as a date. “14 days” is ambiguous if you do not say from when. “Due 14 days from the invoice date” is a sentence a workflow can also understand, because the due date is a field, not a vibe.

Write the payment method on the invoice. Bank details, or a link created by your accounting tool or by Stripe. Do not change bank details inside a reminder email if you can avoid it. Invoice fraud lives on that change. If details must change, say so in a way the client can verify out of band, such as a phone call they start using the number they already had.

The reminder sequence

Four touches, then a person. All of them assume the invoice was correct and was actually sent.

On the day you send it. The covering email is short. Attach the invoice or link it. Say the due date and how to pay. This one can be a template you send yourself, every time, without any AI.

Three days before the due date, only if the status is still unpaid. A single sentence. Many clients pay from this one because they missed the first mail, not because they were refusing.

On the due date, if still unpaid. Polite, specific, and easy to act on. Include the number and the link. Do not editorialize.

Seven days after the due date, if still unpaid. Slightly firmer. Still no speech about lawyers. Ask if something is wrong with the invoice, because sometimes something is.

Then the automation stops, even if the invoice is still open. You write the next message, or you call. A fifth automated email is where small businesses start to sound like a department nobody respects.

If the client replies at any point, the status becomes query and the sequence ends. A robot that chases through a dispute is the bug you will hear about.

Words you can adapt

Sending the invoice:

Subject: Invoice 184 — due 14 days from today

Hello Ada,

Invoice 184 for the March workshop is attached. The amount is on the invoice. It is due 14 days from the invoice date. You can pay by the bank details on the PDF, or with this link: [payment link].

If anything looks wrong, reply to this email and I will fix it.

Sandun

Three days before:

Subject: Invoice 184 is due on Tuesday

Hello Ada,

A quick note that invoice 184 is due on Tuesday. The payment link is unchanged: [payment link]. If it is already on its way, ignore this.

Sandun

Due date:

Subject: Invoice 184 is due today

Hello Ada,

Invoice 184 is due today. If you have already paid, thank you, and I will mark it off as soon as I see it. If not, the payment link is: [payment link].

Sandun

Seven days later:

Subject: Invoice 184 is a week overdue

Hello Ada,

Invoice 184 was due a week ago and still looks unpaid from my side. If there is a problem with the invoice or the work, tell me and I will sort it. If it is just stuck, here is the link again: [payment link].

I will follow up myself if I do not hear back.

Sandun

Edit the name, the number, the date and the sign-off. Delete the “follow up myself” line if you will not. Do not add “we may charge interest” unless you have read the current rules and you intend to do it. The government page for business-to-business late payment is late commercial payments: interest. The figures there are the ones to use, not a number remembered from a talk.

Where the automation sits

The workflow, whether it lives in the accounting tool, Make, Zapier or n8n, is a daily check:

1. Look at invoices whose status is sent.
2. Compare today with the due date.
3. If a reminder for this stage was already sent, do nothing.
4. If the stage is due, send the matching email, or create a draft if you do not trust send yet.
5. Record the stage on the invoice so tomorrow’s run will not repeat it.
6. If status is paid or query, never send.

Draft-first is the right first month. You click send. When the text has gone out untouched for a while, you can let the early reminders send and keep the seven-day note as a draft. The email assistant pattern is the same instinct: the machine prepares, you are still on the hook for the words that leave.

AI is optional here and often unnecessary. The four emails above do not need a model. A model becomes useful only if you want a one-line summary of a long query before you reply. It must not rewrite the amount. Amounts come from the invoice record, not from a sentence the model found plausible.

If you use n8n on a VPS, the reminder workflow is only as reliable as that box. The self-hosting guide is the bar: backups, HTTPS, and a quick way to see that the daily run happened. A cloud Zapier or Make scenario is a better home for “please pay this” if you will not watch a server. The tool comparison is that choice without the invoicing detail.

When to stop being automatic

Stop the sequence, and write by hand, when:

• The client has replied, even with “next week”.
• The invoice might be wrong.
• The work is disputed.
• The client is a person who is struggling, not a forgotten accounts payable queue.
• You are about to mention interest, a debt collector, or a court. Those are decisions. They are not a fifth template. Check the current late-payment guidance if it is a UK business client, and get advice if the sum matters.

Keep a note of who was chased and when. If you are ever asked, you want to show a polite trail, not a comedy of fourteen emails.

The rest of a freelance week is a different problem. Once reminders are boring, the next useful automation is usually the enquiry form, not another email about money. That one is the lead capture guide.