Zeppol / Guides

Shopify B2B invoicing in the EU: mandates, formats and deadlines

Last updated 27 August 2026 · mandate status checked against each country's own page and primary sources on 27 August 2026

Selling B2B from Shopify into the EU is quietly becoming a compliance job. One country after another is making structured e-invoices mandatory, and the PDF your store emails today does not count. This is the overview page: which countries, which dates, which formats, how invoices actually travel, and the VAT details that decide whether they are accepted.

What “e-invoicing” actually means here

An e-invoice is not a PDF, and not an emailed order confirmation. It is structured data, a machine-readable file whose fields (seller, buyer, VAT numbers, line items, tax breakdown, totals) follow the European standard EN 16931. Your buyer's accounting software reads it directly, validates it, and books it without anyone retyping anything.

That is the whole shift. A beautifully designed PDF invoice is, to a compliance system, a picture of an invoice. When a mandate says “e-invoice”, it means the structured file.

Where the EU mandates stand

Each country sets its own timetable and its own delivery model, so what applies to you depends on where your business and your buyer are established. Two models are running in parallel: some countries route invoices over the shared Peppol network, others clear every invoice through a national tax-authority platform that Peppol does not reach. The eight markets a Shopify B2B store most often sells into, and the EU-wide rule behind all of them:

The format stack, untangled

The names look like competing choices. They are not, they sit at different layers, all pointing back to the same standard:

• EN 16931: the European standard defining what an e-invoice must contain and the rules the data must satisfy. See EN 16931 for Shopify.
• UBL and CII: the two permitted XML syntaxes, i.e. how that data is written into a file.
• XRechnung: Germany's pure-XML profile of EN 16931. See XRechnung for Shopify.
• ZUGFeRD (and its French twin Factur-X): a hybrid, a normal-looking PDF with the EN 16931 XML embedded inside it, so a person and a machine read the same file. See ZUGFeRD for Shopify and Factur-X for Shopify.
• Peppol BIS Billing 3.0: the profile used for invoices sent across the Peppol network.

So when a buyer asks for “an XRechnung”, “a ZUGFeRD” or “UBL over Peppol”, they are asking for the same invoice underneath, packaged the way their country or software expects.

How the invoice reaches your buyer

A common misconception is that compliance means joining Peppol. Most mandates specify the format, not the channel: Germany, for instance, accepts a ZUGFeRD invoice delivered by email where the buyer agrees. Peppol is the right answer when your buyer is on the network, which is standard in Belgium and increasingly expected by larger buyers everywhere. See what a Peppol access point is for how the network actually works.

Peppol delivery is also asynchronous: an invoice is submitted, then travels, then is handed to the buyer's Access Point, which signs a receipt for it. That receipt proves the receiving end took custody. It does not say the buyer agreed with the invoice, and Peppol's Message Level Status reports transport, never business acceptance, so anything promising to track acceptance is promising something the network does not carry.

What Shopify gives you, and what it doesn't

Shopify handles the commerce side well: B2B customers, company profiles, price lists, tax settings. What it does not do is produce a compliant e-invoice. There is no EN 16931 output, no XRechnung or ZUGFeRD, no Peppol connection, and no record of what was delivered. The gaps a B2B merchant runs into:

• No structured invoice file. Order confirmations and PDF invoices are not EN 16931 documents. See what an e-invoice actually is.
• No buyer identity data. An e-invoice needs the buyer's company details, VAT number and, for Peppol, their Peppol ID. Standard checkout does not collect them.
• No validation. A rejected invoice is a compliance failure you only learn about later, unless something validates before sending.
• No B2B/B2C separation at invoice time. The mandates apply to business orders only, so the split has to be reliable.

The part that quietly breaks invoices: VAT

Format problems are obvious and easy to fix. VAT problems are neither, and an EN 16931 invoice is validated, so numbers that do not add up to the cent get the invoice rejected. The usual suspects for a Shopify store:

• Tax-inclusive vs tax-exclusive pricing changes how net and VAT are derived from the same order total. See tax-included vs tax-excluded pricing on Shopify.
• Rounding at line level versus document level can leave net plus VAT a cent away from gross, enough to fail.
• Cross-border B2B to a VAT-registered business in another EU country is normally reverse charge: 0% VAT plus the correct legal note on the invoice. See reverse charge VAT on Shopify.
• The buyer's VAT number should be validated against VIES before you rely on it. An invalid number can put the zero-rating itself at risk. See VIES VAT validation for Shopify.

Get these wrong and the invoice is non-compliant even when the XML is perfect.

A short readiness checklist

• Do you know which of your orders are B2B, at invoice time?
• Do you hold the buyer's company name, address and VAT number, and their Peppol ID where relevant?
• Can you produce an EN 16931 invoice in the format your buyer's country expects?
• Is your VAT treatment right per order, including reverse charge and VIES validation?
• Can you deliver by email and over Peppol, and show a receipt for each handover?
• Can you receive e-invoices where that is already required, such as Germany?

This page is the mechanism: how the invoice is put together and what has to be on it. For the calendar, country by country, see the EU e-invoicing mandate table.

Go deeper

Each country's own mandate, in detail:

• Germany's 2027 B2B e-invoicing mandate: dates, XRechnung vs ZUGFeRD, and what Shopify merchants must do.
• Belgium's Peppol mandate: what it requires, and by when.
• Peppol in the Netherlands: voluntary today, and what the 2030 to 2032 proposal would change.
• France's e-invoicing mandate: who must receive, who must issue, and what an approved platform is.
• Spain's Crea y Crece mandate: what Royal Decree 238/2026 actually settles, and what is still a draft.
• Italy's SdI mandate: why it is not Peppol, and who is outside it.
• Poland's KSeF mandate: who it reaches, and who it explicitly does not.
• Romania's RO e-Factura mandate: the same standard as Germany, a different delivery route.
• ViDA, the EU-wide rule behind all of them: what changes from 2030.

Format and VAT detail:

• A focused Sufio alternative for EU Peppol e-invoicing: how a compliance-first tool differs from an invoice-design app.
• VIES VAT validation for Shopify: how to check an EU buyer's VAT number before you zero-rate the invoice, and what to keep as evidence.
• Shopify VAT-exempt B2B orders: when zero-rating is correct, and what evidence to keep.

Frequently asked questions

This guide is general information for Shopify merchants, not legal or tax advice. Mandate dates, thresholds and national rules change, and edge cases exist. Confirm your own obligations with a qualified tax adviser, and check each country's own page above for the primary sources behind its dates.