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

Last updated 26 July 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, so what applies to you depends on where your business and your buyer are established. The picture for the markets a Shopify B2B store most often sells into:

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.
• 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.
• 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.
• 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 the Nordics, and increasingly expected by larger buyers everywhere.

Peppol delivery is also asynchronous: an invoice is submitted, then travels, then is delivered and accepted. “Sent” is not “accepted”, and a serious setup tracks the difference instead of assuming it.

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 delivery or acceptance tracking. The gaps a B2B merchant runs into:

• No structured invoice file — order confirmations and PDF invoices are not EN 16931 documents.
• 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.
• Rounding at line level versus document level can leave net + 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.
• 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.

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 see what was accepted?
• Can you receive e-invoices where that is already required, such as Germany?

Go deeper

• Germany's 2027 B2B e-invoicing mandate — dates, XRechnung vs ZUGFeRD, and what Shopify merchants must do.
• A focused Sufio alternative for EU Peppol e-invoicing — how a compliance-first tool differs from an invoice-design app.

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.