What is E-Invoicing?

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:

1. XML schema validation — is the document well-formed?
2. EN 16931 business rules — are required fields present and correct?
3. 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.

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.

The fastest way to get started with e-invoicing:

1. Understand your obligations — Check the e-invoicing deadlines for your country. Are you required to receive, send, or both?
2. Choose your format — Use the Format Finder to determine which e-invoice format your country and trading partners require.
3. Validate a sample invoice — Upload an e-invoice to the free validator to see what compliance looks like.
4. Integrate validation — Add Invoice Navigator's API to your invoice pipeline. The quickstart guide gets you running in 5 minutes.