E-Invoicing Standard
What Is Factur-X?
A hybrid electronic invoice format that combines a human-readable PDF with embedded structured XML data. Designed for interoperability between visual document workflows and automated processing systems across the European e-invoicing landscape.
What is Factur-X?
Factur-X is a hybrid electronic invoice format that combines a human-readable PDF/A-3 document with an embedded XML data file conforming to the Cross Industry Invoice (CII) standard. This dual-layer structure allows Factur-X invoices to be read by humans and processed by machines simultaneously, without requiring separate document versions.
How Factur-X Works
A Factur-X invoice is built on the PDF/A-3 container format, an ISO standard for long-term archival that allows files to be embedded as attachments within a PDF document. The visual layer of the invoice is the PDF itself, which can be opened, viewed, and printed using any standard PDF reader. It looks exactly like a traditional invoice.
Embedded inside this PDF is an XML file named "factur-x.xml" that contains the same invoice data in a structured, machine-readable format. This XML conforms to the Cross Industry Invoice (CII) data model, which is one of the two syntaxes recognized under the European e-invoicing standard EN 16931 (the other being UBL).
When a receiving system processes a Factur-X invoice, it extracts the embedded XML attachment from the PDF/A-3 container and parses the CII data. This allows the invoice to be imported into accounting software, matched against purchase orders, validated for tax compliance, and archived with structured metadata, all without manual data entry. If the receiving system does not support automated extraction, the invoice remains a fully functional PDF that can be processed manually.
This dual-layer design is what distinguishes Factur-X from pure XML formats like UBL or Peppol BIS Billing. Rather than requiring the sender and receiver to both support a specific XML schema, Factur-X provides a fallback: the PDF layer ensures the invoice is always readable, while the XML layer enables automation when both parties support it.
Factur-X Profiles
Factur-X defines five profiles, each specifying a different level of detail in the embedded XML. Higher profiles include all fields from lower profiles plus additional data elements.
Minimum
Fields: Invoice number, invoice date, seller name, buyer name, total amount, VAT total, currency code.
When to use: Archival and simple workflows where only basic metadata is needed for identification and matching. Not sufficient for automated processing of line items.
Basic WL (Without Lines)
Fields: All Minimum fields plus payment terms, seller/buyer addresses, tax registration numbers, and document-level allowances and charges.
When to use: Workflows that require header-level financial data and party identification but do not need individual line-item detail. Common in simplified B2B transactions.
Basic
Fields: All Basic WL fields plus line-item details including item descriptions, quantities, unit prices, line-level tax amounts, and product identifiers.
When to use: Most B2B transactions where the receiving system needs to process individual line items for matching against purchase orders or contracts.
EN 16931 (Comfort)
Fields: All Basic fields plus the full set of mandatory and conditional fields defined by the EN 16931 European e-invoicing standard, including buyer/seller references, delivery details, and structured payment instructions.
When to use: Required when compliance with the European e-invoicing standard EN 16931 is necessary. This is the profile mandated for public procurement in the EU and the baseline for most regulatory e-invoicing requirements.
Extended
Fields: All EN 16931 fields plus additional data elements for complex scenarios, including detailed allowance/charge breakdowns, additional party roles, and extended payment terms.
When to use: Complex invoicing scenarios involving multi-party transactions, detailed discount structures, or industry-specific data requirements that go beyond what EN 16931 defines.
Factur-X vs ZUGFeRD
Factur-X and ZUGFeRD are two names for the same Franco-German hybrid e-invoicing standard. France adopted the name Factur-X, while Germany continues to use ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland). From the EN 16931 profile onward, the two are technically identical: the same CII XML schema, the same PDF/A-3 container specification, and the same profile definitions.
The convergence occurred with ZUGFeRD 2.0, when the French FNFE-MPE (Forum National de la Facture Electronique) and the German FeRD (Forum elektronische Rechnung Deutschland) agreed to align their specifications. ZUGFeRD 1.0 was a Germany-specific format with a different XML structure. From version 2.0 onward, a ZUGFeRD invoice at the EN 16931 profile is indistinguishable from a Factur-X invoice at the same profile.
For businesses operating across France and Germany, this means that a single Factur-X/ZUGFeRD invoice at the EN 16931 profile satisfies both French and German requirements. There is no need to generate separate formats for each country.
Factur-X vs UBL
Document Format
Factur-X: Hybrid PDF/A-3 with embedded XML. The invoice is a visual PDF document with structured data attached.
UBL: Pure XML. The invoice is a structured data file with no visual representation included. A separate rendering step is needed to produce a human-readable version.
XML Schema
Factur-X: Uses the Cross Industry Invoice (CII) schema maintained by UN/CEFACT.
UBL: Uses the Universal Business Language (UBL) schema maintained by OASIS.
Fallback Readability
Factur-X: Always readable as a PDF, even by recipients who do not support XML extraction. No special software needed to view the invoice.
UBL: Requires a rendering engine or compatible software to display the invoice in a human-readable form.
Primary Use Cases
Factur-X: B2B invoicing where recipients have mixed capabilities (some automated, some manual). Common in France, Germany, and other CII-adopting markets.
UBL: B2B and B2G invoicing in Peppol-connected markets, public procurement in the EU, and environments where all parties support structured data exchange.
Factur-X vs Peppol BIS Billing
Factur-X and Peppol BIS Billing operate at different layers of the e-invoicing stack. Factur-X is a document format: it defines how an invoice is structured and packaged. Peppol is a network and a set of specifications for transmitting business documents between participants.
Peppol BIS Billing 3.0, the specification for invoices on the Peppol network, uses UBL 2.1 as its document format. It does not support CII XML or the PDF/A-3 hybrid container that Factur-X uses. This means a Factur-X invoice cannot be sent directly over the Peppol network without converting the CII XML to UBL.
Both Factur-X (via CII) and Peppol BIS Billing (via UBL) can express the EN 16931 semantic data model, but they use different syntaxes to do so. A business that needs to support both Factur-X and Peppol must either generate invoices in both formats or use a conversion service that transforms CII to UBL (or vice versa) as part of the transmission workflow.
Where Factur-X Is Required
France
France is rolling out mandatory B2B e-invoicing under the DGFiP. Factur-X is one of three accepted formats (alongside UBL and CII). All VAT-registered businesses will be required to send and receive structured e-invoices through registered Plateformes de Dematerialisation Partenaires (PDPs) or the public invoicing portal (PPF). The phased rollout began with large enterprises and will extend to all businesses.
Germany
Germany has adopted ZUGFeRD (the German name for Factur-X) as a standard e-invoicing format. B2G e-invoicing is already mandatory at the federal level, and the XRechnung (UBL-based) format is the primary requirement for public sector invoicing. ZUGFeRD/Factur-X is widely used in B2B transactions and is gaining adoption as Germany moves toward broader e-invoicing mandates.
European Union
The EU Directive 2014/55/EU requires all public sector entities to accept e-invoices conforming to EN 16931. Factur-X at the EN 16931 (Comfort) profile satisfies this requirement, as it implements the CII syntax recognized by the standard. As individual member states implement their own e-invoicing mandates, Factur-X is positioned as one of the compliant format options.
Cross-Border B2B
For businesses trading between France and Germany, Factur-X provides a single format that satisfies requirements in both countries. Its hybrid nature also makes it practical for trading partners who may not have automated XML processing capabilities, as the PDF layer ensures the invoice is always accessible.
Who Uses Factur-X
SMBs
Small and medium businesses benefit from the hybrid nature of Factur-X. They can send invoices that are automatically processable by large buyers with ERP systems while remaining readable as standard PDFs for smaller recipients. This eliminates the need to maintain separate invoice formats for different customers.
Accounting Firms
Firms managing invoicing for multiple clients use Factur-X to produce invoices that satisfy both the client's need for visual documents and the regulatory requirement for structured data. The embedded XML enables bulk extraction and processing during tax preparation and audit support.
ERP Vendors
Enterprise resource planning providers integrate Factur-X generation and extraction into their invoicing modules. This allows their customers to produce compliant e-invoices directly from the ERP without additional conversion tools or manual steps.
Public Sector Suppliers
Businesses that invoice government entities in France and Germany use Factur-X to meet public procurement e-invoicing mandates. The EN 16931 (Comfort) profile satisfies the requirements of EU Directive 2014/55/EU for structured e-invoices in public procurement.
Common Misconceptions
Myth: Factur-X replaces PDF invoicing
Reality: Factur-X does not replace PDF invoicing. It enhances it. A Factur-X invoice is a fully valid PDF/A-3 document that looks and prints exactly like a standard PDF invoice. The difference is that it also contains an embedded XML file with structured data, allowing automated processing without losing the human-readable format. Businesses that receive Factur-X invoices can open them in any PDF reader.
Myth: Factur-X and ZUGFeRD are different standards
Reality: Factur-X and ZUGFeRD 2.x are the same standard from the EN 16931 profile onward. The Franco-German cooperation that created the specification resulted in two names: France adopted Factur-X, and Germany uses ZUGFeRD. The underlying CII XML structure, the profile definitions, and the PDF/A-3 container specification are identical. A ZUGFeRD 2.x invoice at the EN 16931 profile is a Factur-X invoice, and vice versa.
Myth: Any PDF with XML attached is Factur-X
Reality: A Factur-X invoice must conform to specific technical requirements. The PDF must be PDF/A-3 compliant (not just any PDF). The XML must follow the CII (Cross Industry Invoice) schema, not an arbitrary XML format. The XML must be embedded as an associated file with the correct relationship type. Simply attaching an XML file to a standard PDF does not produce a valid Factur-X document.
Myth: Factur-X works on the Peppol network
Reality: Peppol uses UBL (Universal Business Language) as its document format, not CII. A Factur-X invoice, which contains CII XML, cannot be transmitted directly over Peppol without format conversion. Businesses that need to send invoices via Peppol and also produce Factur-X invoices typically generate both formats or use a service provider that handles the CII-to-UBL conversion.
How AutoFact AI Supports Factur-X
AutoFact AI is designed to support businesses and their advisors in working with Factur-X invoices across extraction, validation, and compliance workflows.
CII XML Extraction from PDF/A-3
Extracts the embedded factur-x.xml file from PDF/A-3 containers and parses the CII data into structured fields for downstream processing, matching, and archival.
Profile Detection and Classification
Automatically identifies which Factur-X profile (Minimum, Basic WL, Basic, EN 16931, or Extended) a given invoice conforms to, enabling profile-aware validation and routing.
EN 16931 Compliance Mapping
Validates extracted CII data against the mandatory and conditional field requirements of EN 16931, flagging missing or non-conformant elements before submission.
Cross-Format Interoperability Support
Supports workflows where Factur-X invoices need to be reconciled with UBL-based documents, providing field-level mapping between CII and UBL data models.
Structured Data Validation
Validates tax calculations, party identifiers, and line-item data within the CII XML against jurisdiction-specific rules, aligning with French and German regulatory requirements.
Regulatory Authority Mapping
Factur-X requirements are shaped by regulatory frameworks across multiple jurisdictions and standards bodies.
Direction generale des Finances publiques (DGFiP)
France
- What they regulate: French e-invoicing mandate and Factur-X format requirements.
- What AutoFact AI maps to: Factur-X generation, profile detection, CII extraction.
- What risk this removes: Non-compliant invoice format, missing structured data.
Bundeszentralamt fur Steuern (BZSt)
Germany
- What they regulate: German e-invoicing regulations and ZUGFeRD adoption.
- What AutoFact AI maps to: ZUGFeRD/Factur-X interoperability.
- What risk this removes: Format incompatibility between French and German counterparts.
European Committee for Standardization (CEN)
European Union
- What they regulate: EN 16931 European e-invoicing standard.
- What AutoFact AI maps to: EN 16931 profile compliance mapping.
- What risk this removes: Non-conformance with European semantic data model.
Peppol (OpenPeppol AISBL)
International Network
- What they regulate: Peppol network document format requirements.
- What AutoFact AI maps to: Format conversion guidance (CII to UBL).
- What risk this removes: Inability to transmit via Peppol without format alignment.
AutoFact AI is not certified by, affiliated with, or endorsed by any regulatory authority listed above. References describe technical alignment with published regulatory requirements only.
Frequently Asked Questions
Factur-X & EU E-Invoicing Resources
Extract, Validate, and Process Factur-X Invoices
AutoFact AI extracts CII data from Factur-X containers, detects profiles, validates against EN 16931, and flags compliance gaps before submission. Start your free trial and bring structured intelligence to your hybrid invoice workflows.
14-day free trial · No credit card required · Setup in minutes