How long should you wait before chasing an unpaid invoice in Switzerland?

The Swiss guides we read suggest waiting for the due date plus 2 to 3 days (Helvetia), or 5 to 7 days when in doubt (AXA). The usual payment term is about 30 days.

How many reminders before debt enforcement?

The law sets no number. The practice AXA describes is one reminder followed by one to two notices, 10 to 14 days apart, then a decision on enforcement.

Can an AI send unpaid-invoice reminders on its own?

It can spot overdue invoices, check payment and draft the message. We recommend a person approves each send, at least at the start, and always for the notices.

What happens if the client has already paid?

Before any drafting, the payment is looked up in the bank statements. If it has arrived, no reminder is sent and the file is closed.

When does automated chasing stop making sense?

Below about ten overdue invoices a month, a calendar reminder and a template are enough. For a few clients with very large amounts, the phone is still better.

Chasing unpaid invoices: sequence, tone and when a person takes over

Chasing an unpaid invoice: what sequence, what tone, and when does a person take over?

Short answer: in Switzerland, the common practice is a friendly reminder shortly after the due date, then one or two firmer notices spaced 10 to 14 days apart, before considering debt enforcement. An AI can spot the overdue invoice, check that the payment has not already arrived and draft each message. A person must approve each send and take over as soon as the client replies, disputes the invoice or stays silent too long.

An unpaid invoice is rarely a refusal to pay. Most often it is a lost invoice, an internal approval still pending or a simple oversight. The real problem for a small business lies elsewhere: the reminder goes out late, or not at all, because nobody has time to reconcile the books and the bank every week. This article gives a sequence, a tone for each step, and above all the list of moments where automation must stop.

What Swiss guides say about timing

We read three published sources: a guide from the insurer AXA Switzerland, a guide from the insurer Helvetia, and a French collection plan from Dext. The first two describe Swiss practice; the third reflects the French legal framework, which we do not carry over. The figures below come from the guides and are not rules of law: Swiss law is silent on the form and number of reminders, as Helvetia points out.

Question	What the guides say	Our call
Usual payment term	About 30 days; 10 to 14 days for very small businesses	A precise due date on every invoice, never "within 14 days"
Wait before the first reminder	2 to 3 days after the due date (Helvetia), 5 to 7 days when in doubt (AXA)	Three working days, except for large amounts
Gap between two messages	10 to 14 days	Ten days, to leave room for an internal approval
Messages before enforcement	One reminder and one to two notices (AXA: three in total)	Three messages, then a decision by a person
Legal duty to chase	None: enforcement can start once the term has expired	Chase anyway, to understand why the invoice is unpaid

These ranges are bounds. A client who always pays at 45 days is not chased like a new client with no history. Questions about reminder fees, default interest and enforcement are legal matters: have your accountant or counsel validate them before writing them into a template.

The four-message sequence, with a tone for each step

Here is the sequence we recommend to a service business on 30-day invoices. Each message adds one piece of information and lowers the effort for the client.

Due date + 3 working days: the friendly reminder. Neutral tone, no accusation. State the invoice number, the amount and the new requested date, and note that the payment may have crossed the letter.
About 10 days later: the first notice. Same content, more direct tone, a new precise date. Ask for a reply if the invoice raises a problem.
Another 10 days later: the final notice. Factual and firm. This is where, and not before, the guides allow a mention of legal follow-up. This message is always read by a person.
After that: a decision, not a message. Enforce, negotiate an instalment plan or write the debt off. No AI makes that call.

One tone rule fits in a sentence: the reminder talks about the invoice, the notice talks about the date, and neither talks about the client. Helvetia and AXA both note that the line between a reminder and a notice is mostly a matter of wording.

What an AI prepares, step by step

The studio's collection flow runs in six steps, from detecting the overdue invoice to matching the payment received. For the business owner, the split looks like this.

Step	Who does it	Why
Spot overdue invoices	The AI, in the accounting system	A reading task, no judgment needed
Check whether payment has already arrived	The AI, in the bank statements	Avoids chasing a client who has already paid
Draft the message in the right tone	The AI, using the client record	Tone depends on payment history
Approve: send, edit, suspend	A person	A commercial message affects the relationship
Send reminders 1, 2 then 3	The AI, from your mailbox	The client receives an email from your own address
Match the payment and close	The AI	Stops the sequence as soon as the money lands

The second row is the decisive one. Chasing a client who paid yesterday is the most expensive mistake in trust, and the easiest to avoid: the bank match happens before any drafting.

Structure of a reminder that gets a reply

A useful reminder has five elements, in this order. The Helvetia and AXA guides list the same ones: who is writing, which invoice, the amount due, a new precise date and the payment details.

A subject line that says it all: "Reminder: invoice no. 2026-118, due 15 October".
A neutral opening sentence: "Unless we are mistaken, this invoice is still open".
The facts: number, date, amount, the work concerned.
A single request: payment by a precise date, or a word if the invoice raises a problem.
A graceful exit: "If your payment crossed this message, please disregard it".

The last line is not decorative politeness. It covers the common case where the transfer left the day before, and it keeps the relationship intact. It is also the kind of sentence an AI reproduces well, provided you give it your own wording rather than a generic template.

The five moments when a person takes over

An automated reminder with no exit is a risk, not a gain. Here are the five situations where the sequence stops and a human takes the file.

The client replies. As soon as an answer arrives, even one line, the sequence pauses. A reminder that goes out after "I will pay Friday" damages the relationship.
The client disputes the invoice. A disagreement about the work or the amount calls for a conversation, not a template.
The amount is high or the client is strategic. Set a threshold: above it, the first message is a phone call, not an email.
The client has a sensitive history. A known cash-flow difficulty, a long-standing client, a personal relationship: the client record must switch the file to manual handling.
The third message had no effect. What follows (enforcement, instalments, write-off) is a management decision, sometimes made with your accountant.

These rules are written once, with you, during setup. They are tested on your real invoices before the first send.

When not to automate the reminder

Automating collection is the wrong choice in several cases, and it is better to say so.

Fewer than about ten overdue invoices a month. A calendar reminder and a message template are enough. Setup cost would exceed the time saved.
Few clients, very large amounts. Each unpaid invoice is a relationship matter, handled by phone.
Untidy invoicing. If due dates are unreliable in the books, the AI will chase on bad data. Clean up the due dates first.
Contracts with variable payment terms. The more exceptions, the larger the share of human validation, and the smaller the gain.

To check whether your case falls in the useful zone, a short diagnostic of the time spent on the task is the right first step: see the processes the studio automates.

What to measure to know whether it works

Three figures are enough, taken before and after setup on your own invoices: the average real payment delay, the number of invoices overdue by more than 30 days, and the time spent each week on reminders. Record them for a month before changing anything: without a starting point, no improvement can be demonstrated. Do not adopt another company's figure as a target; yours depends on your sector and your clients.

How to start without risk

Begin with one month in draft mode: the AI prepares each reminder, nobody receives anything, and you compare with what you would have sent. This test reveals badly dated invoices, clients to handle separately and phrasings that do not sound like you. Then move to sending with approval, and, if you wish, to direct sending for the friendly reminder alone. Notices stay approved by a person. The same logic of adapting the message to the context applies to following up on a quote without nagging.