Turn an e-invoice XML (CII or UBL) into a readable invoice table - locally in the browser, with no upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
An e-invoice such as XRechnung, or the XML inside a ZUGFeRD or Factur-X file, carries the invoice-relevant data as structured XML per EN 16931. That is made for software, not for the human eye: raw XML full of tags is barely readable. This tool reads the XML and presents the core fields as a clear invoice table - invoice number, date, invoice type, seller and buyer, line items, tax and totals, plus the Leitweg-ID (buyer reference). The result is a standalone HTML file you can open in any browser, print or save as a PDF.
Both syntaxes permitted by EN 16931 are recognised: UN/CEFACT CII (root element CrossIndustryInvoice, as in XRechnung-CII and ZUGFeRD/Factur-X) and OASIS UBL (Invoice-2, as in XRechnung-UBL). The tool detects the format from the root element automatically and maps the fields of both syntaxes onto the same table. The document type codes 380 (commercial invoice) and 381 (credit note) are spelled out. Just drop the .xml; several files at once are fine, each becomes its own HTML view.
Everything runs entirely locally in the browser (pure JavaScript, no server, no SaxonJS) - the invoice with its business data never leaves your device. Every value read from the XML is rendered HTML-safe, so the view stays reliable even with unusual content. It is explicitly a view and not a checking service: the tool shows what the XML says and does not judge whether the invoice conforms to EN 16931 or to a profile such as XRechnung 3.0.2.
| Input formats | XML |
|---|---|
| Output format | HTML |
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Renders an e-invoice XML in the two syntaxes permitted by EN 16931 as a readable HTML table: UN/CEFACT CII (CrossIndustryInvoice, also from ZUGFeRD/Factur-X) and OASIS UBL (Invoice-2). The core fields are mapped (invoice number, date, type 380/381, seller/buyer, line items, tax, totals, Leitweg-ID); very rarely used detail fields are not shown. Labels appear in German (de page) or English (otherwise); the invoice data itself is carried over 1:1. It is a view, not a validator: the tool does not check whether the invoice conforms to EN 16931 or to a profile such as XRechnung 3.0.2.
No. Reading the XML and building the HTML view run entirely locally in the browser (pure JavaScript, no server); the invoice with its business data never leaves your device.
The two syntaxes permitted by EN 16931: UN/CEFACT CII (CrossIndustryInvoice, also from ZUGFeRD/Factur-X) and OASIS UBL (Invoice-2). The XML root element decides which mapping applies.
No. It is purely a view and shows 1:1 what the XML says. Whether the invoice conforms to EN 16931 or a profile such as XRechnung 3.0.2 is not something it judges.
The Leitweg-ID is the buyer reference that public-sector buyers in Germany use to route an XRechnung. If it is present in the XML, the table shows it.
Yes. The result is a standalone HTML file; open it in the browser and print it, or save it as a PDF via the print dialog.