Chasing an unpaid invoice, without losing the client

Thirty days have passed, the invoice is unpaid, and this client orders from you every month. A three-step grid to chase payment without damaging the relationship.

Jérôme Knops

By Jérôme Knops

Published October 9, 2026 · 5 min read

Ask an AI

The question comes pre-written, with this article's address.

Thirty days have passed. The invoice is still sitting in the "pending" column, and the client on the other end is also the one who calls you about the next order. Chasing it risks annoying them. Not chasing it means leaving money outside the business. The right reminder exists: it is staged, written in advance, and it never mixes the tone of a friendly nudge with the tone of a formal notice.

Why we hesitate to chase

A building materials merchant or a heating installer lives off repeat clients. The one who owes €2,400 for three weeks is often the same one who will place a new order next month. Chasing too early or too bluntly can look like doubting them. Not chasing makes the due date look like a suggestion.

The discomfort comes from a mix-up: an overdue invoice gets treated as a personal matter, when it is really a calendar matter. A grid written in advance, with fixed delays and neutral wording, takes the reminder out of the relationship register.

The three-step grid

Three reminders, three tones, three delays. No step is skipped, and the tone does not change from one step to the next depending on the day's mood.

StepDelayToneChannel
1. Nudge5 days after the due dateNeutral, assumes an oversightMessage or email
2. Reminder15 days after the due dateFactual, restates the amount and dateEmail, referencing step 1
3. Formal notice30 days after the due dateFormal, states what happens nextCall, then letter

Step 1 always goes out, even for a good client, even for €300. It is this step that prevents reaching step 3: a nudge received five days after the due date almost always gets settled without friction, because it still arrives within the normal window of a simple oversight.

What to write at each step

The wording matters as much as the delay. A nudge that sounds like a formal notice puts off a client who simply forgot; a formal notice that sounds like a nudge has no effect at all.

  • Step 1: "Invoice #… from … (€2,400 excl. tax) does not appear to have been settled yet. Let us know if it reached you." No deadline, no alarmed tone.
  • Step 2: "Our first message from … went unanswered. Invoice #… is still open for €2,400 excl. tax, due since …. Can you give us a settlement date?" We restate the facts and ask for a precise date.
  • Step 3: "Without payment within eight days, we will proceed with the steps set out in our contract." We announce a real action we are ready to take, never an empty threat.

A merchant who tested this grid over one quarter saw most unpaid invoices settled at step 1 or 2; only a handful of accounts, usually already fragile for other reasons, went as far as step 3. The example is an assumption used to show the calculation, not a measured result.

What the absence of a grid costs

Here is a worked example, with cautious assumptions. An eight-person company has €40,000 of pending invoices at any given time, across all clients. Without a grid, the average payment delay drifts from 30 to 55 days, because reminders go out at random, whenever someone remembers.

Twenty-five extra days of delay on €40,000, at a cost of money of 6% a year, represent roughly €165 of cash tied up per month, on top of the time spent figuring out who has already been chased and who has not. The calculation is easy to redo with your own figures: average outstanding balance, rate, number of extra days.

What changes with an application built for the business

A reminder grid fits on one page, but it requires knowing, for every invoice, where it stands. This is where it breaks down most often: step 1 goes out, nobody logs the date, and step 2 never follows.

In an application built for the business, every invoice carries its due date and the step it has reached. The day the next step's delay falls due, it shows up in the right person's daily list, with the text ready to send. The owner sees the total per step at a glance: what has just been chased, what is approaching a formal notice, what is settled. Nothing is automatic to the point of going out unreviewed: the person validates the send, the application only proposes it at the right time.

Chasing an unpaid invoice: the key takeaways

Chasing an unpaid invoice damages the relationship when it is improvised: too late, too blunt, or forgotten and then abrupt. A three-step grid, with a fixed delay and tone set in advance, removes the hesitation and protects the business relationship, because the client knows what to expect.

The real work is not writing the three messages, it is knowing, every day, which invoice has reached which step. That tracking is what, in most businesses, falls between two chairs and lets quotes go unchased. Billing right after the work is finished already reduces the problem upstream; the reminder grid closes it downstream. See the daily list for how an application can carry this tracking without a spreadsheet kept up to date by hand.

Jérôme Knops
About the author

Jérôme Knops

Founder and CTO of Edenio

Jérôme Knops is the founder of Edenio, where he designs and builds custom business applications for construction, supply chain and distribution companies. He runs the scoping meetings, writes the code, and stays the person you talk to once the tool is in production.

See all their articles