Belgium's 2028 E-Reporting: The Five-Corner Model, and Why Both Sides Report

The short answer

From 1 January 2028, Belgium adds near real-time e-reporting on a five-corner Peppol model. The tax authority becomes an additional participant, receiving structured invoice data shortly after issuance rather than in a periodic return. Reporting is transaction by transaction, it replaces the annual customer listing, and both supplier and customer report separately.

A preliminary draft law amending the VAT Code was approved by the federal cabinet on 18 July 2026. If you are building for the 2026 B2B mandate now, this is the thing to keep in view while the code is open.

What the fifth corner actually is

The four-corner model most people know:

C1 supplier → C2 supplier's provider → C3 buyer's provider → C4 buyer

The invoice travels between two certified access points and the tax authority sees nothing until a return is filed.

The fifth corner adds the administration as a participant:

C1 → C2 → C3 → C4
      ↘         ↙
        C5  tax authority

Both providers send structured data to the authority as part of the exchange. Reporting stops being a monthly or annual summarisation exercise and becomes a property of the transaction itself.

Why both sides report

This is the design decision that matters most for implementers, and it is easy to skim past.

If only the supplier reported, the administration would hold one unverified assertion per invoice. With both parties reporting independently, it holds two records of the same transaction from two different systems, and can match them. A mismatch is a signal. A missing counterpart is a signal.

That is what makes the model a fraud-detection instrument rather than a faster filing cabinet, and it is why the annual customer listing becomes redundant — the matching that the listing enabled once a year now happens continuously.

The practical consequence: your provider must file correctly on both legs. If you are the buyer's provider, you have a reporting obligation on invoices you did not create and cannot alter. Getting that right is a different problem from sending.

We have already built this

Not a claim we make lightly — it is the same architecture Belgium is describing, and we operate it in production in Oman.

Under Oman's model both the supplier's provider and the buyer's provider file a Tax Data Document for the same invoice, and a deterministic UUID — derived identically by both sides from the invoice's own fields — lets the authority correlate the two filings without either party coordinating with the other. Two independent reports, one transaction, matched by construction.

The lesson that transferred: the hard part is not sending to a fifth corner. It is making both filings agree when they are produced by two different systems, in two different companies, from the same document. Deterministic derivation is what makes that tractable. Timestamps, ordering and retry semantics are where it goes wrong.

No platform accreditation — unlike France

Worth stating plainly, because it shapes vendor choice.

Belgium has indicated no official accreditation process will be required for platforms or invoicing software. Compare France, where the PDP regime creates a registered class of providers and the choice of vendor is constrained by that register.

For Belgium your provider needs to be a certified Peppol access point that can file both sides correctly. It does not need a Belgian licence, and — as foreign companies often ask — it does not need to be a Belgian company.

What to do now, in 2026

You do not need to build 2028 today. You do need to avoid decisions that make it expensive.

• Keep the invoice UUID stable and derivable. If your invoice identity is a database sequence that only your system knows, correlating two independent filings later will be painful. Derive it from the document.
• Store the document you actually sent, byte for byte. Reporting a transaction you can no longer reproduce is not a position you want to be in.
• Treat inbound as a first-class path. In 2028 the buyer's side has its own obligation. If your inbound handling is a mailbox someone checks, that becomes a compliance gap rather than an inconvenience.
• Choose a provider that has done dual filing somewhere. Ask directly. The answer is either yes with a jurisdiction attached, or a roadmap.
• Watch ViDA. Belgium is early, not unique — the EU direction of travel is toward exactly this, and building Belgium properly is building most of the rest.

Related reading

• Belgium e-invoicing compliance — the current mandate, in full
• Belgium B2B e-invoicing 2026 — what is already in force
• Oman's five-corner model explained — the same shape, running today
• E-invoicing mandates 2026 tracker

Primary sources: European Commission — eInvoicing in Belgium · einvoice.belgium.be · FPS BOSA

The 2028 regime is at preliminary draft law stage. Details can change before it is enacted; where this article describes the proposal rather than settled law, it says so.