How How to Validate E-Invoices Works
E-invoice validation checks a document against three progressive layers:
Layer 1: XML Schema Validation
Is the document well-formed XML? Does it follow the correct schema (UBL 2.1, CII D16B, FatturaPA)? Are required XML elements present? This catches structural problems like missing tags, invalid data types, and malformed XML.
Layer 2: EN 16931 Business Rules
Does the invoice satisfy the European standard's business rules? Examples: BR-01 (invoice must have an invoice number), BR-CO-10 (sum of line amounts must equal invoice total), BR-S-08 (VAT breakdown must match line items). There are ~170 business rules in the core standard.
Layer 3: Country-Specific CIUS Rules
Does the invoice meet national requirements? Germany's XRechnung adds ~30 rules (like mandatory Leitweg-ID for B2G). Peppol BIS adds network-specific rules. Each country CIUS adds, tightens, or clarifies the base EN 16931 rules.
Invoice Navigator runs all three layers in a single API call, returns detailed error reports with fix guidance, and auto-remediates structural issues while preserving financial fields (amounts, VAT, IBANs are never modified).
According to Invoice Navigator’s analysis of over 50,000 validated invoices, the most common validation failures are missing buyer references (BR-10) and incorrect tax category codes (BR-CL-17).
Why How to Validate E-Invoices Matters
Validation before submission prevents:
- Rejection — Government portals (ZRE, SDI, KSeF) reject non-compliant invoices, causing payment delays
- Compliance risk — Invalid invoices may not satisfy VAT deduction requirements during tax audits
- Peppol delivery failure — The Peppol network validates at Access Points; non-compliant invoices are bounced
- Operational disruption — Rejected invoices require manual intervention, breaking automated invoice pipelines
According to Invoice Navigator's analysis of validation traffic, the most common error categories are missing required fields (35%), calculation mismatches (25%), and format-specific rule violations (20%).
How to Get Started
Get started with e-invoice validation in three steps:
- Try the free validator — Upload any e-invoice at invoicenavigator.eu/validator to see instant validation results against EN 16931 and country-specific rules.
- Explore the API — Follow the API quickstart to validate your first invoice programmatically. Average response time is under 500ms.
- Enable auto-remediation — Turn on auto-fix in your API calls to automatically correct structural errors. Review the Evidence Pack to see exactly what was changed.
Validate Your E-Invoice Now
Upload any e-invoice and get instant validation against 1,300+ rules. Free online validator — no signup required.
Start ValidatingContinue Learning
What is Peppol?
Peppol (Pan-European Public Procurement Online) is the dominant e-invoicing network in Europe. It’s a set of open specifications that define how businesses exchange electronic documents — invoices, credit notes, purchase orders — across borders, systems, and formats. Think of it as SMTP for invoices. Your ERP connects to a certified Access Point. The Access Point routes your invoice to the receiver’s Access Point. Both sides speak the same language (Peppol BIS Billing 3.0), regardless of what ERP, accounting system, or country either party operates in. Originally an EU-funded project launched in 2008 for public procurement, Peppol now covers B2B e-invoicing across 39+ countries with 300,000+ registered participants. As of 2026, Belgium, Germany, and Poland mandate Peppol for B2B transactions. France, Spain, and others are adding Peppol support alongside national systems.
What is Peppol?
Peppol (Pan-European Public Procurement Online) is the dominant e-invoicing network in Europe. It’s a set of open specifications that define how businesses exchange electronic documents — invoices, credit notes, purchase orders — across borders, systems, and formats. Think of it as SMTP for invoices. Your ERP connects to a certified Access Point. The Access Point routes your invoice to the receiver’s Access Point. Both sides speak the same language (Peppol BIS Billing 3.0), regardless of what ERP, accounting system, or country either party operates in. Originally an EU-funded project launched in 2008 for public procurement, Peppol now covers B2B e-invoicing across 39+ countries with 300,000+ registered participants. As of 2026, Belgium, Germany, and Poland mandate Peppol for B2B transactions. France, Spain, and others are adding Peppol support alongside national systems.
Read moreWhat is XRechnung?
XRechnung is Germany's national implementation (CIUS) of the EN 16931 European e-invoicing standard, mandatory for all public sector invoicing in Germany.
Read moreWhat is ZUGFeRD?
ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is a hybrid e-invoice format that embeds machine-readable XML data inside a PDF/A-3 document. Open the file in a PDF reader — you see a normal invoice. Parse the embedded XML — you get structured data that an ERP can process automatically. ZUGFeRD 2.x and Factur-X are the same specification. They unified in 2020. The only difference is the name: ZUGFeRD is the German branding, Factur-X is the French. The underlying XML is CII (Cross Industry Invoice) D16B syntax, and the embedded file is always named factur-x.xml. The current version is ZUGFeRD 2.3.2 (aligned with Factur-X 1.07.2), released in late 2024. It’s EN 16931-compliant and accepted as a valid e-invoice format under Germany’s B2B mandate.
Read more