Receivables management and debt collection: how to design smooth handovers
This article explains receivables management and debt collection: how to design smooth handovers in the context of German receivables management. It is written for companies, self-employed professionals, accounts receivable teams and creditors that need a clear, documented next step. Fortis Inkasso GmbH & Co. KG can support professional debt collection processes; the article does not replace case-specific legal advice.
Target operating model and KPIs
A target picture makes receivables management measurable. The central KPIs are DSO, the share of overdue items by age bracket, the average days in default, the success rate per dunning level and the write-off rate. Without these figures, any improvement remains an assertion.
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. In receivables management, a documented standard process pays off more than a chain of individual decisions. A short note in the system replaces any later reconstruction from memory.
Process and responsibilities
Clear responsibilities prevent friction between sales, accounting and legal. Sales knows the customer relationship, accounts receivable knows the payment status, legal knows enforcement. The process has to define who decides when and who escalates.
An escalation matrix based on amount and age of the receivable reduces one-off decisions. Small amounts run automatically, large amounts are reviewed individually. KPIs such as DSO and the overdue share make the effect of process changes visible. For the constellation set out here the rule is: how to design smooth handovers.
Data and systems
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.
An export in a clearly defined format is essential as soon as cases are handed to a service provider. An interface or a structured CSV file is far superior to a manual collection of documents. A short written procedure is followed in daily practice more reliably than an extensive manual. The effort is one-off; the benefit repeats with every case.
Controls and escalation rules
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. An annual review of whether the defined stages still fit the customer base is worthwhile. Applied to this topic it means: how to design smooth handovers.
30-/90-day implementation
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. Effective receivables management combines prevention before the due date with consistent escalation after it. A fixed cycle is more effective than a review that only happens when someone asks for it.
