The Invoice That Outlived the Project: Notes on Chasing £420 With a Smile

On 12 January 2026 I sent a £420 invoice for a small identity and poster job. It was due on 26 January. It was paid on 4 November. In between there were four reminders, one very polite final email, and a useful lesson in what “flexible” actually costs.

I’m not naming the client. They were pleasant throughout. That’s part of the point. Late payment rarely arrives with horns and a tail; it usually arrives with a friendly email, a new excuse and a promise to “sort it at the end of the month”.

The job, the invoice and the first fortnight

The work was finished just before Christmas. It was a straightforward brief: a small logo refresh, a set of posters and a few social templates for a community organisation. The kind of job I like — useful, modest, close to home.

I didn’t ask for a deposit. I didn’t name the person who would actually pay the invoice. I didn’t put a late fee in the quote. I simply did the work, sent the files and trusted that a nice project would end with a nice payment.

The invoice went out on 12 January with 14-day terms. By 29 January I had heard nothing. By 3 February I sent the first nudge.

Reminder one: the friendly nudge

This is the email I sent, more or less:

“Hi [Name], hope you’re well. Just checking in on invoice [number] for £420, which was due on 26 January. Is it in the queue? Happy to re-send if that helps. Thanks, Drew.”

It was fine. It was polite. It was also the beginning of a pattern.

The reply came two days later: “So sorry, it’s with accounts. Should be sorted this week.”

It wasn’t.

What the delays actually looked like

Over the next few months I heard several variations on the same theme. The treasurer was a volunteer. The annual review had slowed things down. The bank signatories had changed. Someone had been on leave. The invoice had been “misplaced” but was now “definitely in the system”.

None of it was hostile. All of it was plausible. That’s what makes this kind of thing so slippery. A single delay is an event. A repeated delay is a system. The tricky part is noticing when one has become the other.

By July I had sent three reminders. By September I had sent four. Each time I kept the tone light, because I didn’t want to seem difficult. Each time I told myself the same thing: it’s only £420, they’re good people, it’ll land eventually.

But “eventually” is not a payment term.

The email I should have sent in January

Looking back, the first invoice should have been clearer. Not aggressive — just specific. Something like:

“Payment is due within 14 days. Work begins on receipt of a 50% deposit. Final files are released once the balance has cleared. Please confirm the name and email of the person who will process payment.”

That last line matters more than I used to think. “Accounts” is not a person. A named human with an email address is a person. If nobody can tell you who pays, the invoice is already drifting.

Red flags I now circle in red

I’ve built a small list from this job. It isn’t scientific, but it has saved me time since:

• No deposit requested, especially on projects over a few hundred pounds.
• No named person responsible for payment.
• A promise to “sort it at the end of the month” before the invoice has even been sent.
• Vague references to “accounts” with no date attached.
• Enthusiasm for the work, followed by silence on the paperwork.
• A request to “just send the final files” before payment has cleared.
• Two missed promised payment dates. After two, I stop treating it as a delay and start treating it as a system.

The final email, which was polite but finished

On 14 October I sent the last email. It was not angry. It was not elaborate. It simply moved the conversation from “whenever” to “by a date”.

“Hi [Name], I’m writing to confirm final payment of invoice [number] for £420. As of today it is significantly overdue. I’ve attached a statement. Please confirm by Friday 23 October when the payment will be made. If I don’t hear back, I’ll need to pause any further work and consider next steps. I’d much rather close this out simply. Thanks, Drew.”

The money arrived on 4 November 2026. No drama. No argument. Just a slow, grinding delay that took most of the year to resolve.

What I changed in my terms

I haven’t become a hard-nosed negotiator. I’ve just become clearer. My quotes now include:

• A 50% deposit before work starts.
• 14-day payment terms on the balance.
• The name of the person who will process the invoice.
• A simple late fee clause, whether or not I ever use it.
• A line saying final files are released on cleared funds.
• A calendar reminder on day 15, day 30 and day 45.

None of that is unusual. None of it is rude. It just gives everyone a map.

The quiet cost of being flexible

The £420 was the visible cost. The quiet cost was the headspace. I thought about that invoice far more than I thought about the work itself. I drafted emails in my head on dog walks. I wondered whether I was being too pushy, then whether I was being too soft. I let a small unpaid bill take up a ridiculous amount of room.

Flexibility is a useful tool. It is not a personality. There’s a difference between helping a client through a genuine hiccup and quietly absorbing months of administrative drift because you don’t want to make a fuss.

Where the line sits

A seasonal delay has a date. A boundary problem has a new excuse each time. If you’ve been given two clear promised payment dates and both have passed, it’s no longer about the time of year. It’s about how the client handles money.

That’s when I now ask for a payment plan in writing, pause further work and keep a clean paper trail. It doesn’t have to be confrontational. It just has to be clear.

The invoice is filed now. The templates are saved. The deposit clause is staying. And next time someone tells me it’ll be sorted at the end of the month, I’ll smile, send the terms and put a reminder in my diary.