How to Implement E-Invoicing in Belgium: A Step-by-Step Guide

Belgium's B2B mandate has been live since 1 January 2026 and fully enforced with penalties since 1 April 2026 (see our regulations guide for the full legal background). If you're not yet compliant, here's the practical path to get there.

Step 1: Confirm You're in Scope

You need Peppol-based e-invoicing if you are:

A business established in Belgium, or with a permanent establishment there
Registered for Belgian VAT
Invoicing another Belgian VAT-registered business (domestic B2B)

You're not in the current mandate's scope for B2C invoices (to consumers) or for invoices to businesses outside Belgium — though if you already trade with Germany, France, or the Netherlands, those countries have their own separate mandates and timelines to check.

Step 2: Choose How You'll Connect to Peppol

You have three practical options:

All-in-one Belgian software (e.g. Billit) — handles Peppol registration, invoice generation, and sending/receiving from a single subscription. Simplest option if you only invoice domestically.
A Peppol access point layered onto your existing accounting/ERP software (e.g. Storecove, Pagero, Basware) — useful if your accounting software doesn't have native Peppol support, or if you need one connection covering several EU countries.
A Peppol access point you already use for another country — if you're already sending XRechnung to Germany or Factur-X to France via a multi-country provider, check whether Belgium is already covered before adding a new tool.

See our software comparison for details on each.

Step 3: Register Your Peppol Participant ID

To receive invoices via Peppol, your business needs to be discoverable on the network under a Peppol Participant ID, typically based on your Belgian enterprise number (format: 0208:BE0xxxxxxxxx, using the KBO/BCE company number). Most Belgian-focused software (like Billit) automates this lookup and registration for you during onboarding; with a generic access point, you may need to request registration explicitly.

Step 4: Configure Invoice Generation

Your invoices need to be issued as structured Peppol BIS Billing 3.0 documents (based on UBL 2.1), not just PDFs. In practice this means:

Your invoicing software maps your existing invoice data (customer, VAT number, line items, totals) to the Peppol BIS 3.0 schema automatically
The invoice is validated against Peppol/EN 16931 business rules before sending — most software rejects invalid invoices at this stage rather than letting them fail on delivery
A human-readable version (PDF) can usually be generated alongside the XML for your own records, but the XML is what makes the invoice compliant

Step 5: Test Sending and Receiving

Before relying on your setup for real invoices, confirm both directions work:

Sending: issue a test invoice to a business partner (or your own second Peppol ID, if your provider supports this) and confirm it arrives correctly formatted
Receiving: confirm your software correctly ingests an incoming Peppol invoice into your accounting records — remember, the obligation to receive applies just as much as the obligation to send, and penalties apply to failures on either side

Step 6: Handle Corrections and Self-Billing (If Relevant)

If you use self-billing (where the buyer issues the invoice on the seller's behalf), note that this category had an extended tolerance period running to the end of June 2026 — confirm with your software provider that self-billing workflows are fully supported if you use this arrangement.

Common Pitfalls

Assuming a PDF invoice is enough. It isn't — the structured Peppol BIS 3.0/UBL 2.1 data is what's required, even if you also generate a readable PDF.
Forgetting the receiving side. Businesses focus on sending compliant invoices and overlook that they also need to be able to receive and process incoming Peppol invoices.
Not checking your Peppol ID registration. If your business changed accounting software or legal structure recently, confirm your Peppol Participant ID is still correctly linked to your current KBO/BCE number.
Treating this as a one-time project. The near-real-time e-reporting layer proposed for 2028 is expected to build on the same Peppol infrastructure — getting your current setup right now reduces rework later.

What to Do Next

Confirm your scope (Step 1) and pick a software route (Step 2) if you haven't already
Register your Peppol Participant ID and complete setup
Run a real test invoice in both directions before treating your setup as production-ready
Bookmark our Belgium regulations guide — the near-real-time e-reporting proposal for 2028 is still moving through Parliament and the details may change

Last updated: August 2026.