Invoice is not paid: how the customer relationship remains intact
This article explains invoice is not paid: how the customer relationship remains intact 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: how the customer relationship remains intact. 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. Unpaid invoices often have a formal cause: a missing purchase order number, the wrong recipient or an unclear description of services. The earlier this point is clarified, the less time enforcement costs later.
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.
An escalation matrix based on amount and age of the receivable reduces one-off decisions. Small amounts run automatically, large amounts are reviewed individually. The more precisely an invoice describes the service delivered, the harder it is to delay payment with follow-up questions. The thread running through it stays the same: how the customer relationship remains intact.
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 brief confirmation of receipt from the customer saves a great deal of later discussion. What is prepared properly at this stage shortens every subsequent step.
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.
Four-eyes approval for write-offs and a documented sign-off for instalment plans belong here too. Both protect against silent receivable losses. For recurring services, a consistent invoice structure prevents queries from arising in the first place. For the constellation set out here the rule is: how the customer relationship remains intact.
30-/90-day implementation
The first 30 days are about transparency: structure open items by age, clean up master data, name the owners and document the current dunning deadlines. The goal is a reliable baseline, not a perfect system.
Fine-tuning against the KPIs follows. What demonstrably works is kept; what shows no effect is adjusted. When an invoice stays unpaid, proof of delivery and of the invoice content is the first point to be checked. In practice, reliability pays off faster than pressure.
