How to chase a late invoice without losing the client

Chase in four stages: a neutral nudge the day after the due date, a firmer reminder at day seven, a formal notice at day fourteen quoting your terms and any late-payment interest, and a final letter before action at day thirty. Keep every message short, unemotional and attached to the original invoice. Most invoices are paid at stage one or two.

The mistake almost everyone makes is waiting. You feel awkward, so you leave it a fortnight, and by then you are angry, so the message you finally send carries that. Now it is a confrontation instead of an admin matter.

Chase on day one and it is not a confrontation. It is a reminder that a thing is due, sent the way a dentist reminds you about an appointment.

Stage 1 — the day after (neutral)

Hi Sarah — invoice #1043 for £3,708 was due yesterday. I've attached it again in case it got buried. Let me know if there's anything you need from me.

No apology, no accusation. "In case it got buried" gives them a face-saving exit, which is usually the truth anyway.

Stage 2 — day seven (firmer, still friendly)

Hi Sarah — following up on invoice #1043, £3,708, now a week past due. Could you let me know when it's scheduled for payment? Happy to re-send to a different address if accounts handle it.

"When is it scheduled" is the key question. It asks for a date rather than a yes, and it is much harder to ignore than "any update?".

Stage 3 — day fourteen (formal)

Switch register. Reference the payment terms they agreed, state the amount outstanding, and mention late-payment interest if your terms carry it. In the UK, the Late Payment of Commercial Debts Act gives you a statutory right to interest and a fixed recovery cost even when your own terms are silent; India's MSMED Act gives registered micro and small enterprises a similar right against larger buyers. Knowing this exists changes how you write the message, even if you never invoke it.

Stage 4 — day thirty (final notice)

State that unless payment is received by a named date, you will begin recovery. Then actually do it — small claims, a letter before action, or a debt recovery service. An empty threat teaches the client that your deadlines are decorative.

When to stop chasing and start protecting

If a client has gone two invoices deep without paying one, stop working. Continuing to deliver while unpaid is not loyalty, it is an unsecured loan you did not agree to make. The uncomfortable conversation now is cheaper than the write-off later.

Make it automatic

The reason people do not follow an escalation ladder is that it depends on remembering. Nobody remembers. EstimateBill reminds you on the due date and again three days later, and writes the WhatsApp message for you in a friendly, formal or final tone — so chasing becomes a tap rather than a decision about how annoyed to sound.

What to do when there is no reply at all

Silence is the hardest case, because escalating politeness gets you nowhere. Change the channel rather than the wording. If three emails have gone unanswered, phone. If the phone goes unanswered, message the person who hired you rather than the accounts address — they have a relationship to protect and you do not.

One specific technique that works more often than it should: ask a question that requires an answer other than money. "Can you confirm invoice 1043 was received and approved?" is easier to answer than "please pay", and once someone has confirmed receipt and approval they have removed every excuse except the real one.

Find out who actually pays

In any organisation above about ten people, the person who hired you is not the person who pays you. Your invoice has to be approved by your contact, entered by a bookkeeper and released in a payment run. A delay at any of those three looks identical from outside.

So ask which stage it is stuck at. "Has it been approved yet, or is it waiting with you?" tells you whether to chase your contact or the finance inbox, and stops you sending firm reminders to someone who approved it three weeks ago and is as frustrated as you are.

The purchase-order problem

Large customers frequently will not pay an invoice without a purchase-order number on it. If you did not ask for one at the start, your invoice can sit in a rejected pile for a month with nobody telling you, because the rejection is automated. Always ask, before starting work, whether a PO is needed and what it is.

When to stop working

If a second invoice becomes due while the first is unpaid, stop. Continuing to deliver is an unsecured loan you never agreed to make, and it gets harder to recover with every hour you add. Say it without drama: "I'll pick this back up as soon as invoice 1043 clears." Stopping work over an unpaid invoice covers how to set that up in your terms so it is contractual rather than personal.

What comes after the final reminder

Three realistic options, in rising order of cost.

• A formal letter before action. Free, and it resolves a surprising proportion of cases, because it signals you are not going to drop it.
• A small-claims process. Most countries have one designed to be used without a lawyer, with modest fees and a low ceiling. Slow, but real.
• A debt-collection agency. Fast to start and expensive — commonly a fifth or more of what is recovered — and it ends the client relationship permanently.

Before any of them, be honest about the arithmetic. Pursuing £400 through three months of effort is usually a worse outcome than writing it off and spending the time on work that pays. Pursue on principle only when you can afford to.

Prevention beats all of it

Almost every late invoice traces back to something that happened before the work started: no deposit, no PO, no agreed due date, no written scope, or an invoice sent eleven days after the job finished. Why invoices get ignored covers the failure modes; the two with the biggest effect are taking a deposit and invoicing the same day.

EstimateBill tracks what is unpaid, reminds you on the due date, and writes the follow-up message for you in three tones. See how the reminders work.