Receivables management maturity model: from manual dunning to a data-based process

The focus: from manual dunning to a data-based process. A small set of four to six KPIs reported monthly works best: DSO, overdue share, payment behaviour of the largest customers, the resolution rate for disputed items, and cost per euro recovered.

Clean separation matters: cases held up by a complaint do not belong in the same statistic as genuine payment problems. Otherwise the steering signal becomes blurred. Effective receivables management combines prevention before the due date with consistent escalation after it. The effort is one-off; the benefit repeats with every case.

A workable process describes every stage from invoicing to handover for collection. Each stage needs a defined trigger, a defined channel, a defined deadline, a named owner and a documented result.

An escalation matrix based on amount and age of the receivable reduces one-off decisions. Small amounts run automatically, large amounts are reviewed individually. In receivables management, a documented standard process pays off more than a chain of individual decisions. For the constellation set out here the rule is: from manual dunning to a data-based process.

No automated dunning works without clean data. You need unambiguous customer numbers, maintained address and contact data, correct payment terms in the master record and automatic matching of bank transactions against open items.

E-invoicing supplies structured data that makes allocation and analysis easier. That potential is only realised if routing, order and reference numbers are maintained consistently. KPIs such as DSO and the overdue share make the effect of process changes visible. What counts is less the perfect solution than one that is actually applied day to day.

Controls ensure that defined rules are actually applied. A monthly reconciliation of open items, a sample check on dunning-level compliance and a report on cases that have sat without action longer than agreed all work well.

Every exception to the rule is justified and noted in the system. That keeps it traceable why a case was treated differently. A short written procedure is followed in daily practice more reliably than an extensive manual. Translated into practice this means: from manual dunning to a data-based process.

The start works best in two waves. By day 30: stocktake, ageing analysis and definition of dunning levels. By day 90: automated reminders, escalation rules by amount and age, and monthly reporting.

Fine-tuning against the KPIs follows. What demonstrably works is kept; what shows no effect is adjusted. An annual review of whether the defined stages still fit the customer base is worthwhile. A short note in the system replaces any later reconstruction from memory.