Invoice is not paid despite a clear payment deadline: when default arises automatically

The starting point is default. Under section 286 of the German Civil Code it arises through a reminder, but at the latest 30 days after the due date and receipt of the invoice; against consumers only if the invoice pointed out that consequence.

This overview does not replace legal advice in the individual case. It does show which points should be settled before any escalation. A brief confirmation of receipt from the customer saves a great deal of later discussion. The effort is one-off; the benefit repeats with every case.

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. For recurring services, a consistent invoice structure prevents queries from arising in the first place. In concrete terms this comes back to one point: when default arises automatically.

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. When an invoice stays unpaid, proof of delivery and of the invoice content is the first point to be checked. This care costs minutes and saves days if the matter is ever disputed.

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. Standardisation reduces effort here far more than additional checking does.

Patchy documentation is another risk. If nobody can prove when which reminder was sent, enforcement becomes unnecessarily laborious in a dispute. Unpaid invoices often have a formal cause: a missing purchase order number, the wrong recipient or an unclear description of services. That brings the starting point back into view: when default arises automatically.

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. The more precisely an invoice describes the service delivered, the harder it is to delay payment with follow-up questions. The earlier this point is clarified, the less time enforcement costs later.