Your invoices, compliant before September 1.

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.

Try it in three clicks — no signup, no API key

  1. 1. Validate
  2. 2. Repair
  3. 3. Proof

Valid Factur-X invoice

A valid Factur-X EN16931 hybrid PDF invoice — passes every check with no findings.

UBL invoice with an arithmetic error

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.

CII invoice with a structural error

A CII invoice with an empty element (PEPPOL-EN16931-R008) — Repair can fix this automatically.

or choose a file (XML or PDF): No file selected

14 mapped rule codes in the taxonomy · 94 rule-encyclopedia pages (188 with EN/FR) · ruleset XRechnung 3.0.2 / Schematron 2.5.0

What else it does

Factur-X profiles

Detects the embedded CII invoice in hybrid PDFs and classifies its profile: Minimum, Basic WL, Basic, EN16931, or Extended.

Repair

Removes empty elements and fixes missing currency notation — never amounts, VAT, dates, or party identities.

Proof / verify

Every issued report is registered by its own hash, so anyone can confirm it's genuine without re-uploading the invoice.

Lifecycle statuses (FR)

Look up or validate AFNOR XP Z12-012 CDAR status codes and transitions for the French e-invoicing reform.

MCP for AI agents

A Model Context Protocol server exposes six tools — validate, repair, explain, batch, verify, status lookup — to Claude and other agent clients.

CI/CD

A GitHub Action and an n8n node validate invoices as part of your pipeline.

Regression monitoring

Watch a sample so it's automatically re-checked the moment a ruleset update would make it fail.