Invoice is not paid, because the customer is insolvent: what may still be possible

The technical question is when a claim becomes enforceable and which ancillary claims arise. The basis is the due date, default and the contractual agreement, supplemented by the statutory rules on default interest and recovery costs.

This overview does not replace legal advice in the individual case. It does show which points should be settled before any escalation. When an invoice stays unpaid, proof of delivery and of the invoice content is the first point to be checked. A fixed cycle is more effective than a review that only happens when someone asks for it.

What needs checking is the conclusion of the contract, the service rendered, a proper invoice and the payment term. Only when this chain is unbroken do the consequences of default apply. Against consumers, the notice about the 30-day rule is added.

The invoice itself must contain the mandatory details so that it can be verified. Faulty invoices hand the debtor a convenient argument for holding back. Unpaid invoices often have a formal cause: a missing purchase order number, the wrong recipient or an unclear description of services. The link to the subject of this article is direct: what may still be possible.

Traceability matters more than decimal places. The breakdown should show the principal, the start of default, the interest period, the rate, the interest amount and any flat fees separately, so that the total remains verifiable.

Partial payments are recorded with their date and reduce the interest amount from the day of receipt. Without that allocation, differences arise that have to be explained later. The more precisely an invoice describes the service delivered, the harder it is to delay payment with follow-up questions. What counts is less the perfect solution than one that is actually applied day to day.

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. 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 brief confirmation of receipt from the customer saves a great deal of later discussion. The thread running through it stays the same: what may still be possible.

The practical consequence is changed payment behaviour. Customers who know that deadlines are monitored and default consequences are calculated pay earlier on average, without any dispute arising.

In ongoing customer relationships, clear but factual communication of the consequences works best. Transparency before the due date is more effective than pressure afterwards. For recurring services, a consistent invoice structure prevents queries from arising in the first place. What is prepared properly at this stage shortens every subsequent step.