Businesses entering Europe’s e-invoicing ecosystem quickly realise one thing. Creating an invoice PDF is easy. Creating a structured invoice that tax systems, ERPs and Peppol networks can actually read is where complexity starts. That is where Cross Industry Invoice (CII) comes in. It is one of the core structured invoice formats used across Europe, especially within EN 16931 compliant e-invoicing frameworks like Factur-X and several public procurement models.

Key Takeaways

• Cross Industry Invoice (CII) is a structured XML invoice standard developed under United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT). It is widely used for EN 16931 compliant e-invoicing across Europe
• Most EN 16931 implementations today use CII D16B, while newer releases such as D22B exist for specific use cases and future developments.
• Factur-X invoices in France are built using CII XML structure
• CII helps systems exchange invoice data automatically without manual intervention
• Businesses often compare cross industry invoice vs UBL invoice vs Factur-X invoice while implementing European e-invoicing

What is Cross Industry Invoice (CII)?

Cross Industry Invoice, commonly called CII, is a structured electronic invoice format based on XML. It was developed by UN/CEFACT to standardise invoice exchange between businesses, governments and accounting systems.

In simple terms, CII defines how invoice data should be structured inside an XML file.

Instead of sending an invoice as a visual document like PDF, businesses send invoice data in a machine-readable structure. Systems can automatically validate, process and archive the invoice without manual entry.

This is why CII became important in European e-invoicing frameworks.

Especially after EN 16931 introduced standardised invoice requirements across EU member states.

A lot of businesses searching for cii invoice meaning assume CII is a platform or a software. It is not. It is simply a structured invoice syntax.

Think of it as a common invoice language systems agree to understand.

Where is CII Used? 

CII is heavily used across European e-invoicing ecosystems.

You will commonly see it in:

• France e-invoicing frameworks
• Factur-X invoices
• German ZUGFeRD invoices
• XRechnung invoices used in German public procurement
• Peppol-enabled invoice exchanges
• Public procurement invoicing
• Cross-border B2B invoicing

Germany provides a good example of how CII is used in practice. The XRechnung standard, which is mandatory for invoicing many German public authorities, supports both CII and UBL syntaxes. As a result, businesses supplying the public sector often encounter CII-based invoice structures even if they are not directly working with Factur-X or ZUGFeRD.

France is another major example.

Under the upcoming French e-invoicing reform, businesses will exchange structured invoices through PAs connected to DGFiP. EN 16931 compliant formats including CII, UBL and Factur-X are accepted.

This matters operationally.

Because companies implementing French e-invoicing usually discover very late that ERP invoice exports are not automatically EN 16931 compliant.

That becomes a problem during testing.

Cross Industry Invoice Format

The cross-industry invoice format is XML-based.

It organises invoice information into structured data blocks such as:

• Seller information
• Buyer information
• Invoice lines
• Tax details
• Payment terms
• Totals
• Currency information

Unlike PDFs, XML invoices are designed for systems, not humans.

A human-readable PDF may still exist alongside it. But the legally relevant invoice data sits inside the XML structure.

A typical CII invoice contains:

• Header section
• Trade transaction section
• Settlement information
• Tax breakdown
• Monetary summation

The structure looks technical because it is.

And honestly, many finance teams underestimate this during implementation. The challenge is not generating XML once. The challenge is generating consistent XML from multiple ERPs every single day.

Cross Industry Invoice Schema

The cross-industry invoice schema defines how invoice information must be structured inside a CII XML file. It establishes the technical rules that systems use to create, exchange and validate electronic invoices consistently.

The schema specifies elements such as:

• Mandatory and optional data fields
• Accepted data formats and data types
• Tax calculation requirements
• Invoice relationships and references
• Validation and business rules

However, it is important to understand that businesses do not always implement the base CII schema in exactly the same way.

Across Europe, the EN 16931 standard provides a common semantic model for electronic invoices. CII is one of the approved syntaxes used to represent that model. Individual countries and frameworks can then apply additional implementation guidelines known as Core Invoice Usage Specifications (CIUS) or extensions.

For example, Germany's XRechnung and France's Factur-X both build on the underlying CII structure while introducing their own requirements for specific business and regulatory use cases.

This is why two invoices may both be based on CII but still contain different validation rules, mandatory fields or implementation requirements depending on the country, network or reporting framework involved.

The schema itself ensures that invoice data remains structured and predictable.

For example:

• Dates must follow defined formats
• VAT calculations must reconcile correctly
• Currency codes must follow recognised standards
• Buyer and seller identifiers must meet prescribed requirements

This level of standardisation is one of the main reasons tax authorities increasingly prefer structured e-invoicing models over traditional document-based invoices.

Manual interpretation often leads to inconsistencies.

Structured invoice schemas significantly reduce that risk.

Today, the cross industry invoice schema serves as one of the primary syntaxes used to implement EN 16931-compliant e-invoicing across Europe, including frameworks such as XRechnung, Factur-X and other country-specific implementations.

Cross Industry Invoice Specification

The cross-industry invoice specification refers to the complete technical and semantic rules governing CII invoices.

One detail that often gets overlooked is the version being implemented. Most EN 16931-compliant e-invoicing frameworks today, including Factur-X and many public sector implementations across Europe, are based on the UN/CEFACT CII D16B syntax. Newer versions such as D22B have also been published by UN/CEFACT, but D16B remains the version most commonly supported across production e-invoicing ecosystems. 

It includes:

• XML syntax rules
• Business validation rules
• Tax data mapping
• Semantic data models
• Interoperability standards

The specification is maintained under UN/CEFACT standards.

One important thing businesses often miss is this.

Passing XML validation does not always mean the invoice is operationally compliant.

An invoice may technically validate but still fail downstream due to ERP mapping errors, incorrect tax treatment or buyer master data mismatches.

This happens more often than vendors admit during demos.

Cross Industry Invoice XML Example

The following cross industry invoice XML example is intended to illustrate the overall structure of a CII invoice.

It is not a production-ready template.

A real CII document requires namespace declarations, schema-compliant element hierarchies, mandatory business fields and validation against the applicable UN/CEFACT CII version and EN 16931 requirements. Depending on the implementation, additional country-specific requirements may also apply through frameworks such as XRechnung or Factur-X.

<rsm:CrossIndustryInvoice

xmlns:rsm="urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100" xmlns:ram="urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100"

xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:100">

   <rsm:ExchangedDocument>

      <ram:ID>INV-1001</ram:ID>

      <ram:TypeCode>380</ram:TypeCode>

      <ram:IssueDateTime>

         <udt:DateTimeString format="102">

            20260528

         </udt:DateTimeString>

      </ram:IssueDateTime>

   </rsm:ExchangedDocument>

   <rsm:SupplyChainTradeTransaction>

      <ram:ApplicableHeaderTradeAgreement>

         <ram:SellerTradeParty>

            <ram:Name>ABC Technologies Ltd</ram:Name>

         </ram:SellerTradeParty>

         <ram:BuyerTradeParty>

            <ram:Name>XYZ Retail GmbH</ram:Name>

         </ram:BuyerTradeParty>

      </ram:ApplicableHeaderTradeAgreement>

      <ram:ApplicableHeaderTradeSettlement>

         <ram:InvoiceCurrencyCode>EUR</ram:InvoiceCurrencyCode>

      </ram:ApplicableHeaderTradeSettlement>

   </rsm:SupplyChainTradeTransaction>

</rsm:CrossIndustryInvoice>

In practice, production CII invoices contain significantly more information, including tax breakdowns, invoice line details, payment terms, document references and validation attributes required by EN 16931 and country-specific implementation guidelines.

Cross Industry Invoice vs UBL vs Factur-X

A lot of businesses compare cross industry invoice vs ubl invoice vs factur x invoice as if one is universally better.

That is usually the wrong approach.

The right choice depends on:

• Country mandate
• ERP capability
• Buyer requirements
• PA compatibility
• Existing invoicing workflows

For example, Factur-X works well when businesses still want a readable PDF attached alongside structured XML.

When to Use Cross Industry Invoice (CII)

Businesses typically use CII when:

• Operating in EN 16931 compliant environments
• Implementing France or Germany e-invoicing
• Exchanging invoices via Peppol
• Supporting Factur-X or ZUGFeRD invoices
• Automating invoice processing between systems

CII becomes particularly relevant for enterprises managing multiple ERP systems across countries.

Because once invoice volumes increase, manual correction workflows become expensive very quickly.

This is where implementation quality matters more than invoice generation itself.

Benefits of Cross Industry Invoice Format

The main benefit of the cross-industry invoice format is automation.

Structured invoices reduce manual intervention across invoicing workflows.

Other benefits include:

• Faster invoice processing
• Better ERP interoperability
• Reduced invoice rejection risk
• Improved VAT compliance
• Easier tax reporting
• Standardised invoice validation

For governments, structured invoice formats also improve audit visibility.

This is one reason many countries are shifting toward continuous transaction controls and real-time reporting frameworks.

France is already moving aggressively in this direction through its PA and DGFiP-connected model.