Validate an e-invoice
Drop an XML invoice in. It runs the official European Commission EN 16931 schematron and, when the file declares XRechnung, the German BR-DE layer on top. Every rule that fires is listed with a link to a plain-English explanation. Nothing is stored — your file is processed in memory and discarded.
What gets checked
EN 16931 — the European semantic standard
The core business rules every compliant invoice must satisfy: mandatory fields, VAT category logic,
and the calculation chain from line amounts through to the amount due. These are the
BR-*, BR-CO-*, BR-CL-* and BR-DEC-* rules.
XRechnung 3.0 — the German CIUS
Germany narrows EN 16931 further. The BR-DE-* rules add mandatory buyer reference,
seller contact details, payment instructions and address fields that are optional elsewhere — which is
why an invoice that passes EN 16931 can still be rejected by a German receiver.
Peppol BIS Billing 3.0
The profile used across the Peppol network, including Belgium's mandatory B2B e-invoicing since
January 2026. Adds electronic address and business process requirements
(PEPPOL-EN16931-*).
Rejected because of the data, not the format?
If the problem is that your accounting system exports a spreadsheet rather than structured XML, the CSV converter builds a valid XRechnung, Peppol or UBL invoice from it — and validates every one before you download it. Up to three invoices per upload is free. Got a PDF invoice instead? The Factur-X / ZUGFeRD inspector checks whether XML is embedded inside it and validates that.