Check a UBL e-invoice against EN 16931 and Peppol, then keep the evidence
Find out in seconds which business rule a rejected invoice breaks, fix it, and close the ticket with a signed report your customer or access point can check.
Free validator
Drop a UBL invoice or credit note here or choose a file. The check runs in your browser; the file is not uploaded.
The workspace: what you keep
Signed, retained reports
Every check is stored with SHA-256 digests of the file, its content and the report, signed by the service. The invoice itself is never stored.
Verification links
Send a link instead of a screenshot. The recipient sees the verdict, the rule releases and the findings, and can re-check their copy of the file.
Version diff and profiles
Upload the corrected invoice and see which findings were fixed or introduced. Profiles require extra fields your company always needs.
Questions
Does my invoice leave my computer?
Not in the free validator on this page: the rules run in your browser and the file is never uploaded. In the workspace the file is sent once to be checked; only the report and its digests are stored, never the XML.
Which rules are checked?
All 981 assertions of the CEN EN 16931 UBL artefacts 1.3.17, or, for Peppol invoices, the CEN 1.3.16 copy that OpenPeppol bundles plus all 165 Peppol BIS Billing 3.0.22 assertions. Every report names the exact releases.
How do you know the results match the official rules?
Every release is compared with the official Schematron files on thousands of test documents, including all example and unit-test files published by CEN and OpenPeppol. The method and the latest result are on the rules page.
What is not checked?
Full XML Schema validation, CII/ZUGFeRD/Factur-X, national rule sets outside Peppol (for example XRechnung), and whether parties, tax numbers or bank accounts exist. Each report repeats this list.