Invoice is not paid in agency or freelance work: how to use proof of performance
This article explains invoice is not paid in agency or freelance work: how to use proof of performance 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
In practice, payment defaults rarely stem from unwillingness to pay alone. More often the causes are unclear descriptions of services, disputed variations, missing acceptance records, late invoicing, or invoices that reach the wrong contact person.
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. The more precisely an invoice describes the service delivered, the harder it is to delay payment with follow-up questions. Standardisation reduces effort here far more than additional checking does.
Which evidence is decisive
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. That keeps the case understandable for colleagues with no prior knowledge of it.
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. A brief confirmation of receipt from the customer saves a great deal of later discussion. That brings the starting point back into view: how to use proof of performance.
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.
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 recurring services, a consistent invoice structure prevents queries from arising in the first place. This care costs minutes and saves days if the matter is ever disputed.
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. When an invoice stays unpaid, proof of delivery and of the invoice content is the first point to be checked. The thematic core stays the same: how to use proof of performance.
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. Unpaid invoices often have a formal cause: a missing purchase order number, the wrong recipient or an unclear description of services. In practice, reliability pays off faster than pressure.
