Germany is moving B2B invoicing to structured electronic formats in phases between 2025 and 2028. For SAP teams, the key issue is not only legal readiness, but whether billing, tax, master-data, and e-document workflows can support structured invoice issuing and receiving without losing traceability to SAP source records.
Guide scope: This article covers Germany B2B rules, transition dates and accepted formats. For SAP architecture selection, inbound readiness and delivery scope, use the Germany E-Invoicing Implementation for SAP page.
Key dates
1 Jan 2027
Businesses with prior-year turnover > €800K: issuing mandatory
1 Jan 2028
Remaining in-scope Germany-established, non-exempt issuers: structured e-invoice issuing mandatory
At a glance
- Mandate: Structured B2B e-invoicing (EN 16931 compliant formats only; PDF no longer qualifies)
- Formats: XRechnung; qualifying ZUGFeRD 2.0.1 or later except MINIMUM and BASIC-WL; other EN 16931-compliant formats
- Platform / channel: Direct exchange between trading partners (no central platform)
- Who is affected: Germany-established businesses involved in in-scope domestic B2B transactions, subject to statutory exclusions and transition rules
- SAP scope: SD billing, FI invoices, tax codes, master data, e-document output + inbound processing
Executive Summary
| Mandate name | Germany structured B2B e-invoicing (Wachstumschancengesetz / Growth Opportunities Act) |
|---|---|
| Current status (as of July 2026) | Receiving structured e-invoices mandatory since 1 January 2025; issuing becomes mandatory 1 January 2027 for businesses with prior-year turnover above €800,000 and 1 January 2028 for remaining in-scope Germany-established, non-exempt issuers. |
| Who is affected | Businesses issuing or receiving domestic B2B invoices in Germany. |
| Business risk | Invoice rejection, manual rework, VAT deduction risk on non-compliant invoices, and weak audit evidence. |
| SAP impact | SD billing, FI invoices, tax codes, master data, e-document output, inbound processing, and monitoring. |
| Recommended next step | Review SAP invoice flows and format readiness before the January 2027 issuing phase. |
What Is the Requirement?
The Growth Opportunities Act, passed in March 2024, redefined what counts as an electronic invoice in Germany: only structured formats compliant with the European standard EN 16931 qualify. A PDF is no longer an e-invoice. The rollout is deliberately phased:
- 1 January 2025: in-scope Germany-established businesses must be able to receive structured e-invoices. Buyer consent is no longer required for structured invoices.
- 1 January 2027: businesses with prior-year turnover above €800,000 must issue structured e-invoices for domestic B2B transactions; paper and unstructured formats are no longer permitted for them.
- 1 January 2028: the issuing obligation extends to remaining in-scope Germany-established, non-exempt issuers.
Accepted formats include XRechnung (the national standard, pure XML) and qualifying ZUGFeRD from version 2.0.1 (except MINIMUM and BASIC-WL profiles), plus other formats that meet the statutory structured-data requirements. Unlike Italy or Poland, Germany has (as of July 2026) no central government exchange platform — invoices flow directly between trading partners, which makes format validation and inbound processing an in-house responsibility.
Business Impact for Finance and Tax Teams
Because there is no clearing platform, a non-compliant invoice is not rejected by an authority — it simply may not qualify as a valid invoice for VAT deduction. Finance teams need reliable invoice data, clear exception handling, and evidence that issued and received invoice records can be traced back to SAP source documents. Inbound is the immediate workload: since January 2025, suppliers can send structured invoices whether or not the recipient’s AP process is ready for them.
Scope qualification: The issuing obligation concerns in-scope domestic transactions between Germany-established businesses. Statutory exclusions include specified tax-exempt transactions and document types such as qualifying small-value invoices and tickets. German VAT registration by itself does not necessarily establish that a person is established in Germany for this rule.
How This Impacts Your SAP Environment
- SD billing and FI invoice data must support structured output in XRechnung or ZUGFeRD and inbound XML processing.
- Customer and vendor master data must contain reliable tax identifiers, addresses, and routing information (for example Leitweg-ID in public-sector scenarios).
- Tax codes and document types need mapping to EN 16931 fields, including credit memos and corrections.
- Error handling must be owned by finance and IT, not left in disconnected queues.
How S4FN Supports SAP Compliance
S4FN can review SAP source data, mandate-specific mapping, validation workflow, exchange process, and exception handling for Germany e-invoicing readiness. For the public-sector variant of the requirement, see Germany XRechnung: SAP e-invoicing readiness.
Primary Source and Verification
Verified on: 10 July 2026. Confirm establishment, transaction scope, exclusions, turnover transition and the exact accepted format profile before implementation.
Review Germany E-Invoicing Readiness in SAP
Discuss SAP source data, structured invoice output, inbound process impact, and implementation assumptions with S4FN.