The short version

As of January 1, 2026, most VAT-registered businesses in Belgium are legally required to send and receive structured electronic invoices for domestic B2B transactions, using the Peppol network (specifically the Peppol BIS Billing 3.0 format, itself based on the European standard EN 16931). A PDF attached to an email no longer counts as a compliant invoice between two Belgian businesses.

If you run an SME in Belgium and your invoicing still goes out as a PDF, a Word document, or a paper document, this is not a "nice to have" digitalization project anymore — it is a legal deadline with real consequences for VAT deduction rights if you get it wrong.

This article explains, without vendor hype, what actually changes and the concrete steps to take.

What "structured e-invoicing" actually means

The confusion most business owners run into is thinking a PDF invoice is already an "electronic invoice." It isn't, under this rule.

A structured e-invoice is a machine-readable data file (XML, following the Peppol BIS / EN 16931 standard) that a computer system can parse automatically — no human needs to open, read, and re-type it into accounting software. A PDF is a picture of an invoice for a human to read; a structured e-invoice is data a system can process directly.

Peppol (Pan-European Public Procurement Online) is the network — a standardized, secure way for invoicing software from different vendors to exchange these structured documents, similar in spirit to how email works across different providers. You don't send Peppol invoices "to Peppol" — you send them, through an accredited Access Point, to your counterparty's own Access Point.

Who is affected

The obligation applies to B2B transactions between Belgian VAT-registered businesses established in Belgium. In practice, this touches essentially every SME that invoices other Belgian companies — which is most of them, even service businesses that assume "this is a big-company problem."

A few nuances worth checking with your accountant rather than assuming:

  • Transactions with private consumers (B2C) are not covered by this specific mandate.
  • Cross-border invoicing has its own timeline tied to the EU's broader ViDA (VAT in the Digital Age) initiative, which is rolling out over a longer horizon.
  • Certain exempt activities under Belgian VAT law may have different treatment.

Don't take a blog post's word for your specific situation — this is exactly the kind of thing to confirm with your accountant or a tax advisor before your compliance date, not after.

Why this is happening now

Belgium isn't doing this in isolation. It's part of a broader European push (ViDA) toward real-time, digital VAT reporting to close the VAT fraud gap, which is large enough across the EU that governments are willing to force a technical migration to close it. Belgium moved earlier than some neighbors on the B2B domestic leg specifically.

The upside most compliance articles skip: structured invoicing, done properly, typically means fewer manual entry errors, faster invoice approval cycles, and less time reconciling accounts payable — because the data arrives ready to import instead of needing to be retyped or OCR'd from a PDF. Treated only as a compliance cost, it's a burden. Treated as a forcing function to clean up how invoicing data moves through your business, it pays for itself over time.

The practical checklist

1. Check what your current software already supports

Most modern accounting and ERP platforms used in Belgium (and many invoicing modules in CRM/ERP suites) have added or are adding native Peppol support, because their entire customer base needs it simultaneously. Before buying anything new:

  • Ask your current software vendor directly: "Do you support sending and receiving Peppol BIS invoices, and is it enabled on our account?"
  • If yes, the real work is configuration and testing, not procurement.
  • If no, or if the answer is vague, that's your signal to evaluate alternatives now rather than in December.

2. Confirm your Access Point

You don't connect to Peppol directly — you go through an accredited Access Point provider (often your accounting software vendor, sometimes a separate specialized provider). Confirm which one you'll use and that your company's Peppol identifier (usually derived from your Belgian enterprise number) is correctly registered.

3. Map your actual invoice volume and counterparties

Before the deadline, pull a simple list: who do you invoice, and who invoices you, that are Belgian B2B counterparties? This tells you the real scope of testing needed — a company issuing 15 invoices a month to five regular clients has a very different rollout than one issuing hundreds to shifting counterparties.

4. Test receiving before you need to

Receiving structured invoices correctly (so they flow into your accounting system without manual re-entry) is often the part teams forget to test. Send yourself a test invoice through your Access Point before your suppliers start sending real ones.

5. Don't forget the human side

Whoever currently opens PDF invoices, checks them, and enters them manually will have a changed job. If your bookkeeping process still routes through someone manually retyping numbers from an emailed PDF, that workflow needs to change — not just the invoice format. Budget time for this, not just software configuration.

6. Build in a buffer, don't wait for January

Access Point providers and accounting software vendors are dealing with their entire customer base migrating in the same window. If you wait until the last weeks before the deadline to ask for help, you will be in a queue with everyone else who also waited.

What this is not

This is not a reason to rip out a working accounting system and start a six-month ERP replacement project — for most SMEs, this is a configuration and process change, layered on top of what you already use, not a rebuild. Be wary of anyone selling you a large platform migration as the only way to become compliant; for most businesses, it isn't.

Where Robust Code fits

We're not an accounting software vendor, and we won't tell you to rip out a system that's fine. Where we typically help SMEs in this situation is reviewing how invoicing data currently flows between your accounting/ERP tools and the rest of your operations (CRM, project systems, reporting), and making sure a Peppol migration doesn't quietly break something else that depends on that data — before it becomes a January surprise.

If you want a second pair of eyes on your current setup, get in touch — a short technical review is usually enough to tell you whether you're on track or need to move faster.