Article · 9 min
Shopify E-Invoicing for Germany 2027 (ZUGFeRD)
Germany's B2B e-invoicing mandate phases in from 2025-2028. What XRechnung & ZUGFeRD mean for Shopify stores selling B2B in Germany — and how to prepare.
The German E-Invoicing Mandate: The Timeline to 2028
| Date | Obligation | Who |
|---|---|---|
| Jan 1, 2025 | Must be able to receive e-invoices | all German businesses |
| Jan 1, 2027 | Must issue e-invoices (domestic B2B) | turnover > €800k |
| Jan 1, 2028 | Must issue e-invoices (domestic B2B) | all remaining businesses |
The receiving obligation is already live. A plain PDF emailed to a business customer is, from 2025, no longer guaranteed to count as a proper invoice — and from 2027/2028 issuing one for domestic B2B will not satisfy the law. For a Shopify store doing wholesale or B2B volume into Germany, this is not optional.
What Counts as an E-Invoice (XRechnung vs. ZUGFeRD)
Two compliant formats dominate in Germany:
- XRechnung — a pure structured XML format. No visual layout; it is data only. Common for public-sector (B2G) invoicing and accepted for B2B.
- ZUGFeRD (≥ 2.0.1) / Factur-X — a hybrid: a human-readable PDF/A-3 with the structured XML embedded inside it. You see a normal-looking invoice; the accounting system reads the XML. This is usually the more practical choice for B2B because it works for recipients at any level of automation.
The takeaway for store owners: your system needs to emit one of these structured formats for domestic B2B — not a styled PDF that merely looks like an invoice.
Who the Mandate Applies To — and Who's Exempt
In scope: wholesale orders, B2B accounts, and any invoice you issue to a German business customer once your issuing deadline (2027 or 2028) arrives.
Out of scope (for now): B2C invoices to private consumers, and cross-border invoices (a German seller to an Austrian business, for example, follows different rules). Small-value invoices under €250 (Kleinbetragsrechnungen) and certain tax-exempt supplies have eased rules.
If you run a B2B operation on Shopify — now easier without Plus since April 2026 — the issuing obligation will reach you. The receiving obligation already has: from 2025 you must be technically able to accept an XRechnung or ZUGFeRD invoice from a supplier.
The Shopify Problem: Standard Invoices Aren't E-Invoices
Some invoicing apps have added ZUGFeRD or XRechnung export, but coverage is uneven: the embedded XML must validate against EN 16931, carry the correct Pflichtangaben, handle reverse-charge and intra-community cases, map your tax rates correctly, and remain GoBD-compliant in archiving. A PDF with a malformed or incomplete XML payload is not compliant — it just looks compliant. This is the same gap we cover in the broader Shopify cost and compliance picture: the App Store solves the average case, and German B2B invoicing is not the average case.
What Shopify Stores Should Do Now
1. Confirm you can receive e-invoices today. Since 2025 your business must accept XRechnung/ZUGFeRD from suppliers. At minimum you need software that can open and archive them GoBD-compliant.
2. Identify your issuing deadline. Over €800k prior-year turnover → 2027. Otherwise → 2028. Don't wait for the deadline; supplier and customer systems will demand it earlier in practice.
3. Audit your current invoicing tool. Does it export valid ZUGFeRD ≥ 2.0.1 or XRechnung? Does the XML validate? Does it handle your B2B edge cases (reverse charge, partial deliveries, credit notes)? If the answer is "a PDF that looks right," that is not a yes.
4. Decide build vs. buy. If a SaaS invoicing app covers your cases compliantly, use it. If your B2B invoicing has edge cases the template engine can't express — multi-position Leistungszeiträume, Sammelrechnungen, complex storno chains — a custom build that emits compliant e-invoices and archives them correctly is the cleaner long-term answer.
E-Invoicing as a Custom Build: Integrate It Once, Correctly
The mandate is a hard, dated requirement — the kind of deadline that, like the checkout extensibility cutover, rewards the stores that move early and punishes the ones that wait. Services like NoRentApps build custom Shopify invoicing that is e-invoice-ready for German B2B from day one — fixed price, code you own, no per-invoice fees.
FAQ
Frequently Asked Questions
When does the German e-invoicing obligation apply to Shopify stores?+
Receiving e-invoices has been mandatory since January 1, 2025 for all German businesses. Issuing e-invoices for domestic B2B becomes mandatory on January 1, 2027 for businesses with over €800,000 prior-year turnover, and January 1, 2028 for all remaining businesses. B2C and cross-border invoices are outside the current scope.
Is a PDF invoice still allowed?+
For domestic German B2B, a plain PDF is not an e-invoice under the mandate. An e-invoice must be a structured format conforming to EN 16931 — XRechnung (pure XML) or ZUGFeRD/Factur-X (a PDF/A-3 with embedded XML). A styled PDF that merely looks like an invoice does not satisfy the requirement once your issuing deadline applies. PDFs remain fine for B2C consumer invoices.
What's the difference between XRechnung and ZUGFeRD?+
XRechnung is a pure structured XML format with no visual layout — data only, common in public-sector invoicing. ZUGFeRD (version 2.0.1 or higher) / Factur-X is a hybrid: a human-readable PDF/A-3 with the structured XML embedded inside it, so it works for recipients at any level of automation. Both conform to EN 16931. For B2B, ZUGFeRD is usually the more practical choice.
Can Shopify generate compliant e-invoices?+
Not natively. Shopify's built-in documents are not structured e-invoices, and many invoicing apps produce styled PDFs rather than valid ZUGFeRD/XRechnung. Some apps have added e-invoice export, but the embedded XML must validate against EN 16931, carry correct Pflichtangaben, and handle reverse-charge and B2B edge cases. Stores with non-trivial B2B invoicing often need a custom build to be reliably compliant.