E-invoice validators
Check an invoice against EN 16931, Peppol BIS Billing 3.0, XRechnung or Factur-X / ZUGFeRD with the rule owners' own published rules: CEN's validation artefacts, OpenPeppol's Schematron, KoSIT's XRechnung configuration and the Factur-X profile rules. The answer lists every rule an invoice breaks.
Check a UBL or CII invoice against the European e-invoicing standard EN 16931 with CEN's official rules.
Checked against 5 published cases
Check a Factur-X or ZUGFeRD 2 invoice, as a PDF or its XML, against the rules for its profile.
Checked against 2 published cases
Check a UBL invoice or credit note against Peppol BIS Billing 3.0 with OpenPeppol's official rules.
Checked against 3 published cases
Check an XRechnung 3.0 invoice the way German public buyers do, with KoSIT's official validator configuration.
Checked against 3 published cases
Which rules, and how we know they run correctly
Each validator runs the rule owner's own published rules, pinned to a release:
- CEN/TC 434 EN 16931 validation artefacts, version 1.3.17
- OpenPeppol BIS Billing 3.0 Schematron (compiled with SchXslt 1.10.1), version 3.0.22
- KoSIT validator configuration for XRechnung 3.0.2, version 2026-08-31
- Factur-X 1.09.2 / ZUGFeRD 2.5 schemas and Schematron (FNFE-MPE and FeRD), as distributed with Mustang, version 1.09.2
Before every release, our test suite runs the rule owners' own tests against them: 1,818 unit tests from CEN and OpenPeppol, where each test says which rule must fire and which must not, and every invoice in KoSIT's XRechnung test suite and CEN's and Peppol's examples, all of which must be accepted. The accuracy report lists the published cases, and the live API is checked against them every five minutes.
An invoice is not stored or logged; the answer holds only the findings. PDF/A-3 conformance of a Factur-X PDF is not checked, only the invoice inside it and its XMP metadata.
As an API
Each validator is a POST endpoint and an MCP tool. An answer lists every finding with the rule's ID, level and the rule owner's own message.