E-Invoicing in SAP: Why Acting Now Makes All the Difference

The topic has been on the table for years. And yet the same phrases keep coming up: "We still have time." Or: "We'll deal with it when the moment comes." Or: "Our tax advisor is handling it."

The reality is different. The German e-invoicing mandate does not lead up to a single deadline — it is already in force. Since 1 January 2025, all domestic B2B companies in Germany have been required to be able to receive e-invoices. From 2027, the next stages kick in, affecting the entire outbound invoicing process. Organizations that wait any longer will pay for it later — in time, in consulting costs, and in the worst case with a compromised VAT input tax deduction.

"2026 is the critical preparation year. Organizations that are not ready by the end of 2026 will be competing in 2027 against the rest of the market for the same consultants — at the same time."

What the E-Invoicing Mandate Really Means

One common misconception first: as of 2025, a plain PDF invoice is no longer an e-invoice within the meaning of the new Section 14 of the German VAT Act (UStG). Previously, the term "electronic invoice" was understood more broadly — a PDF sent by email was considered electronically transmitted. That is no longer the case. An e-invoice in the new legal sense is a structured, machine-readable XML record. That sounds technical, but it has direct accounting and tax consequences.

The legal basis is Section 14 UStG as amended by the Growth Opportunities Act (Wachstumschancengesetz) of March 2024, clarified by the BMF letter of 15 October 2024 (establishing the core principles and administrative position) and the supplementary BMF letter of 15 October 2025 (introducing error classifications, validation obligations, and amendments to the VAT Application Decree). Permitted formats are those that comply with or are interoperable with the European standard EN 16931 — in Germany in practice primarily XRechnung and ZUGFeRD from version 2.0.1 in EN-16931-compliant profiles.

The Two Main Formats at a Glance

XRechnung is a purely machine-readable XML format and the national German CIUS (Core Invoice User Specification) of EN 16931. It is the mandatory format for invoices to public sector bodies (B2G). Without dedicated viewer software, the content is not directly readable by humans.

ZUGFeRD is a hybrid format: it combines a visually readable PDF/A-3 file with an embedded structured XML file and is particularly suited to B2B processes. Importantly, not every ZUGFeRD profile meets EN 16931. The relevant profiles are EN-16931-compliant ones — specifically from version 2.0.1 onward. The advantage: humans can read the invoice as usual, while systems simultaneously process the XML data automatically.

The XML record is always authoritative — if an accompanying PDF differs in content from the XML, the XML structure takes precedence.

Both formats are built on the same standards. The choice between them depends on the recipient's requirements, the desired level of automation, and the organization's own IT infrastructure.

The Implementation Timeline — What Applies When

The e-invoicing obligation is not being introduced all at once, but in clearly defined stages. That creates room to maneuver — but not unlimited room.

The Implementation Timeline at a Glance

Since 1 January 2025: Receiving obligation for all domestic B2B companies. E-invoices must be accepted and processable — regardless of company size or industry.
Until 31 December 2026: Paper invoices may still be sent. Other electronic formats such as PDFs are only permitted with the recipient's consent.
From 1 January 2027: Companies with prior-year revenue exceeding €800,000 must send structured e-invoices for domestic B2B transactions. PDF and paper are then no longer permitted without recipient consent.
Until 31 December 2027: Companies with prior-year revenue of up to €800,000 may still issue other invoice types with recipient consent.
From 1 January 2028: All companies in domestic B2B transactions must send e-invoices — with no remaining transition period for the transactions principally in scope.

Important Exceptions

Exceptions apply in particular to invoices for certain VAT-exempt transactions under Section 4 nos. 8 to 29 UStG, low-value invoices up to €250, and travel tickets. B2C transactions are not affected — the existing rules continue to apply. B2G follows its own separate requirements. The obligation applies only to domestic B2B transactions between companies established in Germany — no obligation for exports or intra-community supplies.

The Biggest Risk: the VAT Input Tax Deduction

This is the point that has not yet registered with many organizations. And it is costly.

From 2027, the so-called input tax trap becomes a real risk: if a company accepts a plain PDF invoice from a supplier who exceeded the revenue threshold and should have issued an e-invoice, the VAT input tax deduction can be jeopardized — because no formally valid invoice was present. The company then bears the risk of a mistake made by its supplier.

Invoices can in principle be corrected — but that requires the error to be identified and remedied in time. In the context of a tax audit, this can mean considerable effort. The safer strategy is to avoid being in that position in the first place.

If an accompanying PDF differs in content from the XML record, only the XML is authoritative. Errors in the structured part — even if the PDF looks correct — can jeopardize the recipient's VAT input tax deduction.

This means: it is not only the organization's own invoice issuance that must be correct. Incoming invoices should also be checked for format compliance. Those who do not do this carry the risk — even when the error lies with the supplier.

Practical Note

Format errors can downgrade an invoice to an "other electronic document" — which requires recipient consent and potentially jeopardizes the VAT input tax deduction. Technical validation of incoming invoices is therefore strongly recommended from both a compliance and process perspective.

What This Means for SAP Systems

The e-invoicing mandate is not purely an accounting topic. It reaches deep into IT architecture, process design, master data quality, and system configuration.

Within the SAP environment, SAP Document and Reporting Compliance (SAP DRC) is a central SAP-native option. SAP DRC supports common formats including XRechnung, ZUGFeRD, and PEPPOL, and is compatible with S/4HANA, SAP ERP (ECC), and Central Finance, providing a shared monitor for error tracking and deadline management. Depending on the system landscape, provider and middleware solutions, VIM/OpenText, xSuite, or EDI/PEPPOL service providers may also come into play — either as alternatives or complements. The right architecture depends on the specific system environment.

Typical Stumbling Blocks in SAP Projects

Master data quality: Missing VAT registration numbers, inconsistent tax codes, incomplete addresses, or missing references to purchase orders and goods receipts lead to high error rates in XML generation and validation.
Format versions and profiles: Only EN-16931-compliant profiles are permitted — for ZUGFeRD from version 2.0.1, for XRechnung in the current version. Incorrectly configured profiles produce formally invalid invoices, even if the document looks correct visually.
Archiving: The structured XML original must be stored in a GoBD-compliant, audit-proof manner — not just the accompanying PDF. GoBD requires immutability, traceability, and retention for a minimum of ten years.
Outbound invoicing processes: All invoice-generating processes must be captured — SD billing, FI customer invoice, credit memos, down payment requests, intercompany postings, and manual invoices.
Process design: Who is the process owner? Who decides on rejection? Is there a defined error process and a contingency plan in the event of system failure? These questions must be answered before the solution goes live.

What Organizations Should Specifically Check in SAP Right Now

Anyone wanting to assess their current position should be able to give a concrete answer to five questions:

SAP Readiness: 5 Core Questions

Which document types generate outbound invoices? SD billing, FI customer invoices, manual postings, credit memos, intercompany — all must be within the scope of the solution.
Which customers and suppliers are domestic B2B partners? The obligation applies only to these transactions. Clean segmentation in the business partner, customer, and vendor master is a prerequisite — in S/4HANA led by the Business Partner, technically also via classic tables such as KNA1/KNB1 and LFA1/LFB1.
Which mandatory fields are currently missing from master data? VAT registration numbers, tax numbers, routing IDs / Leitweg-ID for B2G, correct tax codes — what is maintained, what is still missing?
Where is XML generated, validated, and archived? Does this happen within SAP itself (e.g. via SAP DRC), through middleware, or via an external service provider? Is the archive GoBD-compliant and audit-proof?
What does the error process look like for rejected invoices? Who receives the error notification? Who corrects it? Within what timeframe? Is there monitoring in place?

These five questions quickly reveal whether an organization is on track — or whether there is a structural need to act.

The Bottleneck Nobody Is Talking About

There is a structural problem that makes the e-invoicing mandate even more urgent for many organizations than the deadlines themselves: the availability of qualified consultants and implementation partners.

Between ongoing day-to-day business, seasonal peaks, and structural skills shortages, there is little room for last-minute system changes. As the 2027 and 2028 deadlines approach, the pressure on organizations to find qualified staff and consulting capacity is set to peak — precisely when a large share of affected companies will be trying to implement at the same time.

Organizations that start implementation at the end of 2026 will find fully booked SAP implementation partners, rising day rates, and waiting times of several months. The deadline does not wait.

E-Invoicing as an Opportunity, Not Just an Obligation

It is worth not viewing this topic exclusively as a compliance project. Organizations that set things up properly now — receiving and processing structured and validated with clear ownership, outbound sending scalable and format-capable, compliance operations with monitoring and audit-proof archiving — simultaneously lay the foundation for greater automation, faster payment processes, and lower error rates in financial accounting.

They are also prepared for what comes after the e-invoicing mandate: the European reporting system under ViDA (VAT in the Digital Age), which builds on structured invoice data as its foundation.

Self-Assessment: Where Does Your Organization Stand?

If you answer at least two of these questions with "No," there is a concrete need to act:

Can we technically receive and validate XML invoices (XRechnung, ZUGFeRD) for format compliance today?
Are we archiving the XML original in a GoBD-compliant, audit-proof manner — not just an accompanying PDF?
Do we know which SD and FI document types in our SAP system must be sent as e-invoices from 2027?
Is there a defined error process for rejected or invalid invoices?
Have we concretely evaluated SAP DRC or an alternative solution?

Free E-Invoicing Readiness Check for SAP FI/SD/MM

In 30 minutes, we check together whether your organization is prepared for receiving, processing, and sending e-invoices in SAP —

from master data quality through the right system architecture to the error handling process.

Request E-Invoicing Check →