Guide

EU E-Invoicing 2026: A Country-by-Country Guide for Shopify Sellers

Updated 2026-06-13

If you sell across the European Union from a Shopify store, 2026 is the year e-invoicing stops being a future problem and becomes a calendar problem. Several large markets are switching, on different dates, to invoices that software can read automatically. The rules are not identical from country to country, but they share one backbone: the European standard EN 16931. This guide walks through where EU e-invoicing 2026 actually stands, country by country, what the shared standard means in practice, where the EU is heading next under ViDA, and one point that causes a lot of needless worry. In Germany, no certification of your invoicing software is required.

This is a practitioner overview, not tax advice. Where your specific setup matters (where you are established, where you are VAT-registered, who your customers are), confirm the details with your accountant.

What “e-invoice” means in 2026

Across the EU, an e-invoice is not a PDF you email. It is an invoice issued in a structured electronic format that another system can process without a human re-keying it. The reference point is EN 16931, the European semantic standard for the core invoice. It defines the meaning of each field (the business terms), while the actual file is written in one of two technical syntaxes, UBL or UN/CEFACT CII.

Two formats dominate the German-speaking and French markets, and both map to EN 16931:

One detail trips people up with ZUGFeRD and Factur-X. It ships in profiles (MINIMUM, BASIC-WL, BASIC, EN 16931, EXTENDED). Only BASIC and upward carry a full VAT invoice and satisfy the German mandate. MINIMUM and BASIC-WL do not. If a tool says it “supports ZUGFeRD”, ask which profile it generates.

Germany: receiving since 2025, issuing in two steps

Germany’s mandate covers domestic B2B supplies (both parties established in Germany). As of June 2026 the timeline is fixed, with no delays announced:

From the relevant date, a plain PDF no longer counts as a B2B e-invoice in Germany. It becomes an “other invoice” that does not satisfy the mandate.

If you sell into Germany from abroad without a German establishment, the domestic mandate does not directly oblige you to issue. But your German business customers increasingly expect EN 16931 invoices because their own accounting is being rebuilt around them, and if you do hold a German establishment or German VAT registration with domestic supplies, get specific advice. For the full German picture, see our Shopify e-invoicing Germany guide.

France: receiving for all in 2026, issuing in two waves

France is running its own reform on a different clock, and it splits the obligation into two parts:

France uses Factur-X (the twin of ZUGFeRD), so a single hybrid invoice format serves both the German and French mandates. The French model also introduces transmission through accredited platforms called PDP (Plateforme Agréée). That accreditation requirement sits on the transmission platform, not on the software that generates the invoice. Your invoice generator does not need to be accredited to produce a valid Factur-X file. The routing partner is the accredited piece.

The shared backbone: EN 16931

The reason these mandates rhyme is EN 16931. It is the common semantic model behind XRechnung, ZUGFeRD, Factur-X, and the formats used in other EU mandates. Build your invoices around the EN 16931 business terms and the tax treatment that goes with them, and you are aligned with multiple markets at once rather than rebuilding per country.

That tax treatment is part of getting it right. EN 16931 carries category codes for each scenario a cross-border Shopify seller meets:

For B2C distance sales inside the EU, the One-Stop-Shop (OSS) applies once you cross the EU-wide EUR 10,000 threshold. From the crossing transaction you charge the destination country’s VAT rate and report it through OSS, rather than your home rate. An e-invoice is rarely legally required for those consumer sales, but most merchants issue one anyway because customers expect it.

Do you actually need to certify your software? In Germany, no

This is the point that generates the most anxiety and the most misinformation, so it is worth stating plainly. EN 16931 is a standard verified by validating the document, not by certifying the software that made it. The legal duty to issue a correct invoice belongs to the merchant. A tool issuing in the merchant’s name is a delegate, not a regulated entity. Where any accreditation exists, it usually attaches to the transmission layer, not the generator.

Here is the certification picture for the markets a Germany-first seller cares about:

MarketSoftware certification needed?Where the requirement sits
GermanyNoGoBD is principles-based, and the tax authority does not certify invoicing software. The mandate requires the EN 16931 format, full stop.
EU general / AustriaNoNo EU software-certification regime. Austria’s cash-register rules target cash at the point of sale, not online orders.
PeppolNo (for end users)The Access Point operator is accredited. A seller routing through a third-party Access Point is not.
ItalyNoThe SdI clearance system validates the files. The transmission channel is accredited, not the generator.
FranceNo for generationPDP accreditation belongs to the transmission partner. A caveat exists for anti-fraud certification of software that records B2C cash receipts, which a Shopify order invoicer can stay out of by not recording merchant cash takings.
SpainYes (vendor self-declaration)Under Veri*Factu, the software producer files a “declaración responsable”. Only relevant if you produce Spanish SIF records for Spanish merchants.
PortugalYes (full product certification)The tax authority certifies the software product itself (cert number, ATCUD, QR on every invoice, SAF-T). The strongest gate in the EU.
Shopify App StoreNoStandard app review, with no tax-compliance credential to list.

The two genuine exceptions are Portugal (full product certification) and Spain (producer self-declaration). They are real, but they only bite if you produce native Portuguese or Spanish invoicing records for merchants established there. For a Germany-first, EN 16931 and Peppol-routed business, there is no software certification to obtain. The honest, practical move for Portugal is to route through an already-certified local provider rather than self-certify.

Where this is heading: ViDA

The EU’s direction of travel is VAT in the Digital Age (ViDA), the reform package steering the bloc toward structured e-invoicing and digital reporting for cross-border B2B as the default over the coming years. The dates and details continue to be finalised, so treat ViDA as a direction rather than a deadline you can pin today. The practical takeaway does not change. If you are already issuing EN 16931 invoices with correct VAT treatment and keeping the original files, you are building on the foundation ViDA assumes, not against it.

Archiving: keep the original

One rule survives every format change. Keep the original e-invoice file, not a re-rendered copy. For a ZUGFeRD or Factur-X invoice the original is the file with the embedded XML, and for XRechnung it is the XML itself. In Germany the GoBD framework requires invoices to be kept unchanged for at least 8 years (the legal minimum since 2025), and corrections are made by issuing credit notes, never by editing or deleting the original.

A sensible 2026 plan for a Shopify seller

  1. Now: make sure you can receive and archive incoming e-invoices (already required for German businesses, and for all French businesses from September 2026), and check that your current invoices carry the legally required content.
  2. Pick formats: ZUGFeRD or Factur-X in the EN 16931 profile for B2B customers (they still see a readable PDF), and XRechnung for German public-sector buyers.
  3. Capture data at checkout: VAT IDs for B2B (validated against VIES) and the Leitweg-ID for German public-sector orders, so you are not chasing details after the sale.
  4. Validate every file: generated invoices should pass the official validators rather than just “looking right”. You can spot-check an XML invoice with our free Rechnung validator.
  5. Switch issuing before your deadline, not in the final quarter.

FAQ

Is a PDF an e-invoice under the 2026 EU rules?

No. An e-invoice is a structured format conforming to EN 16931, such as XRechnung or ZUGFeRD and Factur-X (profile BASIC or higher). A plain PDF is an “other invoice” and, from the relevant German deadline, no longer counts for B2B.

No. Germany does not certify invoicing software. The mandate requires the EN 16931 format, and conformance is shown by validating the document. The two EU markets that regulate the software itself are Portugal and Spain, and they only apply if you produce native records for merchants established there.

Are the German and French mandates the same?

They share the Factur-X and ZUGFeRD format and the EN 16931 standard, so the invoice file travels across both. The dates differ (Germany 2025/2027/2028, France 2026/2027), and France adds accredited transmission platforms (PDP) that the German model does not.

What is ViDA and do I need to act on it now?

ViDA (VAT in the Digital Age) is the EU package pushing toward structured e-invoicing and digital reporting for cross-border B2B. The dates are still being finalised, so there is nothing to switch on today, but issuing EN 16931 invoices now puts you on the right foundation.


If you would rather not assemble all of this per country, Faktwise is a Shopify app that generates EN 16931 invoices (ZUGFeRD 2.x / Factur-X and XRechnung) automatically when an order is paid, with B2B VAT-ID and Leitweg-ID capture at checkout, gap-free numbering, automatic credit notes, and an EU-hosted archive (Paris). Output is validated against the official KoSIT validator. It is software, not tax advice, so keep your accountant in the loop on your specific situation. There is a free tier of 5 invoices a month, then a flat founding rate of EUR 19/month. See pricing for details.