Dunning Agent

One in two B2B invoices in Europe is paid late. The Atradius Payment Practices Barometer 2025 puts it at 47 percent of all receivables in Western Europe. These are not isolated cases but a structural liquidity problem. Anyone who does not manage the dunning process systematically ends up financing customers involuntarily - and carrying the default risk alone.

Late payments cost more than the outstanding amount

The obvious cost of an unpaid invoice is the outstanding balance. The real cost is significantly higher. Tied-up liquidity is missing for investment, supplier terms deteriorate, and the company’s own credit line is stretched further. At an average DSO of 45 days in the European mid-market, a company with EUR 50 million (USD 54 million) in annual revenue permanently carries around EUR 6.2 million (USD 6.7 million) in open receivables. Every day of DSO reduction releases roughly EUR 137,000 (USD 148,000).

The problem is rarely lack of will. It is lack of system. The clerk monitoring 2,000 open items prioritises on gut feel. The large customer gets dunned, the medium-sized one slips through. Partial payments complicate things. And when month-end close and dunning run collide at the same time, the close wins.

Rule-based escalation replaces gut feel with system

The Decision Layer breaks the dunning run into eight decision steps. Seven of them are fully rule-based: due date check, dunning level, dunning block, fee calculation, text generation, payment matching and dispatch. These steps follow clear rules - date comparisons, escalation logic, statutory interest calculations under European civil law. Human judgement brings no added value here, but human error certainly does.

Concretely: every Friday at 6 a.m., the agent checks every open item against its due date. For every overdue receivable it determines the correct dunning level, calculates late-payment interest to the exact day, matches against any interim payments and generates the appropriate dunning text. Before dispatch it checks whether a dunning block applies. Then it sends the notice - by email or letter, depending on customer configuration. The entire volume of a weekly dunning run is processed in minutes instead of hours.

Dunning blocks protect customer relationships automatically

The biggest fear in receivables management: sending a dunning notice to a customer who has a valid complaint. That destroys trust and ties up sales in apologies instead of selling. In manual processes this happens regularly because the accounting team does not know or overlooks the complaint status.

The agent solves this through a systematic check before every dispatch. If there is an open complaint or credit note request, the debtor is automatically blocked and the responsible clerk is informed. At the same time, the agent differentiates by customer segment: strategic customers can receive longer deadlines or adjusted dunning texts - not because someone remembers, but because the escalation logic provides for it.

Collection escalation stays a strategic decision

Seven of eight decision steps in the dunning run are arithmetic. The eighth is not. Handover to collections or the legal department is a trade-off between receivable size, customer relationship, industry signal and effort. A long-standing customer with a temporary liquidity shortfall deserves different handling than a chronic late payer.

This decision stays with the human. The agent supplies the foundation: complete dunning history, prior payment behaviour, size of the outstanding receivable, number of unsuccessful dunning levels. The decision itself is made by the clerk or the department head - informed, not flying blind.

Every single dunning decision is documented: when the notice was issued, which level, which amount, whether a dunning block was considered. At the next tax audit, it is fully traceable why dunning was issued or not - compliant with German GoBD (German record-keeping standard) bookkeeping principles, and without retrospective reconstruction.