Is a PDF invoice an electronic invoice?

A PDF sent by email is electronic, but it is not a structured electronic invoice as defined by EU Directive 2014/55/EU or the EN 16931 standard. The EU definition requires machine-readable structured data — PDFs don’t meet this requirement because the data is encoded as visual text, not typed fields.

Can I still send PDF invoices in the EU?

It depends on the country and timeline. Belgium banned non-structured invoices for B2B from January 2026. Germany still allows PDFs during the transition period but mandates structured formats for sending from 2027–2028. France mandates structured formats from September 2026. B2C invoices can still be PDF in most countries.

What about ZUGFeRD and Factur-X — aren’t those PDFs?

ZUGFeRD and Factur-X are hybrid formats. They are PDF files — specifically PDF/A-3 — but with structured CII XML data embedded inside. The PDF provides the visual representation; the XML provides the machine-readable data. Because they contain structured data, they meet e-invoicing mandate requirements.

Why are PDFs being phased out for B2B invoicing?

Two reasons: processing cost and tax compliance. PDF invoices require manual processing or OCR, which is expensive and error-prone. Structured e-invoices enable automated tax reporting and reduce VAT fraud — which is why EU governments are mandating the switch.

How do I convert my PDF invoices to structured e-invoices?

You can’t reliably convert a flat PDF to a structured e-invoice — the structured data needs to come from your source system (ERP, accounting software). The approach is to update your invoice generation pipeline to output structured formats (Peppol BIS, XRechnung, Factur-X) from the original invoice data.

E-Invoice vs PDF: Why PDFs Are Being Phased Out Across the EU

Side-by-Side Comparison

Feature	Structured E-Invoice	PDF Invoice
Machine-readable	Yes — structured XML data (UBL or CII)	No — requires OCR or manual data entry
EU mandate compliant	Yes — meets EN 16931 requirements	No — not a structured e-invoice under EU Directive 2014/55/EU
Automated processing	Direct ERP ingestion, no human intervention	Manual entry or error-prone OCR extraction
Data accuracy	Exact — data is typed and validated	Depends on OCR quality or manual accuracy
Peppol delivery	Native — structured XML travels via Access Points	Not supported — Peppol requires structured data
Human readability	Requires a viewer or renderer (unless hybrid format)	Directly readable — looks like a paper invoice
Archival	XML + Evidence Pack for audit trail	PDF/A for visual archival (no structured data)
Validation	Automated against EN 16931, Peppol, country rules	Manual review only
Cross-border use	Standardized across 27+ EU countries	No standard — each PDF looks different
Cost of processing	€0.30-1.00 per invoice (automated)	€5-15 per invoice (manual processing)

Structured E-Invoice

A structured e-invoice is a machine-readable electronic document that follows the EN 16931 European standard. The invoice data is encoded in XML (either UBL 2.1 or CII D16B syntax) with typed fields: invoice number, issue date, line items, amounts, VAT breakdowns, and business identifiers. Software reads and processes this data directly — no interpretation, no OCR, no manual entry.

Common structured e-invoice formats: Peppol BIS 3.0 (UBL-based, pan-EU), XRechnung (UBL/CII, Germany), Factur-X/ZUGFeRD (CII in PDF/A-3, hybrid), FatturaPA (Italy-specific XML).

PDF Invoice

A PDF invoice is an electronic image of an invoice. It looks like a paper invoice on screen. The data is embedded as visual text — the characters "€1,234.56" are a string of pixels or font glyphs, not a typed decimal value that software can calculate with.

Sending a PDF by email is electronic, but it’s not a structured e-invoice. EU Directive 2014/55/EU and the EN 16931 standard explicitly exclude PDF from the definition of a structured electronic invoice. The reason: a PDF requires human interpretation or OCR to extract the data, which introduces errors and prevents automated processing.

Key Differences Explained

Structure vs. Image

An e-invoice is structured data. A PDF is an image of data. This is the fundamental difference. Software can read an e-invoice field by field. A PDF requires either a human or OCR — both introduce errors.

Mandate compliance

EU mandates (Belgium 2026, Germany 2025–2028, France 2026–2027) require structured e-invoices. PDFs sent by email don’t comply, even though they’re "electronic." The exception: hybrid formats like ZUGFeRD/Factur-X that embed structured XML inside a PDF/A-3 container.

Processing cost

Structured e-invoices flow directly into ERPs. PDF invoices require manual data entry or OCR extraction, then human verification. Industry estimates put manual PDF processing at €5–15 per invoice versus €0.30–1.00 for structured e-invoices.

Interoperability

Every structured e-invoice following EN 16931 has the same data fields in the same format, regardless of which country or ERP generated it. Every PDF looks different — different layouts, different field names, different positions. There’s no standardized way to extract data from an arbitrary PDF invoice.

When to Use Structured E-Invoice

·You’re invoicing B2B in Belgium (mandatory since January 2026)
·You’re invoicing B2B in Germany (reception mandatory, sending phased 2027–2028)
·You’re invoicing B2B in France (mandatory from September 2026)
·You need to send invoices via Peppol or another structured network
·You want automated processing without manual data entry

When to Use PDF Invoice

·B2C invoicing (consumer invoices are exempt from e-invoicing mandates)
·During explicit transition periods where PDF is still temporarily accepted
·Internal documents that don’t need to be processed by external systems
·As the visual layer of a hybrid format (ZUGFeRD/Factur-X — but the structured XML does the heavy lifting)

Can You Use Both?

Yes — that’s exactly what ZUGFeRD and Factur-X do. These hybrid formats embed structured CII XML inside a PDF/A-3 container. Open the file in a PDF reader and you see a normal invoice. Feed it to an ERP and the structured XML gets processed automatically. This is the practical bridge for businesses transitioning from PDF workflows to structured e-invoicing.