How E-Invoicing Works
E-invoicing works through structured data exchange. Instead of sending a PDF or paper invoice, the supplier's system generates an XML document following a standard format (like UBL or CII). This document contains all invoice fields — seller, buyer, line items, amounts, VAT, payment terms — in a machine-readable structure.
The invoice is then transmitted to the buyer either directly (email, API) or through a network like Peppol. The buyer's system automatically ingests the structured data into their ERP or accounting software — no manual data entry, no OCR errors.
Before transmission, invoices should be validated against three layers of rules:
- XML schema validation — is the document well-formed?
- EN 16931 business rules — are required fields present and correct?
- Country-specific CIUS rules — does it meet national requirements?
Invoice Navigator automates all three validation layers via API, auto-fixes structural errors, and provides timestamped Evidence Packs for audit compliance.
Why E-Invoicing Matters
E-invoicing is becoming mandatory across the EU because it:
- Closes the VAT gap — The EU loses an estimated €61 billion annually to VAT fraud and errors. Structured e-invoices enable real-time tax reporting and cross-checking.
- Reduces costs — Processing a paper invoice costs €15-30; an e-invoice costs under €1. For businesses processing thousands of invoices, savings are substantial.
- Eliminates errors — Manual data entry from PDFs has a 1-5% error rate. Structured data eliminates transcription errors entirely.
- Enables automation — Structured invoices can be automatically matched to purchase orders, routed for approval, and posted to accounting systems.
- Supports cross-border trade — EN 16931 provides a common language for invoices across all EU member states.
Invoice Navigator validates invoices against all major EU e-invoice formats, covering 1,300+ compliance rules across 27 member states.
Common mistakes when implementing e-invoicing:
- Confusing PDFs with e-invoices — A PDF sent by email is NOT an e-invoice. E-invoices must be in structured XML format (UBL, CII, or a CIUS like XRechnung).
- Using the wrong format for the country — Germany requires XRechnung, Italy requires FatturaPA, France uses Factur-X. Each country has specific requirements.
- Ignoring validation — Sending invoices that fail EN 16931 or country-specific rules leads to rejection, payment delays, and potential compliance issues.
- Not supporting hybrid formats — ZUGFeRD/Factur-X embeds XML inside PDF. Your parser needs to handle both standalone XML and PDF extraction.
How to Get Started
The fastest way to get started with e-invoicing:
- Understand your obligations — Check the e-invoicing deadlines for your country. Are you required to receive, send, or both?
- Choose your format — Use the Format Finder to determine which e-invoice format your country and trading partners require.
- Validate a sample invoice — Upload an e-invoice to the free validator to see what compliance looks like.
- Integrate validation — Add Invoice Navigator's API to your invoice pipeline. The quickstart guide gets you running in 5 minutes.
Validate Your First E-Invoice
Upload any e-invoice and get instant validation against EN 16931 and country-specific rules. Free, no signup required.
Try the ValidatorContinue Learning
How to Validate E-Invoices
E-invoice validation is the process of checking a structured electronic invoice against schema, business rule, and country-specific rule sets to ensure it is compliant before submission to the buyer or tax authority.
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