If you’re preparing for France’s e-invoicing mandate, one of the first technical decisions you’ll face is which structured format to use. The French framework supports three core options — Factur-X, UBL, and CII — and while each can meet the requirements when implemented with the appropriate profile and validation rules, they’re built differently and suit different situations. Understanding the distinction between Factur-X, UBL and CII will help you choose the right electronic invoice format for France rather than defaulting to whichever one your software vendor happens to support.
The Common Ground: EN 16931
Before comparing the three formats, it’s worth understanding what they share. EN 16931 is the European semantic standard that defines the core data of an invoice — invoice number, VAT breakdown, buyer and seller identifiers, line items and totals. The standard defines the content; UBL and CII provide XML syntaxes, while Factur-X packages CII XML with a readable PDF. For France, the applicable profiles and French business rules must also be respected. Choosing a format alone does not establish compliance.
UBL: Pure Structured Data
UBL (Universal Business Language) is a pure XML format — there’s no visual invoice layout in the XML itself, just structured, machine-readable data. A UBL invoice file is built for direct system-to-system exchange, where one ERP or accounting platform transmits data to another without anyone needing to view the raw file.
This makes UBL invoice processing straightforward for fully automated environments: if your systems and your trading partners’ systems both expect structured XML, UBL is a clean, efficient choice. The tradeoff is that a raw UBL file is not a ready-to-read invoice document. Software can render a human-readable view when someone needs to inspect it.
CII: The Cross-Industry Alternative
CII (Cross-Industry Invoice) is UBL’s close cousin — also a pure XML format and another syntax for representing EN 16931 invoice data. CII comes from the UN/CEFACT standard. Its practical suitability often depends on existing ERP capabilities, industry standards and trading-partner requirements.
For most businesses, choosing between UBL and CII comes down less to technical superiority and more to what their ERP system, trading partners or industry already uses. Neither is objectively “better” — both are part of the French core format framework when used with the required profiles and rules.
Factur-X: The Hybrid Approach
Factur-X takes a different approach: it’s a hybrid format that embeds structured UN/CEFACT CII XML inside a human-readable PDF/A-3 file. Open a Factur-X invoice in an ordinary PDF reader and you see the readable invoice. Embedded inside that same file is the structured data a receiving system needs for automated processing.
This dual nature makes Factur-X a practical option for businesses transitioning from traditional PDF invoicing. People can continue visually reviewing invoices, while receiving systems use the embedded XML. The PDF and XML must remain consistent, and the selected profile must meet French requirements. An ordinary PDF without the required structured data is not a Factur-X invoice.
Which One Should You Choose?
The right choice depends on your actual use case, not on picking the “most compliant” option. All three can support compliance when correctly implemented.
Choose Factur-X if:
- Your team or your customers still need to visually review invoices
- You’re transitioning from a PDF-based workflow and want minimal disruption
- You want a single file that works for both human and system readers
Choose UBL if:
- Your invoicing is automated end-to-end and structured XML fits your workflow
- Your trading partners or ERP ecosystem already standardize on UBL
- You’re optimizing for system-to-system exchange
Choose CII if:
- Your industry has already standardized around UN/CEFACT-based exchange
- Your ERP system or existing EDI infrastructure is built around CII
- A trading partner specifically requires it
A Practical Note on Flexibility
Many businesses don’t need to commit to just one format permanently. A well-built compliance platform should be able to generate and validate the required formats and adapt to trading-partner expectations. This flexibility matters for businesses with a diverse customer and supplier base, where some prefer readable Factur-X invoices and others use UBL or CII data. Format conversion must preserve the required invoice information and pass the applicable validation rules.
For a cloud workflow, explore the Docnova e-invoicing portal. If invoices originate in SAP, the Melasoft SAP e-invoicing Add-On provides another implementation route. The choice should start with your ERP, review process and exchange requirements.
Final Thoughts
There’s no universally “correct” format among Factur-X, UBL and CII. The right one depends on who’s on the other end of the transaction and how automated your own processes are. What matters is ensuring that your infrastructure produces correctly validated invoices and exchanges them through a Plateforme Agréée, directly or through a compatible solution.
Discuss your workflow with us: book a Docnova demo or talk to us about SAP e-invoicing integration.