CII Format: The XML Standard for E-Invoicing

Definition: The CII (Cross Industry Invoice) format is a 100% XML-structured e-invoice standard, developed by UN/CEFACT (United Nations) and compliant with the European standard EN 16931. It is one of the three formats officially accepted under the French e-invoicing reform, alongside Factur-X and UBL.

• CII includes no visual document: it is designed to be automatically interpreted and processed by information systems, not to be read by humans.
• It is the most prescriptive of the three: favored by large corporate groups, international environments, and highly industrialized Procure-to-Pay chains.
• As with the other formats, a CII invoice must go through an Approved Platform registered by the DGFiP to be compliant.

In this guide: what the CII format really is, who it is for, when it is the best choice compared with Factur-X and UBL — and when you are better off avoiding it. To see where CII fits among the authorized formats, also check out our dedicated page on e-invoice formats accepted in France.

What Is the CII Format?

The CII format, short for Cross Industry Invoice, is a fully structured e-invoice standard based exclusively on XML data. Unlike hybrid formats, CII does not include any visual document intended for human reading: it is designed from the ground up to be automatically interpreted and processed by information systems.

The CII format was developed at the European level as part of the work carried out by UN/CEFACT (United Nations Centre for Trade Facilitation and Electronic Business), an international body responsible for defining common standards for electronic business exchanges. Its goal is clear: to enable interoperable, reliable, and standardized invoice exchanges, regardless of the industry or country involved.

In the context of e-invoicing, a CII invoice is therefore a structured XML file that describes all invoicing information in a precise, standardized way. In particular, it contains:

• full identification of the issuer and the recipient (entities, identifiers, addresses),

• invoice references (number, issue date, currency),

• a line-by-line breakdown of the products or services invoiced,

• amounts excluding tax, VAT, and totals,

• the VAT rules applied,

• payment terms and conditions,

• order or contract references, where applicable.

All of this information is encapsulated in standardized XML tags, which ensures uniform interpretation by software, with no ambiguity or manual re-entry.

The CII format complies with the European standard EN 16931, which defines the common core of mandatory data for electronic invoices within the European Union. This compliance ensures that CII invoices meet both French regulatory requirements and European standards, particularly for cross-border exchanges.

In practice, CII is mainly intended for environments that are already highly digitized, where data exchanges are automated and direct human readability of the invoice is not a prerequisite. It is particularly well suited to organizations whose systems can generate, receive, and process complex XML flows, with a view to industrializing invoicing processes.

• 100% structured XML format, with no visual component

• European standard stemming from the work of UN/CEFACT

• Compliant with the EN 16931 standard

• No native PDF; human reading possible only through tools

• Designed for complex, interoperable information systems

Why CII Is a Prescriptive XML Format (and What That Means)

The CII format stands out for its highly prescriptive nature. Whereas some formats primarily aim to ease adoption or transition, CII prioritizes strict compliance with international standards and precise data exchange. This orientation has direct consequences for how it is used and for the contexts in which it is truly relevant.

Less pragmatic than a hybrid format such as Factur-X, CII makes no concessions to human readability. It contains no PDF and does not try to accommodate “paper-based” or partially digitized practices. Conversely, it is more prescriptive than UBL in some respects, because it is part of a broader conceptual framework designed for tightly regulated cross-industry and international exchanges.

CII’s structure is rigid and highly standardized. Every piece of invoice information must be placed in a specific tag, according to a strict data model. This rigor guarantees uniform interpretation by information systems but leaves little room for approximation or local adaptation. A missing, poorly structured, or inconsistent data element can lead to the outright rejection of the invoice.

This low tolerance for deviations is both a strength and a constraint. On the plus side, the CII format offers a very high level of reliability, maximum data accuracy, and excellent interoperability between systems, including in multi-country or multi-ERP contexts. It greatly limits ambiguity and misinterpretation, which is crucial in complex environments.

On the downside, CII creates a heavy dependence on tools capable of correctly generating, checking, and interpreting XML. It requires well-structured master data, rigorous configuration, and a high level of digital maturity. Without this technical ecosystem, the format quickly becomes difficult to work with day to day.

In short, CII is not a “flexible” or “beginner-friendly” format. It is a demanding standard, designed for organizations that prioritize compliance, robustness, and large-scale interoperability, at the cost of greater operational complexity.

CII in French E-Invoicing: Role and Use Cases

Within the French e-invoicing framework, the CII (Cross Industry Invoice) format is one of the three formats officially accepted by the French tax administration, alongside Factur-X and UBL.

In concrete terms, CII fits into the new invoice flow model, which relies on Approved Platforms (PA) and the Public Invoicing Portal (PPF). The invoice is issued in CII through an Approved Platform and transmitted to the recipient’s receiving platform; the required invoicing data is then relayed to the tax administration via the PPF, notably for tax verification and to pre-fill VAT returns.

Within this system, CII serves above all as a reliable, standardized data format, perfectly suited to the automated transmission of tax information. Its rigorous XML structure makes it easier for the tax administration’s systems to extract, check, and use VAT data, while ensuring a high degree of consistency across the various platforms involved.

In practice, the CII format is less widespread than Factur-X in the French market. It is rarely chosen as the default format, especially by SMBs and mid-market companies, because it provides no human-readable version for the end user and requires a more advanced technical environment.

CII is mainly used in highly structured environments, where exchanges are already standardized and largely automated: large organizations, international groups, industrial ecosystems, or multi-ERP contexts. In these specific cases, its rigor and alignment with international standards are a real advantage.

In French e-invoicing, then, CII is not a marginal format but a specialized one, intended for well-defined use cases where precision and interoperability take precedence over ease of adoption.

CII vs. UBL vs. Factur-X: When CII Is the Right Choice

Under the French e-invoicing framework, CII, UBL, and Factur-X are all legally compliant. The choice between these formats is therefore not a regulatory matter but a question of how well the format fits your organization. CII stands out for its highly prescriptive, international positioning, which makes it relevant in specific contexts.

Format Comparison by Key Criteria

Human readability
Factur-X is the only format that natively embeds a human-readable PDF. UBL and CII are pure XML formats that require a tool to generate a visual rendering. On this point, CII is the furthest removed from traditional “document-based” practices.

Technical complexity
CII is the most demanding format. Its highly standardized structure calls for precise data configuration and strict compliance with XML schemas, and it tolerates very few deviations. UBL is also structured but is often seen as more pragmatic. Factur-X remains the most technically accessible.

Volume and automation
CII is particularly well suited to high volumes and industrial-scale flows. It enables maximum automation of invoice processing, with a high level of reliability. The higher the volume, the greater the benefit of CII.

International scope
CII is strongly geared toward international interoperability. Stemming from UN/CEFACT’s work, it is designed to operate in multi-country, multi-standard, and multi-ERP environments. On this criterion, it is often more relevant than Factur-X.

Procure-to-Pay and complex information systems
In highly structured Procure-to-Pay chains with multiple interconnected systems, CII integrates naturally. Its rigidity then becomes an advantage, because it ensures a high level of data consistency across the entire chain.

When Should You Choose the CII Format?

The CII format is especially relevant if:

• you operate in an international environment or across multiple subsidiaries,

• your information systems are complex and already highly integrated,

• you have strict standardization requirements for data quality and traceability,

• your flows are mostly machine-to-machine, with no need for a human-readable document.

When Should You Avoid the CII Format?

CII is generally not recommended if:

• you are an SMB with limited digital tools or still undergoing a digital transition,

• your teams need a human-readable PDF for day-to-day checks,

• your priority is a quick rollout and step-by-step implementation of the regulatory framework,

• your suppliers’ technical capabilities vary widely.

Choosing the Right Format

• Factur-X: easier transition, human readability, broad adoption

• UBL: high automation, pragmatic XML approach

• CII: strict standard, international interoperability, complex environments

The best format is not the most technical one, but the one that aligns with your processes, your tools, and your maturity.

How to Issue an Invoice in CII Format

Issuing an invoice in CII (Cross Industry Invoice) format requires a technical environment capable of producing and managing XML data that strictly complies with European standards. Unlike Factur-X, it is not a transitional format but one designed for fully automated exchanges.

Relying on a Compatible ERP or Middleware

In practice, a CII invoice is generated by:

• an ERP with an advanced e-invoicing module,

• or specialized middleware capable of converting invoicing data into compliant CII XML.

Generating a CII file manually is unrealistic at an operational scale. Proper tooling is therefore an essential prerequisite.

Generating Standard-Compliant XML

The CII file must strictly comply with:

• the European standard EN 16931,

• the XML structure defined by UN/CEFACT,

• the consistency rules linking amounts, lines, and VAT.

Every required field must be filled in correctly. CII leaves very little room for approximation: a missing or poorly structured data element can lead to rejection.

Rigorously Configuring Upstream Data

To issue reliable CII invoices, a company needs:

• complete customer and supplier master data,

• correctly coded VAT rules,

• standardized items or services,

• tightly controlled invoicing processes.

The quality of upstream data directly determines whether invoices are issued successfully.

The Issuing Process, Step by Step

1. Creation
   The invoice is generated in the ERP or source system from transactional data.

2. Validation
   Automated checks verify that the CII file is compliant (structure, amounts, tax rules).

3. Transmission
   The invoice is sent through an Approved Platform, which handles:

   • regulatory compliance,

   • transmission to the customer’s receiving platform,

   • reporting of tax data to the tax administration via the PPF.

Once this process is in place, issuing invoices in CII becomes smooth, reliable, and highly automated, but it requires a high level of maturity from the outset.

How to Receive and Process a CII Invoice

Receiving and processing an invoice in CII format means handling a fully structured data flow, with no human-readable document by default. Unlike Factur-X, CII relies exclusively on a strictly standardized XML file, intended to be interpreted by information systems rather than by users.

Receipt via an Approved Platform

Under mandatory e-invoicing, a CII invoice never travels by email. It is received through an Approved Platform designated as the company’s official point of receipt.

This platform handles:

• secure receipt of the CII XML file,

• format compliance checks,

• transmission of tax data to the tax administration via the Public Invoicing Portal,

• routing to the company’s internal receiving system.

The invoice thus enters a traceable, regulated workflow from the moment it is received.

Reading and Processing via the Information System

A CII invoice cannot be read by a human without a tool. It must be processed by:

• an ERP,

• accounting software,

• or a Procure-to-Pay platform capable of interpreting CII XML.

The system reads the structured data directly: amounts, lines, VAT, order references, payment terms. The XML becomes the source of truth, with no manual re-entry or interpretation.

Visual Rendering Generated by the Tool

To support internal checks, tools usually generate a visual rendering from the CII XML.
This rendering:

• lets teams view the invoice,

• makes accounting approvals easier,

• serves as a reference for checks, with no standalone documentary value.

It is not a PDF sent by the supplier, but a representation built from the data.

Natural Integration into Procure-to-Pay

CII comes into its own when it is part of a structured Procure-to-Pay process.
Thanks to the quality of the data:

• purchase order/invoice matching is automated,

• discrepancies are detected immediately,

• approvals move faster,

• payments are safeguarded.

In this context, the invoice is no longer a document to be processed but a data event that fits naturally into the procurement–finance chain.

It is precisely this approach that makes CII a powerful format for well-equipped, highly automated organizations.

CII in Advanced Procure-to-Pay

The CII format reaches its full potential when integrated into an advanced Procure-to-Pay (P2P) process, where the invoice is no longer a document to be processed but a data flow that drives the entire spend cycle. In this context, CII is not merely a compliant format: it is a tool for industrializing financial processes.

CII as the Foundation for Managing Commitments

In a mature P2P process, spend management does not begin with the invoice but at the point of commitment: purchase requisition, purchase order, contract.
The CII format makes it possible to link the final invoice to these commitments with great precision, thanks to:

• standardized purchase order references,

• strictly structured line items,

• strong consistency between purchasing data and invoicing data.

The result: the invoice becomes an automatic confirmation of a commitment that has already been approved, rather than the starting point for controls. The finance department gains visibility, foresight, and a greater ability to make trade-off decisions.

Maximum Automation of Invoice Processing

Thanks to its rigid XML structure, CII enables a high degree of automation:

• accounting integration without re-keying,

• automatic three-way matching of purchase order, goods receipt, and invoice,

• systematic consistency checks,

• seamless triggering of approval or payment workflows.

In a properly configured environment, a CII invoice can be processed without human intervention, barring exceptions. Processing becomes predictable, fast, and scalable.

A Lasting Reduction in Disputes and Anomalies

The strict standardization of the CII format significantly reduces sources of disputes:

• fewer VAT errors,

• fewer line-level discrepancies,

• less ambiguity about amounts or references.

Anomalies are detected upstream, at the data level, rather than after the fact when a document is read. Control becomes systemic rather than corrective.

Who Is This Model Really For?

Integrating CII into an advanced P2P process is mainly suited to:

• large corporate groups or multi-entity organizations,

• well-equipped mid-market companies with robust ERP systems,

• companies processing large volumes of invoices,

• organizations seeking strong, lasting standardization.

For these organizations, CII is not a restrictive format but a financial performance accelerator that makes flows more reliable, reduces processing costs, and strengthens overall spend management.

In an advanced Procure-to-Pay process, CII is therefore not an isolated technical choice. It is a maturity-driven choice, aligned with an industrialized, data-driven vision of the finance function.

CII, Compliance, and Risks

The CII (Cross Industry Invoice) format fits squarely within the regulatory framework for mandatory e-invoicing in France. It is one of the formats officially accepted by the tax administration, alongside Factur-X and UBL, and meets the requirements of the European standard EN 16931. As such, an invoice issued in CII format is legally compliant, provided that it goes through an Approved Platform and that the data transmitted is complete and consistent.

A High Level of Compliance… Under Certain Conditions

CII offers an excellent level of regulatory compliance thanks to its strict XML structure. Every piece of invoicing data (identifiers, amounts, VAT, references) is standardized, which facilitates:

• automated checks,

• the transmission of tax data,

• the traceability required by the tax administration.

However, this rigor means a low tolerance for errors. A poorly structured data element, an incorrect VAT rule, or badly configured master data can lead to the invoice being rejected by the platform or by the receiving system.

Key Risks to Anticipate

The risks associated with CII are not legal but operational:

• technical rejections of invoices that do not comply with the CII schema,

• payment holds caused by data errors,

• heavy dependence on the quality of tools and configuration,

• difficulty making corrections after the fact without resubmitting the flow.

Unlike a hybrid format, CII does not let you “salvage” an invoice with a human-readable document: the XML is the authoritative record.

Planning Ahead to Safeguard Your Invoicing

Using CII reliably therefore requires:

• well-managed information systems,

• thorough testing before go-live,

• clear governance of invoicing data.

When properly deployed, CII reduces the risk of non-compliance. If poorly prepared, however, it can become a source of rigidity and bottlenecks.

The CII (Cross Industry Invoice) format is primarily intended for organizations seeking a high level of standardization, reliability, and automation in their invoicing exchanges. Fully structured, prescriptive, and compliant with the European standard EN 16931, it perfectly meets the requirements of the 2026–2027 e-invoicing reform, but in return it demands a high level of information system maturity.

CII is neither a transitional format nor a universal one. It is designed for complex, international, or highly industrialized environments, where human readability is secondary to data accuracy and interoperability between systems. When properly integrated into an advanced Procure-to-Pay process, it becomes a powerful lever for reducing disputes, securing commitments, and managing financial performance.

The right choice, then, is not the most prescriptive format but the one that truly aligns with your processes, your tools, and your ability to leverage data. For some organizations, CII is the obvious standard. For others, it should remain a later step on the path to compliance.

Information verified on September 1, 2026. Sources: UN/CEFACT, European standard EN 16931, economie.gouv.fr.