Check an e-invoice XML (CII or UBL) structurally against key EN 16931 rules - 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
Before you send or book an e-invoice you want to know whether the basics are right. This tool reads an e-invoice XML (CII or UBL per EN 16931) and checks it against a manageable selection of the most important business rules: are the invoice number, issue date, currency, seller and buyer present? Is a valid document type code set (380 commercial invoice, 381 credit note)? Is there at least one line item? And does the total arithmetic add up - is the sum of the line items equal to the line total, and do net plus tax give the gross total? The result is a readable report with OK/Note per check.
Important and honest: this is a helper for a quick self-check, not an official seal and not an attestation. It checks a curated subset of the EN 16931 business rules, not the full KoSIT Schematron rule set - so it replaces neither the conformance check of your accounting or ERP software nor your tax advisor. A note means "I could not confirm this or it looks inconsistent", not a legal verdict about the invoice.
Both syntaxes permitted by EN 16931 are checked: UN/CEFACT CII (CrossIndustryInvoice, also from ZUGFeRD/Factur-X) and OASIS UBL (Invoice-2). For an XRechnung the Leitweg-ID (buyer reference) is checked too. Everything runs entirely locally in the browser (pure JavaScript, no server, no SaxonJS) - the invoice with its business data never leaves your device. You get the report as a standalone HTML file you can keep, print or save as a PDF.
| Input formats | XML |
|---|---|
| Output format | HTML |
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Checks an e-invoice XML (CII or UBL per EN 16931) against a CURATED subset of the business rules: presence of the mandatory fields (invoice no./date/currency/seller/buyer/at least one line item), a valid document type code (380/381 etc.), the total arithmetic (sum of line items, net + tax = gross, amount due) and the Leitweg-ID for an XRechnung. It is a structural helper for a self-check, NOT a full KoSIT Schematron service and not an attestation - a note is not a legal verdict. Labels appear in German (de page) or English (otherwise); structure and arithmetic consistency are checked, not the substantive correctness of the invoice.
No. Reading the XML and running the checks happen entirely locally in the browser (pure JavaScript, no server); the invoice with its business data never leaves your device.
A curated selection of the EN 16931 business rules: mandatory fields present, a valid type code (380/381), at least one line item and the total arithmetic (net + tax = gross, amount due), plus the Leitweg-ID for an XRechnung.
No. It is a structural helper for a self-check, not an official seal and not an attestation. The full KoSIT Schematron rule set is not reproduced; it does not replace the check by your software or your tax advisor.
A note means "I could not confirm this or it looks inconsistent" - for instance a missing mandatory field or a total that does not add up. Check that spot yourself; it is not a legal verdict about the invoice.
The two syntaxes permitted by EN 16931: UN/CEFACT CII (CrossIndustryInvoice, also from ZUGFeRD/Factur-X) and OASIS UBL (Invoice-2). Drop the .xml; several files at once are fine.