What is CII?

CII defines a different XML structure than UBL for the same invoice data:

<rsm:CrossIndustryInvoice xmlns:rsm="urn:un:unece:uncefact:...">
  <rsm:ExchangedDocumentContext>...</rsm:ExchangedDocumentContext>
  <rsm:ExchangedDocument>
    <ram:ID>INV-2024-001</ram:ID>
    <ram:IssueDateTime>...</ram:IssueDateTime>
  </rsm:ExchangedDocument>
  <rsm:SupplyChainTradeTransaction>...</rsm:SupplyChainTradeTransaction>
</rsm:CrossIndustryInvoice>

CII Namespaces

CII uses different namespace prefixes:

• rsm: Root schema module
• ram: Reusable aggregate components
• qdt: Qualified data types
• udt: Unqualified data types

CII in ZUGFeRD/Factur-X

When you create a ZUGFeRD or Factur-X invoice, the embedded XML file uses CII syntax. The PDF provides human readability; the CII provides machine readability.

Hybrid Format Foundation

CII powers ZUGFeRD and Factur-X, the dominant e-invoice formats in Germany and France. If you trade with these countries, you'll likely encounter CII.

EN 16931 Compliant

CII is equally valid as UBL for EN 16931 compliance. XRechnung even supports both syntaxes—you can submit UBL or CII to German government portals.

Supply Chain Integration

CII is part of UN/CEFACT's broader supply chain standards. If you use other UN/CEFACT documents, CII provides consistency.

Step 1: Understand the Context

If you're creating ZUGFeRD/Factur-X invoices, you're using CII. If you're using Peppol directly, you'll typically use UBL instead.

Step 2: Choose Your Profile

ZUGFeRD/Factur-X support multiple profiles (Minimum to Extended). Choose based on your data requirements and recipient needs.

Step 3: Embed in PDF

For hybrid formats, the CII XML gets embedded in a PDF/A-3 file. Tools handle this automatically, but ensure validation covers both parts.