Guide
E-invoicing in Belgium: getting ready for Peppol
Belgian B2B invoices: establish the applicable scope, prepare Peppol, identify recipients and organise technical checks before the first delivery.
For a Belgian business, adopting structured invoicing starts with scope: which transactions and customers are covered? A VAT number does not describe every situation. Establishment, exemptions and the type of customer need to be checked before changing the invoicing process. Treat that classification as a business decision to document, rather than a setting guessed by the software.
Connect the software to its recipient
Peppol is the reference channel presented by the administration for the relevant exchanges. Ask the provider how it identifies customers, which responses it exposes and how incoming invoices reach the accounts. Confirm the recipient’s electronic address and identifier scheme. Do not confuse this routing information with an email address or a purchase order reference.
Test more than one simple invoice
Prepare a small set of cases: an ordinary invoice, a discount, multiple VAT categories and a credit note referring to an earlier invoice. KlarFakt’s Peppol validator can check supported XML before transmission. It neither verifies the recipient’s actual network registration nor sends the document. Where partners agree another route, establish the applicable conditions and expected format. Do not assume that a PDF accepted by a consumer also satisfies a mandatory B2B exchange.
Position checked on 6 October 2026
Structured invoices for domestic B2B transactions between Belgian VAT businesses since January 2026, subject to exceptions. Peppol is the standard route; an EN 16931-compliant agreement may use another route.
Follow one invoice through to receipt
Start with one representative test invoice and the delivery channel agreed with its recipient. Record separately whether the file passed technical checks, whether transmission was accepted and whether the customer matched it to the underlying transaction. These are three different outcomes. Assign an owner to each failure and retain the original file alongside the responses. Also try a correction and a resend so that the process cannot silently create duplicate entries. A successful local validation report replaces neither a required transmission service nor an assessment of the transaction’s tax treatment. The linked country profile records the reviewed scope and unresolved points.
Sources and next steps
Tools for this topic
Country pages
More guides
- EDI, Peppol and XML: format or delivery channel?
- Electronic credit notes: references, amounts and XML checks
- Peppol identifiers, EndpointID and buyer references
- VAT and rounding: find an invoice XML total mismatch
- EN 16931 explained: the European norm behind every e-invoice format
- Croatia: eRačun and the fiscalisation workflow
No legal advice. Dates and obligations follow the official publications cited in the text; where a date is not final, the text says so.