Outstanding receivables after due date: what to do on day 1, day 7 and day 14

Reviewed: 2026-07-26. “Outstanding receivables after due date: what to do on day 1, day 7 and day 14” is mainly a matter of data quality, evidence and consistent deadlines. Businesses should separate undisputed payment arrears from genuine clarification cases. Not every unpaid invoice is already in default, and not every case requires several reminders. This avoids unnecessary escalation without allowing valid receivables to remain inactive. The contract and German law remain decisive.
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 “what to do on day 1, day 7 and day 14”, this requirement should be recorded in the review note with its date and supporting evidence.
For the focus “what to do on day 1, day 7 and day 14”, 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 “what to do on day 1, day 7 and day 14”, 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 “what to do on day 1, day 7 and day 14”, 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 “what to do on day 1, day 7 and day 14”, 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 “what to do on day 1, day 7 and day 14”, 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 “what to do on day 1, day 7 and day 14” should record the current balance, next date, reason for the decision and responsible person. For outstanding receivables, the next measure should follow directly from the documented status of the file.
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 “what to do on day 1, day 7 and day 14”, 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 “what to do on day 1, day 7 and day 14”, 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 “what to do on day 1, day 7 and day 14” 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 “what to do on day 1, day 7 and day 14”, 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.


