Germany’s
E-invoicing Mandate:
From Readiness to Results
What Finance and IT need to know about deadlines, formats, B2B e-invoicing, ERP integration, and automated invoice processes.
What changes when invoices become structured data
Germany’s e-invoicing mandate is reshaping B2B invoicing at a fundamental level. It is based on the German Growth Opportunities Act, which revised the rules for issuing invoices for transactions carried out after December 31, 2024. Since January 1, 2025, businesses must be able to receive and process e-invoices for domestic B2B transactions. At the same time, e-invoicing is becoming the regular invoice format for transactions between domestic businesses, although transition periods still apply to invoice issuance.
An e-invoice is no longer simply an invoice sent by electronic means. What matters is a structured electronic format that enables electronic processing. This shifts the focus beyond invoice delivery alone. Companies also need the ability to reliably receive structured invoice data, validate it, and integrate it into existing finance and ERP processes.
The mandate is therefore more than a regulatory change. It lays the groundwork for end-to-end digital invoice processes, reduces manual data entry, and prepares businesses for a future transaction-based reporting system. The specific design of such a reporting system has not yet been finalized in law. However, mandatory e-invoicing creates the technical and organizational foundation for it.
For businesses, this creates a clear direction of travel. Compliance is the starting point, but the real value comes from integration, transparency, and automation in accounts payable and accounts receivable processes.
Key milestones through 2028: receiving e-invoices and preparing outbound processes
Germany is rolling out its e-invoicing mandate in phases. Since January 1, 2025, businesses must be able to receive structured e-invoices. For outbound invoicing, transition periods remain in place until the end of 2027. That makes early planning essential. Companies need to look beyond the legal deadlines and prepare the related process, system, data quality, and ERP integration requirements in time.
| Period | Milestone | Business implications |
| Since January 1, 2025 | Businesses must be able to receive e-invoices. | Finance and IT need a reliable process for accepting structured invoice data, checking it, and transferring it into existing systems. This applies to domestic businesses within the meaning of German VAT law, including small businesses. |
| January 1, 2025 to December 31, 2026 | Until the transition period ends, businesses may still use non-structured invoice formats, such as standard PDFs, invoice emails, or image files, provided the recipient agrees. | This window gives companies time to prepare outbound invoicing, including formats, responsibilities, and ERP integration. However, non-structured invoices will only remain workable where recipients continue to accept them. |
| Until December 31, 2027 | Invoice issuers with prior-year revenue of up to €800,000 can use the extended transition period. | Small businesses within this scope should still clarify early how e-invoices will be created, validated, sent, and archived. |
| Until December 31, 2027 | Certain existing EDI procedures may continue to be used during the transition period, provided the relevant mandatory information can be extracted correctly. | Businesses with established EDI processes should assess whether their current setup meets the e-invoicing requirements or needs to be adapted in time. |
| From January 1, 2028 | E-invoicing generally becomes mandatory for domestic B2B transactions, unless an exemption applies. | By then, outbound invoicing, inbound processing, archiving, monitoring, and ERP integration need to be aligned with structured e-invoices. |
Defining the scope of Germany’s e-invoicing mandate
Germany’s e-invoicing mandate is mainly relevant for domestic B2B transactions that fall under German VAT law. For companies, scope is not just a technical question. It depends on the transaction, the legal entity, and the customer or supplier relationship behind each invoice. Finance and IT should therefore work together to identify which invoice flows are in scope before adapting systems and processes.
Start with domestic B2B
invoice flows
The mandate generally applies when both parties are considered domestic businesses for German VAT purposes. This can include a registered office, place of management, residence, habitual residence, or VAT fixed establishment in Germany. Companies should map these criteria against their accounts payable and accounts receivable processes to understand which flows are affected.
Do not mix up
receiving and issuing
Receiving comes first. Since 2025, businesses must be able to receive e-invoices. Issuing them follows a phased timeline, with transition periods running until 2026, 2027, or 2028 at the latest. Small businesses also need to receive e-invoices, but they are exempt from issuing them. That makes it important to separate inbound and outbound invoicing from the start.
Not every invoice
is in scope
The mandate does not cover every invoice. Exemptions include certain low-value invoices up to €250 including VAT, tickets, and invoices to consumers (B2C). These exceptions need to be reflected in the process design, not handled as side notes. Tax, Finance, and IT should define clear rules, so invoices are classified, processed, and archived correctly.
Choosing the right formats and transmission routes
Germany’s e-invoicing mandate does not prescribe one specific transmission channel. For invoice formats, the key reference point is the European standard EN16931. In Germany, this makes formats such as XRechnung and ZUGFeRD especially relevant. Other agreed formats, including EDI, may also be acceptable if the VAT-related mandatory invoice information can be extracted correctly and completely.
For businesses, the choice of format is far more than a technical preference. It affects how invoices are validated, connected to ERP systems, archived, and used in downstream finance processes.
The right setup depends on more than the legal requirement itself. Existing systems, trading partner expectations, automation goals, and the desired level of integration with finance and ERP processes all play a role.
XRechnung for fully structured XML invoice data
XRechnung is a fully structured XML format and is already well established in public procurement. It is particularly useful for companies that want invoice data to move through their processes in a consistently machine-readable way. Finance benefits from clear data for invoice checks and posting, while IT is responsible for processing, validation, and integration with ERP or workflow systems.
ZUGFeRD for hybrid invoices with PDF and XML
ZUGFeRD brings together a human-readable PDF and an embedded XML data set. According to the German Federal Ministry of Finance, ZUGFeRD formats from version 2.0.1 generally meet the VAT requirements for an e-invoice, except for the MINIMUM and BASIC-WL profiles.
This can make the transition easier because the invoice remains readable while also carrying structured data for electronic processing. The decisive element, however, is the structured XML. Companies should make sure their processes can extract, validate, and use the XML data end to end, rather than simply storing the PDF or handling it manually.
EDI for established digital invoice processes
Many companies already use EDI to exchange business documents electronically. This existing infrastructure can be a strong asset, provided the relevant invoice data can be processed correctly, completely, and in a way that aligns with e-invoicing requirements. That means companies should not replace established EDI setups too quickly. They may remain suitable if the VAT-related mandatory invoice information can be extracted correctly and in full.
Peppol as a strategic channel
Peppol is not currently mandatory for B2B e-invoicing in Germany. However, it can play an important role for companies with international operations or standardized partner connections. Organizations that are planning e-invoicing beyond Germany should consider Peppol early in their architecture. This is especially relevant where other country mandates, public-sector invoicing, or e-procurement processes are part of the wider roadmap.
A valid e-invoice is more than a valid format
Germany’s e-invoicing mandate changes the invoice format, but not the underlying content requirements. An e-invoice must be technically receivable and processable. Its structured data also needs to be complete, accurate, and auditable.
Key requirements still apply:
Preparing for e-invoicing readiness
E-invoicing readiness is not achieved by choosing a format alone. Companies need to make sure structured invoice data can move reliably through the entire process, from receipt to archiving. Finance and IT should assess which systems, processes, data flows, controls, and responsibilities need to change.
A successful setup should meet compliance requirements while also creating the basis for automation and process improvement. Companies also need clear rules for determining which legal entities, transactions, supplier relationships, and customer relationships fall within the scope of the German B2B mandate.
Review invoice channels and system dependencies
Companies should start by mapping how invoices enter the organization today and which systems are involved. This includes ERP systems, invoice processing tools, archive systems, approval workflows, and existing EDI or portal-based processes. Without that visibility, e-invoicing is difficult to integrate properly.
Build in validation and data quality
Structured invoice data needs to be complete, accurate, and processable. Finance depends on reliable data for review, account assignment, and posting. IT needs to ensure that formats, interfaces, and validation rules are implemented in a technically stable way.
Define how exceptions and errors are handled
Not every e-invoice may move through the process without issues. Companies need clear procedures for missing mandatory information, format errors, differences between structured data and supporting documents, and supplier queries. Roles, escalation paths, correction processes, and status information should be defined in advance.
Plan ERP integration early
The real value of e-invoicing comes when invoices are not handled in isolation, but connected directly to ERP and finance processes. Only with integration can invoice checks, approvals, posting, monitoring, and archiving be managed efficiently.
Align with business partners
Companies should clarify early which formats and transmission channels will be used with customers, suppliers, and service providers. This reduces coordination effort and helps prevent technical details from becoming bottlenecks shortly before a deadline.
Turning compliance into business value
The e-invoicing mandate starts with compliance, but its impact goes further. Once invoices are available as structured data, companies can manage invoice processes more effectively, automate manual steps, and connect e-invoicing with their existing system landscape.
The greatest value comes when e-invoicing is not treated as a standalone requirement. With the right integration, a legal obligation can become a driver for better transparency, less manual effort, and more resilient digital processes.
Greater control over invoice operations
For Finance, e-invoicing changes how invoice processes are managed day to day. Structured invoice data provides a more reliable basis for review, account assignment, approval, and posting. As a result, invoices can be received and issued in line with legal requirements while also being processed faster, more transparently, and with fewer manual steps.
- Invoice data can be checked earlier and in a more structured way.
- Manual data entry and process breaks can be reduced.
- Approval and posting processes become easier to monitor and manage.
- Errors, missing mandatory information, and exceptions can be handled more precisely.
- Invoice status becomes more transparent, from receipt through to archiving.
- Collaboration with suppliers and internal departments becomes clearer because data, status, and responsibilities are easier to track.
The real value comes when e-invoices are not simply stored, but actively connected to upstream and downstream finance processes. This gives Finance greater control over processing times, data quality, and compliance across the full invoice lifecycle.
Integrated architecture rather than another tool
For IT, e-invoicing becomes a question of architecture. Receiving or generating the right format is only the first step. If invoice data still must be moved between tools by hand, the process remains fragile. IT teams therefore need a setup that can handle different formats and channels, connect to ERP and workflow systems, validate data, monitor status, and support archiving without adding another disconnected layer to the landscape.
- Relevant formats and transmission channels, such as XRechnung, ZUGFeRD, EDI, email, and Peppol where appropriate, need to be supported and connected technically.
- ERP systems, archive solutions, workflow tools, and existing EDI processes need to be integrated.
- Validation rules and exception handling need to be implemented reliably.
- Data flows need to be traceable, secure, and audit-ready.
- Future mandate changes should be manageable without rebuilding the architecture from scratch.
- International requirements should be considered early to avoid separate country-by-country solutions.
This is where IT creates the technical foundation for e-invoicing to become part of existing business processes rather than another system sitting next to them. The value lies in an integrated architecture that supports compliance while strengthening operational stability.
Finance and IT need to build the case together
E-invoicing sits between Finance and IT. Finance defines what the process needs to achieve from a business and compliance perspective. IT makes it work across data flows, interfaces, systems, and operational controls. The strongest results come when both teams agree early on how e-invoices will be received, checked, processed, monitored, and archived.
- Compliance requirements need to be translated into clear process and system requirements.
- Business validation rules and technical checks need to work together.
- Exceptions, errors, and supplier queries need clear ownership.
- Automation depends on data quality, process logic, and integration.
- Monitoring needs to provide both business visibility and technical traceability.
- E-invoicing readiness should support future digital invoicing and reporting processes.
The business case is not created by receiving an e-invoice alone. It comes from making structured invoice data usable throughout the process: in the ERP system, in approval workflows, in the archive, in reporting, and, looking ahead, across future e-invoicing and reporting mandates.
How SEEBURGER supports e-invoicing readiness in Germany
Germany’s mandate is not just about receiving structured invoice data. Companies also need to validate e-invoices, connect them with ERP and finance processes, archive them in an audit-ready way, and stay prepared for further national and international mandates. SEEBURGER supports this broader setup by combining e-invoicing compliance with integration, process automation, and scalable operations.
With the SEEBURGER E-Invoicing Hub and Peppol Access Point, companies can receive, process, transmit, and integrate e-invoices through a central setup. The Hub is an integrated SaaS solution for inbound invoices, outbound invoices, and regulatory reporting, providing a centralized view of e-invoicing processes.
Discover more about the SEEBURGER E-Invoicing Hub