How to Validate E-Invoices

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).

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%).

Get started with e-invoice validation in three steps:

1. Try the free validator — Upload any e-invoice at invoicenavigator.eu/validator to see instant validation results against EN 16931 and country-specific rules.
2. Explore the API — Follow the API quickstart to validate your first invoice programmatically. Average response time is under 500ms.
3. 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.