← All guides · Formats & conversion
PDF invoice vs e-invoice: why a PDF is no longer an invoice in much of the EU
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
A PDF invoice is a document a person reads. A structured e-invoice (EN 16931, sent as UBL 2.1 XML or embedded in a Factur-X PDF) is data your client's system validates and books automatically. In Italy a plain PDF has not counted as an invoice since 2019; Belgium, Poland, France, Germany and Spain all phase in the same position between 2026 and 2028 — after which a PDF alone gets rejected and payment stalls.
What counts as an e-invoice?
Under the European approach reflected in this product, an electronic invoice is an invoice issued in a structured electronic format that allows automatic processing — here, an EN 16931 invoice as UBL 2.1 XML, or the same XML embedded in a Factur-X PDF. A PDF without structured data, including a scanned paper invoice, is an electronic document but not a structured e-invoice.
The legal shift: from document to data
For decades an invoice was a document, and emailing a PDF felt like modernisation. Tax administrations and large buyers learned the limits of that: a PDF cannot be validated automatically, cannot be booked without retyping, and hides its figures in layout. The EU's mandates therefore define the invoice as data. Italy moved first, requiring B2B invoices through its SdI platform in structured form since 2019 — in the words of this product's mandate table, a plain PDF is not an invoice there.
The ViDA programme generalises the Italian lesson: intra-EU B2B structured invoicing becomes mandatory on 1 July 2030, and member states are moving earlier on their own timetables. The direction is one-way. Every year, more of your clients' systems will treat a lone PDF the way a web form treats a photograph of a filled-in form — as something that has to be transcribed before it exists.
What actually happens to a PDF in a mandate country
The rejection is mechanical, not personal. Your client's accounts system — or the platform their country requires — receives the file and looks for the structured invoice. Finding only a visual document, it cannot validate the business rules, cannot match VAT identifiers, and cannot book the payable amount. The invoice bounces, or sits in an exception queue, while your payment terms run from an issue date the client's system never accepted.
The acceptance checker on this site exists to predict that moment. Give it the invoice date, the buyer's country and the buyer's size class, and it computes the verdict from the mandate table: structured invoice required, PDF accepted until a stated date, or PDF still accepted. It is the same computation the converter stamps onto every conversion result, so the answer you check is the answer your invoice carries.
The countries, in mandate order
Italy is the settled case: SdI since 2019. Belgium's B2B mandate runs through Peppol from 1 January 2026. Poland's KSeF phases in from February 2026 for large taxpayers and April 2026 for everyone else. France requires all businesses to receive structured invoices from 1 September 2026, with SMEs issuing from 1 September 2027. Germany has required receiving since January 2025 and phases issuing in from January 2027 for turnover above EUR 800k, then all businesses from January 2028. Spain starts October 2027 for turnover above EUR 8M and October 2028 for the rest.
The other countries in the table — the Netherlands, Austria, Ireland, Sweden, Denmark and Portugal — have no domestic B2B issue mandate yet, though Portugal already requires structured invoices for B2G and Denmark is digitalising bookkeeping. Their backstop is the same: ViDA, 1 July 2030, for intra-EU B2B. A supplier who converts once, properly, is ready for every row of that table.
Why clients prefer data even where PDFs are legal
Mandates explain the floor, not the whole behaviour. Large buyers push structured invoicing ahead of the law because it pays: automatic booking removes retyping cost, rule validation removes query traffic, and clean data pays on time more often. If your biggest client asks for an e-invoice while their country's mandate is still a year away, they are not being bureaucratic — their payables process has already moved.
There is also a defensive reason to convert early. When a mandate lands, every supplier converts at once, and the errors surface in a rush — wrong VAT categories, missing identifiers, totals that do not reconcile. Converting while it is still optional lets you fix your template calmly, invoice by invoice, instead of debugging your billing under deadline with payments held.
The middle path: Factur-X, the PDF that carries data
If your clients love PDFs, the hybrid answers them. A Factur-X PDF looks and files exactly like the invoices they know, but it embeds the structured EN 16931 invoice as XML, byte-identical to the standalone UBL file. Their people read the document; their systems extract and book the data. Nobody has to change how they approve an invoice for the invoice to become data.
This is the output pair every conversion here produces: UBL 2.1 XML for systems and channels, Factur-X PDF for humans and files. Sending both covers every receiving process — and when a client upgrades their system mid-relationship, the XML they start ingesting is the same invoice they have been reading all along.
Moving your billing from PDF to structured
The move is smaller than it looks, because the data is the same invoice you already write. What changes is discipline: complete party addresses and VAT identifiers, one line per item with its own VAT category and rate, and totals computed from the lines rather than typed. Validation then proves each invoice against the EN 16931 core rules before it leaves.
Start with one live invoice through the free converter, then check each client's country in the acceptance checker and note their date. By the time a mandate reaches your client base, structured invoicing is already your routine — and your invoices are the ones that get booked and paid while competitors' PDFs sit in exception queues.
Is your invoice a document or data? 5 checks
- Open your last invoice: if the only file is a PDF with no embedded XML, it is a document, not structured data.
- Run the acceptance checker for each EU client's country and record the date a PDF alone stops being accepted.
- Check your invoice data for the fields systems validate: VAT identifiers, complete addresses, per-line VAT categories and rates.
- Convert one invoice and compare the Factur-X PDF (what people read) with the UBL XML (what systems book).
- Set your template so totals are always computed from lines — never typed — before the next billing run.
Worked example: the same invoice, two fates
A software freelancer invoices a Belgian client EUR 2,400.00 for brand identity design, reverse charge (category AE, 0%), payable EUR 2,400.00. Sent as a plain PDF in 2026, it lands in a country where the Peppol B2B mandate has run since 1 January 2026: the client's system needs the structured invoice, and the PDF waits in an exception queue while the freelancer chases payment.
Sent as the converted pair — UBL XML plus Factur-X PDF — the same EUR 2,400.00 invoice validates against the EN 16931 rules, the reverse-charge line is supported by the buyer's VAT identifier on the invoice, and the client's system books it on arrival. Same work, same price, same client: the format decided whether the invoice existed.
Frequently asked questions
Is an emailed PDF legally an invoice?
In countries without a structured mandate, generally yes as a document. Where a B2B structured mandate is in force — Italy since 2019, Belgium from 2026 — a plain PDF does not satisfy the invoicing obligation and is rejected.
What about a scanned paper invoice?
A scan is a picture of a document: no structured data, so it has the same problem as a born-digital PDF, plus OCR errors. It is not an EN 16931 e-invoice.
Do I have to stop sending PDFs entirely?
No — send the Factur-X PDF, which is a PDF carrying the structured invoice inside it, alongside the UBL XML. Humans keep their document; systems get their data.
When does my country change?
Use the acceptance checker: it computes the verdict from the mandate table for 12 countries — invoice date, buyer country and buyer size — including the 1 July 2030 ViDA backstop.
What does converting cost?
One invoice conversion and the checker are free. Pro ($19/month) covers bulk runs of up to 200 invoices, country rule packs, monitored clients and accounting exports.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- What is a Factur-X invoice? The PDF with the invoice inside it
- What is EN 16931 and why does your invoice need to follow it?
- Belgium's Peppol e-invoicing mandate: what B2B suppliers must do from 2026
- Italy's SdI e-invoicing: the mandate that has run since 2019
- Will my client accept a PDF invoice? How to know before you send