Invoice is not paid, because the customer disputes the service: how to respond

The first question is always how solid the claim actually is. The focus: How to respond. Separating the due date, proof of performance and the communication trail quickly shows whether this is a liquidity problem, a clarification problem or a process problem. Settling this point once removes the need to renegotiate it in every individual case later.

The first few days decide whether a case runs as routine or as a special exception. A clear initial assessment keeps it in the routine. Unpaid invoices often have a formal cause: a missing purchase order number, the wrong recipient or an unclear description of services. What is prepared properly at this stage shortens every subsequent step.

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. The more precisely an invoice describes the service delivered, the harder it is to delay payment with follow-up questions. In concrete terms this comes back to one point: How to respond.

A sequence with few, clearly timed stages works best. After the due date comes a short reminder, a few days later a formal reminder with a specific date, then the announcement of handover. Each stage is documented before the next begins. This care costs minutes and saves days if the matter is ever disputed.

Every stage should state the outstanding amount, the invoice number and the new deadline unambiguously. Collective reminders without a breakdown reliably produce queries rather than payments. A brief confirmation of receipt from the customer saves a great deal of later discussion. 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. For recurring services, a consistent invoice structure prevents queries from arising in the first place. The thematic core stays the same: How to respond.

Not every case belongs outside the company immediately. Handover is sensible when deadlines and contact attempts are exhausted, the amount justifies the effort and the documents are complete. Fortis Inkasso operates as a registered collection service provider. That keeps the case understandable for colleagues with no prior knowledge of it.

A handover requires the invoice, the contractual basis, proof of performance, the reminder history and current debtor data. The more complete the package, the faster processing starts. When an invoice stays unpaid, proof of delivery and of the invoice content is the first point to be checked. Standardisation reduces effort here far more than additional checking does.