UN/CEFACT CII e-invoice format
XML (UN/CEFACT Cross Industry Invoice, D16B)
The exchange syntax for France’s Chorus Pro platform and the format many SAP/Sage ERP back-ends produce natively. Also the XML embedded inside every Factur-X/ZUGFeRD PDF.
Deadline: France: phased B2B mandate, September 2026 (receiving) / September 2027 (issuing).
UN/CEFACT Cross Industry Invoice (D16B) is EN 16931’s other syntax binding, structurally quite different from UBL despite carrying the same semantic content — different element names, different nesting depth, UN/CEFACT-style date formatting (CCYYMMDD, not ISO dashes).
InvoiceHub compiled the official CEN EN 16931 CII Schematron the same way it did for UBL — the actual CEN artifact, not a hand-approximated subset — so CII validation, generation, and conversion carry the same authority as the UBL side of the product.
Try it
curl -X POST https://api.invoicehub.dev/api/v1/convert \
-H "Authorization: Bearer ih_live_xxx" \
-H "Content-Type: application/json" \
-d '{"from": "UBL_2.1", "to": "UN_CEFACT_CII", "document": "<source UBL document>"}'Structure
<rsm:CrossIndustryInvoice xmlns:rsm="urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100" ...>
<rsm:ExchangedDocument>
<ram:ID>INV-2026-0142</ram:ID>
<ram:TypeCode>380</ram:TypeCode>
</rsm:ExchangedDocument>
<rsm:SupplyChainTradeTransaction>
<ram:ApplicableHeaderTradeSettlement>
<ram:SpecifiedTradeSettlementHeaderMonetarySummation>
<ram:DuePayableAmount>1190.00</ram:DuePayableAmount>
</ram:SpecifiedTradeSettlementHeaderMonetarySummation>
</ram:ApplicableHeaderTradeSettlement>
</rsm:SupplyChainTradeTransaction>
</rsm:CrossIndustryInvoice>Common validation errors
- BR-02 — Missing invoice number (ram:ExchangedDocument/ram:ID).
- BR-05 — Missing invoice currency code.
- BR-CO-10 — Sum of line net amounts ≠ document line-extension total.
Generate or convert to UN/CEFACT CII
POST /api/v1/generate for structured JSON in, or POST /api/v1/convert from any other supported format.