Compare · Structured E-Invoice vs PDF Invoice
E-Invoice vs PDF: Why a PDF Is Not a Structured E-Invoice
EU e-invoicing mandates require structured, machine-readable invoice data. A PDF — even one sent by email — does not meet this requirement. Here’s why the distinction matters and what it means for your invoice pipeline.
TL;DR
- Use Structured E-Invoice if: When you need to comply with EU e-invoicing mandates, automate invoice processing, or send invoices via Peppol or other structured networks.
- Use PDF Invoice if: When you’re sending invoices to consumers (B2C), where mandates don’t apply, or during transition periods where PDF is still temporarily accepted.
- Use both if: ZUGFeRD and Factur-X combine both: a visual PDF with embedded structured XML. This is the bridge format — human-readable and machine-processable in one file.
| 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) |
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).
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.
Structure vs. Image
Mandate compliance
Processing cost
Interoperability
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
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)
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.
Upload any invoice — PDF, UBL, CII, ZUGFeRD — and see if it passes EU validation rules.
Checking is free. The first verified download every 30 days is free. After that €1.90 per invoice, or €9 a month for all of them.
Frequently Asked Questions
- 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.