Valid Factur-X invoice
A valid Factur-X EN16931 hybrid PDF invoice — passes every check with no findings.
Deterministic EN16931 / Peppol BIS3 / XRechnung validation, including Factur-X (CII) hybrid PDFs and the French e-invoicing reform's lifecycle statuses — no AI, nothing stored.
A valid Factur-X EN16931 hybrid PDF invoice — passes every check with no findings.
A UBL invoice whose totals don't add up (BR-CO-15) — reported with expected-vs-found, never auto-fixed.
Not repairable by design: arithmetic findings (BR-CO-*) are reported, but amounts are never touched — that's a feature, not a gap.
A CII invoice with an empty element (PEPPOL-EN16931-R008) — Repair can fix this automatically.
This sample is not repairable: arithmetic findings (BR-CO-*) are reported with expected-vs-found, never fixed — amounts are never touched.
or choose a file (XML or PDF): No file selected
No issues found.
| Rule | Severity | Explanation | How to fix |
|---|
Detects the embedded CII invoice in hybrid PDFs and classifies its profile: Minimum, Basic WL, Basic, EN16931, or Extended.
Removes empty elements and fixes missing currency notation — never amounts, VAT, dates, or party identities.
Every issued report is registered by its own hash, so anyone can confirm it's genuine without re-uploading the invoice.
Look up or validate AFNOR XP Z12-012 CDAR status codes and transitions for the French e-invoicing reform.
A Model Context Protocol server exposes six tools — validate, repair, explain, batch, verify, status lookup — to Claude and other agent clients.
A GitHub Action and an n8n node validate invoices as part of your pipeline.
Watch a sample so it's automatically re-checked the moment a ruleset update would make it fail.