The push for structured e-invoicing across Europe is accelerating fast — but not every country is moving in the same direction. While Belgium, the Netherlands, and most of Northern Europe have embraced Peppol UBL as their primary standard, France and Germany are rolling out hybrid formats like Factur-X and ZUGFeRD that embed structured XML inside a PDF envelope. For SMBs trading across borders, this creates a real compliance headache. Understanding Factur-X Peppol interoperability is no longer optional — it is the key to staying compliant, efficient, and future-ready under the upcoming ViDa 2030 framework.
- Factur-X and ZUGFeRD are hybrid e-invoicing formats (PDF + embedded XML) used in France and Germany — they comply with EN 16931 but are structurally different from Peppol UBL.
- Peppol BIS 3.0 is the dominant cross-border e-invoicing standard across the EU, used natively in Belgium, the Netherlands, and over 30 countries worldwide.
- The EU’s ViDa 2030 mandate will require interoperable, structured e-invoicing for all intra-EU transactions, making format bridging between Factur-X and Peppol essential.
- A Peppol API can automatically translate and route hybrid format invoices into Peppol-compatible UBL, allowing SMBs to maintain a single system for multi-country compliance.
The Great Divide: Peppol UBL vs. French and German Hybrid Formats
Peppol has become the de facto standard for structured e-invoicing in much of Europe. It operates through a four-corner model — sender, sender’s access point, receiver’s access point, receiver — and uses UBL (Universal Business Language) or CII (Cross Industry Invoice) XML as its document format. It is clean, machine-readable, and built for automated processing.
France and Germany took a different path. Rather than adopting pure XML, both countries standardised on hybrid formats: Factur-X (the French implementation) and ZUGFeRD (the German equivalent, now aligned to ZUGFeRD 2.x). Both embed a CII-compliant XML payload inside a PDF/A-3 file. The human-readable PDF satisfies traditional invoice requirements; the embedded XML enables automated processing. Both formats comply with the European standard EN 16931, which defines the semantic data model for e-invoices across the EU.
The problem? While both approaches are EN 16931-compliant in theory, a Peppol access point cannot natively receive or send a Factur-X PDF. The delivery mechanism, the document wrapper, and the technical validation rules are all different. For a Belgian or Dutch SMB that sells to French or German clients — or vice versa — this gap can block invoicing workflows entirely. You can read more about the foundational differences in our guide on e-invoicing acronyms and what they mean in practice.
Why Factur-X and ZUGFeRD Matter for Your 2026 EU Strategy
France is rolling out its mandatory e-invoicing reform in phases. Large enterprises already face obligations, with mid-sized and smaller businesses following in 2026 and 2027. If you supply French customers, they will increasingly expect invoices in a format their plateforme immatriculée (accredited platform) can process — and that often means Factur-X. Our detailed guide on French e-invoicing deadlines for SMBs maps out the exact timeline.
Germany’s situation is equally significant. From January 2025, German businesses are already required to be able to receive structured e-invoices (ZUGFeRD or XRechnung). The mandate to send structured invoices for B2B transactions is expanding rapidly through 2027 and 2028. If you sell into Germany and send a plain PDF, your invoice may simply not be accepted.
Ignoring these formats means risking late payments, rejected invoices, and ultimately non-compliance penalties — all of which hit cash flow directly. We covered how Peppol validation errors damage cash flow in 2026, and the same logic applies when hybrid format invoices are rejected at the border.
ViDa 2030 Mandate: Harmonizing Cross-Border Data Requirements
The EU’s VAT in the Digital Age (ViDa) package is the most significant VAT reform in decades. It introduces mandatory real-time digital reporting for all intra-EU B2B transactions, with full implementation targeted for 2030. Under ViDa, every cross-border invoice must be transmitted as a structured electronic document and reported to tax authorities in near real-time.
Crucially, ViDa does not prescribe a single format — it sets interoperability requirements. Invoices must comply with EN 16931, contain specific VAT data fields, and be transmissible through approved digital channels. This means that whether you use Peppol UBL or Factur-X, the invoice data must be mappable, comparable, and reportable in a standardised way. Our deeper analysis of why e-invoicing alone is not enough for ViDa’s Digital Reporting Requirements explains what else your systems need to handle.
For SMBs, the practical implication is clear: you cannot afford to operate in a format silo. If your ERP generates Peppol UBL for Belgian clients but has no strategy for French or German trading partners, you are already behind. The ViDa 2030 ERP data mapping guide on our blog walks through the EN 16931 field alignment your systems need to get right now.
Technical Hurdles: Mapping Hybrid XML Data to Peppol BIS 3.0 Standards
Both Factur-X and Peppol BIS 3.0 claim EN 16931 compliance — so in theory, the data is compatible. In practice, the technical mapping involves several non-trivial challenges.
Document format extraction
A Factur-X invoice arrives as a PDF/A-3 file. The embedded XML (in CII syntax — UN/CEFACT Cross Industry Invoice) must first be extracted and parsed. Peppol BIS 3.0 uses UBL 2.1 syntax by default, which means a CII-to-UBL transformation is required. While both syntaxes can represent the same EN 16931 semantic model, the element names, namespace structures, and cardinalities differ significantly.
Profile and conformance level differences
Factur-X supports multiple conformance levels (MINIMUM, BASIC WL, BASIC, EN 16931, EXTENDED). Not all levels carry the full data set required by Peppol BIS 3.0. A MINIMUM-level Factur-X invoice lacks line-level detail that Peppol validation rules will flag as missing. Your integration layer needs to detect the conformance level and apply the correct enrichment logic.
Identifier and routing differences
Peppol relies on Peppol Participant IDs (registered in the SMP/SML infrastructure) for routing. Factur-X invoices have no concept of a Peppol ID — they carry SIRET numbers or VAT identifiers. Mapping these to valid Peppol participant identifiers requires a lookup layer, often via the Peppol directory. Our guide on checking whether your customer is registered on Peppol explains how this lookup works in practice.
How a Peppol API Simplifies Multi-Format Compliance for SMBs
Managing these transformations manually is not realistic for most SMBs. The answer is a Peppol API that handles format detection, XML extraction, CII-to-UBL conversion, participant lookup, and Peppol network delivery — all in a single automated pipeline.
At Kleinkode, our Peppol API integration service is built precisely for this use case. Instead of maintaining separate workflows for French clients (Factur-X via a plateforme agréée), German clients (ZUGFeRD or XRechnung), and Benelux clients (Peppol UBL), you connect your ERP once via API. The integration layer handles format translation and routing automatically based on the recipient’s country and registration status.
This approach gives you three concrete advantages. First, single-system operation: your ERP generates one invoice record; the API handles all output format variants. Second, real-time validation: the API validates against both the source format’s rules and the Peppol BIS 3.0 schematron before transmission, catching errors before they cause rejected invoices. Third, audit-ready data retention: every transformation is logged and the original hybrid PDF is preserved alongside the transmitted UBL, satisfying archiving requirements in both the origin and destination country.
If you are comparing whether to build this capability in-house or rely on a specialist, our analysis of outsourcing Peppol integration versus building it yourself gives a clear cost-benefit breakdown. For ERP-specific implementation, our Peppol ERP, accounting, and webshop connection service covers the full integration landscape.
Preparing Your ERP for the 2027 German E-Invoicing Wave
Germany’s e-invoicing rollout is the next major compliance wave after France. From 2027, virtually all German B2B suppliers will be required to send structured invoices. The preferred formats are XRechnung (pure XML, mandatory for public sector) and ZUGFeRD 2.x (hybrid, widely accepted for private sector B2B). Both are EN 16931-compliant and both present the same Peppol interoperability challenge as Factur-X.
The good news: the technical mapping between ZUGFeRD and Peppol BIS 3.0 follows the same CII-to-UBL logic as Factur-X. If your API integration already handles Factur-X, extending it to ZUGFeRD is a relatively minor configuration change. The key is not to wait until 2027 to start. ERP data field alignment, participant ID lookup infrastructure, and format testing all take time. Our PINT migration guide for international e-invoicing also covers how the Peppol International model (used beyond the EU) factors into your long-term architecture.
For businesses already on Microsoft Dynamics 365 or SAP, the integration path is well-defined but requires specialist configuration. Starting the technical conversation now — rather than in Q4 2026 — is the difference between a smooth rollout and a costly emergency project.
Frequently Asked Questions
Is Factur-X the same as Peppol BIS 3.0?
No. Both comply with the EN 16931 semantic standard, but they differ fundamentally in format and delivery. Factur-X is a hybrid PDF/A-3 file with embedded CII XML, sent via email or a French accredited platform. Peppol BIS 3.0 is a pure UBL 2.1 XML document delivered through the Peppol four-corner network via registered access points. Automatic transformation between the two is technically possible but requires a dedicated API integration layer.
Can I send a Factur-X invoice through Peppol?
Not directly. To transmit a Factur-X invoice via Peppol, the embedded CII XML must be extracted and transformed into Peppol BIS 3.0 UBL format. The recipient must also have a registered Peppol Participant ID. A Peppol API integration service handles this automatically — the sender simply submits the Factur-X file and the API manages extraction, conversion, and delivery.
What does ViDa 2030 require for cross-border invoices?
Under the ViDa (VAT in the Digital Age) framework, all intra-EU B2B transactions must be reported digitally and in near real-time from 2030. Invoices must comply with EN 16931 and be transmitted through approved digital channels. ViDa does not mandate a single format, but requires interoperability — meaning your system must be able to produce and receive structured data regardless of whether the counterparty uses Peppol UBL, Factur-X, or another EN 16931-compliant format.
What is the difference between ZUGFeRD and Factur-X?
ZUGFeRD (Germany) and Factur-X (France) are technically near-identical hybrid formats — both embed CII XML inside a PDF/A-3 file and both comply with EN 16931. Factur-X is formally the French national profile; ZUGFeRD 2.x is the German implementation. They share the same underlying specification (ZUGFeRD 2.1 = Factur-X 1.0 at the EN 16931 level), which means a single CII-to-UBL mapping engine can handle both for Peppol transmission.
Do SMBs need separate systems for Peppol and Factur-X compliance?
No — not if you use a properly integrated Peppol API. A single API connection between your ERP and a Peppol access point can handle format detection, conversion, and routing for multiple countries. This eliminates the need to maintain parallel systems for French, German, and Benelux trading partners, and positions your business for ViDa 2030 compliance from a single integration point.
When does Germany’s B2B e-invoicing obligation to send structured invoices apply?
Germany requires all businesses to be able to receive structured e-invoices (ZUGFeRD or XRechnung) from January 2025. The obligation to send structured invoices applies to large enterprises from 2027 and to all remaining B2B suppliers from 2028. Businesses selling into Germany should prepare their ERP and API integrations well before the 2027 wave.
Cross-border e-invoicing compliance is not a future problem — it is a 2026 challenge that is already affecting invoice acceptance rates and payment cycles across the EU. Whether you are navigating French Factur-X mandates, preparing for the German ZUGFeRD wave, or aligning your systems with ViDa 2030 requirements, the smartest move is to audit your current setup now. Find out exactly where your gaps are with a free, structured assessment: Plan je gratis Peppol risico-scan.