SFERE / EXPLAINED

Peppol, EN 16931 and Belgian e-invoicing

Structured e-invoicing goes beyond exporting a PDF: business rules and identifiers matter.

Reviewed on 2026-11-08

Belgian B2B requirement

Since 1 January 2026, structured e-invoicing is required for Belgian B2B transactions within the legal scope. Exceptions and specific scenarios must be checked; there is no identical blanket B2C mandate.

EN 16931

European semantic standard describing a shared electronic-invoice model: supplier, customer, amounts, taxes, due dates, references and validation rules.

Peppol BIS Billing

An interoperability specification and document profile based on EN 16931, exchanged through a network of access points. Organisations can use an accredited provider rather than operating an access point themselves.

Where integrations fail

VAT mapping, rounding, addresses, participant identifiers, credit notes, units, purchase orders, delivery states and ERP/accounting reconciliation. A syntactically valid XML may still be operationally wrong.

At a glance

TermFunction
EN 16931European semantic invoice model
Peppol BISDocument profile and validation
Peppol networkInteroperable delivery through providers

How SFERE can support

SFERE: ERP data and rules review, integration, exchange testing and exception handling. No in-house operated Peppol access point.

Official laws, standards & publisher resources

This is an editorial explanation. Verify consolidated laws, applicable standards and interpretations for your activity, country and date. Full standards may require a licence.