Automation MCP Server Blog Pricing

CII to UBL Conversion API

Convert a UN/CEFACT CII XML invoice to UBL XML for Peppol BIS Billing, NLCIUS, EHF, PINT or EN 16931 workflows.

POST https://api.invoicexml.com/v1/convert/cii/to/ubl
  • Peppol BIS, NLCIUS, EHF or PINT output
  • Every EN 16931 business term mapped
  • Validated against the chosen profile
  • Missing Peppol data pointed out

Technical reference

Convert a UN/CEFACT Cross Industry Invoice (CII) XML document to UBL XML. The API maps every EN 16931 Business Term from the CII nested structure to the equivalent UBL flat component model and validates the result. Name a UBL profile in the optional profile field, such as peppol-bis-3, and the invoice declares that profile and is validated against its rules, ready for the Peppol network.

Code Example

curl -X POST https://api.invoicexml.com/v1/convert/cii/to/ubl \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "[email protected]" \
  -F "profile=peppol-bis-3" \
  -F "validationLanguage=en"

Request

Parameter Type Description
file * binary The XML invoice file to convert.
profile string Optional. UBL profile of the converted invoice: en16931 (the default), peppol-bis-3, nlcius, ehf or pint, in any letter case. The invoice declares the profile's specification identifier (BT-24) and, where the profile requires one, its business process (BT-23), must meet the profile's requirements (for Peppol, the seller and buyer electronic addresses and a buyer or order reference), and is validated against the profile's rule set. With the default, the invoice declares plain EN 16931, whatever the uploaded file declared, and is validated against the EN 16931 rules. Any other value is rejected with a 400 (errorCode 4002).
validationLanguage string Optional. Language of the finding messages when the converted invoice is rejected: en (default), de or fr, in any letter case. Only each finding's message changes; rule, btCodes, fields and raw stay the same. Any other value is rejected with a 400 (errorCode 4002). See localized error messages.

Content-Type: multipart/form-data

Headers

Header Value
Authorization * Bearer YOUR_API_KEY
Content-Type multipart/form-data

Response

200 Converted XML

Returns the converted UBL XML document.

Content-Type: application/xml

Useful resources

Companion material for integrating against the API.

Frequently Asked Questions

What CII versions are accepted?

The endpoint accepts CII in the schema release EN 16931 binds to. This is the same schema used inside ZUGFeRD and Factur-X files.

Is the output Peppol BIS compliant?

Send profile=peppol-bis-3 and it is: the invoice declares the Peppol BIS Billing specification (BT-24) and business process (BT-23), must carry the seller and buyer electronic addresses and a buyer or order reference, and is validated against the Peppol rule set before delivery. Missing Peppol data comes back as a 400 that names the Peppol rule and the field.

Which values does profile take?

en16931, peppol-bis-3, nlcius, ehf and pint, in any letter case, the same UBL profiles as /v1/create/ubl. For XRechnung use /v1/convert/cii/to/xrechnung. The default is en16931 on every convert-to-UBL route: the invoice declares plain EN 16931, whatever the source CII declared, and is validated against the EN 16931 rules. /v1/create/ubl differs on purpose: its options.profile defaults to Peppol BIS Billing.

Are all EN 16931 fields preserved?

Yes. The conversion maps every EN 16931 Business Term (BT) from CII to UBL. No semantic data is lost, only the XML syntax changes.

Can I convert ZUGFeRD or Factur-X embedded XML?

Yes. Send the hybrid PDF to /v1/convert/facturx/to/ubl or /v1/convert/zugferd/to/ubl, which read the embedded XML and take the same profile field. To work with the XML itself, extract it with /v1/extract/xml and pass it to this endpoint.

Is the output validated?

Yes. The generated UBL document is validated against the rules of its profile before delivery: the EN 16931 Schematron business rules by default, or the rules of the profile you name. If validation fails, the API returns a 400 response with the specific rule violations.

Start free today

Ready to automate your invoices?

Validate, convert and embed compliant e-invoices through one API. Start your 30-day free trial. No credit card required.

GDPR Compliant No credit card required Setup in minutes
Peppol UBL
Factur-X
EN 16931
142 / 142 passed
Compliant
PDF/A-3 embedded