Validator
Validate an e-invoice
Checked against 222 EN 16931, Peppol BIS 3.0 and InvoiceVerify rules. Results stay in your browser.
Prüfung auf BR-18
BR-18 · Name des Steuervertreters fehlt
Fügen Sie Ihre Rechnung ein oder laden Sie sie hoch. Verletzt sie BR-18, wird der Treffer unten im Bericht hervorgehoben.
Ausführliche ErklärungDrop your e-invoice here
UBL 2.1 · Peppol BIS 3.0 · XRechnung · Factur-X / ZUGFeRD (XML or PDF)
Processed in memory and never stored. PDFs are unpacked in your browser.
How this checker compares with the official rules
We run the official unit tests of the CEN EN 16931 validation artefacts 1.3.17 and the Peppol BIS Billing 3.0 rules 3.0.22 in UBL and CII and compare every expected verdict of a rule this checker covers. The figures below are the last run, written by the comparison itself. Where we answer differently on purpose, or don't check at all, it's listed below.
Same verdict as the official EN 16931 and Peppol Schematron for every rule we check, on all 1,919 official test cases (CEN 1.3.17 · Peppol BIS 3.0.22), checked 17 November 2026: 929 verdicts compared, 0 different. 177 rules those tests exercise aren't checked here.
Official test files: CEN 1.3.17 · Peppol 3.0.22Reproduce: npm run compare-officialWhat isn't covered
Deliberate differences
A missing due date is a warning, not an error
EN 16931 says a positive amount due needs a due date or payment terms (BR-CO-25), but the official CEN rules stopped checking it in version 1.3.16. We still warn on invoices, because many buyers' systems ask for one, so an invoice the official rules accept can show this warning here. Credit notes get nothing, as in the official tests. Factur-X / ZUGFeRD keeps it as an error, because its own rules still check it.
One VAT breakdown row per standard rate
A standard-rated rate used on lines, allowances or charges without a VAT breakdown row of its own is reported as BR-S-01 here. The official BR-S-01 only asks for one standard-rated row in total, so on its own it lets a missing rate through (the totals rules usually catch it). The same applies to the IGIC and IPSI categories (BR-VAT-01).
Our own extra checks
Rules starting with IV- are InvoiceVerify's own: they are not part of any official rule set. Only IV-VAT-01 (a VAT number that doesn't match its country's format) and the file checks (not well-formed XML, not an invoice, wrong data types) are errors; the others are warnings or notes. So an invoice the official rules accept can fail here on a malformed VAT number.
Some official rules share one ID
The one-breakdown-row rules of the other VAT categories (BR-Z-01, BR-E-01, BR-AE-01, BR-IC-01, BR-G-01, BR-O-01, BR-IG-01, BR-IP-01) are reported as BR-VAT-01, their taxable-amount rules (BR-Z-08 … BR-IP-08) as BR-VAT-08, and the 28 decimal rules (BR-DEC-01 … BR-DEC-28) as BR-DEC. The verdict is the same; only the ID in the report differs.
Which files get the Peppol rules
Files that declare Peppol BIS Billing 3.0 get its rules, in UBL and in CII. When you choose the Peppol rule set yourself, every UBL file gets them, and every CII file except Factur-X / ZUGFeRD, XRechnung and SI-UBL 2.0 files, which keep their own rules because they aren't Peppol documents.
Not checked here
- 64 EN 16931 rules that the official tests exercise, mostly VAT details of allowances and charges (BR-S-03 … BR-O-14), the VAT amount per category (BR-S-09 and its twins), some code lists (BR-CL-03 … BR-CL-20) and allowance or charge reasons (BR-CO-21 … BR-CO-24).
- 17 Peppol BIS rules, among them R006, R054, R080, R100, R101, the code lists CL002, CL003 and CL007, and the checks that an exemption reason code matches its VAT category (P0104 … P0111).
- 96 national rules that Peppol runs for Denmark, Germany, Greece, Italy, Norway and Sweden, and their identifier formats (PEPPOL-COMMON-R042 and R044 … R057). The Dutch rules (NL-R-001 … 009) are covered.
- XSD schema validation, and the CEN syntax rules (UBL-SR, UBL-CR, CII-SR).
So a pass here is a strong signal, not a guarantee: your access point validates every invoice against the full official set before sending it. Every official rule the tests exercise that we don't check is listed in conformance.json ; the comparison is compare-official-tests.mjs .
Validate for a specific country or format
Before you send: is the customer on Peppol? Search the official Peppol Directory by company name, VAT or company number, or Peppol ID — free.
Germany · XRechnung
XRechnung or ZUGFeRD? Check it in German too
This validator applies the XRechnung rules (BR-DE) automatically when a file declares XRechnung 3.0. The German checker runs the same XRechnung rules entirely in your browser and explains every fix in German.
- XRechnung ValidatorPaste an XRechnung (UBL or CII) or a ZUGFeRD PDF and see 32 XRechnung rules (BR-DE) with the fix in German. Runs in your browser; nothing is uploaded.in German
- XRechnung vs. ZUGFeRDXRechnung or ZUGFeRD: how they are built, the profiles, and which format suits which customer.in German
- Leitweg-ID prüfen und findenThe routing ID German public buyers require: how it is built, its check digits and where it goes (BT-10).in German
Prefer English?XRechnung validatorGermany's e-invoicing obligation: 2025, 2027 and 2028
France · Factur-X
Factur-X PDF for France?
The Factur-X validator also checks the PDF itself: the attached XML, the profile the French reform accepts and the PDF/A-3 metadata.
Netherlands · SI-UBL 2.0
SI-UBL 2.0 invoice for the Netherlands?
The validator applies the Dutch NLCIUS rules when a file declares SI-UBL 2.0. The SI-UBL checker explains each Dutch rule and runs entirely in your browser.
Peppol UBL check for CI
Free GitHub Action and CLI: fails the build when a generated invoice breaks one of 222 Peppol / EN 16931 rules. Offline, MIT.
On GitHub now; Marketplace listing coming soon