Invoice is not paid and the customer does not respond: escalation without losing time

Reviewed: 2026-07-26. This article, “Invoice is not paid and the customer does not respond: escalation without losing time”, explains a specific part of debt recovery under German law. The first task is to distinguish a due and substantiated claim from booking errors, legitimate objections and simple delay. Not every unpaid invoice is already in default, and not every case requires several reminders. A documented workflow protects liquidity, evidence and the customer relationship. The information is general and does not replace a review of the individual case.
When default begins under German law
Under section 286 BGB (German Civil Code), default generally requires a due obligation and a reminder sent after the due date. A reminder is unnecessary, for example, where a calendar date for payment was agreed, the debtor seriously and finally refuses payment, or the statutory 30-day rule applies. For consumers, that 30-day rule requires a specific notice in the invoice or payment statement. Default does not arise where the debtor is not responsible for the delay. For the specific issue “escalation without losing time”, this requirement should be recorded in the review note with its date and supporting evidence.
For “escalation without losing time”, the starting point is not the reminder stage but a verified set of facts. The reviewer records the legal basis of the claim, contracting party, amount, due date, receipt and payments before drawing a legal or operational conclusion. In “escalation without losing time”, this control determines whether the standard workflow applies or an individual review is required.
Reminder: form, content and evidence
A Mahnung (German payment reminder) is generally not subject to a prescribed form and may therefore be made orally or by telephone. It must, however, clearly demand the due performance. For evidentiary purposes, text form stating the invoice number, outstanding amount, due date and a reasonable payment deadline is normally preferable. The business should retain the date, channel and content. German law does not automatically require several reminders, although a staged commercial process may still be appropriate. For “escalation without losing time”, the workflow should continue only after ownership, deadline and the exception route are clearly set in the system.
The rule should not exist only in a manual. The system should define a trigger, case owner, deadline and escalation path, making it clear why the case was processed, paused or transferred. For “escalation without losing time”, quality control should reconcile the balance and underlying entries once more against the original evidence.
Escalate without wasting time
If the debtor does not respond, sending the same message every week is rarely useful. A better escalation rule records contact attempts, states a final deadline, channels objections and triggers the announced measure once the deadline expires. Earlier action may be appropriate for high values, visible financial distress, imminent limitation or a foreign debtor. Threats, unclear additional charges or inconsistent messages from different contacts weaken credibility and evidence instead of improving recovery. In “escalation without losing time”, this control determines whether the standard workflow applies or an individual review is required.
For larger portfolios, apply the rule consistently while allowing justified exceptions. Defined thresholds, a documented exception route and sample controls help prevent automation from producing factually incorrect measures. The outcome for “escalation without losing time” should record the current balance, next date, reason for the decision and responsible person. When an invoice remains unpaid, the amount, due date and receipt should be verified before any escalation.
Validate the claim before escalation
Before any reminder or handover, the creditor should reconcile the creditor and debtor identities, contract, performance, invoice amount, due date, payments, credit notes and objections. The company name and legal form must match the actual contracting party. For ongoing contracts, termination, term and billing period must be checked. Only the balance remaining after all payments and credits may be pursued. A short internal approval step prevents non-existent claims, duplicate handling and unnecessary costs. For “escalation without losing time”, quality control should reconcile the balance and underlying entries once more against the original evidence.
A common mistake is to infer default directly from an open balance. Corrections, counter-rights and receipt issues must be checked first, and calculations should allow a third party to reconstruct every amount and period. For the specific issue “escalation without losing time”, this requirement should be recorded in the review note with its date and supporting evidence.
Communicate firmly and customer-focused
Effective payment communication is factual, specific and free from unnecessary pressure. It states the invoice, balance, due date, payment method, contact and clear deadline. It also provides a channel for documented objections and genuine payment difficulties. Courtesy does not mean allowing deadlines to pass without consequence; consistency does not mean threats or public shaming. A uniform tone and a single contact are more likely to preserve the commercial relationship than changing and contradictory messages. The outcome for “escalation without losing time” should record the current balance, next date, reason for the decision and responsible person.
The article therefore leads to a reviewable decision rather than a blanket measure. Once the claim and evidence are clear, Fortis Inkasso GmbH & Co. KG can take the next out-of-court step; objections should first be assessed legally. For “escalation without losing time”, the workflow should continue only after ownership, deadline and the exception route are clearly set in the system.
Sources
Primary sources and official information used in this article.


