Belgium’s B2B e-invoicing mandate is in force: since 1 January 2026, VAT taxable persons established in Belgium must exchange structured electronic invoices. For SAP teams this is now an operations question, not a planning one — the review below covers what applies and where SAP landscapes typically need work.
How should SAP teams prepare for Belgium B2B e-invoicing?
SAP teams preparing for Belgium B2B e-invoicing should confirm legal scope, Peppol document profiles, participant identifiers, access-point responsibilities, source-data quality and exception handling. The implementation design should map these requirements to the exact SAP landscape and establish monitoring, rejection handling and evidence retention before production.
Key dates
1 Jan 2026
Mandatory for VAT taxable persons established in Belgium
Jan 2028
Coalition-policy target for e-reporting; not yet enacted
At a glance
- Mandate: Structured B2B e-invoicing via Peppol network (EN 16931)
- Formats: Peppol BIS (EN 16931 compliant)
- Platform / channel: Peppol network via accredited access points
- Who is affected: VAT taxable persons established in Belgium
- SAP scope: SD billing, FI invoices, tax codes, master data, Peppol connectivity + inbound processing
Executive Summary
| Mandate name | Belgium B2B e-invoicing (structured electronic invoices) |
|---|---|
| Current status (as of July 2026) | Mandatory since 1 January 2026 for in-scope VAT-taxable persons established in Belgium. The official FAQ describes targeted technical flexibility for electronic self-billing through 30 June 2026 when the business can demonstrate that its software provider is still implementing the required function; this is not a general exemption. |
| Exchange model | Peppol network with Peppol BIS format (EN 16931). Other networks/formats allowed only by mutual agreement and only if EN-compliant. Paper and plain PDF no longer qualify between in-scope parties. |
| Business risk | Invoices in non-compliant formats, AP processes unable to receive Peppol invoices, and VAT deduction exposure. |
| SAP impact | SD billing, FI invoices, tax codes, master data, Peppol access point connectivity, inbound processing, and monitoring. |
| Recommended next step | Verify both outbound and inbound Peppol flows are live for all Belgian company codes. |
| What’s next | Near-real-time e-reporting for 2028 is a federal coalition-policy target that still has to be transposed into Belgian law. It should be monitored, not presented as an enacted operative mandate. |
Scope, Exclusions and Targeted Tolerance
The B2B obligation applies to in-scope transactions between Belgian VAT-taxable persons. B2C transactions are outside this B2B rule. A VAT-taxable person not established in Belgium and without a Belgian fixed establishment is not in scope merely because it has a Belgian VAT identification. The small-business exemption scheme does not create a general e-invoicing exemption, and the agricultural special scheme has at least a receiving obligation. Transaction-specific exclusions must be checked against the current official scope guidance.
SAP Readiness Questions
- Are all Belgian company codes connected to a Peppol access point for both sending and receiving?
- Can SAP source data populate the required Peppol BIS fields, including correct VAT treatment and partner identifiers?
- How are received Peppol invoices validated and posted in AP, and who owns rejections and corrections?
- Is the invoice archive keeping the structured XML, not just a PDF rendering?
How S4FN Can Help
S4FN can review invoice flows, Peppol BIS mapping assumptions, validation workflow, and technical integration options for Belgian SAP company codes.
Primary Sources and Verification
Verified on: 10 July 2026. Reconfirm transaction scope, establishment, targeted tolerance and any enacted e-reporting law before implementation.
Review Belgium E-Invoicing in SAP
Discuss country scope, source data, and implementation assumptions with S4FN.