Belgium's VAT E-Reporting Mandate Confirmed For 2028

On July 18, 2026, Belgium's federal Council of Ministers approved a pre-draft law that adds a near-real-time VAT e-reporting layer on top of the country's existing B2B e-invoicing mandate, starting January 1, 2028, and built on what's called a Peppol five-corner model. The Cabinet, under Prime Minister Bart De Wever and on a proposal from Finance Minister Jan Jambon, also agreed to scrap the annual client listing obligation that Belgian VAT filers have dealt with for decades. If you run EDI or B2B integration for a company trading with Belgian partners, this is the second shoe dropping after January 2026's mandatory structured invoicing rollout, and it changes what "compliant" actually means for data flowing through your access point.

What Belgium's Cabinet just approved

The pre-draft measure would require suppliers and buyers to report selected invoice data to Belgium's tax authority, FPS Finance, in near real time, using the Peppol network as the transport layer rather than a separate reporting portal. The tax authority becomes the fifth corner in a framework that currently stops at four: supplier, supplier's access point, buyer's access point, buyer. This is not enacted law yet. As of this writing it remains a pre-draft that still has to clear parliament, and the dataset, exact deadlines, and penalty structure are expected to come via a future Royal Decree.

The timeline so far

Belgium has moved through this rollout faster than almost any other EU country, and the dates matter for anyone planning integration work against a moving target.

That June 2026 Peppol figure is worth sitting with: Belgium's Peppol registrations passed 2.1 million by June 2026, making it the largest national Peppol network in the world. Belgium didn't phase this in by company size the way Germany or Poland did. Every VAT-registered business was in scope from day one.

Four-corner vs. five-corner: what changes in the data flow

Since January 2026, Belgian B2B invoices already move as structured EN 16931 documents in Peppol BIS 3.0 / UBL format between access points. If you've mapped an EDIFACT INVOIC or an X12 810 onto a VAN before, the four-corner model isn't conceptually new. It's a routing layer with certified intermediaries instead of your usual VAN.

The fifth corner changes the obligation, not the wire format. In architectural terms, this positions Belgium in a five-corner Peppol model: supplier, supplier's access point, buyer's access point, buyer, and the tax administration as the fifth corner receiving the reported subset from both sides of the transaction. Both sides report, which is a dual-sided control model similar in spirit to what France and Poland have built into their own continuous transaction control regimes, and a pattern this blog has flagged before as creating more rejection and reconciliation edge cases than four-corner exchange ever did.

What this means for EDI and B2B integration teams

Nobody needs a new platform accreditation for this, which is one genuine piece of good news. Still, there's real work to plan for before 2028:

• Ask your Peppol access point or EDI provider now, not in late 2027, what their roadmap looks like for dual-sided five-corner reporting, since the exact dataset depends on a Royal Decree that hasn't been published yet.
• Audit which Belgian trading partners still route through legacy EDIFACT or custom VAN mappings rather than native Peppol BIS 3.0, because those mappings will need a compliant bridge before the reporting layer goes live.
• Close out any self-billing invoice flows that leaned on the tolerance period, since that exception expired on 30 June 2026 and self-billed invoices are now fully in scope with no further leniency guaranteed.
• Build validation and error-handling for near-real-time rejection scenarios now, borrowing from whatever playbook your team already built for France's or Germany's CTC rollouts.

Vendor landscape handling the mapping

EDI providers that already handle your retail or automotive EDIFACT and X12 traffic, EDICOM, TrueCommerce, Cleo, SPS Commerce, and tax-focused platforms like Pagero, are the ones most readers will lean on for this same Peppol connection rather than standing up a separate compliance stack. The practical question to ask any of them is whether their Belgian access point roadmap includes sandbox testing for the reporting payload, not just invoice delivery.

This isn't limited to commercial invoices either. Freight and carrier invoices moving through Belgian ports and distribution hubs will eventually need the same structured, EN 16931-aligned format, which is where transport execution platforms sit alongside EDI providers in reconciling freight invoice data against TMS and ERP records, a gap that already costs mid-market shippers 3% to 7% of annual freight spend when it's handled manually.

What hasn't changed

B2C invoicing stays out of scope entirely under both the 2026 and proposed 2028 rules. Cross-border intra-EU B2B transactions also wait for the EU-wide ViDA digital reporting mandate, which doesn't apply until 1 July 2030, so Belgian entities invoicing partners outside Belgium aren't yet forced onto this five-corner structure for those flows.

Action items before 2028

1. Q4 2026: inventory every Belgian trading partner and how invoices currently reach them, Peppol-native or bridged from legacy EDI.
2. H1 2027: get a written five-corner certification timeline from your access point or EDI vendor.
3. H2 2027: run parallel test reporting if your vendor offers a sandbox against the published dataset.
4. January 2028: go live, assuming the pre-draft clears parliament on schedule.