E-invoicing in Germany: XRechnung, ZUGFeRD and a practical guide

Germany is taking a phased approach toward mandatory e-invoicing with three main milestones:

As the second stage nears, the leniency granted since 2025 will run out. With large businesses being required to issue e-invoices, this means companies of all sizes must be able to receive them. Those that cannot will risk government penalties and face operational setbacks such as increased invoice rejections and manual workarounds.

Three main factors have driven Germany's shift to e-invoicing:

Germany's current e-invoicing requirements should be viewed as more than a standalone compliance obligation; they establish the structured invoice data that will support the country's next phase of VAT digitalisation.

German authorities have been explicit about what comes next: the e-invoicing mandate is forming the foundation for future digital reporting requirements, also known as e-reporting.

In September 2026, Germany's Federal Ministry of Finance (BMF) announced a timeline for a future B2B digital reporting system. According to the announcement, e-reporting legislation is expected to begin in 2027, followed by a voluntary pilot phase from early 2029. Mandatory e-reporting is then planned to go live in Germany by 1 July 2030.

Germany’s plan for mandatory e-reporting lines up with real-time reporting obligations that will be introduced with the EU’s VAT in the Digital Age initiative (ViDA). The EU-wide ViDA initiative establishes that by 2030, VAT reporting for cross-border B2B transactions within the EU will become fully digital. ViDA introduces Digital Reporting Requirements (DRR) that require near-real-time, transaction-level reporting to tax authorities.

Germany’s B2B e-invoicing framework follows a decentralised, post-audit approach. Businesses exchange invoices directly using compliant structured formats, without submitting each invoice to a central government platform for clearance or approval.

Tax authorities may request invoice data during an audit, but there is no obligation to transmit data to the tax office at the time of issuance. Instead, companies can choose to continue exchanging invoices directly with their trading partners.

Germany also applies a substantial national data protection framework alongside the GDPR through the BDSG (Bundesdatenschutzgesetz). Trading partners must implement appropriate technical and organisational safeguards based on the sensitivity of the data.

Germany's decentralised model separates e-invoicing and e-reporting, as seen in the typical invoicing procedure:

1. A business creates and sends an invoice via the EN 16931-compliant format and channel (e.g. EDI, Peppol, email, API integration) previously agreed upon between trading partners.
2. The recipient processes the invoice.
3. Invoice data is recorded in the recipient’s ERP and tax processes.
4. VAT returns and related tax information are reported later.

ELSTER (ELektronische STeuerERklärung) is Germany's electronic tax reporting system for private individuals and businesses alike. Businesses use ELSTER for filing VAT returns to the relevant Finanzamt (local tax office).

ELSTER is not a platform for exchanging e-invoices or e-reporting. This separation is important because ELSTER doesn't play the same role as Italy's SDI or Poland's KSeF. Those platforms form part of centralised e-invoicing models, which require the use of a government-specified platform for both exchanging e-invoices and e-reporting.

As of 2026, Germany has not confirmed whether ELSTER will be expanded to align with future real-time VAT reporting obligations.

To comply with Germany’s e-invoicing mandate, business must use structured electronic invoices that align with EN 16931 standards. The two most common formats for e-invoices in Germany are ZUGFeRD and XRechnung, which are designed to serve different purposes.

For many private sector businesses, ZUGFeRD can offer a smoother transition because it retains a familiar PDF view while providing structured data. XRechnung is more common in public sector invoicing and may be required by certain government customers. The right choice depends on who you invoice and the requirements of your customers.

Germany’s B2B e-invoicing mandate is not connected to the B2G mandate, which has required e-invoicing to the public sector since 2020.

One potential source of confusion is that while Germany's core B2B e-invoicing mandate is largely uniform nationwide, public sector (B2G) invoicing remains fragmented.

Suppliers to federal authorities follow federal requirements, often using public sector portals such as OZG-RE, while individual German states (Bundesländer) and municipalities may operate on different platforms and administrative processes.

Although Bundesländer requirements generally form around standards such as the use of XRechnung, the practical implementation is not fully harmonised.

As a result, different Bundesländer may have different requirements:

• Different public-sector platforms
• Different onboarding requirements
• Different implementation timelines
• Different administrative procedures

Public sector customers may require identifiers such as a Leitweg-ID to ensure invoices are routed to the correct authority or department.

Best practices for navigating Bundesländer-specific requirements:

• Verify invoice submission requirements with each public sector customer before implementation.
• Use EN 16931-compliant formats such as XRechnung wherever required.
• Consider a service provider or platform capable of supporting multiple public sector channels and workflows.
• Document state-specific requirements centrally so procurement, finance, and accounts receivable teams work from the same information.
• Include public sector customers in e-invoice testing before moving to implementation.

While these best practices are not necessarily required, they prepare businesses for both state-specific obligations and eventual e-reporting regulations set by the BMF and ViDA.

Each German business needs both a compliant invoice format and an appropriate delivery method. XRechnung and ZUGFeRD are formats, while Peppol, email, APIs and EDI networks are delivery methods.

Peppol or another interoperable network

A Peppol Service Provider or comparable network provider can route structured invoices between connected participants. This can be useful for public sector invoicing and for organisations trading across several markets.

Direct API or EDI integration

Direct system integration can suit organisations with high invoice volumes or established trading partner connections. The integration can automate transmission between ERP, accounting and recipient systems. By 2028, EDI will require EN 16931-compliant or interoperable formats, therefore remaining a compliant exchange method when paper and PDFs are no longer valid.

E-invoicing service provider or platform

A service provider may support format validation, transformation, routing, integration and archiving. This can reduce the number of direct connections a business needs to maintain, particularly when customers require different formats or submission routes.

Email submission

Email submission may be used where accepted. Businesses should still ensure that the invoice file itself contains the required structured data and that the chosen route supports appropriate security, traceability and exception handling.

Germany's mandate does not prescribe a single technology approach, which gives businesses flexibility in how to exchange invoices. However, that flexibility also makes it important to assess solutions against a set of technical, operational, and compliance criteria.

Whether you use direct integration, email or a service provider, the underlying solution must be able to support your compliance, operational, and future reporting requirements. Businesses with varied customer and supplier requirements may need a solution that supports more than one exchange method.

Many businesses focus on the issuing deadlines, but the first compliance challenge is correctly receiving and processing structured invoices. E-invoicing readiness extends beyond selecting a format or service provider; it requires coordination across finance, tax, procurement, accounts payable, accounts receivable, and IT to ensure invoices can be exchanged, validated, archived, and reported efficiently.

Only with this cross-departmental effort can businesses determine readiness for the German e-invoicing mandate. Form a dedicated team to align a companywide compliance plan, then follow these practical steps:

1. Map inbound and outbound invoice flows.
2. Identify the entities and transactions that fall within scope.
3. Confirm the deadlines applicable to each business entity.
4. Assess whether existing systems can create and process structured invoices.
5. Confirm accepted formats and channels with key trading partners.
6. Validate customer, supplier, VAT and routing data.
7. Test receipt, issuance, validation, rejection and correction workflows with representative trading partners.
8. Establish compliant archiving and audit trail procedures.
9. Assign responsibilities across tax, finance, IT, procurement, accounts payable and accounts receivable.
10. Monitor regulatory and technical updates.

Germany's e-invoicing mandate is more than a one-time regulatory change. This is particularly relevant in Germany, where businesses are simultaneously preparing for domestic e-invoicing requirements while awaiting clarity on both domestic and ViDA reporting obligations.

While the immediate focus for most German businesses is meeting the 2027 and 2028 deadlines, the decisions made today around formats, data quality and invoice exchange methods will also shape readiness for future demands.

And the implications extend beyond compliance, into opportunities for a better-functioning business. For many organisations, the lasting impact of e-invoicing will not be compliance itself; it will be the improvements it drives in data quality, process efficiency, competetive advantage and reporting readiness.