The reason chasing feels awkward is that it is usually framed as a confrontation. It almost never is. In service businesses the overwhelming majority of late invoices are late because they are sitting in an approval queue, or the person who signs them is away, or it went to the wrong inbox.
Which means the goal of a chaser is not to apply pressure. It is to find out where the invoice is stuck and remove whatever is blocking it.
Send it before it is late
The most effective message in the sequence is the one that goes out three days before the due date, and it is the one almost nobody sends.
It is not a chase. It is a heads up, and it costs the relationship nothing:
Just a heads up that invoice INV-0042 falls due on Thursday. No action needed if it is already scheduled. If you need anything from us to get it processed, reply and we will sort it out.
That last sentence is doing the real work. It gives a busy person a reason to reply now rather than after it has gone late.
Escalate in stages, not in tone
The mistake is jumping from silence to firmness. Each message should be slightly more direct than the last, and each should ask for exactly one thing.
| When | What it is | What you ask for |
|---|---|---|
| 3 days before | Heads up | Nothing |
| On the day | Due today | Nothing, or the link |
| 1 to 7 days late | Polite note | Who signs it off |
| 8 to 21 days late | Following up | A payment date |
| 22 to 45 days late | Firm | A reply, even a bad one |
| Over 45 days | Direct | A date, or an escalation path |
The line that unblocks the most invoices
Somewhere around the one week mark, this is the most useful thing you can write:
These things usually just get stuck in an approval queue. If you can point us at whoever needs to sign it off, we will chase it from our side instead.
It does three things at once. It removes blame, it acknowledges that the delay is probably structural, and it offers to take the work off their plate. People reply to that.
What not to do
Do not threaten early. Mentioning interest or legal action at two weeks turns an administrative delay into a dispute. Keep those for genuinely delinquent accounts, and understand that using them ends the relationship.
Do not apologise for asking. "Sorry to bother you about this" invites the reader to treat it as optional. You did the work. Be warm and be direct.
Do not send on a Sunday. It reads as pestering, it will not be actioned until Monday, and it makes you look like you have nothing better to do.
Do not chase manually and inconsistently. The invoice that gets chased twice in a week and then forgotten for a month is worse than one on a steady schedule.
Make it stop when it should
Whatever you use to chase, it has to stop the moment an invoice is paid. Nothing damages a client relationship faster than a reminder for something they settled a fortnight ago, and nothing makes you look less organised.
The same goes for the invoice you know is late for a good reason. If a client has told you the payment run is on the fifteenth, pause the chasing on that one invoice rather than letting it fire on the eleventh.
When the answer really is no
Occasionally an invoice is not stuck, it is disputed, and nobody has told you. That is why the firmer messages ask for a reply rather than a payment. A client who says "we are not paying this because the scope changed" has given you something to work with. Silence has given you nothing.
Ask early enough and directly enough that a dispute surfaces while it is still small.