Zeppol / Guides

What is an e-invoice?

Last updated 3 September 2026

Short answer: an e-invoice is an invoice a computer can read — structured data, normally XML, in a format both sides have agreed on. That is the whole idea, and it is why the PDF you email your customers does not count. This page explains what actually makes an invoice "electronic", what all the acronyms mean, why European governments are making it compulsory, and what it means if you sell on Shopify.

The definition, in one paragraph

In the EU the term has a legal meaning, set out in Directive 2014/55/EU and pinned down by the EN 16931 standard. An e-invoice is an invoice that is issued, transmitted and received in a structured electronic format which allows it to be processed automatically and electronically. Two words carry all the weight: structured (the data sits in defined fields, not in a picture of a page) and automatically (the buyer's system can book it without a human re-typing anything).

E-invoice vs PDF vs paper

Most merchants assume they already send e-invoices, because they stopped posting paper years ago. Under the mandates, emailing a PDF sits in the same box as posting a letter — it is a document made for a human, and that is exactly what the rules are moving away from.

There is one honest exception. In a hybrid format — ZUGFeRD in Germany, Factur-X in France — a compliant XML file is embedded inside the PDF. The file looks like an ordinary PDF when you open it, but the machine reads the XML hidden in it. That qualifies. A PDF exported from a Shopify invoice app does not, because there is nothing inside it to read.

What's actually in an e-invoice

Open one in a text editor and you find no layout at all — no logo, no font, no column widths. Just labelled data: who sold, who bought, VAT numbers, one block per line item with quantity, unit price and tax category, a VAT breakdown grouped by rate, and totals. Roughly like this, stripped down:

Because it is data rather than a picture, it can be checked before it is sent. That is the part people underestimate: an e-invoice is not just formatted, it is validated. If a required field is missing, if the VAT category is wrong for a cross-border B2B sale, or if the totals are a cent out, the document fails the rules and gets rejected — by the network, the tax authority, or the buyer's system.

EN 16931: the standard underneath everything

For invoices to be readable across borders, everyone has to agree on which fields exist and what they mean. That agreement is EN 16931, the European standard for the semantic model of a core invoice. Every European e-invoicing format you will meet is a way of expressing it.

One distinction is worth fixing in your head early, because it causes most of the confusion: format is not delivery. EN 16931 and its profiles say what the document contains. Peppol is the network that carries it from you to the buyer — think of the format as the letter and Peppol as the postal system. Compliance usually means getting both right. If you want the layer-by-layer version, we wrote one: EN 16931 explained.

Why governments are mandating it

Not for your convenience. The driver is the VAT gap — the difference between VAT owed and VAT actually collected, which runs into tens of billions of euros a year across the EU. Structured invoices give tax authorities transaction data in a consistent, checkable shape, close to the moment it happens, instead of a paper trail reconstructed after the fact. Fraud gets harder; audits get cheaper.

The rollout, in the order it actually happened and is happening:

Two things follow from that table. First, the direction is one-way — no country has reversed course. Second, receiving comes before sending: you are usually obliged to accept e-invoices a year or more before you are obliged to issue them, which is the window most sellers sleep through. Germany is the sharp end, and we've laid out the dates in detail in Germany's 2027 B2B e-invoicing mandate.

What this means if you sell on Shopify

If you only sell B2C, the mandates are mostly not aimed at you — they target business-to-business (and business-to-government) invoicing. If you sell B2B into the EU, or you have a handful of business customers buying through the same storefront, this lands on you.

Shopify, out of the box, cannot produce an e-invoice. Specifically, nothing in the platform:

• maps an order into the EN 16931 fields in UBL or CII,
• applies a national profile such as XRechnung, or builds a ZUGFeRD hybrid PDF,
• validates the document against the EN 16931 business rules, or
• delivers it over Peppol and tracks whether it arrived.

Most "invoice" apps in the Shopify ecosystem are invoice design tools — they make a branded PDF, which is a genuinely useful thing and not the thing a mandate asks for. The gap between a beautiful PDF and a valid e-invoice is where merchants get caught.

And the hardest part is not the XML. It is the numbers. Whether your Shopify prices include or exclude tax changes how net and VAT are derived; rounding can leave you a cent off, which is enough for a validator to reject the document; and selling to a VAT-registered business in another EU country usually means reverse charge — 0% VAT with the correct category code and legal note, and the buyer's VAT number checked against VIES. Get the format right with the numbers wrong and you have an invoice that fails cleanly instead of messily.

Go deeper

• EN 16931 explained — the standard behind XRechnung, ZUGFeRD and UBL, layer by layer.
• Peppol for Shopify — what the network is and how a store connects to it.
• Germany's 2027 B2B e-invoicing mandate — the dates, the formats, and what merchants must do.

Frequently asked questions

This guide is general information for Shopify merchants, not legal or tax advice. Rules, mandates and thresholds vary by country and change over time — confirm your obligations with a qualified tax adviser.