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

This article explains outstanding receivables after due date: what to do on day 1, day 7 and day 14 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.
Starting point: What to do on day 1, day 7 and day 14
When an invoice is not settled as agreed, the first week shapes everything that follows. The focus of this article is one specific point: What to do on day 1, day 7 and day 14. A structured approach here noticeably shortens the time amounts stay open and creates the basis for any later escalation. In practice, reliability pays off faster than pressure.
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. The portfolio should be screened at least quarterly for cases approaching the limitation period. A fixed cycle is more effective than a review that only happens when someone asks for it.
Requirements and documents
The quality of the documentation decides both speed and prospects of success. As a rule you need the contractual basis, the invoice with number and due date, proof of delivery or performance, the payment history and current debtor data with a serviceable address. The earlier this point is clarified, the less time enforcement costs later.
Correct master data matters just as much: full company name, legal form, register number and a deliverable address. Even small discrepancies lead to queries later, or to a payment order that cannot be served. Outstanding receivables lose recovery probability with every month that passes, which makes speed a success factor in its own right. Applied to this topic it means: What to do on day 1, day 7 and day 14.
Step-by-step approach
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. Small improvements here work through the entire receivables portfolio.
Every stage needs a date, a channel and an owner. Follow-up dates are stored in the system so that no deadline lapses and no case is left sitting. An overview by age bracket shows immediately which outstanding receivables need attention first. Settling this point once removes the need to renegotiate it in every individual case later.
Common mistakes and risks
Inconsistency is the main risk. If dunning levels are applied differently depending on the customer, a pattern emerges that debtors adapt to. Add missing deadlines, unclear amounts and letters with no traceable sender in the system. This care costs minutes and saves days if the matter is ever disputed.
Patchy documentation is another risk. If nobody can prove when which reminder was sent, enforcement becomes unnecessarily laborious in a dispute. For outstanding receivables, the date of the last customer response should always be recorded alongside the amount. For the situation described here, the task is this: What to do on day 1, day 7 and day 14.
When Fortis can be involved
The right moment for handover is largely a resource question. As soon as the internal effort per case exceeds the expected return, outsourcing is worthwhile. Fortis Inkasso works as a registered collection service provider and can take on cases individually or in batches. The effort is one-off; the benefit repeats with every case.
One last internal check pays off before instructing: amount correct, payments allocated, address current, objections documented. Those four points decide how quickly processing starts. A fixed follow-up date stops individual receivables from quietly ageing in the portfolio. Standardisation reduces effort here far more than additional checking does.


