UN/CEFACT Cross Industry Invoice
The UN/CEFACT Cross Industry Invoice syntax used by EN 16931, Factur-X and ZUGFeRD profiles.
Current version and implementation status
How to recognize the profile
Do not rely on the file extension alone. Inspect the root namespace, customization/profile identifiers, version values and authority-specific envelope.
- CrossIndustryInvoice
- ram:ApplicableHeaderTradeAgreement
- rsm:CrossIndustryInvoice
Production validation stack
- 1CII XSD
Confirm that the document is well formed and structurally compatible with the intended CII syntax.
- 2EN 16931 rules
Apply semantic and business-rule checks rather than accepting a file merely because it parses.
- 3Profile rules
Validate currencies, countries, tax categories, units, payment means and other controlled values against the correct release.
- 4Hybrid PDF attachment rules when embedded
Apply the national, network or authority restrictions that narrow the base syntax.
Common errors and corrective action
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Countries using or referencing this profile
Questions people ask
What is CII?
The UN/CEFACT Cross Industry Invoice syntax used by EN 16931, Factur-X and ZUGFeRD profiles.
How is CII validated?
A production check normally applies CII XSD, EN 16931 rules, Profile rules, Hybrid PDF attachment rules when embedded. Local browser preflight cannot replace the official validation artefacts or authority outcome.
Which version should I use?
The current research note is: D16B and newer profile bindings; France references D22B for its reform specifications. Confirm release notes at the official source before production deployment.
Inspect and prepare CII files
Invoice format detector
Identify common XML, JSON and national electronic invoice signatures.
Structured invoice viewer
Read supplier, buyer, dates, currency, totals and line items.
XML / JSON invoice to readable PDF
Turn supported structured invoice data into a clean human-readable print or PDF view.
XML and JSON field explorer
Search field names, values and document paths.