Formats and countries flow through eConnect into one clean stream for your ERP. The recipient gets the document in the agreed format of their software, often UBL or NLCIUS, not automatically as raw XML.
Schedule a meeting
API documentation
eConnect's PSB automatically transforms between all supported e-invoicing formats. The recipient always receives documents in the format configured in their setup, regardless of the format the sender used.
An invoice supplied by a French supplier in Factur-X can arrive at a Dutch recipient as NLCIUS and at a German recipient as XRechnung. You don't need to adapt your integration when a supplier or customer invoices in a different format. The transformation happens fully automatically on sending and receiving.
All supported formats trace back to the same semantic model (EN 16931), which makes lossless conversion technically possible.
Conversion between the two officially recognised syntax bindings of EN 16931.
Conversion between the Dutch and German national implementations of BIS Billing V3.
Conversion from the hybrid PDF/XML format to structured XML formats and back.
The Transform API supports the most commonly used conversions between international and national standards.
Besides automatic transformation on sending and receiving, eConnect offers a standalone Transform API. Via POST /api/v1/generic/transform?targetFormat={URN} you convert a document directly, without storage or sending.
The Transform API recognises the source format automatically based on the XML content. If automatic detection fails, you supply the source format via ?sourceFormat={URN}. The converted document is returned directly as XML.
Use cases: testing transformations before going live, manual conversion for partners with specific requirements, pre-processing for systems expecting a fixed format, or comparing the same document across multiple formats.
E-invoicing formats aren't isolated islands. They are built in layers:
- EN 16931 is the European semantic standard. All European formats are based on it.
- UBL 2.1 and CII are the two official syntax bindings.
- Peppol BIS Billing V3 is the European Peppol profile on top of UBL or CII.
- NLCIUS (Netherlands), XRechnung (Germany) and Factur-X (DE/FR) are national implementations.
Because all formats rest on the same foundation, lossless conversion is technically achievable. eConnect safeguards the validity of the transformed document through automatic schema validation after every conversion.
The PSB recognises the source format automatically on every transformation; no manual parameter setup needed.
Transformations are executed entirely in memory. No intermediate storage or external transfer.
Every conversion complies with the European semantic model EN 16931, the common foundation of UBL, CII and Peppol BIS.
The PSB automatically transforms between all supported formats: UBL, CII, Peppol BIS Billing V3, NLCIUS, XRechnung and Factur-X/ZUGFeRD. Not every combination is available; the current transformation table can be requested via the API. Automatic transformation on sending and receiving is available from the 10K package.
The PSB recognises the source format automatically based on the XML content. You don't need to specify which format you're supplying. If automatic detection fails, you can supply the source format via the ?sourceFormat={URN} parameter in the API call.
Yes, for all formats based on EN 16931. Because these formats use the same semantic model, no data is lost during conversion. Formats outside EN 16931 (such as FatturaPA for Italy) require routing via a local partner.
Yes. Via the standalone Transform API (POST /api/v1/generic/transform) you convert documents without storage or sending. That makes it suitable for testing, pre-processing and comparison. The Validate API (POST /api/v1/generic/validate) additionally checks whether the transformed document meets the applicable validation rules.
Yes. Transformation converts a document from one format to another. Validation checks whether a document meets the rules of a specific format. On sending, the PSB performs both steps: first transforming to the recipient's format, then validating before the document goes onto the network. Both are also available separately as standalone API endpoints.
Schedule a meeting
Get a quote via Cora