Current format baseline: ZUGFeRD 2.5.2 / Factur-X 1.09.2
The corrected package becomes valid on 1 September 2026, and SAP DRC has supported its Schematron artefacts since 18 August. Re-test profile-specific mappings, EXTENDED cardinalities and empty optional CII elements. XRechnung 4.0 is not yet a productive target.
Germany · B2B e-invoicing · Phased from 2025 to 2028
Germany B2B e-invoicing in SAP: choose the right implementation path
Start with the SAP landscape and invoice scope
SAP teams should first confirm the entities and transactions in scope, required invoice formats, receipt capability, outbound timing, source-system readiness and exception ownership. Select SAP DRC, SAP DRC with an SAP BTP extension or an on-stack S4FN Add-on only after checking the exact SAP release, supported processes, integration requirements and operating model.
Prepare your SAP landscape for Germany’s phased B2B e-invoicing requirements. We review your SAP release, invoice flows and XRechnung or ZUGFeRD needs, then identify whether SAP DRC, SAP DRC with an SAP BTP extension or an on-stack S4FN Add-on is the path to assess first.
- ECC or S/4HANA readiness check
- Required XRechnung or ZUGFeRD format and the appropriate exchange channel
- Inbound and outbound invoice process review
- SAP DRC vs SAP BTP extension vs S4FN Add-on decision
What you get from the fit check
- Landscape and mandate scope
- Implementation path to assess first
- Priority technical gaps
The fit check starts from your SAP landscape.
01 · 2025
Receiving is mandatory
Since 1 January 2025, businesses considered domestic under German VAT rules must be able to receive e-invoices. An email inbox is sufficient for the legal receipt requirement, but SAP teams must still decide how invoices will be validated, visualized, processed, archived and linked to operational evidence.
01 · 2027
Issuing for > €800k turnover
From 1 January 2027, German invoice issuers with prior-year turnover above €800,000 can no longer rely on the general transition period for domestic B2B invoices and must issue structured e-invoices where the German B2B e-invoicing rules apply.
01 · 2028
Remaining non-exempt issuers
From 1 January 2028, remaining non-exempt domestic B2B invoice issuers can no longer rely on the transition period.
German B2B e-invoices must be based on structured data that enables electronic processing, typically aligned with EN 16931.
The buying question
SAP DRC, SAP DRC with an SAP BTP extension, or an on-stack S4FN Add-on?
Germany e-invoicing is supported through SAP Document and Reporting Compliance, but product availability alone does not determine the architecture. The decision depends on the exact release, supported processes, integration scope and operating model.
Standard SAP DRC
SAP DRC provides standard Germany e-invoicing capabilities, but its fit depends on the exact release, licensed components, supported scenarios and required integration scope.
Best fit
Review first when the exact SAP release and Germany scenario are supported and standard SAP processes cover the required inbound and outbound scope.
Watch out
Release fit, licensing, scenario coverage, inbound/outbound assumptions.
Typical buyer question
“We’re on S/4HANA. Is standard DRC enough for Germany?”
DRC + SAP BTP
Best fit
Review when DRC remains the core solution but feeder systems, non-standard transformations, additional validations or custom integration flows must be handled outside the ERP core.
Watch out
Integration ownership, monitoring, error handling, data movement.
Typical buyer question
“Our invoice flows aren’t standard. Where does BTP come in?”
on-stack S4FN Add-on
Best fit
Review when the exact ECC or SAP S/4HANA release is supported, a mandate-specific on-stack deployment is preferred, and the required formats, channels, transport governance and support model are confirmed.
Watch out
Confirm SAP traceability, transport governance and the support model.
Typical buyer question
“We’re on ECC with no S/4 plan. Do we really need DRC?”
How it runs inside SAP
From SAP source document to structured exchange
Inbound and outbound are not the same scope
Outbound: issuing
- SD/FI invoice types and corrections
- Customer master data and tax IDs
- XRechnung XML or ZUGFeRD structured invoice data generation
- Exchange channel and delivery evidence
Inbound: receiving and operational processing
- Structured intake and format validation
- Business-readable visualization for AP
- Posting, matching, exception handling
- Archive and audit evidence
Advanced SAP processing is an operational choice, not the legal minimum.
The engagement
Germany SAP E-Invoicing Fit Check
Receive a landscape-specific implementation recommendation based on your SAP release, Germany scope and invoice flows.
- Confirm whether Germany B2B scope applies to your SAP landscape
- Identify affected SAP invoice flows
- DRC vs SAP DRC with an SAP BTP extension vs on-stack S4FN Add-on fit
- Master data and tax mapping gaps
- The next technical step for implementation
Request your SAP Fit Check
Send your SAP release and Germany scope. We’ll reply with the recommended path: SAP DRC, SAP DRC with an SAP BTP extension, or on-stack S4FN Add-on.
We review the submitted SAP landscape before recommending a path.
Germany SAP E-Invoicing Readiness Checklist
Everything to confirm before development starts. SAP-specific.
- SAP release
- Company codes
- SD/FI invoice types
- Credit memo / correction scenarios
- Customer / vendor tax IDs
- Address data
- XRechnung / ZUGFeRD format need and Peppol / email / portal exchange channel
- Inbound supplier invoice process
- AP visualization
- Exception handling
- Archive and audit evidence
- Structured invoice part retained in original form
- DRC / eDocument / BTP / add-on fit
SAP Germany e-invoicing: straight answers
Can an on-stack S4FN Add-on be used instead of SAP DRC?
Potentially, after confirming the SAP release, required formats and channels, licensing, transport governance and support model. The fit check determines whether the S4FN Add-on covers the stated scope.
Which German invoices are out of scope or exempt?
Several cases can sit outside the B2B issuing obligation, for example B2C sales, many tax-exempt transactions, small-value invoices up to €250, tickets, and certain small-business cases. Exact treatment depends on the transaction.
Does German VAT registration alone trigger the B2B e-invoicing obligation?
Not necessarily. A German VAT registration on its own does not automatically create the obligation; it depends on a domestic business / establishment assessment for the parties involved.
Is B2G (public sector) the same as this?
B2G is different. Public-sector invoices may require XRechnung, a Leitweg-ID, and platform-specific submission rules. This page focuses on domestic B2B.
Does Germany require a central government platform?
For B2B, Germany’s model is based on structured formats exchanged between businesses, not a single central clearance platform. Formats and exchange channels are what matter for your SAP setup. A future reporting system is planned separately, but it is not the same as today’s B2B invoice exchange obligation.
Is ZUGFeRD enough, or do we need XRechnung?
XRechnung and ZUGFeRD 2.0.1+ generally meet the German e-invoice requirements; which you generate from SAP depends on your customers and channels. We map this in the fit check. For ZUGFeRD, the profile matters: BMF refers to ZUGFeRD 2.0.1+ except MINIMUM and BASIC-WL profiles.
Do we need Peppol for Germany B2B invoices?
Not necessarily. Peppol is one exchange option; German B2B does not mandate it universally. Whether it fits depends on your trading partners and existing channels.
Is a PDF invoice still acceptable?
A simple PDF is no longer considered an e-invoice for transactions from 1 January 2025 onward. During transition periods, certain non-structured invoices may still be permitted depending on the case.
Can ECC systems support Germany e-invoicing?
Potentially, yes. ECC landscapes may meet the mandate via an on-stack S4FN Add-on or applicable SAP eDocument components, but the exact path depends on release, SAP Notes, licensing, supported scenarios, and the required formats/channels.
From Germany mandate scope to an SAP implementation path
Send your SAP release and Germany entity and transaction scope. We reply with the implementation path to assess first: SAP DRC, SAP DRC with an SAP BTP extension or an on-stack S4FN Add-on.
Request Germany SAP Fit CheckRegulatory basis: German Federal Ministry of Finance FAQ on mandatory e-invoicing, status March 2026. This page is a technical SAP readiness guide, not legal or tax advice.
DRC Sprint Country Compliance Pack
Germany: turn mandate scope into SAP delivery
The Germany pack connects structured B2B e-invoicing requirements to system evidence, architecture decisions, implementation work and operational controls.
What the pack connects
- 01Mandate controlsScope, scenarios, deadlines and exceptions
- 02SAP evidence checksRelease, component, configuration, data and process evidence
- 03Delivery assetsDecision records, test scenarios, work packages and operating controls
Germany focus: XRechnung and ZUGFeRD selection, buyer identifiers, inbound readiness, exchange channels and transition controls.
Content verified: 24 August 2026. ZUGFeRD 2.5.2 and Factur-X 1.09.2 become valid on 1 September 2026, and SAP DRC supports the corresponding validation artefacts. XRechnung 4.0 remains a preparation topic rather than a productive mapping target.