Why a PDF invoice is not an e-invoice

A PDF invoice is not an e-invoice. A PDF is a document made for people to read, while an e-invoice is structured data, such as a UBL file that follows the European standard EN 16931, which the customer's software can read field by field without anyone retyping it.

The confusion is understandable: a PDF is electronic, and you send it electronically. But the EU definition looks at the format, not the delivery method. An electronic invoice is one issued, transmitted and received in a structured format that software can process. An emailed PDF fails that test, however tidy it looks.

PDF vs e-invoice at a glance

	PDF invoice	Structured e-invoice
Made for	People	Software
Contents	Text and layout on a page	Named fields: seller, buyer, lines, VAT, totals
At the customer	Someone reads it and types the data in	Their system reads the fields directly
Checks	A person spots mistakes, or doesn't	Rules validate the file before or on arrival
Usual delivery	Email	A network such as Peppol

What makes an invoice structured

Three layers work together:

• The data model. EN 16931 is the European standard that says which information an invoice holds and what each piece means, from the seller's VAT number to each line's tax category. It does not prescribe a file format itself.
• The syntax. The data is written in an XML format. EN 16931 can be carried in UBL 2.1 or in the UN/CEFACT Cross Industry Invoice. The guide to EN 16931 explained goes into the fields.
• The specification and network. Peppol BIS Billing is a Peppol specification built on EN 16931 and sent as UBL. The Peppol network moves those files between businesses through access points. If the network is new to you, start with what Peppol is.

Why the difference matters

• No retyping. According to the European Commission, PDF and other visual formats still need someone to look at the invoice and enter its data by hand. A structured invoice skips that step.
• Fewer errors. A wrong VAT number or a total that doesn't add up can be caught by validation rules, not by a tired person on a Friday.
• The law, in more and more places. Several countries now require structured invoices between businesses, each on its own timetable. Belgium is one: see Belgium's B2B e-invoicing mandate. Where a mandate applies, a PDF by email generally no longer counts as the invoice.

Is a PDF still useful?

Yes, as a copy. People like to read an invoice, and a well-designed PDF is the easiest way to do that. A receiver may also turn an incoming e-invoice into a PDF for reading. The point is which file is the invoice. Where structured invoicing is required, the e-invoice is the record and the PDF is a courtesy. The piece on invoice layouts covers what makes that readable copy clear.

You may also meet hybrid formats that put an XML file inside a PDF. Whether they satisfy a given country's rules depends on that country, so check before relying on one. When choosing software, check that it produces the structured invoice itself and not just a PDF with the data printed on it, and read each invoice through once before it goes; the invoice checklist helps.

How to tell which one you are sending

A few quick questions settle it for your own invoices:

1. What is the file? If the attachment ends in .pdf and nothing else travels with it, it is a PDF invoice.
2. How does it travel? An e-invoice on the Peppol network goes from your access point to your customer's, not from your mailbox to theirs.
3. What does the customer do with it? If someone on their side types your invoice into their system, they received a document, not data.
4. Does your software validate it? Software that produces e-invoices checks the required fields before sending and tells you what is missing.

If the answers point to a PDF, the move to e-invoicing starts with clean customer data: correct VAT numbers, legal names and addresses. Those fields end up in the structured file and are checked on the way, so errors that a person used to overlook now stop an invoice. Fixing them before you switch saves a round of rejected invoices later.

Frequently asked questions

Is an invoice sent by email an e-invoice?

Not under the EU definition if it is a PDF or an image. Email is a delivery method; what counts is whether the invoice is structured data that software can process.

Is a scanned paper invoice an e-invoice?

No. A scan is a picture of a paper document. Someone still has to read it, even if text recognition helps.

What file format is a Peppol invoice?

An XML file in UBL syntax, following the Peppol BIS Billing specification, which builds on EN 16931.

Can an e-invoice include attachments?

Generally, yes. Peppol BIS Billing lets supporting documents, such as a timesheet or a delivery confirmation, travel with the invoice as attachments. Your provider or your customer may set limits on size or file types, so check before relying on large files.