Actually private
Invoices are business data. Unlike upload-based validators, parsing and validation happen in your browser via WebAssembly-free, dependency-free JavaScript. Works offline once loaded.
Open an e-invoice. Understand it. Validate it.
Drop an XRechnung, Factur-X / ZUGFeRD, UBL, CII or Peppol BIS invoice below. You get a readable invoice and a full EN 16931 business-rule check — with every error explained in plain language.
Drag & drop an invoice file here — .xml or Factur-X/ZUGFeRD .pdf
…or paste invoice XML anywhere on this page (Ctrl/Cmd+V)
🔒 Everything runs locally in this tab. Your invoice is never uploaded — this page makes no network requests with your data and uses no analytics. Verify the source.
Tested against the official corpora
The engine is verified against the EU (ConnectingEurope), KoSIT XRechnung and OpenPeppol test suites — 129 official files. See the conformance report.
Errors you can act on
Not just "[BR-CO-15] failed": each finding says what is wrong, where, and what the numbers should have been.
For developers too
The same engine is an MIT-licensed, zero-dependency TypeScript library with a CLI and an MCP server for AI agents. Use it in your stack.
Why e-invoicing, why now
Structured e-invoicing (EN 16931) is becoming mandatory across Europe. Key dates already in law:
| Country | What | When |
|---|---|---|
| Germany | All businesses must be able to receive e-invoices (issuing phases in 2027–2028) | since Jan 2025 |
| Belgium | B2B e-invoicing via Peppol | Jan 2026 |
| Poland | KSeF clearance (large taxpayers Feb, all VAT payers Apr) | Feb–Apr 2026 |
| France | All companies must receive; large & mid-size must issue (SMEs 2027) | Sep 2026 |
| Slovakia | Domestic B2B/B2G e-invoicing (zákon č. 385/2025 Z. z.) | Jan 2027 |
Questions people ask
Is my invoice uploaded anywhere?
No. The validator is a static page; your file is read by JavaScript in your browser and never leaves your machine. There is no server to upload to, no analytics, no cookies.
Which rules are checked?
The EN 16931 business rules: mandatory fields (BR-*), totals arithmetic (BR-CO-*), decimal precision (BR-DEC-*), all ten VAT category rule groups (standard, zero, exempt, reverse charge, intra-community, export, IGIC, IPSI, not-subject, split payment) and the code list rules (BR-CL-*) — about 165 rules. National extensions such as XRechnung's BR-DE rules are on the roadmap.
My accounting software produced an invalid invoice. What now?
Each finding names the official rule and explains it in plain terms — send both to your software vendor. The rule IDs (like BR-CO-15) are the standard vocabulary every e-invoicing implementer understands.
Can I validate many invoices at once?
Use the CLI: npx einvoice-kit validate *.xml — same engine, exit codes for CI pipelines. Details.