Open receivables automation: rules for reminders, dunning notices and handovers
This article explains open receivables automation: rules for reminders, dunning notices and 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
The focus: rules for reminders, dunning notices and handovers. 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. Open receivables are reconciled with bank transactions monthly so that phantom balances never reach a reminder letter. Standardisation reduces effort here far more than additional checking does.
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. A well-maintained open items list is the basis for every DSO and ageing analysis. Everything else is subordinate to this goal: rules for reminders, dunning notices and handovers.
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. A monthly look at the age structure reveals shifts earlier than any individual case review. 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.
Every exception to the rule is justified and noted in the system. That keeps it traceable why a case was treated differently. Positions with no movement for several months belong on a separate review list. In concrete terms this comes back to one point: rules for reminders, dunning notices and 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. An open items list should show invoice number, due date, remaining balance, dunning level and last contact for every position. Settling this point once removes the need to renegotiate it in every individual case later.
