Available now · Pro plan or above

Convert UN/CEFACT CII to XRechnung 3.0 (CII)

Germany requires XRechnung for invoicing federal and most state public-sector buyers (B2G); CII is the native syntax for many SAP-based senders.

Deadline: Live since 2020 for federal buyers; B2B receipt mandatory since 2025.

SAP and many German ERPs export CII natively. XRechnung 3.0 supports both UBL and CII syntax — the additional mandatory fields (buyer reference/Leitweg-ID, business process, electronic addresses, seller contact phone) are identical regardless of which syntax carries them.

InvoiceHub runs the official EN 16931 CII core Schematron plus KoSIT’s XRechnung CII delta ruleset together, so the same authoritative rule set applies whichever syntax you started from.

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": "UN_CEFACT_CII", "to": "XRechnung_CII", "document": "<source document>"}'

Real XRechnung 3.0 (CII) output

Excerpt from actual, verified conversion output — not a mocked example.

<rsm:CrossIndustryInvoice ...>
  <rsm:ExchangedDocumentContext>
    <ram:BusinessProcessSpecifiedDocumentContextParameter>
      <ram:ID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</ram:ID>
    </ram:BusinessProcessSpecifiedDocumentContextParameter>
    <ram:GuidelineSpecifiedDocumentContextParameter>
      <ram:ID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</ram:ID>
    </ram:GuidelineSpecifiedDocumentContextParameter>
  </rsm:ExchangedDocumentContext>
  ...
  <ram:DefinedTradeContact>
    <ram:TelephoneUniversalCommunication><ram:CompleteNumber>+49 30 1234567</ram:CompleteNumber></ram:TelephoneUniversalCommunication>
  </ram:DefinedTradeContact>
</rsm:CrossIndustryInvoice>

Common validation errors

Get an API key

Free tier includes unlimited validation and UBL 2.1 generation. This conversion requires the Pro plan or above.

Start freeSee pricing

Other conversions