Convert XRechnung XML to ZUGFeRD PDF using REST-API
Upload an XRechnung XML invoice (CII or UBL syntax, auto-detected) and receive a ZUGFeRD 2.x compliant PDF/A-3. The API parses the XRechnung payload, renders a clean visual layer, and embeds the EN 16931 CII baseline as factur-x.xml inside a ZUGFeRD-branded PDF/A-3 container. The XRechnung CIUS layer is downgraded to the EN 16931 baseline so the embedded XML can be consumed by every ZUGFeRD reader.
https://api.invoicexml.com/v1/convert/xrechnung/to/zugferd
Code Example
curl -X POST https://api.invoicexml.com/v1/convert/xrechnung/to/zugferd \ -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 ZUGFeRD PDF/A-3 as a binary file.
Frequently Asked Questions
Why is the embedded XML downgraded from XRechnung to EN 16931?
ZUGFeRD consumers expect the embedded conformance URN to belong to the ZUGFeRD / EN 16931 family. Re-branding the XRechnung CIUS URN to the EN 16931 baseline keeps the document spec-conformant without losing any Business Term data, every XRechnung field is a superset of EN 16931.
Is the input Schematron-validated?
Yes. The XRechnung document is validated against the XRechnung Schematron rules before the PDF is built. Validation failures are returned as 400 with the specific rule violations.