Receivables management up to the Mahnbescheid (German court order for payment): how to define escalation paths

An unpaid invoice is rarely an isolated event; it is usually the result of several small gaps in the process. This article starts exactly there: How to define escalation paths. The aim is an approach that avoids escalation yet stays documented well enough to hold up. Settling this point once removes the need to renegotiate it in every individual case later.

In practice this means reconciling payment terms, invoice date and incoming payments before any contact is made. Only then can you judge whether this is a genuine payment problem or a case that simply needs clarification. Effective receivables management combines prevention before the due date with consistent escalation after it. Standardisation reduces effort here far more than additional checking does.

Evidence is the currency in any dispute. What is needed: the contract or order confirmation, the invoice with number and date, proof of delivery or acceptance, the correspondence on the case and a statement of all payments received so far. That keeps the case understandable for colleagues with no prior knowledge of it.

Missing evidence can often be obtained retrospectively: delivery notes, timesheets, email confirmations or handover records. That effort is usually smaller than writing the receivable off. In receivables management, a documented standard process pays off more than a chain of individual decisions. For the constellation set out here the rule is: How to define escalation paths.

The approach follows the calendar rather than instinct. Day one after the due date: check incoming payments. Days three to five: friendly reminder. Days ten to fourteen: formal reminder with a final period. After that period: decide on escalation. A short note in the system replaces any later reconstruction from memory.

Under German law default occurs at the latest 30 days after the due date and receipt of the invoice, though against consumers only if that consequence was pointed out. From that point default interest can be charged. KPIs such as DSO and the overdue share make the effect of process changes visible. The effort is one-off; the benefit repeats with every case.

The common sources of error are quickly named: reacting too late, undocumented agreements, instalment plans without written confirmation, and assuming a phone call replaces a formal reminder. None of these is legally complex; all of them cost time. Small improvements here work through the entire receivables portfolio.

Patchy documentation is another risk. If nobody can prove when which reminder was sent, enforcement becomes unnecessarily laborious in a dispute. A short written procedure is followed in daily practice more reliably than an extensive manual. In concrete terms this comes back to one point: How to define escalation paths.

A collection agency makes sense once internal escalation is exhausted: the deadline has passed, there is no response and no reliable payment commitment. Fortis Inkasso GmbH & Co. KG takes on cases at this stage, reviews the documents and continues contact on the creditor's behalf. What counts is less the perfect solution than one that is actually applied day to day.

Cooperation can be limited to individual cases or set up as an ongoing process. Which variant fits depends on volume and on internal capacity. An annual review of whether the defined stages still fit the customer base is worthwhile. This care costs minutes and saves days if the matter is ever disputed.