• Enquiry
  • Quote
  • Agree
  • Work
  • Invoice
  • Paid

The First Fourteen Days

Most late invoices are not disputes. They are invoices that nobody has processed, and the fortnight after the due date is when a single message resolves the majority of them.

For a software-side reference alongside this discussion of payment follow-up, disputes, and small-business administration, Monitask provides guidance on being more proactive at work.

Why the window matters

An overdue invoice ages badly. Urgency fades, disputes become more likely, and the debtor begins prioritising other creditors. (R3, the UK restructuring and insolvency trade body, describing the pattern.)

In the first fortnight none of that has happened. The invoice is recent, the work is remembered, and nobody has formed a position.

Which makes this the cheapest recovery available, and the effort is a message.

Day one

A short, neutral message on the day after the due date.

"Hi — invoice 214 was due yesterday and I don't think it's come through. Could you check whether it's gone into the run? Happy to resend if you need it."

Three things it does: it establishes that you noticed, it offers an explanation that is not their fault, and it removes the obstacle of a missing document.

No apology, no accusation. Both are read as weakness in slightly different ways.

Send it even when you are confident it is coming. The habit is what makes it unremarkable, and a firm that always asks on day one is a firm that gets paid before firms that ask on day thirty.

Day seven

A firmer message, still written by you rather than generated.

"Following up on invoice 214, now a week past due. Could you let me know when it's scheduled? If there's a query on it, tell me now and I'll sort it today."

The second sentence is the important one. A query you do not know about is a query nobody is resolving, and asking directly surfaces it a fortnight earlier than waiting will.

Day fourteen

A phone call.

Not another email. The pattern of escalation that works is not increasingly stern messages — it is a change of channel, because a different channel reaches a different person.

Ask three questions: has it been approved, is it scheduled, and if not what is stopping it.

Then write down what you were told, and send a one-line confirmation of it. "Thanks — noting you've said it will go in the run on the 28th." That converts a verbal assurance into a dated record and makes the next conversation easier.

The tone throughout

Businesslike, brief, and assuming good faith until there is evidence otherwise.

Most late payment is process rather than intent. Invoices that never entered a system, approvals sitting with somebody on leave, purchase orders that do not match.

A supplier who treats every delay as bad faith burns relationships over administration, and the relationships are worth more than the fortnight.

Equally: a supplier who never asks is one that gets paid last, because the ones who ask create work that gets cleared and the ones who do not create none.

Who to send it to

The same question as the invoice itself.

Day one and day seven go to whoever processes invoices. Day fourteen, the telephone call, can go to the person who instructed the work — not to complain about accounts, but because they have an interest in their supplier being paid and frequently more influence than they realise.

"I don't want to make this your problem, but invoice 214 is a fortnight over and I'm not getting anywhere with accounts" is a sentence that produces action surprisingly often, because it is a request for help rather than a complaint.

Use it once per customer. Repeated, it becomes a complaint after all.

Recording the chase

Every contact, with the date and what was said.

One line in the job file each time. It costs seconds and it is what makes any later step possible — a record showing four contacts across six weeks is a different document from a recollection that you chased a few times.

It also stops you chasing twice in a week or forgetting for a month, both of which happen without a written sequence.

And where it does escalate, the log is the first thing anybody will ask for.

What not to do in this window

Do not stop work without saying so first. Where stages are the arrangement, a pause is legitimate and it should be announced rather than discovered.

Do not add interest yet. It is available in some circumstances and applying it at day seven turns a routine delay into a confrontation.

Do not go silent and resentful. The commonest actual behaviour, and it produces a chase at day sixty carrying two months of accumulated irritation, which is when tone stops being controllable.

When the answer is that they cannot pay

Occasionally the honest answer arrives early, and it changes everything about what to do next.

A customer who says they are struggling has given you information most debtors withhold, and the correct response is not escalation but a plan.

An agreed schedule with dates and amounts puts you ahead of every creditor who is still sending reminders, and a firm in difficulty pays the people it has made a commitment to.

Get it in writing, keep it small enough to be met, and treat a missed instalment as the signal rather than waiting for three.

The reminder nobody reads

Automated reminders work on the invoices that were going to be paid anyway.

That is most of them, which is why the automation is worth having — but it does nothing for the ones that need a person, and a firm relying entirely on scheduled emails discovers this at day sixty.

The manual message at day one and the call at day fourteen are the parts that do work. The template is the thing that fails.

The short version

  • Most late invoices are unprocessed rather than disputed, and the first fortnight is when one message resolves them
  • An overdue invoice ages badly: urgency fades, disputes appear, and the debtor reprioritises
  • Day one: a neutral message offering an explanation that is not their fault and removing the missing-document obstacle
  • Day seven: firmer, and ask directly whether there is a query — that surfaces it a fortnight earlier than waiting
  • Day fourteen: change channel and telephone, then confirm in writing what you were told
  • Do not add interest yet, do not stop work without announcing it, and do not go silent and resentful

For broader background on payment follow-up, disputes, and small-business administration, see Square.