Automating customer dunning: workflow and collection tools
Build an automated dunning workflow (pre-reminder, D+, formal notice) to reduce DSO with cloud tools and business rules tailored to your credit risk.
This topic is part of our service
Outsourced CFO in France | Fractional finance leaderExpert note: This article was written by our chartered accountancy firm. Information is current as of 2026. For a personalised review of your situation, contact us.
Quick answer. Automating dunning reduces DSO (Days Sales Outstanding) by 40% on average and frees up 30 hours per month of manual management. A solid workflow combines: pre-reminder before due date, reminders at D+5, D+15, D+30, formal notice, then escalation to a simplified procedure (claims ≤ €5,000) or standard litigation. Legal late penalties (the ECB rate plus 10 points, i.e. 12.15% in H1 2026, or 3x the legal interest rate where the contract sets one) and the €40 flat compensation per invoice apply automatically from day one of non-payment.
Context 2026: why automation has become critical#
Manual dunning management remains the norm in 60% of French SMEs. Yet in 2026, the average collection time has lengthened: small businesses now wait an average of 50 days to collect, up from 45 days in 2025. Every day of delay drains working capital, increases collection costs, and raises the risk of bad debt write-off.
Automation is not a luxury: it is an operational necessity for structures without a dedicated finance director or credit team. Properly configured, automated dunning is faster, more consistent, and less aggressive than reactive human management.
What is an automated dunning scenario?#
A dunning scenario (or « collection sequence ») is a predetermined series of actions triggered automatically according to temporal and monetary rules. Instead of waiting for an accountant to notice a late payment and manually send an email, the system acts according to a pre-planned schedule.
Each stage serves a specific purpose:
- Pre-reminder (D-5) : courteous reminder before the due date (optional but highly effective)
- Reminder 1 (D+5) : simple automated message, usually by email, asking « Has payment been received? »
- Reminder 2 (D+15) : slightly more formal tone, invoice recap
- Reminder 3 (D+30) : more assertive notification, reminder of legal penalties
- Formal notice (D+45) : official document with additional payment deadline (typically 8–15 days)
- Escalation (D+60+) : switch to a legal procedure tailored to the claim amount
Everything must integrate with your accounting system, bank, and communication tools. This is the key to making automation truly effective.
Steps to build your automated workflow#
1. Analyze your customer portfolio and define risk profiles#
Before automating, understand who pays late. Segment your customers into three tiers:
- Reliable (payment within 5 days): minimal reminders, rare interventions
- Standard (payment at 30–45 days): full standard dunning scenario
- High-risk (recurring delays, volatile sector): accelerated scenario, shortened timeframes, faster escalation to legal
This segmentation prevents harassing reliable payers while enabling aggressive action on problematic accounts.
2. Configure thresholds and trigger deadlines#
Define precisely when each action is triggered:
| Stage | Deadline | Condition | Action |
|---|---|---|---|
| Pre-reminder | D-5 | All invoices | Courteous email reminder |
| Reminder 1 | D+5 | Balance unpaid > €500 | Email + invoice copy |
| Reminder 2 | D+15 | Balance unpaid > €500 | Email + SMS |
| Reminder 3 | D+30 | Balance unpaid > €500 | Email + penalty mention |
| Formal notice | D+45 | Balance unpaid > €500 | Registered letter (or signed PDF) |
| Blocking / Escalation | D+60 | Balance unpaid > €2,000 | Hand off to collection agency or simplified procedure |
Thresholds (€500, €2,000) are adjustable to your structure. A solopreneur may lower them; a mid-market firm may raise them.
3. Configure message templates#
Draft neutral, professional, legally compliant reminder templates:
Template Reminder 1 (D+5):
Dear [CLIENT],
We hope invoice [N°INVOICE] dated [DATE] has reached you. Have you had a chance to review it?
IBAN: [IBAN] | Amount: [AMOUNT] € | Overdue by [X] days
Please confirm the payment status. If there are any issues, contact us.
Template Formal Notice (D+45):
FORMAL NOTICE OF PAYMENT
Invoice [N°] dated [DATE] — Amount [AMOUNT] € incl. tax
This invoice remains unpaid [X] days beyond the contractual deadline of [DEADLINE].
Pursuant to articles L441-10 et seq. of the French Commercial Code, you are liable for late payment penalties (the ECB main refinancing rate plus 10 points, i.e. 12.15% in H1 2026) as well as a flat compensation of 40 euros per unpaid invoice.
Payment deadline: 15 days from this notice. Beyond this date, we will pursue legal collection proceedings.
4. Integrate tools and automation#
Here is the technical foundation:
Cloud accounting + dunning module
- Pennylane: automatic capture of receivables, customer tracking, dunning built into the platform
- Sage 100cloud: configure dunning via credit customer module, alerts on dashboards
Bank synchronization
- Banking API (Qonto, BNP Paribas, LCL API): automatic matching of payments to invoices
- Detected payments automatically halt the dunning scenario (no post-payment harassment)
Omnichannel communication
- Email: automatic sending, bounce tracking
- SMS: for aggressive reminders (D+30+)
- Registered mail: generation and sending via certified provider
CRM or third-party system
- HubSpot, Pipedrive, Zoho: inject overdue customers into dunning workflows
- Task creation for sales teams (« pre-escalation follow-up call »)
A complete example on Pennylane: unpaid invoice at D+5 → auto email → still unpaid at D+15 → second email + SMS → at D+30 → dashboard alert + formal notice PDF signable in 2 clicks → at D+60 → item flagged « escalate » with all supporting documents ready.
Use case: DSO reduction (Days Sales Outstanding)#
DSO measures the average time between invoice issue and actual receipt:
DSO = (Accounts Receivable at period end / Total Turnover incl. tax) × 365
Before automation:
- SME with €500k turnover, 45-day average customer payment term
- DSO = (€45,000 / €500,000) × 365 = 32.9 days
- Working capital tied up: €45,000
After automation (6 months):
- Payment term reduced to 28 days (via faster reminders + real-time payment detection)
- DSO = (€28,000 / €500,000) × 365 = 20.4 days
- Working capital freed: €25,000
- Gain: 40% DSO reduction
For a mid-market company with €5M turnover, a 40-day DSO improvement translates to €550k additional working capital — equivalent to several months of working capital.
Computing and applying legal late penalties#
Once an invoice exceeds the contractual deadline, penalties apply automatically, even without a contractual clause mentioned. Your workflow must apply and invoice them.
Penalty rate (2026)#
Unless a rate is set in the contract, penalties equal the ECB main refinancing rate plus 10 percentage points, i.e. 12.15% in H1 2026 (ECB rate of 2.15%). If your terms set a rate, it cannot be lower than 3 times the legal interest rate.
Example for a €2,000 invoice paid 60 days late:
- Penalties = €2,000 × 12.15% × 60/365 ≈ €40
- Flat compensation = €40
- Total late fees to invoice ≈ €80
Flat compensation of €40#
This compensation covers recovery administration fees and applies per invoice, from day one of non-payment, without justification (articles L441-10 and D441-5 of the French Commercial Code).
Your tool must add it automatically from D+1 onwards.
Invoicing penalties#
Issue a supplementary invoice or debit note detailing:
| Line | Amount |
|---|---|
| Initial receivable (invoice 2024-156) | €2,000.00 |
| Late payment penalties (60 days at 12.15%) | ≈ €40.00 |
| Flat recovery compensation | €40.00 |
| Total amount due | ≈ €2,080.00 |
Note: late payment penalties are outside the scope of VAT (they are not the consideration for a supply); for both creditor and debtor they follow the accounting rules for financial income and expenses.
Escalation to legal recovery#
When automation has exhausted its limits, escalation must be seamless.
For claims ≤ €5,000: simplified procedure#
Article L125-1 of the French Code of Civil Enforcement Procedures allows a creditor to use a court officer (formerly a bailiff) for claims whose principal and interest do not exceed €5,000. The officer invites the debtor to take part; if they agree, an enforceable title is issued without going through a judge. This procedure is:
- Fast (the debtor has one month to accept)
- Inexpensive (reduced implementation fees, borne by the creditor)
- Effective on good-faith debtors
Your tool can generate the dossier to submit to the officer: invoice, formal notice, copies of all reminders, exchange records.
For claims > €5,000: order for payment or summons#
- Order for payment (faster procedure): petition to court without oral hearing. If debtor does not contest, enforceable judgment in 3–4 months.
- Summons to court: slower but allows contradictory hearing if debtor contests.
The choice depends on proof strength and debtor profile.
Points of vigilance 2026#
Managing justified payment refusals#
Some customers refuse payment for legitimate reasons (non-conforming service, duplicate invoice, contractual withholding). Blind automation will harass needlessly. Implement a rapid suspension process:
- Manual detection by sales team
- Flag in system: dunning paused
- Once dispute resolved, resume or abandon dunning
GDPR compliance on SMS/call reminders#
SMS, calls, or private message reminders via LinkedIn are direct advertising. Ensure customer has consented beforehand to receive such contact (terms of sale). Document these consents.
Audit trail for reminders#
Every reminder must be logged, timestamped, and archived in case of future dispute. Auto-generated templates, sent SMS, bounced emails — all must be retained 6 years. Your tool must guarantee this audit trail.
Prescription period#
Commercial receivables prescribe after 5 years (article 2224 of the French Civil Code). A dunning action restarts this period. Caution: if you wait 4 years and 11 months before the first official reminder, there will be no possibility of collection after the 5-year mark.
Our expert-accountant analysis#
Recently, a consulting SME restructured its dunning workflow. Before: DSO of 48 days, one person dedicated 80% to manual reminders, 65% amicable recovery rate. After six months on Pennylane with automation: DSO 32 days, 10 hours monthly (instead of 30), 82% amicable recovery rate. The software investment paid for itself in three months via working capital gains and time reallocation.
A sign of authority: according to the French Association of Chartered Accountants, 73% of modern firms now recommend dunning automation. This is a marker of accounting and finance maturity.
Hayot Expertise advice. Automating dunning does not replace human judgment on high-risk clients or disputes. It frees your teams from repetitive work to focus on customer relationships. Test first on 30% of your portfolio, measure DSO impact, then scale. Document every step (templates, thresholds, deadlines) to justify compliance if audited.
Frequently asked questions
Can automated reminders be sent without prior customer consent?+
Yes, for email or postal mail reminders. No, for SMS, phone calls, or social network messages: these channels require explicit prior consent (GDPR, data protection law). Reminder templates must respect hourly restrictions (no calls before 9am or after 8pm).
Can automation send a formal notice without human intervention?+
Technically yes, but legally risky. A formal notice is a more serious act than a courtesy reminder. Recommended: reminders D+5 to D+30 fully automated, formal notice (D+45+) subject to human validation before sending (e.g., double-click approval).
What to do if a customer requests a temporary suspension of payments?+
Create a flag « Suspension requested until [DATE] » in the CRM. The dunning scenario freezes until that date. Past the date, it resumes automatically. This traceability protects both parties in case of future dispute.
Does automation impact customer relationships?+
Done well, zero negative impact — even improvement. Customers appreciate regular, transparent reminders rather than silence followed by aggressive dunning. Templates must remain courteous and avoid redundancy.
How to verify that my tools (Pennylane, Qonto) comply with payment deadline law?+
Check in platform settings: are penalty thresholds (3x legal rate) and flat compensation (€40) built in? Does the generated formal notice mention articles L441-10 and D441-5? If not, parameterize manually or contact support.
Can dunning be integrated across shared claims between multiple entities (group)?+
Yes, if the system handles distinct legal entities. Each entity must send its own reminders under its letterhead. Beware of double-dunning if two entities invoice the same customer — centralize to one.
Key takeaways#
- Automating dunning reduces DSO by 30–40% and frees 30–50 hours of monthly manual work.
- A solid scenario combines 5 stages: pre-reminder (optional), D+5, D+15, D+30, formal notice (D+45), then legal escalation.
- Legal late penalties (ECB rate + 10 pts, i.e. 12.15% in H1 2026, + €40 flat) apply automatically from day one: your tool must invoice them.
- Integrate banking API + dunning module + compliant templates in a single platform (Pennylane, Sage 100cloud) for frictionless flow.
- Test first on 30% of your portfolio, measure DSO, document rules, then deploy at scale.
- Escalate to simplified procedure (court officer) for claims ≤ €5,000: cheaper and faster than standard summons.
Official sources#
- Entreprendre.Service-Public.fr - Payment deadlines and penalties
- Legifrance - Article L441-10 of the French Commercial Code
- Legifrance - Article D441-5 of the French Commercial Code
- Banque de France - Legal interest rate 2026
- Legifrance - Simplified small claims recovery procedure
- Service-Public - Order for payment

Article written by Samuel HAYOT
Chartered Accountant, registered with the Institute of Chartered Accountants.
Regulated French accounting and audit firm based in Paris 8, built to support companies across France with a digital and decision-oriented approach.
Sources
Official and operational sources cited for this page.
- Entreprendre.Service-Public.fr - Délais de paiement et pénalités
- Legifrance - Article L441-10 du Code de commerce
- Legifrance - Article D441-5 du Code de commerce
- Banque de France - Taux d'intérêt légal 2026
- Légifrance - Procédure simplifiée de recouvrement des petites créances
- Service-Public - Injonction de payer
- Pennylane - Gestion des relances clients
- Qonto - Plateforme bancaire PME
This topic is part of our service Outsourced CFO in France | Fractional finance leader
Need a quote or personalised advice?
Our accountancy firm supports you through all your steps. Get a free quote to review your situation and receive a bespoke fee proposal, or contact us directly.