Germany and Belgium share a border, significant trade routes, and EU membership — but they've taken opposite approaches to e-invoicing mandates. Understanding the differences matters, especially if your business operates in both markets or trades cross-border between them.
Two Philosophies
The core difference is philosophical. Germany prioritised format flexibility — allowing businesses to choose between multiple EN 16931 formats and delivery methods. Belgium prioritised network simplicity — mandating a single format on a single network.
Format Approach (Germany)
“We define the data standard (EN 16931). You choose how to implement it — XRechnung, ZUGFeRD, or any compliant format. Delivery method is your choice too.”
Network Approach (Belgium)
“We define the format (Peppol BIS 3.0) and the delivery network (Peppol). One format, one network, one set of rules. No alternatives.”
Germany: Format Approach
Germany's approach under the Wachstumschancengesetz focuses on the data standard, not the delivery mechanism. Any format that conforms to EN 16931 is accepted, and delivery can happen via email, EDI, portals, or Peppol:
Multiple Formats Accepted
XRechnung (pure XML, ~27% market share) and ZUGFeRD 2.x (hybrid PDF+XML, ~73% market share) are the two dominant formats. Any EN 16931-compliant format is technically valid.
Multiple Delivery Methods
No single delivery network is mandated for B2B. Invoices can be sent via email, uploaded to portals, exchanged through EDI, or routed via Peppol. Only federal B2G mandates XRechnung via the ZRE portal.
KoSIT Validation
KoSIT maintains the validation ruleset, but validation is the sender’s responsibility. There’s no network-level validation gate — an invalid invoice can reach the recipient.
Scale: 3.6 Million Businesses
Germany’s size makes a single-network mandate harder. With 3.6 million VAT-registered businesses, the flexibility approach was partly pragmatic — forcing all businesses onto one network in a short timeframe would be logistically challenging.
Belgium: Network Approach
Belgium chose to mandate both the format and the delivery network. There is exactly one compliant path:
Single Format: Peppol BIS 3.0
Only Peppol BIS Billing 3.0 (UBL 2.1) is accepted for mandate compliance. No ZUGFeRD, no alternative XML formats, no PDF fallback.
Single Network: Peppol eDelivery
Invoices must be delivered via the Peppol network through certified Access Points. Direct email exchange, portal uploads, and EDI do not satisfy the mandate.
Network-Level Validation
Access Points validate invoices before accepting them. Invalid invoices are rejected at the network edge — they never reach the recipient. This ensures consistently high data quality.
Result: 99.2% Compliance in 90 Days
Belgium’s single-path approach achieved the highest first-quarter compliance rate of any EU e-invoicing mandate. With no format ambiguity or delivery choice, businesses had a clear, singular integration target.
Head-to-Head Comparison
| Dimension | Germany | Belgium |
|---|---|---|
| Philosophy | Format flexibility | Network simplicity |
| Accepted formats | XRechnung, ZUGFeRD, any EN 16931 | Peppol BIS 3.0 only |
| Delivery network | Any method (email, EDI, Peppol) | Peppol only |
| Validation | Sender’s responsibility | Network-level (Access Point) |
| Mandate timeline | Receive: Jan 2025, Send: Jan 2028 | Full B2B: Jan 2026 |
| Affected businesses | ~3.6 million | ~1 million |
| B2G standard | XRechnung (mandatory) | Peppol BIS 3.0 |
| Cross-border | Via Peppol (partial) | Native Peppol (built-in) |
| E-ordering planned | Not announced | 2027 target |
| ViDA readiness | Requires network layer | Infrastructure ready |
| First-quarter compliance | 92% receiving-capable | 99.2% full compliance |
ViDA Convergence
The EU's VAT in the Digital Age (ViDA) directive is pushing both models toward convergence. ViDA's Digital Reporting Requirements (DRR) will require EN 16931 structured invoices exchanged over Peppol for intra-community B2B transactions by 2030.
Germany’s Gap: Network Layer
Germany’s format-first approach means it already has EN 16931 compliance. But ViDA requires a network layer for cross-border transactions. Germany will need to build or mandate Peppol connectivity where it’s currently optional.
Belgium’s Head Start
Belgium’s Peppol-first approach means its ViDA readiness is essentially built-in. The same Peppol infrastructure that handles domestic B2B will handle intra-EU transactions when ViDA takes effect.
Convergence Point
By 2030, both countries will effectively be using EN 16931 formats on the Peppol network — at least for cross-border transactions. The question is whether Germany will extend its Peppol mandate to domestic B2B as well.
Which Is Better?
The honest answer: it depends on your perspective. Neither model is objectively superior — they reflect different priorities and different market realities:
Germany's Format Approach Is Better If...
- You’re a large enterprise with existing EDI infrastructure
- You need ZUGFeRD’s hybrid format for mixed-readiness trading partners
- Your suppliers/customers aren’t on Peppol yet
- You value gradual transition over immediate full compliance
Belgium's Network Approach Is Better If...
- You’re an SME looking for the simplest compliance path
- You want cross-border invoicing to work out of the box
- You value network-level validation and data quality guarantees
- You want a platform that will extend from invoicing to ordering
If your business operates in both markets, the practical answer is: support both. Use XRechnung/ZUGFeRD for German domestic, Peppol BIS 3.0 for Belgian domestic, and Peppol for cross-border. A good e-invoicing platform handles all three from a single integration.
One Platform, Both Markets
InvoStaq supports XRechnung, ZUGFeRD, and Peppol BIS 3.0 from a single integration. Compliant in Germany and Belgium — and ready for ViDA.