Diesen Leitfaden gibt es auch auf Deutsch: GoBD-konforme Rechnungen mit Shopify.

If you run a Shopify store from Germany, your invoices are subject to a set of rules most e-commerce founders only hear about for the first time during a tax audit: the GoBD — the German tax authority's principles for the proper keeping and retention of books, records and documents in electronic form.

A default Shopify setup does not by itself establish a GoBD-ready invoicing process. This guide explains what the rules require, where native order data needs additional controls, and what a stronger setup looks like in practice.

What the GoBD actually requires

The GoBD is administrative guidance from the Federal Ministry of Finance (BMF) that tells auditors how to assess electronic bookkeeping. For invoicing, three requirements matter most.

1. Traceable, sequential invoice numbering

§ 14 (4) UStG requires every invoice to carry a fortlaufende Nummer — a sequential number, from one or more series, that uniquely identifies the invoice. Strictly speaking, German case law does not demand a mathematically gapless sequence at all costs; what it demands is that the sequence is systematic, unique and traceable, and that any gap can be explained.

In practice, unexplained holes can create avoidable questions and complicate reconciliation. A dedicated transactional counter is therefore a useful engineering control: it minimizes gaps, prevents duplicates, and makes exceptions easier to document. That is a risk-reduction choice, not a claim that German law demands mathematical gaplessness in every case.

2. Immutability (Unveränderbarkeit)

Once an invoice is issued, it must not be possible to alter it without a trace. A record whose content can silently change later is, in GoBD terms, not a record at all. Corrections happen through new documents — a cancellation invoice (Stornorechnung) or credit note that references the original — never by editing the original PDF or the data behind it.

This is an important implementation detail to test in any invoicing app. If a tool re-renders an old invoice from current product data, a later price change or product rename can alter the document. Ask whether the app stores an issue-time snapshot, then verify it with a test order.

3. Retention — now 8 years for invoices

Invoices and accounting vouchers historically had to be kept for 10 years. Since 1 January 2025, the Fourth Bureaucracy Relief Act (BEG IV) shortened the retention period for invoices under § 14b UStG and booking vouchers under § 147 AO to 8 years. The clock starts at the end of the calendar year in which the invoice was issued, and the period does not expire while the documents are still relevant to an open tax assessment. (Books, annual financial statements and some other records remain at 10 years — ask your Steuerberater what applies to each document class.)

Retention is not "keep a PDF somewhere." Electronic invoices must be stored in their original, machine-readable format, protected against alteration, and retrievable for the auditor's data access (the famous Z1/Z2/Z3 access modes). A structured e-invoice received as XML must be archived as XML, not just as a printout.

Why Shopify order numbers need careful handling

Shopify assigns every order a number: #1001, #1002, #1003. Using that number on an invoice is not automatically forbidden, but it does not remove the obligation to maintain a unique, systematic, and traceable invoice-number series.

Order numbers are not invoice numbers

An order number identifies a sales event, not a tax document. It is assigned when the order is created — before payment and before you know whether an invoice will be issued. A dedicated number allocated at issuance separates the tax-document sequence from cancellations, tests, and other order events.

Gaps require reconciliation

Shopify's order sequence develops holes as a matter of routine:

• Cancelled orders keep their number but never become revenue.
• Test orders during development consume numbers.
• Abandoned or failed payments can leave gaps depending on your checkout flow.
• Deleted draft or archived orders vanish from view while the counter marches on.

These events can make a shared order-and-invoice sequence harder to reconcile years later. If you use order numbers, preserve the records and process documentation needed to explain non-invoice numbers. A dedicated invoice counter reduces that operational burden.

The order confirmation is not an invoice

Shopify's order confirmation email lacks mandatory invoice content under § 14 (4) UStG: your tax number or VAT ID, a proper VAT breakdown per rate, the invoice date as distinct from the order date, and — for B2B — the customer's VAT ID and any reverse-charge wording. Sending it "as the invoice" leaves your business customers unable to deduct input VAT and leaves you non-compliant.

Orders remain editable

Shopify lets you edit orders after the fact — add items, change quantities, adjust prices. Useful operationally; fatal if your "invoice" is generated live from order data, because the document your customer holds and the one your system shows can diverge.

What a compliant setup looks like

A GoBD-clean invoicing flow on Shopify has these properties:

1. A dedicated invoice number series, independent of order numbers, incremented transactionally so no number is ever skipped or issued twice — typically with a configurable prefix and optional yearly reset (e.g. RE-2026-00001).
2. Invoices generated at a defined trigger — normally when the order is paid — capturing prices, tax rates and addresses as of that moment, then frozen.
3. Locked documents. Once issued, the invoice is immutable. Refunds and corrections produce credit notes (Gutschriften/Stornorechnungen) in their own sequential series, referencing the original invoice number.
4. Complete § 14 UStG content: full seller and buyer details, tax number or USt-IdNr., invoice date, delivery date, net amounts per VAT rate, VAT rates and amounts, and the applicable notes for exemptions or reverse charge.
5. An audit-ready archive: every document retained for the full retention period in its original format, exportable for the auditor and for your Steuerberater (DATEV-friendly exports save everyone hours).
6. Process documentation (Verfahrensdokumentation): a written description of how invoices are created, numbered, stored and corrected. Your app provider should make this easy to produce.

A note on e-invoicing

GoBD compliance is the foundation, but Germany's B2B e-invoicing mandate builds on top of it: since January 2025 every German business must be able to receive structured e-invoices, and issuing becomes mandatory in 2027–2028. If you are fixing your invoice numbering now, document how the setup will later connect to EN 16931-compliant formats such as XRechnung or ZUGFeRD. We cover the full timeline in our separate guide to the German e-invoicing mandate.

The bottom line

GoBD readiness is not about pretty PDFs. It depends on verifiable controls: a systematic and traceable number series, records that cannot silently change, and an archive that preserves required documents for the applicable retention period. The goal is a process you and your tax adviser can explain and test.

Primary sources

• § 14 UStG: invoice requirements
• German Federal Ministry of Finance: current GoBD guidance
• German Federal Ministry of Finance: E-invoice FAQ

Facturely automates dedicated sequential numbering, frozen issue-time records, and linked refund credit notes for Shopify stores.

This article is general information, not tax advice. For your specific situation, consult your Steuerberater or tax advisor.