Your file stays put: everything runs in your browser

Does your invoice pass the official validators?

Drop in a Factur-X PDF or a CII XML file. The SDK reads it back into a typed object, then the three official schematrons judge it: EN 16931 (CEN), Factur-X, and the French BR-FR rules of the XP Z12-012 standard.

This validator runs entirely in your browser: it needs JavaScript to read the file and execute the schematrons. Your file is never uploaded either way. Without JavaScript, the SDK is still usable from npm.

Drop a file here

Factur-X PDF or CII XML · it never leaves your machine

Choose a file

Nothing at hand?

Loading…

What this tool checks

Four judges

The SDK checks the model, the arithmetic in integer cents and the French rules, giving the exact path of the offending field. The three official schematrons then rule on the XML as it stands, with their own rule codes.

Three tolerances, stated openly

Three warnings are flagged as tolerated, never hidden: each one pits a PEPPOL or CII rule against a requirement of the French standard. The reason is shown alongside every one of them.

What is still missing

The PDF/A-3 check by veraPDF needs Java, and therefore a server: it does not run here. The SDK passes it in continuous integration on every published version.

A sample invoice to take away

The sample Factur-X PDF is produced by the SDK itself: EN 16931 profile, French statements, PDF/A-3b verified by veraPDF. Its deliberately faulty twin carries four common defects, listed on the PDF page itself, so you can check that a receiving pipeline rejects what it ought to reject.

What gets counted

Your invoice is neither uploaded nor read anywhere but on your own machine. Only a content-free signal is sent on each check: the server answers with nothing at all and keeps a single log line, at an already-truncated address. Enough to know whether the tool is used — no cookie, no identifier, and nothing about your invoice.

The same rules as in CI

The rule sets come from the mustangproject repository at a pinned commit, compiled and then executed by Saxon-JS — exactly what judges the SDK on every commit.

This tool is not legal advice and does not replace the accredited platform that will transmit your invoices. XSLT engine: Saxon-JS 2.7 © Saxonica, redistributed unmodified (licence).