A Dutch disciplinary appeal has confirmed that statutory audit opinions need sufficient evidence and a clear record of later file changes. The outcome draws attention to the records behind revenue, invoices and financial accounts. Weak evidence can undermine reported figures and delay decisions on cash, finance or a sale.
Why this matters
This ruling concerns an accountant’s work in statutory audits. It does not set a new contract rule for Dutch businesses. Still, a lender, accountant or buyer must be able to follow a material invoice from contract to ledger. That record helps staff see what work the customer accepted, what amount remains disputed and what cash can reasonably be expected.
Example
A company sends a large invoice before month-end. The customer approved the work on a call, but nobody recorded it. A later scope change sits in the project manager’s messages. When the customer disputes the price, finance has an invoice and ledger entry but no complete file. Payment remains uncertain while staff reconstruct the decision.
XTROVERSO tips
- Trace five material invoices. Start with the contract or quotation. Check delivery, customer acceptance, price changes, invoice details and the ledger entry. Record any missing link.
- Keep changes visible. Do not overwrite the only spreadsheet or file. Preserve the earlier version and record what changed, when, why and who approved it.
- Separate invoiced work from accepted work. Your cash planning should show which invoices are accepted, disputed or waiting for approval. The total debtor balance may hide collection risk.
- Review an ordinary transaction. Do not inspect only the largest problem file. Select a normal completed job and check whether the usual process produced a clear record.
- Ask where reviews get stuck. Ask your accountant or finance adviser which records cause repeated questions. Fix the monthly process instead of building a rescue file at year-end.
Want a clearer record from contract to invoice? We can help set up a practical review
The data, sourcing, and analysis behind this article were conducted by Paolo Maria Pavan. AI was not used to identify sources, build the factual basis, or produce the analytical judgment contained here. AI was used only as a drafting aid. The final English text was personally reviewed, edited, and approved by Paolo Maria Pavan before publication.
