Definition: Dunning Automation
Dunning automation is the use of software to generate, schedule, and send payment reminders for overdue invoices automatically, based on predefined escalation rules or AI-driven prioritization logic.
Core characteristics of dunning automation
Dunning automation systems monitor open invoices in the ERP or accounting system continuously and trigger reminders without manual tracking in spreadsheets. They combine rule-based escalation with growing use of predictive models that assess which customers are likely to pay without further intervention.
- Continuous monitoring of invoice due dates and payment status
- Multi-stage escalation (friendly reminder, formal reminder, final notice)
- Automated interest and fee calculation per statutory requirements
- Integration with ERP, CRM, and accounting systems for real-time open-item data
Dunning automation vs. accounts receivable automation
Dunning automation covers specifically the reminder and escalation process once an invoice is overdue, while accounts receivable automation spans the entire receivables lifecycle, including credit checks, invoice issuance, cash application, and dispute management. The two are closely linked: dunning automation’s output, structured payment and dispute data, becomes the input accounts receivable teams use to refine credit policy. Most Mittelstand finance teams start with dunning automation because it addresses the most repetitive manual task first, then expand toward broader receivables automation once the reminder process is reliable.
Importance of dunning automation in enterprise AI
Late payments are a persistent drain on Mittelstand liquidity. According to the EOS European Payment Report 2025, 22 percent of B2B invoices in Germany are paid late or not at all, and nearly half of affected companies report resulting profit losses. Automating the step that follows invoice processing closes the most common gap between delivering a service and actually collecting payment for it.
Methods and procedures for dunning automation
Three approaches cover most dunning automation deployments, depending on process maturity and data availability.
Rule-based escalation tiers
The majority of dunning automation setups start with fixed escalation tiers tied to days overdue: a friendly reminder, a formal written reminder, and a final notice before legal collection. This logic runs as part of broader workflow automation, triggered directly by open-item data from the ERP system rather than by a finance employee checking spreadsheets.
- Configurable thresholds per customer segment or contract type
- Automatic interest and late-fee calculation in line with statutory rates
- Escalation to a human collections specialist once a final notice is reached
AI-driven payment prediction and prioritization
More advanced deployments use machine learning models trained on historical payment behavior to score each overdue account by likelihood of voluntary payment. Customers who reliably pay within a few extra days receive a lighter touch or an automatic grace period, while higher-risk accounts are escalated faster and routed to a human collections specialist earlier. This reduces unnecessary friction with reliable customers while shortening the time to intervention for accounts genuinely at risk of default.
Omnichannel communication automation
Modern dunning automation sends reminders across the channel the customer actually uses, email, postal letter, customer portal, or increasingly SMS and WhatsApp Business, instead of relying on a single format for every account. Templates are personalized by language, customer segment, and dunning stage, and every message that goes out is logged automatically for audit purposes.
Important KPIs for dunning automation
Measuring dunning automation requires tracking collection speed, cash impact, and process quality together.
Operational KPIs
- Days Sales Outstanding (DSO): target reduction of 8-12 days
- Average days to first reminder: target under 2 days after due date
- Straight-through processing rate for reminders: target above 80%
- Collection rate within 30 days of first reminder: target above 70%
Strategic KPIs
Beyond operational speed, finance leadership tracks the effect on working capital and bad debt. McKinsey’s 2025 analysis of order-to-cash automation found that organizations automating dunning and collections workflows reduce DSO by 8 to 12 days on average, directly freeing up working capital without new financing.
Quality KPIs
Error rate in generated reminders, duplicate notices, wrong amounts, reminders sent for disputed invoices, is the leading indicator of whether automation is trusted internally. Finance teams should also track the complaint rate from customers who received a reminder in error, since repeated mistakes erode confidence in the automated process faster than any manual error would.
Risk factors and controls for dunning automation
Automating a legally sensitive communication introduces risks that must be controlled before go-live.
Legal and compliance risk
Under German civil law (BGB Section 286), a debtor can fall into default automatically 30 days after an invoice is due and received, without a formal reminder. Automated reminders must nonetheless reflect correct statutory interest rates and current dispute status, or they create legal exposure rather than reducing it.
- Incorrect interest or fee calculations on contested invoices
- Reminders sent for invoices already in a payment plan or active dispute
- Missing legally required disclosures on formal notices
Customer relationship risk
An escalation tier applied uniformly to every account can damage long-term customer relationships, particularly for strategic accounts with a legitimate dispute or a temporary liquidity issue. Dunning automation should route judgment calls, large accounts, disputed amounts, or customers with a track record of eventual payment, to a human reviewer before escalating, rather than letting fixed rules run unchecked.
Data and documentation risk
German companies must retain dunning correspondence and the underlying open-item data in an auditable, unalterable format to satisfy GoBD requirements. When a third-party dunning platform processes customer payment data, a data processing agreement and a documented DSGVO basis for scoring customers by payment risk are required before go-live.
Practical example
A 110-employee wholesaler of electrical components in Lower Saxony was managing dunning manually across three sales regions, with one finance employee tracking overdue invoices in spreadsheets and drafting reminder letters individually. Average time to the first reminder was 11 days after the due date, and DSO had crept to 54 days. After connecting a dunning automation layer to the company’s ERP open-item data, reminders began triggering automatically on day two, with risk-based prioritization separating reliable long-term customers from higher-risk new accounts. Within four months, DSO dropped to 41 days and the finance employee redirected most of their time to credit management instead of drafting reminders by hand.
- Three-stage automated reminder sequence triggered directly from ERP open-item data
- Risk-based prioritization that escalates high-risk accounts faster while giving reliable payers an automatic grace period
- Personalized, legally compliant reminder letters and emails generated per customer segment and language
- Real-time dashboard showing overdue status, dunning-stage distribution, and cash-flow impact
Current developments and effects
Three trends are reshaping dunning automation heading into 2026.
AI-prioritized risk scoring
Predictive models increasingly replace fixed day-based escalation tiers, scoring each account continuously rather than only at fixed intervals. This lets finance teams intervene earlier on accounts showing early warning signs rather than waiting for a missed due date.
- Continuous risk scoring instead of fixed day-based triggers
- Early-warning alerts before an invoice is even overdue
- Dynamic grace periods for historically reliable payers
Integration with institutional customer knowledge
Dunning decisions improve when they draw on more than payment history alone, account notes from sales, prior dispute resolutions, and relationship context that otherwise sits in individual inboxes. Superkind’s Company Brain approach is one example of connecting this institutional memory directly into an AI-driven collections workflow, so a reminder reflects the full customer relationship rather than only the open-item balance.
Self-service and omnichannel collection
Customer self-service portals that let a debtor view, dispute, or pay an overdue invoice directly are becoming a standard companion to automated reminders, reducing the volume of phone calls finance teams field purely to clarify amounts. Combined with e-invoicing mandates, this is pushing the entire invoice-to-cash chain toward structured, machine-readable data rather than PDF attachments.
Conclusion
Dunning automation turns a repetitive, legally sensitive task into a structured workflow that runs with minimal manual effort. Done well, it shortens the time between an invoice falling overdue and payment arriving, without damaging the customer relationships that make up a large share of Mittelstand revenue. The companies that get the most value treat escalation rules, legal compliance, and the human review step for judgment calls as equally important as the automation itself. As AI-driven prioritization matures, dunning automation is moving from a fixed-schedule reminder engine toward a continuously learning part of the broader receivables process.
Frequently Asked Questions
What is the difference between dunning automation and accounts receivable automation?
Dunning automation covers specifically the reminder and escalation process for overdue invoices. Accounts receivable automation is the broader umbrella that also includes credit checks, invoice issuance, and cash application. Most companies automate dunning first because it is the most repetitive, rule-driven part of the receivables process.
Is dunning automation compliant with DSGVO and German civil law?
Yes, when configured correctly. Reminders must reflect the correct statutory default rules under BGB Section 286 and the interest rates under BGB Section 288, and any third-party platform processing customer payment data needs a data processing agreement under DSGVO. Companies should also document the legal basis for any payment-risk scoring applied to customers.
What does dunning automation cost for a small or mid-sized company?
For a company sending a few hundred to a few thousand reminders per month, implementation typically costs in the low five-figure to low six-figure euro range, depending on ERP integration complexity and whether AI-based prioritization is included. Cloud-based solutions with standard ERP connectors sit at the lower end of that range.
How long does it take to roll out dunning automation?
Companies with clean open-item data and a standard ERP can go live with rule-based escalation tiers within 4 to 8 weeks. Adding AI-driven risk scoring and omnichannel communication typically extends the timeline to 10 to 14 weeks, since it requires historical payment data to train and validate the prioritization model.
Will automated reminders damage important customer relationships?
Not if the system is configured to route judgment calls to a human reviewer. Large accounts, disputed invoices, and customers with a track record of eventual payment should be flagged for review rather than escalated automatically on a fixed schedule. Companies that do this report fewer complaints than under manual processes, since reminders go out consistently and without the delays that often frustrate reliable customers.
Which ERP and CRM systems can dunning automation connect to?
Most dunning automation platforms offer connectors for SAP, DATEV, Microsoft Dynamics, and other common Mittelstand ERP systems, alongside CRM integration for account context. Systems without a modern API can typically still be reached through batch file exports or RPA-based integration as an interim step.
