Guide

Shopify E-Invoicing in Germany: The Guide for International Merchants

Updated 2026-06-10

Shopify E-Invoicing in Germany: The Guide for International Merchants

Germany is rolling out mandatory electronic invoicing for domestic B2B transactions, and the deadlines are no longer distant: the receiving obligation has been live since January 2025, and issuing becomes mandatory in two steps in 2027 and 2028. If you run a Shopify store and sell to business customers in Germany, or you are a German-established merchant selling through Shopify, this guide explains what the mandate actually requires, which formats count as e-invoices, and what to set up now.

The timeline: three steps, no delays announced

Germany’s e-invoicing mandate applies to domestic B2B transactions, meaning supplies between businesses that are both established in Germany. As of June 2026, the timeline stands as legislated, with no postponements announced:

One more date to keep in view: France is launching its own mandate based on the Factur-X format, with the first wave in September 2026. The two countries deliberately share a hybrid format standard (more below), so preparing for Germany largely prepares you for France too.

What legally counts as an e-invoice

This is where most merchants get caught out. Under the German rules, an e-invoice is an invoice issued in a structured electronic format conforming to the European standard EN 16931, one that software can process automatically.

A PDF attached to an email is not an e-invoice, no matter how professional it looks. Neither is a scanned paper invoice or a Word file. From the relevant deadline onwards, those are merely “other invoices” and do not satisfy the mandate. Two formats dominate in Germany:

XRechnung 3.0.2

A pure XML format maintained by Germany’s KoSIT standards body. No PDF, no visual layer. It can be expressed in two syntaxes (UBL 2.1 or UN/CEFACT CII) and is the established standard for invoicing German public-sector customers (B2G), where an additional routing identifier is mandatory: the Leitweg-ID, carried in the buyer reference field BT-10. Government invoice portals validate incoming files against the official KoSIT validator and reject anything non-conformant.

ZUGFeRD 2.4 / Factur-X

A hybrid format: a PDF/A-3 file with a machine-readable XML (factur-x.xml) embedded inside. Humans see a normal, readable PDF invoice; accounting software reads the embedded XML. ZUGFeRD 2.4 and the French Factur-X 1.08 are the same specification under two names, which is why it travels well across both markets. One critical detail: only the profiles BASIC, EN 16931 and EXTENDED qualify as e-invoices under the German mandate. The stripped-down MINIMUM and BASIC WL profiles do not, because they do not carry a full VAT invoice. If a tool advertises “ZUGFeRD support”, always ask which profile it generates.

For most Shopify merchants, ZUGFeRD/Factur-X in the EN 16931 profile is the practical default for B2B customers (the recipient still gets a readable PDF), with XRechnung reserved for public-sector buyers.

Does this affect you? A quick triage

Beyond format: German invoices have content rules too

An e-invoice that validates technically can still be wrong legally. German law (§ 14(4) UStG) prescribes the mandatory content of any invoice: full names and addresses of supplier and customer, the supplier’s tax number or VAT ID, issue date, a unique sequential invoice number, quantity and description of goods, the supply date, the net amount per VAT rate, and the VAT rate and amount. Where an exemption applies, the invoice must reference it instead (for example for intra-Community supplies or reverse-charge services). Simplified rules exist only for small-value invoices up to €250 gross (§ 33 UStDV).

Two further German specialties matter for store owners:

Why Shopify alone doesn’t cover this

Shopify does not generate legally complete German invoices, let alone EN 16931 e-invoices. Order confirmations are not invoices; they lack sequential invoice numbers, the supplier’s tax identifiers, correct exemption wordings, the structured XML layer, and a compliant archive. Every merchant in scope needs either an external invoicing system wired to Shopify or a Shopify app that generates compliant documents directly from order data.

When evaluating a solution, check specifically:

  1. Formats and versions: XRechnung 3.0.2 and ZUGFeRD 2.4/Factur-X with profile EN 16931, not just “PDF invoices”.
  2. Validation: every generated invoice should be checked against the official validators (KoSIT for XRechnung; Mustangproject and veraPDF for ZUGFeRD/PDF-A-3). Files that fail validation get rejected by recipients.
  3. VAT logic: correct treatment per scenario (domestic German VAT, intra-EU B2B with VAT ID validation, OSS distance selling, exports) with the legally required wordings.
  4. Checkout data capture: B2B invoices need the customer’s VAT ID (validated against the EU’s VIES system); German public-sector invoices need the Leitweg-ID. Capturing these at checkout avoids email back-and-forth later.
  5. Credit notes and archive: automatic credit notes on refunds, and tamper-proof retention of every document.

A sensible preparation plan

  1. Now: make sure you can receive and archive incoming e-invoices (this obligation is already live for German businesses), and audit whether your current invoices meet § 14(4) UStG.
  2. Next: pick your formats (ZUGFeRD EN 16931 for B2B, XRechnung for B2G), and set up VAT ID / Leitweg-ID capture at checkout.
  3. Before your deadline (2027 or 2028): switch issuing to e-invoices for domestic B2B customers, with validation and archiving running automatically. Run it well before the deadline rather than in the last quarter.

FAQ

Is a PDF invoice an e-invoice under German law?

No. An e-invoice must be a structured format conforming to EN 16931 (such as XRechnung, or ZUGFeRD/Factur-X in profile BASIC, EN 16931 or EXTENDED). A plain PDF is only an “other invoice”.

I sell only to consumers in Germany. Do I need e-invoices?

The issuing mandate covers domestic B2B transactions, so pure B2C sales are out of scope. General invoice content and retention rules still apply.

What is the Leitweg-ID?

A routing identifier that German public-sector customers assign so invoices reach the right internal office. It is mandatory for B2G invoices (carried in field BT-10) and must be obtained from the customer before invoicing.

What happens if I send a non-conformant e-invoice?

Public-sector portals reject it outright; B2B customers will reject it too because a non-compliant invoice endangers their input VAT deduction. Either way, you re-issue and your payment is delayed.

How long must invoices be kept in Germany?

Eight years since 1 January 2025 (§ 14b UStG, § 147 AO), unchanged and machine-readable, in the original format.


If you’d rather not build any of this yourself: Faktwise is a Shopify app that generates legally correct German invoices and e-invoices (ZUGFeRD 2.4/Factur-X and XRechnung 3.0.2) automatically when an order is paid. It handles gap-free numbering, automatic credit notes on refunds, a GoBD-compliant archive, VAT ID and Leitweg-ID capture at checkout with VIES validation, and every file is validated against the official KoSIT, Mustang and veraPDF validators. EU-hosted (Paris), free for up to 5 invoices a month, then a flat €19/month unlimited with a 14-day trial.