Insight
Belgium's B2B e-invoicing mandate: the January 2026 big bang
Belgium did not phase this by company size. Every business issuing a B2B invoice moved on the same day, over Peppol, which makes it the cleanest case study in Europe for what a mandate actually costs.
What changed and when
From 1 January 2026, B2B transactions between Belgian taxable persons require structured electronic invoices exchanged over the Peppol network. Unlike France or Germany, Belgium took a single-date approach rather than phasing by turnover, so a two-person consultancy and a large manufacturer faced the same deadline.
A structured invoice is not a PDF. A PDF emailed to a customer is a picture of an invoice; what the mandate requires is a machine-readable document in a defined format, transmitted through a network that both parties are registered on. This distinction is where most of the unexpected work lives.
Peppol is a delivery network with registered participants and access points, which means compliance is partly a matter of your software and partly a matter of being reachable on the network at all.
Why the "we already send electronic invoices" answer usually fails
Almost every business sends invoices electronically in the ordinary sense — they are attached to emails. That is not what the mandate means, and the gap between the two is the entire project.
The practical test is whether your customer's accounting system can read your invoice without a human retyping it. If a person on their side opens your document and keys the values into their ledger, you are not sending a structured invoice, whatever the file format.
The second test is whether your own system can receive one. Reception is frequently the neglected half: businesses focus on issuing and then discover their suppliers are sending structured documents their software cannot ingest.
Where the effort actually goes
Rarely on the invoice format itself, which accounting software vendors have largely handled. The effort goes into data quality: enterprise numbers, VAT identifiers, customer records that are complete and correct, and product or service lines that map to something a structured document can carry.
Businesses that have been invoicing with free-text descriptions and inconsistent customer naming find that a structured format is unforgiving in a way a PDF never was. A human reading a PDF tolerates a missing reference; a validation rule does not.
The other cost is the exception path. What happens when a document is rejected, when a customer is not reachable on the network, when a credit note has to reference an invoice that failed. Those flows need an owner, because unlike a bounced email they do not surface on their own.
What this predicts for the rest of Europe
Belgium is useful as a preview. Poland moves to KSeF clearance during 2026, France phases reception and issuance from September 2026 by company size, and Germany requires reception already with issuance phased across 2027 and 2028. By 2030 the ViDA framework extends structured invoicing to intra-EU B2B transactions generally.
A business trading across several of these markets is not facing one project but a sequence of them on different dates with different national platforms — clearance models in some countries, network models in others.
The strategic answer is to fix the underlying data once. Customer master, tax identifiers, product lines and the ability to emit and ingest a structured document are common to every one of these mandates; the national plumbing on top is comparatively cheap to add per market.
A short readiness check
Can your system emit a structured invoice, and can it receive one? Are your customer records complete enough to pass validation — legal entity names, enterprise and VAT numbers, addresses? Do you know which of your customers and suppliers are reachable on the relevant network?
Who owns a rejected document, and how would they know it had been rejected? What is the fallback when a counterparty is not reachable?
If you trade in more than one mandated market, is anyone tracking the dates? The most common failure we see is not technical unreadiness but nobody holding the calendar across markets.
Questions
Is a PDF invoice compliant?
No. A PDF is a picture of an invoice; the mandate requires a structured, machine-readable document exchanged over the network. If a person on the receiving side retypes your values, you are not compliant regardless of file format.
Does this affect us if we are not Belgian?
It applies to B2B transactions between Belgian taxable persons, but if you invoice Belgian business customers it affects how they need to receive from you. Confirm your specific position with your tax adviser.
Our accounting software says it supports Peppol. Are we done?
Usually not. The format is the easy half. Data quality — complete customer records, correct tax identifiers, structured line items — is where the work is, because validation rules are far less forgiving than a human reading a PDF.
What about credit notes and corrections?
They are part of the same structured flow and need to reference the original document. This is the area most often left until a real correction arrives and nobody knows how to issue it.
We trade in several EU markets. One project or several?
Fix the underlying data once — customer master, identifiers, line structure — then add national plumbing per market. Treating each mandate as a separate project repeats the expensive part several times.
Where this sits in what we do
This article covers one decision inside a wider engagement. The solution page sets out how that engagement runs, what it includes and what it costs to find out.
- Complete Digital Transformation — The whole stack, sequenced — brand, web, marketing, CRM, automation, reporting and infrastructure — with benefits measured afterwards rather than projected and forgotten.
- The EU AI Act: what actually applies from 2 August 2026
- Poland's KSeF mandate: what clearance invoicing changes
- AI for custom customer care: what it can answer and what it must not
- When to build software instead of buying it
- All insight articles
Trading across several e-invoicing mandates?
We will audit the data underneath rather than the invoice format, because that is the part every mandate has in common and the part that is expensive to fix late.
Get in touch