Blog Revo: What 190,000 Incorrect VAT Payment Notices Teach Us

The issuance of 190,000 incorrect VAT payment notices highlights the vulnerability of digital tax processes. Although the VAT amounts and advance payments had been correctly paid and recorded, a technical issue prevented them from being properly allocated to the relevant VAT liabilities. As a result, businesses faced discrepancies between the economic reality and the administrative records maintained by the tax authorities.
Automation increases the speed, scale, and impact of errors. Mistakes that once remained isolated can now flow automatically through invoicing, accounting, payment, and tax reporting systems. An incorrect VAT number, a wrong tax treatment, or an inconsistent transaction status can quickly spread across multiple systems, business partners, and tax administrations.
The solution is to move controls upstream. With mandatory e-invoicing, upcoming Belgian e-reporting requirements, and the EU’s VAT in the Digital Age (ViDA) framework, tax data will increasingly be transmitted in near real time. Businesses therefore need robust preventive controls at the source, ensuring that tax determinations, master data, invoices, and accounting records are correct before information enters the wider digital reporting chain.

What happened?

In early August 2026, Belgium’s FPS Finance (Federal Public Service Finance) mistakenly sent approximately 190,000 VAT payment notices and debt demands to businesses that had already paid their VAT liabilities on time. Many notices indicated that VAT remained unpaid and, in some cases, warned of penalties and required payment within a very short period.

What was the underlying issue?

The problem was not that taxpayers failed to pay VAT. The issue arose within the Belgian tax administration’s VAT processing systems.

According to FPS Finance, technical problems prevented certain VAT payments and advances from being correctly allocated to:

the VAT debts arising from periodic VAT returns; or
the balance of the taxpayer’s VAT current account.

As a result:

Businesses made their VAT payment.
The payment was received and registered by the tax authority.
The system failed to correctly match the payment to the corresponding VAT liability.
The VAT debt therefore appeared as still outstanding in the administrative records.
Automatic collection and reminder processes generated payment demands and debt notices.

Why is this important?

The incident is a classic example of a reconciliation failure in a highly automated tax environment.

The economic reality was: VAT was paid.

The administrative reality became: VAT appeared unpaid.

When payment data, VAT return data, and taxpayer account data are no longer synchronized, automated systems begin generating incorrect outcomes. The error then propagates through the compliance chain without human intervention.

Connection with e-invoicing, e-reporting and ViDA

The case demonstrates a broader lesson for the digitalization of VAT.

Under:

mandatory B2B e-invoicing in Belgium,
future Belgian near real-time e-reporting (targeted for 2028), and
the EU’s VAT in the Digital Age (ViDA) digital reporting requirements from 2030,

tax administrations will increasingly rely on automated exchanges of digital data. A single incorrect data element, mismatched status, or reconciliation issue can quickly spread across accounting systems, reporting platforms, and tax authority databases.

Key lesson

The Belgian VAT notice incident was fundamentally a data reconciliation problem rather than a VAT payment problem.

The lesson for both tax administrations and businesses is that:

Digital tax compliance is only as reliable as the underlying reconciliation processes that connect transactions, invoices, payments, accounting entries, and tax reporting.

Controls therefore need to move upstream, ensuring that data is validated and reconciled before it automatically flows through interconnected VAT reporting systems.

Click on the logo to visit the website