Factur-X vs UBL vs CII: Which France E-Invoicing Format Should ERP Teams Test?
Published August 2026 by Solarc Labs
France defines a structured and hybrid format foundation
The current French external specifications define the core invoice formats around UBL, UN/CEFACT CII and the hybrid Factur-X format. UBL and CII are structured XML syntaxes. Factur-X combines a human-readable PDF/A-3 representation with structured invoice data embedded in the file. For an ERP team, that means format readiness is not just whether a file extension can be generated. The produced document has to match the syntax, profile and business data rules expected by the target flow.
UBL is a structured XML route, not a visual invoice
UBL represents invoice information as structured data. That makes it suitable for machine-to-machine exchange, but it also means field population, code lists, identifiers, tax breakdowns and totals need to be produced consistently by the source mapping. A valid-looking PDF generated elsewhere does not prove that the UBL payload is correct. Test the actual UBL generated by each production source path, including edge cases that are normally rare in a sales demo.
CII carries the same business job through a different syntax
UN/CEFACT Cross Industry Invoice is another structured syntax used in the French specification. ERP and middleware teams should not assume that support for one syntax means a separate mapping into the other is automatically correct. Conversion and mapping layers can introduce their own defects even when both sides are intended to represent the same business invoice concepts. Representative corpus testing is therefore useful at the actual output boundary, not only at the upstream data model.
Factur-X adds a readable PDF and embedded structured data
Factur-X is a hybrid invoice format: the PDF is the readable representation and the structured invoice data is carried within the PDF/A-3 container. That creates more than one failure surface. The PDF container, embedded XML, profile and business-rule content all need to agree sufficiently for the intended downstream workflow. A team that tests only whether the PDF opens can miss defects in the structured payload that the automated e-invoicing path will use.
The correct test question is which formats your real source systems produce
Do not manufacture one example of every format purely to say all three were tested. Start with the formats and profiles actually produced by the ERP, billing systems and conversion layers in scope. Then choose representative invoices across those paths and record recurring structural or business-rule failures. InvoiceBatch FR uses UBL, CII and Factur-X corpus preflight as an upstream evidence job. It is not a Plateforme Agréée and does not replace the production transmission or recipient-acceptance layer.
Primary sources
Sources used for this article
Continue the job