Debt collection for businesses

Business debt collection in construction: how to document progress payments, acceptances and change orders

Abstract stacked cards forming an ascending step pattern – illustration for the topic Debt collection for businesses

This article explains business debt collection in construction: how to document progress payments, acceptances and change orders 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 document progress payments, acceptances and change orders. 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.

Structural factors add to this: long payment terms, an obligation to perform first, and seasonal swings in the customer's liquidity. These patterns can be recognised early and planned for. In business-to-business trade, nine percentage points above the base rate plus the EUR 40 flat fee are the usual ancillary claims. What counts is less the perfect solution than one that is actually applied day to day.

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. Settling this point once removes the need to renegotiate it in every individual case 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 larger the volume, the more important standardised data formats and clearly defined service levels become. For the situation described here, the task is this: how to document progress payments, acceptances and change orders.

Prevention before due date

The most effective lever sits before the due date. It includes a credit check on new customers, clear payment terms in the quotation, deposits or stage payments on larger orders, and an invoice sent immediately after the service is delivered.

A friendly reminder a few days before the due date is service, not suspicion. It clears up questions before the amount ever becomes overdue. For business customers, a credit check before granting new payment terms is worth the effort. Small improvements here work through the entire receivables portfolio.

Escalation after due date

After the due date, consistency counts. A short reminder after a few days, a formal reminder with a calendar deadline and a final announcement of the next steps before the case is handed over have all proved effective.

Announced steps have to actually happen. A reminder with no consequence weakens the effect of every letter that follows. Framework agreements should state how partial performance and interim invoices are handled. Everything else is subordinate to this goal: how to document progress payments, acceptances and change orders.

Practical example

By way of illustration: a customer pays two invoices on time, the third stays open. Instead of sending a reminder straight away, a short phone call reveals that a partial delivery was disputed and payment is being withheld for that reason.

After correction and reissue with the purchase order number and a new deadline, the payment arrives. The case was never a credit risk but a process error, visible only because someone asked. Companies with a steady volume of receivables benefit from a fixed handover cycle rather than one-off ad hoc instructions. What is prepared properly at this stage shortens every subsequent step.

Get what you're owed.

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

Submit a claim