Skip to main content

Automate Dunning – Cut DSO by 21 days

Cut DSO by 14-21 days with automated dunning for Lexoffice, DATEV, or sevDesk. 70% fewer collections cases, § 286/288 BGB compliant, approval gates.

FinanceForderungsmanagementDSGVOGoBDLexofficeDATEV
Branche
Finance / B2B / Agency
Umsetzung
4-6 Wochen
DSO Reduction
-21 days

Dunning Workflow

Daily triggered run checks all open AR, escalates by rule across 4 stages (approval checkpoint from stage 3) and stops automatically on payment.

BPMN Elemente
Trigger
Start Event
Process
Task
Integration
Service Task
Output
End Event
Gateway
XOR (Exklusiv)

Before vs. After

Days Sales Outstanding (DSO)
Before
~50 days
After
~30 days (-21 days)
First customer contact after due
Before
21+ days, inconsistent
After
Day 3 automated, friendly
Collections handoffs per year
Before
~40 cases × 20% fee
After
~10 cases (-70%)
Finance time on dunning
Before
4-6h every Friday
After
~30min approvals per week
Late fee calculation
Before
Manual in Word, error-prone
After
§ 288 BGB day-accurate
Audit trail under dispute
Before
Patchy, Excel lists
After
GoBD-compliant, 10-year archive

The Challenge

Overdue receivables are the silent liquidity killer in mid-market finance. A typical German B2B firm with 200-600 open invoices spends 4-6 hours every Friday pulling AR aging reports, drafting dunning letters in Word, calculating late fees and § 288 BGB interest, and documenting sends. Results are inconsistent: long-standing customers get forgotten or treated too harshly, new customers slip through, and average Days Sales Outstanding (DSO) sits at 45-60 days instead of the target 30. Soft costs compound: customers are surprised by dunning letters because first contact often comes 21+ days after due date. Legal exposure grows when § 286 BGB notice timelines aren't cleanly documented. Every collections handoff costs 15-25% of the receivable plus interest – money that earlier, more consistent outreach would usually have saved. Extrapolated: a company with €2M annual revenue and 50-day DSO ties up ~€275,000 more working capital than at DSO 30.

Our Solution

An orchestrated dunning workflow that plugs natively into your existing invoicing system – Lexoffice API, DATEV Unternehmen Online, sevDesk, or Billomat – and runs a daily AR check. Four configurable stages (friendly reminder, 1st dunning with new deadline, 2nd dunning with late fee and interest, final notice with collections warning) with customer-segment-specific escalation profiles. Long-standing high-credit customers get gentler tone and longer deadlines; new customers strict. Payment reconciliation runs in real time before every stage – no customer gets dunned for an already-paid invoice. Messages are AI-personalized (industry, invoice context, payment history) while preserving brand tone, with human approval gates from the 2nd stage onwards. Legal-grade deadline math per § 286 BGB, 10-year GoBD-compliant archival, and full GDPR audit trail built in. Optional self-service installment flow lets customers propose payment plans via a link, auto-configured in Stripe or GoCardless. Outcome: DSO drops 14-21 days, collections handoffs drop 60-80%, finance team reclaims 3-5 hours per week.

Key Features

Native Invoicing Integration

Direct integration with Lexoffice, DATEV Unternehmen Online, sevDesk, or Billomat – no dual entry, no CSV exports. AR is synced hourly.

Customer-Specific Dunning Profiles

Per segment (long-standing, new, enterprise, public sector): own escalation profiles with tone, deadlines, late fees, and path.

Real-Time Payment Reconciliation

Before each stage, the system checks current payments via bank API or invoicing system. Already-paid invoices drop out of the dunning queue automatically.

§ 286/288 BGB Auto-Calculated

Default onset, late fees, and statutory interest (5%/9% above base rate) calculated day-accurate and audit-safe. Notice timing verifiable in court.

Approval Gates from Stage 2

Reminder and 1st dunning run fully automated. From 2nd dunning (with late fee) onwards and before collections: human approval via Slack, Teams, or email link.

Installment Self-Service

1st dunning email includes a link for customers to propose installment plans themselves. Auto-configured via Stripe Billing or GoCardless SEPA mandates.

Results

-21 days
DSO Reduction
~€275k
Working Capital Freed
3-5h
Weekly Time Saved
-70%
Collections Handoffs

DSO from ~50 to ~30 days, 60-80% fewer collections cases, 3-5h/week reclaimed

These figures indicate the expected magnitude of this reference architecture — based on industry benchmarks, public studies of comparable setups, and our own tests on real stacks. Actual results in live deployment vary with company size, process maturity, and integration depth.

Integrations

Seamless connection to your existing infrastructure

Lexoffice

Invoicing System

Native Office API for AR, dunning stages, and payment reconciliation

DATEV Unternehmen Online

Invoicing System

DATEVconnect integration for tax consultancies and mid-market on DATEV

sevDesk / Billomat

Invoicing System

Alternative invoicing connection for SMB and freelancer portfolios

Stripe Billing / GoCardless

Installments

Self-service installments via payment link, automated SEPA mandates

Brevo / Mailjet

Email Delivery

Transactional email with delivery receipts, open and click tracking

Slack / Microsoft Teams

Approval Workflow

Approval notifications with one-click approve for finance and management

Security & Compliance

Enterprise-ready with highest security standards

GoBD-Compliant Archive

Every dunning event archived immutably for 10 years with timestamp, recipient, text, approver. BMF Nov 2019 compliant.

GDPR & EU Hosting

Processing exclusively in EU data centers (Frankfurt, Munich). Art. 28 DPA, automated retention and access request processes.

§ 286/288 BGB Compliance

Default onset, late fees, and interest calculated audit-safe and day-accurate. Notice timing defensible in court.

Encrypted Communication

All dunning emails sent via TLS 1.3. DKIM, SPF, and DMARC configured to prevent phishing confusion.

Technology Stack

n8nLexoffice APIDATEV Unternehmen OnlinesevDesk APIStripePostgreSQLClaude/GPT-4Brevo

Frequently Asked Questions

Yes. We have native adapters for Lexoffice, DATEV Unternehmen Online, sevDesk, and Billomat – even in combination. The workflow logic is identical, only the adapter swaps out. Switching later (e.g., from Lexoffice to DATEV) is just an adapter reconfiguration, not a new workflow.
No. Before every dunning stage the system checks current payments in real time – via bank API (Finom, Qonto, Fyrst) or via the payment reconciliation in Lexoffice/DATEV. As soon as payment is detected, the dunning process closes automatically and a confirmation email goes out.
Yes. Workflow logic respects default onset per § 286(1) BGB (notice) and § 286(3) BGB (30-day B2B rule). Interest per § 288 BGB is calculated with the current base rate + 9pp (B2B) or + 5pp (B2C) day-accurate. Late fees are configurable, with adequacy defaults pre-set.
Customer segmentation. Per segment (long-standing A/B, new, enterprise, public sector) you set escalation profiles: tone, deadlines, late fees, path. Long-standing customers typically get longer deadlines, softer wording, and no late fee in stage 2. An exception list covers strategic accounts that require manual approval at every stage.
Yes, built in. GoBD: every dunning event is archived immutably for 10 years with timestamp, recipient, text, approver, and delivery receipt. GDPR: EU hosting (typically Frankfurt or Munich), DPA under Art. 28, automated retention, Art. 15 access requests handled.
4-6 weeks typical. W1-2: current-state analysis, data source integration, dunning profiles and tone defined, approval flows. W3: test run with historical data (parallel ops). W4: pilot with selected customers. W5-6: full rollout and fine-tuning. From W7 onward, steady state with ~30 min/week approval time.

Automate dunning and cut DSO?

30 minutes on your AR book, your DSO, and which integration (Lexoffice, DATEV, sevDesk) fits – no pitch, concrete numbers for your case.