Convert XRechnung to UBL using REST-API

Convert an XRechnung XML invoice (CII or UBL syntax, the root element is auto-detected) to a plain EN 16931 UBL 2.1 XML document. The German XRechnung CIUS layer is dropped, the document is rebranded with the base EN 16931 customization, and the output is ready for the Peppol network or any EN 16931-conformant consumer.

POST https://api.invoicexml.com/v1/convert/xrechnung/to/ubl

Code Example

curl -X POST https://api.invoicexml.com/v1/convert/xrechnung/to/ubl \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "[email protected]"

Request

Parameter	Type	Description
file *	binary	The XML invoice file to convert.

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 2.1 XML document.

Content-Type: application/xml

Frequently Asked Questions

Which XRechnung syntax is accepted?

Both. XRechnung allows the invoice to be encoded as UBL or CII; the endpoint auto-detects the root element and converts either to UBL 2.1.

Is German-specific data lost?

No. The conversion preserves every EN 16931 Business Term, only the customization identifier (BT-24) is rebranded from XRechnung to the EN 16931 baseline. Buyer reference, Leitweg-ID, and other XRechnung-mandated fields remain in the document.

Is the output validated?

Yes. The generated UBL is validated against EN 16931 Schematron rules. Validation failures are returned as 400 with the specific rule violations.