ZUGFeRD vs Factur-X — What's the Difference?

Side-by-Side Comparison

History: A Joint Franco-German Initiative

ZUGFeRD originated in Germany around 2010 as an initiative by FeRD (Forum elektronische Rechnung Deutschland) to create a hybrid e-invoicing format that would combine human-readable PDFs with machine-readable structured data. ZUGFeRD 1.0 was released in 2014 and gained significant traction in the German-speaking market.

Meanwhile, France was developing its own approach to e-invoicing. Rather than creating a competing standard, the French and German standardisation bodies decided to collaborate. In 2017, FeRD and FNFE-MPE (the French e-invoicing forum) agreed to align their efforts and create a joint standard. The result was a unified technical specification published under two names: ZUGFeRD 2.0 in Germany and Factur-X 1.0 in France.

This joint version was built from scratch on the EN 16931 European standard, which had just been finalised. Both ZUGFeRD 2.x and Factur-X 1.x use the same CII XML schema, the same PDF/A-3 embedding approach, and the same profile system. The Franco-German cooperation is one of the most successful examples of European e-invoicing harmonisation.

Why Two Names for the Same Thing?

The dual naming is purely a matter of market recognition and branding. ZUGFeRD was already an established name in Germany, Austria, and Switzerland. Introducing the name "Factur-X" in France made the standard more accessible to French businesses and institutions, who would naturally prefer a French-sounding name to a German acronym.

There is no technical difference between the two at the core profile levels. When someone in France asks for a "Factur-X EN 16931 invoice" and someone in Germany asks for a "ZUGFeRD EN 16931 invoice," they are asking for the exact same file. The embedded XML filename is even standardised as factur-x.xml in both cases (since ZUGFeRD 2.1).

The only minor divergence is that ZUGFeRD includes an additional XRechnung profile that Factur-X does not have. This profile adds Germany-specific validation rules (such as the mandatory Leitweg-ID) to satisfy German B2G requirements. Since this is a Germany-only concern, it does not exist in the French Factur-X specification.

Profile Levels Explained

Both ZUGFeRD and Factur-X define multiple profiles that control how much structured data is included in the embedded XML. Understanding profiles is essential for choosing the right level of compliance:

• Minimum: Only the most basic metadata — invoice number, date, total amount, and buyer/seller references. The PDF is the authoritative document; the XML is supplementary. Not EN 16931 compliant.
• Basic WL (Without Lines): Header-level data including tax breakdown, payment information, and party details, but no individual line items. Not EN 16931 compliant.
• Basic: Full invoice data with line items in a simplified structure. Provides enough data for automated processing but does not satisfy all EN 16931 requirements.
• EN 16931 (Comfort): The full European standard profile. This is the level where ZUGFeRD and Factur-X are technically identical. It satisfies all EN 16931 requirements and is the minimum for regulatory compliance in most EU mandates.
• Extended: Adds fields beyond EN 16931 for complex business scenarios — additional party roles, detailed delivery information, accounting cost centres, and more.
• XRechnung (ZUGFeRD only): Adds German CIUS rules on top of EN 16931. Required for German government invoicing when using the ZUGFeRD/hybrid format.

For regulatory compliance, always use the EN 16931 profile or higher. The Minimum and Basic profiles are useful for voluntary adoption and transitional scenarios but do not meet EU e-invoicing mandate requirements.

Are They Interchangeable?

Yes, at the EN 16931 profile level. A ZUGFeRD EN 16931 file is byte-for-byte compatible with a Factur-X EN 16931 file. The PDF/A-3 structure is identical, the embedded XML uses the same CII schema, and the XMP metadata follows the same conventions. Any software that can read one can read the other.

At the Extended and XRechnung profiles, there can be minor differences. The Extended profile may include additional fields that are not uniformly supported by all readers. The XRechnung profile exists only in ZUGFeRD and includes German-specific validations that would not apply in a French context. But at the EN 16931 level — which is where regulatory compliance lives — they are completely interchangeable.

In practice, this means you can generate a single EN 16931 hybrid invoice and send it to both German and French trading partners. The German recipient will recognise it as ZUGFeRD; the French recipient will recognise it as Factur-X. No conversion is needed.

When to Use Which Name

While the technology is the same, using the right name in the right context avoids confusion:

• Use "ZUGFeRD" when invoicing German or Austrian businesses and government agencies. German regulations, portals, and documentation refer to the format as ZUGFeRD.
• Use "Factur-X" when invoicing French businesses or dealing with French government platforms. France's upcoming B2B e-invoicing mandate references Factur-X as one of the accepted formats.
• Use either name (or both) when invoicing in Belgium, Luxembourg, or other countries where both names are recognised. Many organisations in these countries are familiar with both terms.
• Use "CII hybrid" or "EN 16931 PDF/A-3" in technically precise contexts where you want to avoid the branding question entirely and focus on the underlying standard.

How InvoicePeppol Helps

InvoicePeppol converts your PDF invoices into EN 16931-compliant format. Our AI extracts all invoice data and generates validated XML that works as both ZUGFeRD and Factur-X. Whether your trading partners are in Germany, France, or elsewhere in Europe, InvoicePeppol produces output that meets their requirements.

Frequently Asked Questions