Since January 1, 2025 E-invoicing is mandatory in Germany. All companies must be able to receive electronic invoices – and from 2027/2028 onwards, also send them. This guide explains everything you need to know: deadlines, formats, exceptions, and implementation in SAP.
What is the e-invoicing obligation?
The e-invoicing obligation requires companies in Germany to create, send, and receive electronic invoices in a structured data format. This is based on the... Growth Opportunities Act, which was adopted by the Federal Council on March 22, 2024 and fundamentally changed Section 14 of the Value Added Tax Act (UStG).
An e-invoice within the meaning of the law is not Simply send an invoice in PDF format via email. This is an invoice in a structured electronic format that allows for automatic processing. The invoice must comply with the European standard. EN 16931 be compatible or interoperable with it.
For companies using SAP as their ERP system, this means that e-invoicing processes must be directly integrated into SAP – for both incoming and outgoing invoices. Solutions such as GOpus® eInvoice This seamless integration is precisely what enables it.
Who is affected by the e-invoicing obligation?
The obligation to issue e-invoices generally applies all companies in Germany, who operate in the B2B (business-to-business) sector:
- All domestic B2B sales – regardless of company size or industry
- Corporations (GmbH, AG) as well as partnerships and sole proprietor
- Corporations using SAP systems just like medium-sized companies
- Small value invoices up to €250 (according to §33 UStDV)
- Travel tickets (according to §34 UStDV)
- Tax-exempt services according to §4 Nos. 8 to 29 UStG
- B2C invoices – invoices to private individuals are not affected
Important: The obligation to Reception The requirement for e-invoices has been in effect for all companies since January 1, 2025 – without exception and without a transition period.
Timetable and transition periods
The legislator has provided for a phased timetable with transition periods:
Which e-invoice formats are permitted?
Not every electronic document qualifies as an e-invoice. Legislation requires a structured format according to the European standard EN 16931:
XRechnung
German standard, pure XML format according to EN 16931. Mandatory for B2G since 2020, now also a B2B standard. Ideal for fully automated processing.
ZUGFeRD 2.x
Hybrid format: PDF + embedded XML. Profiles COMFORT, EXTENDED and XRECHNUNG are EN-16931 compliant. Profile MINIMUM is sufficient. not out of.
Factur-X
German-French equivalent to ZUGFeRD, technically identical. Particularly relevant for cross-border invoices between Germany and France.
Peppol BIS Billing 3.0
European network for e-documents. Based on EN 16931, ideal for international invoice exchange and connection to government agencies.
Checklist: How to prepare your company
The switch to e-invoicing affects not only IT, but also processes, organization and compliance:
- Ensure reception capability – Can you receive and process XRechnung and ZUGFeRD files? Mandatory since January 1, 2025.
- Inventory of invoicing processes How are invoices created, sent, received, and archived? Where are there breaks in the process?
- Check ERP system Does your SAP system support these formats? Is an add-on like this one available? GOpus® eInvoice necessary?
- Set format – XRechnung for machine processing or ZUGFeRD for visual + machine representation?
- Inform business partners – Coordinate future formats and transmission methods with customers and suppliers.
- Adjust archiving – Ensure GoBD-compliant, audit-proof archiving (10-year retention requirement).
- Set up validation - With a E-Invoice Validator Check for compliance with standards.
- Conduct test phase – Test the entire process with selected business partners.
- Employees are trained – Familiarize financial accounting, purchasing and IT departments with new processes.
- Keeping deadlines in mind – Plan sufficient lead time for the changeover.
Implementing mandatory e-invoicing in SAP
For companies using SAP ERP or SAP S/4HANA, direct integration into existing SAP processes is the most efficient approach. A standalone solution outside of SAP creates media breaks and additional manual effort.
GOpus® eInvoice – SAP certified
Success story: Westfalen AG
The Westfalen AG GOpus® eInvoice has integrated the entire e-invoicing process into SAP – from invoice receipt and automatic processing to sending in all relevant formats. The result: full compliance with e-invoicing regulations and a significant reduction in manual effort in accounting.
Frequently asked questions about the obligation to issue e-invoices
What is the e-invoicing obligation and who does it affect?
What happens if I fail to comply with the e-invoicing obligation?
What transitional periods apply?
How do I implement the e-invoicing requirement in SAP?
What is the difference between ZUGFeRD and XRechnung?
How long does the introduction take?
Do I need to archive e-invoices?
Does the e-invoicing requirement also apply internationally?
Further information
- GOpus® eInvoice – The SAP solution for e-invoicing, ZUGFeRD & XRechnung
- eInvoicing AZ: All terms related to electronic invoicing
- Free e-invoice validator – check invoices online
- E-invoicing regulations by country worldwide
- E-invoicing obligation varies by federal state in Germany
- Success story: Westfalen AG with GOpus® eInvoice
- ZUGFeRD vs. XRechnung: Which format is suitable?
- Invoice receipt: Receiving e-invoices in SAP
- Outgoing invoices: Sending e-invoices from SAP
- GOpus® eInvoice: S/4HANA vs. ERP in comparison
- E-Invoice Checklist: 10 Steps to Compliance
