When you need this
Every e-invoice in the EU follows the European standard EN 16931, which allows two XML syntaxes: UBL (from OASIS) and CII (from UN/CEFACT). On top of that come national flavours. Two of them matter most when you do business with Germany:
- XRechnung is the German flavour of EN 16931, pure XML in UBL or CII. German public authorities require it, and many German companies use it too.
- ZUGFeRD (called Factur-X in France) is a PDF with a CII XML embedded in it. The customer sees a normal PDF, the accounting software reads the XML.
Not every recipient, portal or accounting program accepts every variant. Typical cases for this tool:
- A German public authority wants an XRechnung and you have a ZUGFeRD PDF. Then a few items are usually missing that XRechnung requires on top – above all the Leitweg-ID, the buyer reference that German authorities use to route invoices. The tool asks for them.
- Your software writes CII, the portal wants UBL – or the other way round. The content is the same invoice, just written differently.
- You received an XRechnung and nobody on your side can read it. Turn it into a ZUGFeRD PDF with a readable layout, or simply open it in the e-invoice viewer.
- You need a plain EN 16931 invoice in UBL without the German additions, for a recipient that expects the European standard as it is.
A rule ID from the validation, such as BR-DE-15, is explained in the e-invoice validation rules.
How it works
- Drop the file. XML or ZUGFeRD/Factur-X PDF. The tool shows what it has read: format, number, date, seller, buyer, amount due.
- Choose the target: XRechnung 3.0 in UBL or CII, ZUGFeRD/Factur-X in the profile EN 16931 (as a PDF or as XML only), or EN 16931 in UBL.
- Add what is missing. If the target requires data your invoice does not have, the tool asks for it. Only XRechnung requires extra data. The tool never fills in anything that is not in the invoice.
- Convert and validate. The new file goes through the XML schema and the business rules, like the KoSIT validator for XRechnung. You can only save it once no errors are left.
What happens during the conversion
EN 16931 describes an invoice as a list of fixed terms: BT-1 is the invoice number, BT-112 the total with VAT, BG-25 an invoice line. For UBL and for CII the standard defines where in the XML each term goes. The tool reads your invoice term by term into this common model and writes it out again in the other syntax. Amounts, quantities and texts are copied character by character; nothing is recalculated.
The tool keeps track of every element it has read. If one is left over, it is not part of EN 16931 – and then no target format can hold it either. The tool lists such items one by one instead of dropping them silently. Typical examples are parts of the ZUGFeRD profile EXTENDED, such as package quantities, or sub-lines of the XRechnung extension.
In a few places the syntaxes differ, and the tool tells you about those too:
- CII takes only one reference to a preceding invoice (BT-25), UBL any number.
- UBL requires the total VAT amount (BT-110) and, where a gross price is given, the price discount (BT-147). If a CII invoice lacks them, the tool derives them from the VAT amounts or as gross price minus net price, and says so in the list of changes.
- In UBL the remittance information and the direct debit mandate belong to the payment means. If the invoice has no payment means, they are not carried over.
- Logistics charges from the profile EXTENDED count as document-level charges there. The tool carries them over as such charges (BG-21) and tells you.
A ZUGFeRD PDF from an XRechnung
An XRechnung is pure XML; there is nothing to look at. For a ZUGFeRD PDF the tool therefore draws a layout from the invoice data, built like the invoice page in the e-invoice viewer: sender, address, invoice details, lines, totals, payment and footer, over several pages for long invoices, with English labels. It shows only what is in the XML. At the bottom of each page it says that the layout was generated from the XML and that the XML is authoritative.
The validated XML is attached to the PDF as factur-x.xml, and the whole file is marked as
PDF/A-3, with the font (DejaVu Sans) and the colour profile embedded. After creating it, the tool reads the
XML back from the new PDF and compares it with the validated one. The automated tests also check the
generated PDFs with veraPDF, the free PDF/A validator.
If your invoice already came as a ZUGFeRD PDF, for example in the profile EXTENDED, it gets a new layout as well. The layout of the old PDF is not carried over.
What XRechnung requires on top
XRechnung makes some data mandatory that is optional in EN 16931. If any of it is missing, the tool asks for it. Next to each field is the rule that would otherwise fail:
- Buyer reference (BT-10, rule BR-DE-15) – for German public authorities the Leitweg-ID they give you
- a contact person at the seller with telephone and email (BG-6, BR-DE-2 and BR-DE-5 to 7)
- electronic addresses of seller and buyer (BT-34, BT-49), here an email address
- post code and city of both parties (BR-DE-3, -4, -8, -9)
- payment instructions (BG-16, BR-DE-1) – if you enter an IBAN, the tool adds a SEPA credit transfer
The tool also sets the specification identifier (BT-24) to XRechnung 3.0 and, where it is missing, the business process type (BT-23) to the usual value. In the other direction, from XRechnung to ZUGFeRD or to EN 16931 UBL, only the specification identifier changes; everything else already fits.
Example: an electrician’s invoice
The sample in the tool is a made-up German XRechnung in CII syntax, the same as in the e-invoice viewer: invoice RE-2026-0042 of 15 October 2026 to a German municipality, Leitweg-ID 04011000-12345-03, three lines. The descriptions are in German, as they would be in a real German invoice:
- 100 m of sheathed cable at €0.89 = €89.00 (19 % VAT)
- 3 hours of installation at €65.00 = €195.00 (19 %)
- 1 technical book at €24.90 (7 %)
Net 89.00 + 195.00 + 24.90 = €308.90. VAT 19 % on €284.00 = €53.96 and 7 % on €24.90 = €1.74 (1.743 rounded), together €55.70. Amount due €364.60.
- To XRechnung UBL: the tool asks for nothing – all mandatory data is already there – and reports “All data transferred unchanged”. Number, dates, amounts and texts appear character by character in the UBL file as before in the CII file, just in other places. The validation against the UBL 2.1 schema, EN 16931 and XRechnung 3.0 reports no errors.
- To ZUGFeRD: exactly one item changes – the specification identifier (BT-24) becomes
urn:cen.eu:en16931:2017. The result is then validated against the rules of ZUGFeRD 2.5.2 in the profile EN 16931, without errors. As a PDF it shows “Invoice number RE-2026-0042”, the lines, “Total with VAT” and “Amount due”. - To EN 16931 UBL: the same single change of BT-24; validated against the UBL schema and the EN 16931 rules, without errors.
The automated tests of the tool replay these cases on every change, plus 98 invoices from the test collections of KoSIT and of the ZUGFeRD Mustang project for the conversion itself.
Limits
- EN 16931 UBL is not Peppol BIS. Peppol BIS Billing 3.0 uses UBL as well, but with its own specification identifier and additional rules (PEPPOL-EN16931-R…, PEPPOL-COMMON-R… and national rules such as DE-R or NL-R). The tool neither produces Peppol BIS nor checks its rules. If you send through Peppol, your access point validates against them.
- It sends nothing. The tool creates the file; delivering it – by email, through a portal or a Peppol access point – is up to you. What each country requires for delivery is summarised for Germany and France in the e-invoice viewer; in France, for example, invoices between businesses must go through an approved platform.
- The French rules of the e-invoicing reform (DGFiP) are not checked, only EN 16931, XRechnung and ZUGFeRD/Factur-X.
- The layout in the ZUGFeRD PDF is plain and always the same – no logo, not your letterhead. From a ZUGFeRD PDF only the embedded XML is converted; for the e-invoice only the XML counts anyway.
- Characters missing from the font DejaVu Sans (such as Chinese characters) appear as boxes in the layout. In the XML they are correct.
- MINIMUM and BASIC WL have no invoice lines and are not complete e-invoices. One cannot be made from them without inventing data.
- Data outside EN 16931 is not carried over (see above). If validity depends on it – for example prepayments in the XRechnung extension that change the amount due – the validation fails and the result cannot be saved.
- If the original invoice has errors, so does the result. The tool does not repair content.
- Validation is against XRechnung 3.0. An older XRechnung is set to 3.0 during conversion and must meet its rules.
- Files up to 50 MB, no encrypted PDFs.
The conversion changes the format, not the content. The issuer remains responsible for the invoice. Keep the invoice as you received or sent it; in Germany the XML is authoritative for a hybrid format such as ZUGFeRD (section 14.4 UStAE). The converted file is a working copy for the program that needs it. Before saving, you confirm that you understand this.
How your invoice is protected
Reading, converting and validating run entirely in your browser. There is no upload, and nothing is stored at xmoo.app. The processing runs in an isolated frame with its own, sealed-off origin: this page shows ads, but their scripts cannot reach the invoice, and neither ads nor analytics run inside the frame. A security policy forbids the frame to send anything over the network. It only loads fixed program files from xmoo.app, such as the validation rules.
For developers: the same conversion as an API
To convert invoices continuously from your own software, this converter is available as a REST API: the xmoo E-Invoice API. It converts between XRechnung (UBL or CII) and ZUGFeRD (XML or PDF/A-3) with the same core as this tool. If the target lacks mandatory data, it names the fields instead of inventing anything, and it only returns a result that passes the official validation.
Unlike this tool, the API sends the invoice to our server in Helsinki (EU); it is processed in memory only and never stored. Billing runs through RapidAPI, with a free plan of 50 requests a month to try it out.
Frequently asked questions
How do I convert a ZUGFeRD PDF to XRechnung?
Drop the PDF into the box above, choose “XRechnung 3.0 (UBL)” or “(CII)”, fill in the fields the tool asks for – usually the Leitweg-ID and a contact person – and press “Convert and validate”. Once the validation reports no errors, you can save the XRechnung.
How do I turn an XRechnung into a PDF?
Choose “ZUGFeRD / Factur-X, profile EN 16931 (CII)” and save the ZUGFeRD PDF. It is a readable PDF with the XML inside. To print it once, the e-invoice viewer is enough.
What is the difference between UBL and CII?
They are two XML languages for the same content: UBL comes from OASIS, CII from UN/CEFACT. EN 16931 and XRechnung allow both; ZUGFeRD/Factur-X always uses CII.
Is data lost in the conversion?
Not the data of EN 16931: the tests show this with every invoice of the KoSIT test collection, converted there and back. Data outside the standard cannot be held by any target format; the tool lists it before the conversion.
Is my invoice uploaded?
No. Everything happens in your browser (see above).
Is there a German or French version?
Yes: the E-Rechnung-Konverter in German and Convertir une facture électronique in French.
Sources
- Semantic model and syntaxes: EN 16931-1:2017 (BT/BG terms) and CEN/TS 16931-3-2 (UBL) and -3-3 (CII); the mapping follows the EN 16931 validation artefacts 1.3.17 of the European Commission
- XRechnung 3.0: specification of KoSIT (in German) and XRechnung Schematron 2.6.0 (national rules BR-DE)
- ZUGFeRD 2.5.2 (Factur-X 1.09.2): information package from FeRD; PDF structure (attachment, PDF/A-3 metadata) following the reference library factur-x 7.7; PDF/A check in the tests with veraPDF 1.30.3
- Schemas: OASIS UBL 2.1 and UN/CEFACT CII D16B, as in the XRechnung validator configuration of KoSIT
- XML authoritative for hybrid formats: BMF letter of 15 October 2025, section 14.4 UStAE (in German)
- Peppol BIS Billing 3.0: specification
and rules of OpenPeppol (rule IDs from
rules/sch/PEPPOL-EN16931-UBL.sch, retrieved 18 November 2026) - Test invoices: XRechnung test suite of KoSIT (Apache 2.0) and Mustang project (Apache 2.0)
Software used and licences
- Reading, converting, writing and the PDF layout are xmoo.app’s own code.
- pdf-lib 1.17.1 builds the ZUGFeRD PDF. Copyright Andrew Dillon, MIT licence. fontkit 1.1.1 (the build for pdf-lib) embeds the font, copyright Devon Govett and Andrew Dillon, MIT licence.
- DejaVu Sans 2.37, copyright Bitstream (Bitstream Vera), changes by the DejaVu project in the public domain, licence. Only a subset with the characters used is embedded in the PDF.
- The sRGB colour profile is calculated by xmoo.app and free to use.
- SaxonJS 2.7 runs the validation rules. Copyright Saxonica Ltd, redistributed unchanged under the SaxonJS licence (which also contains the disclaimer). Includes big.js, copyright Michael Mclaughlin, MIT licence.
- EN 16931 validation artefacts 1.3.17, © European Union, under the EUPL 1.2; XRechnung Schematron 2.6.0 of KoSIT and ZUGFeRD 2.5.2 / Factur-X 1.09.2 of FeRD and FNFE-MPE under the Apache License 2.0, here in compiled form (SEF); the latter taken from factur-x by Alexis de Lattre (Akretion), BSD licence.
- XML schemas UBL 2.1 (copyright OASIS Open, with the XML Signature schema, copyright The Internet Society and W3C) and UN/CEFACT CII D16B (copyright UN/CEFACT), redistributed unchanged with their copyright notices. xmllint-wasm 5.3.0 checks the XML schema: libxml2 as WebAssembly, MIT licence.
Page last updated: 18 November 2026