Open receivables prioritized by risk: a scoring model for amount, age and creditworthiness
This article explains open receivables prioritized by risk: a scoring model for amount, age and creditworthiness 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 scoring model for amount, age and creditworthiness. 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. A well-maintained open items list is the basis for every DSO and ageing analysis. This care costs minutes and saves days if the matter is ever disputed.
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. A monthly look at the age structure reveals shifts earlier than any individual case review. The link to the subject of this article is direct: a scoring model for amount, age and creditworthiness.
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. Positions with no movement for several months belong on a separate review list. The effort is one-off; the benefit repeats with every case.
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.
Every exception to the rule is justified and noted in the system. That keeps it traceable why a case was treated differently. An open items list should show invoice number, due date, remaining balance, dunning level and last contact for every position. The thread running through it stays the same: a scoring model for amount, age and creditworthiness.
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. Open receivables are reconciled with bank transactions monthly so that phantom balances never reach a reminder letter. A short note in the system replaces any later reconstruction from memory.
