Business debt collection implementation: a 90-day plan from pilot case to regular operation
This article explains business debt collection implementation: a 90-day plan from pilot case to regular operation 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
The focus: a 90-day plan from pilot case to regular operation. 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.
Every KPI needs a target value, an owner and a trigger for action. A rise in DSO beyond a defined threshold should automatically prompt a review. Companies with a steady volume of receivables benefit from a fixed handover cycle rather than one-off ad hoc instructions. In practice, reliability pays off faster than pressure.
Process and responsibilities
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.
The interface with sales is particularly important. Payment holds or goodwill decisions should not happen informally but according to fixed rules and with a note in the system. In business-to-business trade, nine percentage points above the base rate plus the EUR 40 flat fee are the usual ancillary claims. The thread running through it stays the same: a 90-day plan from pilot case to regular operation.
Data and systems
The system landscape determines the effort. Accounting software, ERP and payment processing should be connected so that incoming payments are allocated automatically and the remaining balance is always shown correctly.
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. The larger the volume, the more important standardised data formats and clearly defined service levels become. A fixed cycle is more effective than a review that only happens when someone asks for it.
Controls and escalation rules
Escalation rules should be written down: which stage applies from which day of default, from which amount an individual review takes place, and from when a case is automatically passed to collection or legal.
Four-eyes approval for write-offs and a documented sign-off for instalment plans belong here too. Both protect against silent receivable losses. For business customers, a credit check before granting new payment terms is worth the effort. For the constellation set out here the rule is: a 90-day plan from pilot case to regular operation.
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.
A realistic schedule beats an ambitious one. Three stages implemented properly are worth more than ten stages nobody follows day to day. Framework agreements should state how partial performance and interim invoices are handled. Settling this point once removes the need to renegotiate it in every individual case later.
