E-Invoice vs PDF Invoice: What Counts as an E-Invoice?

Quick answer: E-invoice vs PDF comes down to structure. An e-invoice is a structured data file, such as UBL or CII XML following EN 16931, that software can read and process automatically. A PDF is a picture of an invoice for people to read. Under e-invoicing mandates in Germany, France, Belgium, Poland and elsewhere, a PDF is not an e-invoice, even when emailed.

Lots of businesses describe their emailed PDF as an "electronic invoice", and in everyday language it is. The problem is that tax authorities now use the term in a narrower, technical sense. This article explains what an e-invoice is, where a PDF still counts, and how hybrid formats sit in between. If you still mostly send PDFs, our free invoice generator creates them in your browser; just know where they stop being enough.

What is an e-invoice?

The clearest definition comes from the EU's public procurement Directive 2014/55/EU: an electronic invoice is "an invoice that has been issued, transmitted and received in a structured electronic format which allows for its automatic and electronic processing". Three elements matter:

• Structured: every value sits in a defined field (seller VAT number, invoice number, line amount) rather than in free text on a page.
• Machine-readable: the buyer's software can import it without a person retyping or a scanner guessing.
• End-to-end electronic: issued, sent and received as data, not printed and scanned along the way.

Germany, France, Belgium, Croatia and the 2030 EU ViDA rules all use this structured definition. See our e-invoicing guide for the bigger picture.

Why tax authorities want structured invoices

With PDFs, the tax authority only sees invoice data much later, in summarised VAT returns or during an audit. With structured e-invoices, the data can be checked automatically and, in many systems, reported in real time. That makes it easier to spot missing trader fraud, fake invoices and mismatches between what a seller declares and what a buyer deducts. For businesses, the promised benefit is faster processing: no retyping, fewer disputes over unreadable scans, automatic matching to purchase orders, and in some countries pre-filled VAT returns. Whether you feel those benefits depends on your software, but the direction of travel is clear in almost every mandate.

Is a PDF invoice an e-invoice?

Under the current general EU VAT rules, a PDF sent by email is an "electronic invoice" because the VAT Directive defines it broadly as an invoice issued and received in any electronic format. That is why PDFs have been legally fine across Europe for years.

Under e-invoicing mandates, the answer is no. A PDF is an unstructured document. Germany calls it an "other invoice" (sonstige Rechnung), and from the dates in each mandate it is no longer acceptable for in-scope domestic B2B sales. The EU's ViDA reform brings the VAT Directive in line with the structured definition from 2030.

E-invoice vs PDF invoice: side-by-side comparison

	Structured e-invoice	PDF invoice
What it is	Data file (XML or JSON) with defined fields	Fixed-layout document
Read by	Software first, people via a viewer	People first, software via OCR
Standards	EN 16931, UBL 2.1, UN/CEFACT CII, Peppol BIS Billing 3.0, national formats	None for content (PDF/A for archiving)
Sent via	Peppol, platforms, tax authority systems, sometimes email	Email, portal upload, post
Validation	Automatic checks against business rules	Manual review
Meets mandates?	Yes, if the right format and channel	No, where a mandate applies
Cost to create	Needs compatible software	Free tools available
Best for	B2B and B2G in mandate countries, high-volume buyers	B2C, small clients, countries without mandates

What is EN 16931 and why does it matter?

EN 16931 is the European standard for the core content of an electronic invoice, published by the European Committee for Standardization (CEN). It defines a semantic data model: a list of business terms, each with a code such as BT-1 (invoice number), and rules about which are mandatory. It allows two syntaxes, UBL 2.1 and UN/CEFACT CII. National formats such as XRechnung (Germany), Peppol BIS Billing 3.0 and the Croatian HR CIUS are specifications (CIUS) built on top of it. Our EN 16931 e-invoice template guide lists the fields.

Common e-invoice formats by country

"E-invoice" is a category, not a single file type. Each mandate names the formats it accepts:

Country or network	Format	Syntax	Type
Peppol countries (Belgium, Norway, Australia and others)	Peppol BIS Billing 3.0, PINT	UBL	Pure XML
Germany	XRechnung; ZUGFeRD 2.x	UBL or CII; CII in PDF/A-3	XML; hybrid
France	Factur-X, UBL, CII	CII in PDF/A-3; UBL; CII	Hybrid or XML
Italy	FatturaPA	National XML	Pure XML via SdI
Poland	FA(3) structured invoice	National XML	Pure XML via KSeF
Spain (public sector)	Facturae	National XML	Pure XML
Saudi Arabia	ZATCA e-invoice	UBL 2.1	XML, or PDF/A-3 with XML
India	GST e-invoice schema	JSON	Registered on the IRP for an IRN

Several of these are national, older than EN 16931 or outside the EU, so they do not all follow the European model. Under ViDA, EU systems are expected to converge on EN 16931-compatible data. The practical rule: your software must produce the exact format your country (or your customer) requires, and a PDF view alone is never enough where a mandate applies.

Hybrid invoices: Factur-X and ZUGFeRD

Hybrid formats combine both worlds: a PDF/A-3 file with the structured XML embedded inside. People open the PDF; software reads the XML. In Germany and France, a hybrid invoice counts as an e-invoice if the XML uses a sufficiently complete profile (for example EN 16931 or higher). If the PDF and the XML disagree, the XML is the legal invoice. For format detail, see XRechnung vs ZUGFeRD.

Worked example: the same invoice as PDF and as structured data

A Dublin consultancy invoices a Brussels client for a strategy workshop. On the PDF, the reader sees a logo, addresses and a table. In the e-invoice, each value has a business term code:

What you see on the PDF	EN 16931 business term	Value
Invoice No.	BT-1 Invoice number	INV-2027-0042
Date	BT-2 Invoice issue date	2027-03-15
Currency	BT-5 Invoice currency code	EUR
From	BT-27 Seller name; BT-31 Seller VAT identifier	Consultancy name; IE VAT number
Bill to	BT-44 Buyer name; BT-48 Buyer VAT identifier	Client name; BE VAT number
Workshop, 2 days at €1,600	BT-129 quantity, BT-146 net price, BT-131 line net amount	2 × 1,600 = 3,200.00
Subtotal	BT-106 Sum of invoice line net amount	3,200.00
VAT (reverse charge)	BT-110 Invoice total VAT amount, VAT category AE	0.00
Total due	BT-112 total with VAT; BT-115 amount due	3,200.00

The maths is the same on both: 2 days × €1,600 = €3,200, and because it is a cross-border B2B service under the reverse charge, VAT on the invoice is €0 and the Belgian client accounts for VAT at its local rate. The difference is that the client's software can post the e-invoice automatically, while the PDF needs someone to key in or check every number. Wording for the reverse charge line is in our reverse charge invoice guide.

When is a PDF invoice still fine?

• Sales to consumers (B2C) in most countries
• Countries without a B2B mandate, including the US and UK as of October 2026
• Small businesses during transition periods, for example German businesses under €800,000 until the end of 2027 (see Germany e-invoicing 2027)
• Most cross-border invoices until ViDA applies in 2030
• Quotes, proformas, statements and receipts, which are not tax invoices

When do you need a real e-invoice?

• Domestic B2B sales in a country whose mandate covers you (Belgium, Poland, Croatia, Italy, Germany from 2027/2028, France from 2026/2027)
• Invoices to public authorities in most EU countries (B2G)
• Clearance countries such as Saudi Arabia, India above the turnover limit and Malaysia
• Any customer who contractually requires Peppol or a specific format; see what Peppol is

Common mistakes about e-invoices

• Calling a PDF from accounting software an e-invoice. The software matters less than the file format.
• Sending a hybrid with a minimal profile. Germany does not accept MINIMUM or BASIC WL as e-invoices.
• Archiving the PDF view only. Keep the original XML; see how long to keep invoices.
• Editing the PDF after creating the XML. The two then disagree and the XML wins.

Checklist: is your invoice an e-invoice?

• Is it a structured file (XML or JSON), not just a PDF or image?
• Does it follow EN 16931 or the national format required?
• Does it pass validation (no missing mandatory fields)?
• Was it sent through the required channel (Peppol, platform, authority)?
• Is the original structured file archived unaltered?

Next step

If you are in a mandate country, check your deadline in our e-invoicing mandates 2027 list and choose software that issues structured invoices. If you are not, a clean PDF still does the job; pick a layout from our invoice templates and make it in a few minutes.