Your cash is sitting in your invoices.
Payment delay barometers (Altares, Observatoire des délais de paiement) measure an average delay of around 12 to 13 days in France. These aren't final write-offs: the vast majority of these invoices will get paid. But every day of waiting is cash missing at the wrong moment, and late payments are cited as a factor in nearly one in four business failures.
The order of magnitude fits in one line. Your accounts receivable are measured in days of revenue (DSO):
1 day of DSO = annual revenue ÷ 365
For an SMB with €2M in revenue: each day of delay ≈ €5,480 in cash.
Gaining 10 days of DSO, for that SMB, is €55,000 in cash flowing back into the account, permanently. Without selling more, without negotiating anything: by simply collecting what's already invoiced, faster.
The good news: the lever to get there is known, measurable, and it automates end to end.
Why automated reminders collect better.
Manual reminders hit a ceiling for human reasons, not technical ones. You send reminders when you have time, so irregularly. Nobody likes asking for money, so it gets pushed back. One invoice in ten gets forgotten, and it's often the biggest one. The system brings three qualities that no amount of good will can sustain over time:
- Perfect regularity. Every invoice follows the sequence, every day, with no exceptions and nothing forgotten. Regularity is what trains payers: your invoices become the ones that get paid first, because they know the follow-up is coming.
- A constant tone. A reminder written calmly and validated once stays courteous and professional on the 200th send as much as the first. The client always knows where they stand: a clearer relationship, not a tenser one.
- A complete history. Every send, every open, every reply is tracked. The day a case goes to litigation, the full record already exists.
And the time recovered isn't trivial: the person handling invoicing gets back 2 to 4 hours a week, reinvested in the cases that genuinely need a human.
The 5 stages of a reminder sequence that works.
This is the sequence we deploy most often. It starts before the due date, escalates in firmness step by step, and brings in a human exactly when they add the most value.
The courtesy pre-reminder
One week before the due date: reminder of the amount, the date, invoice attached, payment link included. Typical wording: "Unless we're mistaken, invoice F-2026-118 for €3,240 is due on July 8." Most delays are simple oversights: this stage alone eliminates a large share of them.
The factual reminder
The day after the due date, neutral tone, zero reproach: the invoice is now due, the payment link is right there, "if payment has already been sent, please disregard this message." Short, precise, no friction.
The firm reminder
The tone becomes direct: reminder of the delay, reference to the contractual terms, mention of applicable penalties, and an open door: "if there's any issue or dispute with this invoice, let us know, we'll find a solution." Firmness and openness in the same message.
Handing off to a human
The system creates a call task in the CRM for the right person, with the full file: open invoices, reminders sent, replies received, client history. The phone unlocks what email can't, and the call is prepared in zero minutes.
The formal notice, prepared
The system generates the formal notice with the exact breakdown: principal, late penalties, €40 flat recovery fee. A human reviews, validates, sends. Automation prepares the escalation, the decision to escalate stays human.
Two cross-cutting rules complete the sequence. Automatic stop: payment detected means the sequence halts within the minute, never a reminder on a settled invoice. Segmentation: a key account with an internal approval process doesn't get reminded like a small business, delays and templates adapt by segment.
How it's actually wired together.
The principle fits in one sentence: an orchestrator checks your invoicing tool every morning and runs the rules. No change to how you invoice, the system works on top of what you already have.
| Component | Role | Example tools |
|---|---|---|
| Source of truth | Invoices, due dates, payments | Pennylane, Sellsy, Axonaut, QuickBooks, Sage, Stripe, or a well-kept Sheet |
| Orchestrator | Detects due dates, runs the sequence, applies the rules | Self-hosted n8n (our default choice) |
| Sending channel | Reminder emails from your own domain, careful deliverability | Your business mailbox or a dedicated SMTP relay |
| CRM & tasks | Call tasks, history, team visibility | Pipedrive, HubSpot, or your current tool |
| Guardrails | Dispute exclusions, thresholds, human validation on escalation | Rules inside the orchestrator + weekly review |
The daily workflow: read open invoices, cross-reference with payments received, calculate each invoice's position in the sequence, send the day's reminders, create tasks, log everything. One run a day is enough, the whole thing runs on the same n8n instance as your other automations. On choosing and hosting the orchestrator, see Self-Hosted n8n: The Complete Guide.
The guardrails are worth emphasizing: an invoice flagged as disputed comes out of the sequence, an amount above the defined threshold goes through human validation before sending, and the formal notice letter is never sent without a human eye on it. Automation runs the routine, sensitive decisions stay with you.
The notices that make your reminders solid.
For B2B in France, the legal framework is precise, and it works in your favor. Three points to keep in mind, and to include on your invoices and terms of sale:
- Payment terms are regulated. 30 days by default upon receipt, up to 60 net days (or 45 days end of month) if the contract provides for it.
- Late payment penalties are due automatically. At the rate set in your terms of sale, absent a specific clause, the ECB rate plus 10 points applies. No prior formal notice is needed for them to start accruing.
- The flat recovery fee: €40 per overdue invoice. Mandatory on your invoices. Few businesses actually claim it, having it in the formal notice's breakdown shifts the balance of power.
The system inserts these notices automatically into the letters it generates: the D+30 breakdown comes out accurate, complete, and enforceable. For cases that go beyond amicable collection, your file is already built for a collections professional.
When an AI agent reads the replies.
The sequence described so far is a workflow: rules, delays, templates. It covers 90% of the need. The next tier is an AI agent that understands your clients' replies and acts on them:
- "The transfer goes out Friday." The agent logs the promise, pauses the sequence, checks for payment on Monday. Payment received: case closed. Nothing received: an adapted reminder that references the commitment made.
- "This amount doesn't match the quote." The agent detects the dispute, pulls the invoice out of the sequence, opens a dispute file, and routes it to the right person with full context.
- "Can we spread this over three months?" The agent drafts the payment-plan proposal per your rules, a human validates it, the sequence resets to the new due dates.
At this level, reminders stop being an automatism and become a collaborator that manages accounts receivable end to end. It's the same logic described in AI Agent 24/7 for SMBs, applied to cash flow; the corresponding budget is detailed in How Much Does an AI Agent Cost.
What we measure, how we deploy.
On well-tuned systems, within 2 to 3 months. Published market cases go as far as -17 days.
For the person handling invoicing, reinvested in the cases that need a human.
One to two weeks to deploy, €15 to €50/month to run. ROI starts with the first payments that speed up.
The deployment follows our standard method: mapping the invoicing cycle (who invoices, when, with what tool, where payments land), architecture and sequence validated with you, build and testing on real data in shadow mode, gradual rollout, then monthly DSO tracking. As with everything we deliver: you own 100% of the system, workflows, email templates, and documentation included.
The general automation method, applicable to any process beyond invoicing, is detailed in How to Automate a Business Process in 2026.
Automated reminders: what people ask us.
How do you automate invoice reminders?
The principle: an orchestrator (n8n, for example) checks your invoicing tool every day, detects invoices that are due or overdue, and runs a sequence of personalized emails (D-7, D+1, D+7), creates a call task at D+15, and prepares the formal notice at D+30. As soon as payment is detected, the sequence stops on its own. Typical setup time: one to two weeks.
Does automated reminding risk upsetting my clients?
What actually happens is the opposite: a well-written sequence is more respectful than a late, irritated manual reminder. The tone stays constant, factual, predictable, the client always knows where they stand. Edge cases are handled with rules: key accounts on an adapted track, disputes excluded from the sequence, thresholds above which a human validates before sending.
How much does an automated reminder system cost?
A well-scoped system (an invoicing tool, an email sequence, CRM tasks, automatic stop on payment) runs between €2,000 and €4,000 to set up, with a running cost of €15 to €50 a month. The return is immediate as soon as the first payments speed up: for an SMB with €2M in revenue, every day of payment delay saved is worth around €5,500 in cash.
Which invoicing tools are compatible?
Any tool that exposes an API: Pennylane, Sellsy, Axonaut, QuickBooks, Sage, Stripe for payments, and even a well-kept Google Sheet for smaller structures. The orchestrator connects to it in read mode to detect due dates and payments, without changing anything about how you invoice.
What legal notices do invoices need to support reminders?
For B2B in France, your invoices and terms of sale must state the late-payment penalty rate (absent a specific clause, the ECB rate plus 10 points applies) and the €40 flat recovery fee per overdue invoice. These notices make your reminders enforceable and are inserted automatically into the letters the system generates.
Can the system understand client replies?
Yes, that's the next tier: an AI agent reads replies to the reminders. A payment promise with a date: it reschedules the sequence and checks for payment on that day. A dispute: it pulls the invoice out of the sequence and routes it to a human with full context. A payment-plan request: it drafts the proposal for validation. The reminder stops being an automatism and becomes a collaborator.