Belgium’s 2026 e-invoicing mandate: what have we learned so far?

Summary

• Belgium: Structured B2B e-invoicing mandatory since January 1, 2026 (via Peppol).

• B2G: Mandatory for public procurement contracts published after March 1, 2024.

• Scope: Applies to almost all VAT-registered businesses established in Belgium.

• Format: Peppol BIS Billing 3.0 (UBL 2.1 XML) aligned with EN 16931.

• PDF invoices alone are not compliant for domestic B2B transactions.

• E-reporting: Planned for 2028, building on structured invoice data.

• Network stability confirmed; early challenges relate to registration gaps and data quality.

Belgium has fully transitioned to mandatory structured business-to-business (B2B) e-invoicing as of January 1, 2026. The country adopted a decentralized Peppol-based model rather than a centralized clearance system, requiring VAT-registered businesses to exchange invoices in structured XML format.

While the infrastructure has proven stable, the first months of enforcement highlight the importance of proper Peppol registration, clean master data, and operational alignment ahead of the planned 2028 e-reporting expansion.

The decentralized, structured and mandatory model

‍For B2B e-invoicing, Belgium did not build a central government portal. Instead, it relies on Peppol’s four-corner model, where certified Access Points securely exchange structured business documents.

In practise, Belgium uses Peppol BIS Billing 3.0, based on UBL 2.1 XML, as the standard EN 16931-compliant format, typically exchanged via the Peppol network, although other EN 16931‑compliant formats and networks (e.g., EDI) are permitted where both parties explicitly agree and the European standard is fully respected.

Key scope reminders:

• Applies to domestic B2B transactions between Belgian VAT-registered entities established in Belgium.

• B2C (business-to-consumer) invoices remain outside the scope of the mandate.

• B2G (business-to-government) obligations were already in force for public procurement.

• Near real-time e-reporting is planned from January 1, 2028, but is not yet mandatory.

The shift is not about digitization. It is about structured, machine-readable data.

The stable start

Unlike centralized clearance systems that face “go-live” overload risk, Belgium’s distributed architecture has prevented a single point of failure.

There have been no major nationwide outages. No central bottlenecks. No portal crashes.

Technically, the pipes are working.

Which means any current frictions are not infrastructure. They are behavioral and operational.

The real frictions: What Belgian businesses are learning

1. The “PDF is enough” myth

One of the most common misconceptions is the belief that emailing a PDF qualifies as e-invoicing.

It does not.

A PDF, even with an embedded QR code, is considered unstructured. It may serve as a visual representation, but the legal invoice is a structured XML file transmitted over Peppol.

Hybrid invoices are allowed. The XML is the invoice. The PDF is just a human-readable attachment.

This misunderstanding has led to:

• Suppliers sending non-compliant invoices;

• Buyers manually processing documents they cannot legally accept as structured B2B invoices;

• Increased reconciliation workload.

The mandate is not only about sending invoices electronically. It is about sending structured data.

2. Customers not yet Peppol-registered

In theory, once connected to Peppol, you can send invoices to any registered business.

In practice, many companies discovered their customers were not yet registered on the network at the start of 2026.

This creates a transitional tension:

• You are legally required to send structured invoices.

• Your customer may not yet be reachable via Peppol.

While fallback channels (such as PDF via email) may temporarily support operational continuity, they do not replace the structured obligation. Businesses are now actively pushing their trading partners to register.

E-invoicing compliance has become ecosystem-dependent.

3. Structured data discipline

Moving from PDF to XML forces a shift in mindset.

An XML invoice does not tolerate:

• Missing VAT numbers,

• Incorrect tax category codes,

• Incomplete address fields,

• Free-text workarounds.

Validation happens before transmission. If the structure does not comply with the schema, the invoice fails.

For many SMEs, this is the first time master data quality has become a compliance issue rather than an accounting inconvenience.

4. Receiving non-compliant invoices

Another recurring scenario: “What if I still receive a traditional invoice?”

In early 2026, this remains common.

Businesses must:

• Verify authenticity and integrity,

• Assess whether the supplier is legally obligated to issue via Peppol,

• Encourage alignment with the structured requirement.

The transition period is revealing uneven readiness levels across industries. The structured system works, but only when both parties participate.

Peppol explained: Infrastructure, not software

Peppol is often mistaken for a tool or a government portal. It is neither.

It is an international network that allows structured documents to be exchanged securely between connected participants. You connect once through a certified Access Point and gain interoperability with all registered entities.

Your Peppol ID functions like a digital address for exchanging structured documents. This ID is based on a structured identifier - for Belgian businesses, most commonly the Peppol scheme code 0208 followed by the Enterprise Number (KBO/BCE), or the scheme code 9925 followed by the VAT number. While these are the most frequent formats, other compliant identifiers may also be used. You can learn more about the accepted Peppol ID schemes here.

Once active, invoices can flow seamlessly, without manual emailing, scanning, or re-keying.

The shift is architectural. Belgium has embedded invoice exchange into the network infrastructure.

The hidden efficiency layer

Companies treating the mandate purely as a compliance burden are overlooking a deeper opportunity.

Structured XML enables:

• Automated reconciliation through structured payment references,

• Reduced manual AP and AR processing,

• Faster dispute resolution,

• Cleaner audit trails.

In other words, the mandate forces discipline, but rewards automation.

What happens next?

The next phase is not about technical stability. That has largely been achieved.

The next phase is behavioral normalization:

• Full Peppol registration penetration.

• Elimination of PDF fallback habits.

• Alignment ahead of 2028 e-reporting obligations.

Belgium’s model is not dramatic. It is quiet. Structured. Distributed.

But make no mistake: For VAT-registered businesses established in Belgium, structured e-invoicing is no longer a project. It is a daily operational reality.

Conclusion

Belgium’s transition to mandatory B2B e-invoicing has proven technically stable, but operational maturity is still evolving. The Peppol infrastructure is functioning as designed; the remaining challenges lie in business readiness, registration completeness, and structured data discipline.

For VAT-registered companies established in Belgium, compliance is no longer optional or theoretical. Structured XML invoicing is now embedded in daily operations. The organizations that move beyond minimum compliance and embrace automation, validation, and integration will not only reduce risk, but also gain measurable efficiency advantages ahead of the 2028 e-reporting expansion.

Belgium’s model may be decentralized and quiet, but its impact on financial processes is structural and permanent.

Stay ahead of the mandates

Stay ahead of global e-invoicing mandates with our free monthly newsletter, delivered straight to your inbox with the latest regulatory updates across 50+ jurisdictions. Follow us on LinkedIn for daily compliance insights and expert analysis.