Unpaid invoices

Invoice is not paid after rental or lease: how to separate claim types cleanly

A stylised clock face with a mint hand next to a folded document – illustration for the topic Unpaid invoices

This article explains invoice is not paid after rental or lease: how to separate claim types cleanly 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.

Typical causes in the sector

The focus: how to separate claim types cleanly. The sector-typical problems are interface problems: what sales promised is not in the contract, what was delivered was not signed for, what was billed does not match the order.

Knowing the causes allows targeted countermeasures instead of escalating every receivable individually. That lowers effort and protects the customer relationship. 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.

Which evidence is decisive

The documents should be assembled so that a third party understands the case without explanation. That means the contractual basis, the invoice, proof of performance or delivery, the reminder history with dates and complete debtor details. This care costs minutes and saves days if the matter is ever disputed.

In ongoing business relationships, filing by case rather than by customer works better. With several invoices open, it stays clear which document belongs to which amount. A brief confirmation of receipt from the customer saves a great deal of later discussion. The link to the subject of this article is direct: how to separate claim types cleanly.

Prevention before due date

Prevention means closing sources of error before they become excuses. Complete invoice details, the correct recipient address, a stored purchase order number and a short payment term noticeably reduce the likelihood of a payment problem.

Payment methods play a role too. The easier it is to pay, the smaller the share of delays that stem from pure inconvenience. For recurring services, a consistent invoice structure prevents queries from arising in the first place. Small improvements here work through the entire receivables portfolio.

Escalation after due date

Escalation follows a fixed rhythm rather than a mood. Stage one stays factual and low-key, stage two names default, interest and costs, stage three announces the handover to a collection agency or the court dunning procedure in concrete terms.

The tone stays professional throughout. The goal is payment, not conflict, especially with customers you intend to keep working with. When an invoice stays unpaid, proof of delivery and of the invoice content is the first point to be checked. Everything else is subordinate to this goal: how to separate claim types cleanly.

Practical example

An everyday example: an invoice for a mid four-figure amount is still open after 14 days. The review shows it was sent without a purchase order number and therefore stalled in the customer's approval workflow.

The undisputed portion is settled immediately, the disputed portion clarified separately. That keeps the bulk of the amount moving instead of blocking it alongside the complaint. Unpaid invoices often have a formal cause: a missing purchase order number, the wrong recipient or an unclear description of services. That keeps the case understandable for colleagues with no prior knowledge of it.

Get what you're owed.

Submit for free, in three minutes. The initial consultation is non-binding.

Submit a claim