コンテンツへスキップ
ブログに戻る
Belgium公開日 2026年7月5日10 分で読めます

Belgium's B2B e-invoicing mandate 2026: Peppol, structured invoices & what to do

Belgium's mandatory B2B e-invoicing since 1 January 2026: who is affected, why it runs on Peppol BIS 3.0, structured formats vs PDF, how to send and receive, the tax incentive, penalties and a checklist.

Belgium's mandatory B2B e-invoicing is live: since 1 January 2026 established Belgian VAT-registered businesses must send and receive structured electronic invoices for domestic B2B transactions. Belgium built the mandate on the Peppol network, so if you can already do Peppol you are largely there. This guide explains who is affected, why it runs on Peppol BIS 3.0, the difference between a structured invoice and a PDF, how to send and receive, the tax incentive and the penalties.

What changed on 1 January 2026

From 1 January 2026, a plain PDF or paper invoice no longer satisfies the law for domestic B2B. Invoices between Belgian VAT-registered businesses must be issued and received as structured electronic invoices compliant with EN 16931 — machine-readable data, not an image or a PDF attachment. Both the sender and the receiver are in scope, so every affected business needs to be able to receive as well as send.

Who is affected

  • Businesses established in Belgium and registered for VAT, for their domestic B2B transactions.
  • Both the supplier (must issue a structured invoice) and the customer (must be able to receive one).
  • Some exemptions apply — e.g. certain flat-rate or VAT-exempt situations and businesses in bankruptcy. B2C and cross-border flows are outside this specific obligation.

Why Belgium runs on Peppol

Belgium chose the Peppol network as the default channel and Peppol BIS 3.0 as the default standard. Instead of a central government portal, invoices travel through Peppol Access Points using the four-corner model: your Access Point delivers to the buyer's Access Point. Parties are free to agree on another EN 16931-compliant format and channel, but Peppol BIS 3.0 over Peppol is the fallback everyone can rely on — which is why supporting it is the safe default.

Structured invoice vs PDF

A structured invoice carries every field — parties, lines, VAT breakdown, totals — as XML that software reads directly. A PDF (even a nicely formatted one) is a picture of an invoice; it is not compliant on its own. The accepted Belgian format is Peppol BIS 3.0 (UBL), which is EN 16931-based, so it interoperates with XRechnung, Factur-X and the other European CIUS/profiles built on the same core.

How to send a Peppol BIS 3.0 invoice

You send the invoice data you already have — CSV, Excel, UBL, EDIFACT or legacy XML — and request the Peppol BIS 3.0 profile. MyInvoice returns EN 16931 UBL, validated against XSD and the Peppol Schematron rules:

curl -X POST https://api.myinvoice.llc/v1/convert \
  -H "X-API-Key: ek_live_..." \
  -F "[email protected]" \
  -F "format=csv" \
  -F "profile=peppol-bis-3"

Swap /v1/convert for /v1/send and we transmit it over the network to the receiver instead of handing the XML back, with a delivery status you can poll and webhook events. Worth being precise about who does what: MyInvoice is not itself a certified Access Point — the network hop runs on our white-label partner, which is one — so you get Peppol delivery under one API key without becoming an Access Point or contracting one separately.

Generate a Peppol invoice in your browser

How to receive (and read incoming invoices)

Being able to receive is half the mandate. Documents addressed to you on the network land in your account with the original UBL and a readable summary, and incoming Peppol BIS 3.0, XRechnung, Factur-X or ZUGFeRD documents can be normalised back to clean, structured data your ERP can post — so a supplier on any European format still lands correctly in your books.

The cost-deduction incentive

To soften the transition, Belgium introduced a temporary enhanced tax deduction for small businesses and the self-employed on the costs of e-invoicing software and related consultancy (an increased cost deduction, running through the transition years). It is worth checking with your accountant whether your tooling spend qualifies.

Penalties

Non-compliance can lead to administrative fines that escalate for repeat infractions. But the practical pressure is commercial: from 2026, a customer that cannot receive a structured invoice — or a supplier that cannot send one — simply blocks the transaction. Being unable to invoice or be invoiced is a bigger problem than the fine.

Checklist

  • Confirm whether you are in scope (Belgian, VAT-registered, domestic B2B).
  • Get a Peppol Access Point (or a provider that gives you one).
  • Make sure you can both send and receive Peppol BIS 3.0.
  • Normalise incoming invoices from any EN 16931 format into your ERP.
  • Ask your accountant about the enhanced cost deduction.

Where MyInvoice fits in

MyInvoice turns the data you already have into validated Peppol BIS 3.0 (or XRechnung, Factur-X, UBL) ready for your Access Point — and reads incoming European e-invoices back into structured data. One API, EN 16931 at the core, XSD + Schematron validated before anything reaches your books.

Read the API docs