Germany’s phased timeline

German E-Invoicing Mandate: 2026 Timeline

German businesses have needed to be able to receive structured e-invoices since January 1, 2025. The transition rules mainly concern issuing.

Businesses with more than EUR 800,000 in relevant prior-year turnover generally move to mandatory issuing from January 1, 2027. The requirements broadly apply to qualifying domestic B2B transactions from 2028, subject to statutory exceptions.

Reception since 2025> EUR 800,000 prior-year turnover: 2027Affected domestic B2B transactions from 2028
Legal position and implementation

What applies in 2026?

Legal position: In 2026, domestic businesses must already be able to receive structured e-invoices. For issuing, the general transition rule continues through December 31, 2026: issuers may still use another invoice format. Paper invoices remain possible during this period. An unstructured electronic invoice, such as a PDF sent by email, still requires the recipient’s consent.

Operational recommendation: Use 2026 to make reception, viewing, processing, master data, validation, and archiving reliable. These measures support implementation; they are not separate statutory reception obligations.

01QuoteCash

Receive since 2025

Businesses have needed to be able to receive structured e-invoices since January 1, 2025. The transition rules mainly concern issuing, not basic reception capability.

02QuoteCash

Phased issuing

Businesses above EUR 800,000 in relevant prior-year turnover generally move to mandatory issuing from 2027. Businesses at or below the threshold can use the transition rule through the end of 2027 where applicable.

03QuoteCash

Archive correctly

Invoices generally must be retained for eight years for VAT purposes. For e-invoices, at least the structured part must remain intact in its original form.

How it works

How QuoteCash handles German e-invoicing mandate timeline

QuoteCash provides POST /api/v1/invoices/xrechnung to generate UBL XRechnung XML from structured invoice data. By default, the generated XML is checked by the configured validation service before a successful document response; a failed check returns validation details instead.

For existing XML files, POST /api/v1/validate provides validation without generating a new document. The response reports whether the configured rule set considers the XML valid and includes structured errors and warnings. Validation does not replace a tax, accounting, or recipient-specific review.

Access uses business-scoped API keys that can be created or revoked from the dashboard. Public API usage remains subject to the applicable plan limits.

Who it’s for

Who is this for?

Freelancers and small businesses

Freelancers and small businesses need to treat the 2025 receiving obligation as a current operational requirement rather than a distant roadmap item.

SaaS developers

Developers embedding billing into products need to operationalize the timeline technically, not just explain it in docs. A validating API reduces the risk of custom XML maintenance.

Agencies and resellers

Agencies setting up compliance workflows for clients need clear failure modes and access separation rather than shared export tools.

ERP integrators

Integrators need validation, deadline-aware process planning, and stable response structures so the mandate can be embedded into existing operations.

Editorial note

Last reviewed: July 24, 2026

A product and process view, not legal advice

QuoteCash explains the German e-invoicing transition from the perspective of SMEs, software teams, finance operations, and API integrations. Legal and tax questions should be checked with official guidance or professional advisors.

Implementation guidance

Germany’s e-invoicing timeline explained

The German e-invoicing transition is not a single switch. Since January 1, 2025, German businesses have needed to be able to receive structured e-invoices for many domestic B2B transactions. Issuing obligations are phased in later, with transition periods that depend on business circumstances.

For international software vendors and agencies, the practical message is simple: German customers will increasingly expect structured invoice data, not only PDFs. The earlier your product models buyer references, tax logic, validation results, and artifact storage, the fewer emergency migrations you face later.

Implementation guidance

2025, 2026, 2027, 2028: what to do when

Businesses have needed to ensure reception of structured e-invoices since 2025. An email inbox can be sufficient for basic reception. Viewing, checking, processing, and orderly archiving are sensible parts of a robust operational process, but they should not be presented as separate statutory reception requirements.

For businesses with more than EUR 800,000 in relevant prior-year turnover, the general transition rule normally ends on January 1, 2027. Businesses at or below EUR 800,000 can continue using another invoice format through the end of 2027 where the transition rule applies.

After the transition periods, the requirement generally covers qualifying transactions between domestic businesses from January 1, 2028. Consumer invoices and statutory exceptions are outside that general statement.

Implementation guidance

Who is affected

The mandate primarily concerns domestic B2B transactions where an invoice is required under German VAT rules. Consumer invoices, certain VAT-exempt supplies, small-value invoices up to EUR 250, and tickets are among the statutory exceptions.

Businesses using the Kleinunternehmer scheme are exempt from issuing e-invoices under section 34a UStDV and may issue another invoice format. Recipient consent remains necessary for an electronic “other invoice.” The exemption does not cover reception: Kleinunternehmer must still be able to receive e-invoices. If they switch to regular VAT taxation, the issuing obligation can apply when the other conditions are met.

Implementation guidance

XRechnung versus ZUGFeRD decision guide

XRechnung is the right default when the recipient expects XML, uses a portal, or validates incoming invoices automatically. ZUGFeRD is often better when the recipient needs a readable PDF and structured XML in the same document.

Many businesses will support both. A public-sector customer may require XRechnung, while a mid-market B2B customer may prefer a hybrid PDF. The decision should be stored per customer or recipient group so sales, support, finance, and software do not make conflicting assumptions.

  • Choose XRechnung for strict XML and portal-driven workflows.
  • Choose ZUGFeRD for readable PDF plus machine-readable data.
  • Validate either format before delivery.
  • Document customer format preferences early.
Implementation

Preparation checklist for SMEs and software teams

  1. 1Capture buyer reference, Leitweg-ID, VAT ID, and e-invoice format preference per customer.
  2. 2Preserve the structured part of incoming e-invoices intact in its original form throughout the eight-year VAT retention period.
  3. 3Generate test invoices in both XML and hybrid PDF/XML formats.
  4. 4Run validation before sending customer-facing invoices.
  5. 5Train finance and support teams on common rejection reasons.
  6. 6Document escalation rules for failed validation or customer portal rejection.

Frequently Asked Questions

Does the 2025 E-Rechnung rule already apply to receiving invoices?
Yes. Businesses in Germany must have been able to receive structured e-invoices since January 1, 2025.
Are German small-business scheme users exempt from e-invoice requirements?
Businesses using Germany’s Kleinunternehmer scheme are exempt from the obligation to issue e-invoices under section 34a UStDV, but they must still be able to receive them. If a business switches to regular VAT taxation, the issuing obligation can apply when the other conditions are met.
Which businesses move to mandatory issuing in 2027?
Businesses with more than EUR 800,000 in relevant prior-year turnover generally must issue e-invoices from January 1, 2027. Businesses at or below EUR 800,000 can use the transition rule through the end of 2027 where applicable.
How broadly does the issuing requirement apply from 2028?
After the transition periods, e-invoicing generally applies to qualifying transactions between domestic businesses from January 1, 2028. B2C invoices and statutory exceptions are not covered by that general statement.
How long do electronic invoices need to be kept in Germany?
For VAT purposes, incoming and outgoing invoices generally must be retained for eight years. For an e-invoice, at least the structured part must remain intact in its original form.
Do German businesses need to act before the final issuing deadline?
Yes. Reception capability already applies. Viewing, processing, validation, and archiving are sensible implementation measures, but they are not separate statutory reception obligations.
Is an email inbox enough to receive e-invoices?
An email inbox can be sufficient for basic reception. Viewing, checking, processing, and orderly archiving are sensible parts of a robust operational process.
Is an emailed PDF still enough?
During the general issuing transition through December 31, 2026, a PDF can still be used as an “other invoice” if the recipient consents. It is not an e-invoice under the structured-format definition.
Which format should a SaaS product support first?
Start with the format your German customers ask for most often. For public-sector or strict procurement workflows, that is often XRechnung. For mixed B2B customers, ZUGFeRD may be useful too.