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

Effective receivables management assigns clear roles: sales maintains contract and contact data, operational teams preserve performance evidence, accounting posts and reminds, legal or collection teams assess escalation, and management sets risk limits. Approval thresholds should cover disputes, high values, instalments, write-offs and supply stops. A regular review examines both metrics and individual cases. Shared definitions prevent different departments from handling the same customer with different balances or deadlines. For the specific issue “from manual dunning to a data-based process”, this requirement should be recorded in the review note with its date and supporting evidence.

For the focus “from manual dunning to a data-based process”, a short review note should record the facts, the rule applied and the legal or data date on which the statement is based. The contract, invoice, evidence of performance and communications should be brought together in one case file. In “from manual dunning to a data-based process”, this control determines whether the standard workflow applies or an individual review is required.

A 30-, 90- or 100-day programme starts with a baseline and defined objectives. First remove duplicates, posted payments and dispute cases; then prioritise by age, value and risk. A pilot group tests reminder logic, document standards, external handover and reporting. Rollout follows only after errors are corrected. Measures should include not only cash recovered but also disputes resolved, data completed, handling time reduced and new arrears prevented. Each phase needs owners and completion criteria. For “from manual dunning to a data-based process”, the workflow should continue only after ownership, deadline and the exception route are clearly set in the system.

For recurring cases, use a checklist of mandatory fields and a four-eyes review. A green status should be assigned only when the required evidence is available; otherwise the case should be routed deliberately for clarification. For “from manual dunning to a data-based process”, quality control should reconcile the balance and underlying entries once more against the original evidence.

A maturity model may distinguish five stages: unstructured individual work, standard deadlines, integrated data, risk-based management and continuous improvement. New software alone does not create the next level. Data quality, roles, rules, exception handling, metrics and regular controls are required. The business should define a small number of verifiable criteria for each stage. An advanced AI system is not progress if payments are misallocated, disputes are reminded automatically or responsibilities remain unclear. In “from manual dunning to a data-based process”, this control determines whether the standard workflow applies or an individual review is required.

The workflow should move standard cases quickly while automatically routing disputes, insolvency, data-protection or limitation risks out of the standard path. Human review remains necessary where the data or legal position is not clear. The outcome for “from manual dunning to a data-based process” should record the current balance, next date, reason for the decision and responsible person. Receivables management should automate standard cases while deliberately routing exceptions for review.

Days Sales Outstanding is commonly calculated as average receivables divided by credit sales, multiplied by the number of days in the period. It indicates capital tied up but can be misleading without seasonality, growth, payment terms and sector context. It should be supplemented by the overdue ratio, share over 90 days, dispute rate, promise-to-pay performance and recovery rate. Metrics need consistent definitions and segmentation by customer, country or product. A falling DSO accompanied by higher write-offs would not be a success. For “from manual dunning to a data-based process”, quality control should reconcile the balance and underlying entries once more against the original evidence.

Before escalation, reconcile bank entries, credit notes, returns, partial payments, objections, insolvency signals and limitation dates. An item shown as open in accounting is not automatically due or undisputed; the decision must follow from the complete file. For the specific issue “from manual dunning to a data-based process”, this requirement should be recorded in the review note with its date and supporting evidence.

Common errors include wrong debtor data, reminders before bank reconciliation, unclear due dates, missing performance evidence, endless clarification status, inconsistent interest, undocumented instalments and late limitation review. Using identical standard wording for consumers, businesses and disputed claims is also problematic. A monthly error log with cause and corrective action is more effective than simply sending more reminders. Good processes prevent new errors; a one-off clean-up project otherwise recreates the same backlog a few months later. The outcome for “from manual dunning to a data-based process” should record the current balance, next date, reason for the decision and responsible person.

The process ends with a documented decision stating the current balance, next deadline and responsible person. Fortis Inkasso GmbH & Co. KG can then handle suitable undisputed claims out of court, without implying a guarantee of recovery or legal outcome. For “from manual dunning to a data-based process”, the workflow should continue only after ownership, deadline and the exception route are clearly set in the system.