E-Invoicing for Multi-Entity Companies in Germany

Managing e-invoicing for one German business is relatively straightforward. Managing it across multiple legal entities is not. Each subsidiary may have different ERP systems, invoice formats and operational processes, but every entity remains responsible for meeting Germany's e-invoicing rules. Without a common compliance approach, finance teams often end up managing multiple disconnected processes instead of one scalable framework.

Key Takeaways

• Every German legal entity remains individually responsible for complying with Germany's e-invoicing requirements, even when finance operations are centralised.
• Multi-entity businesses need standardised invoice formats, governance and controls without removing entity-level flexibility.
• One should plan beyond today's mandate: Germany's regime is phased to 2025 (receive), 2027 (issue, turnover > €800k) and 2028 (issue, all). A domestic reporting layer (Stage 2) is expected from 1 July 2030 at the earliest, aligned with the EU's ViDA.
• A single e invoicing solution for multi entity companies helps reduce operational complexity, improves visibility across subsidiaries and simplifies future regulatory changes.
• Choosing the right e invoicing solution provider for multi entity companies is as much about long-term compliance as it is about today's mandate.

What are Multi-Entity Companies in Germany?

A multi-entity company is a corporate group that operates through multiple legal entities under a common parent organisation. These entities may include German subsidiaries, branches or affiliated companies, each with its own VAT obligations, customers, suppliers and accounting records. While finance may be managed centrally, compliance responsibilities remain with each individual legal entity.

What are the challenges of Multi-Entity E-Invoicing?

For a multinational group with ten or twenty German entities, e-Invoicing compliance rarely stays that simple. Every subsidiary often develops differently over time. One may run SAP S/4HANA, another Microsoft Dynamics, while an acquired business could still be using a local ERP. Procurement teams follow different processes. In practice, finance teams usually encounter five recurring challenges.

1. Different ERP systems across subsidiaries

Many corporate groups grow through acquisitions. As a result, subsidiaries often continue using their existing ERP systems for years. Building separate integrations for every ERP quickly becomes expensive. More importantly, every regulatory update has to be replicated across multiple systems. What begins as an IT project gradually becomes an ongoing maintenance exercise. A central e-invoicing platform helps standardise compliance without forcing every subsidiary onto the same ERP.

Example: Consider a manufacturing group with six German subsidiaries. The parent company runs SAP S/4HANA, one acquired business uses Microsoft Dynamics, while another still operates on Oracle NetSuite. Each entity may comply with the same German e-invoicing rules, but integrating and maintaining three different ERP environments quickly becomes a challenge. 

2. Different invoice formats and transmission methods

Germany accepts any structured electronic invoice format that complies with EN 16931 and meets the requirements of § 14 UStG. In practice this means XRechnung (the German CIUS maintained by KoSIT), ZUGFeRD in version 2.0.1 or later (but not the MINIMUM and BASIC-WL profiles, which are deemed image-equivalent), Peppol BIS Billing 3.0, and the French Factur-X format (which shares its data model with ZUGFeRD). 

Also, businesses may exchange invoices through Peppol, EDI or even email where the structured invoice remains intact.

The difficulty for multi-entity groups is consistency.

1. Subsidiaries may exchange invoices through Peppol. 
2. Another may rely on EDI with long-standing customers. 
3. A third may still receive invoices through email. 

Supporting different channels is normal. Managing them through different systems is where complexity increases.

3. Limited visibility across entities

Finance leaders rarely struggle because invoices cannot be generated. They struggle because nobody has a complete picture. One entity may have rejected invoices waiting for correction while another has transmission failures that go unnoticed for days. 

Without central monitoring, identifying these issues becomes dependent on manual follow-ups, spreadsheets and local teams. This becomes even more important as governments continue moving towards real-time compliance.

4. Different customer requirements

Not every customer accepts invoices in the same way. Public authorities may require XRechnung. Private businesses may prefer ZUGFeRD or Peppol BIS Billing 3.0. Some buyers continue using established EDI networks. A good implementation supports these differences without forcing finance teams to manage separate invoicing processes for every customer.

5. Preparing for what's next

Many organisations are treating Germany's 2025 and 2027 milestones as the finish line. They are not. Germany's mandate is phased: structured exchange now, domestic transaction reporting from 1 July 2030 at the earliest under Stage 2, aligned with ViDA. Businesses that plan only for today's requirements may need to rebuild.

Are Intercompany Invoices Between German Entities in Scope? 

Yes, in many cases. The mandate applies to domestic B2B supplies between domestic taxable persons (inländische Unternehmer) i.e. businesses whose seat, place of management or participating VAT establishment (Betriebsstätte) is in Germany (§ 14 Abs. 2 UStG; BMF-Schreiben of 15 October 2024, Rn. 13–16).

Two exceptions matter:

• A mere German VAT registration of a foreign-established business, with no participating establishment, does not trigger the issuing obligation.
• Within a VAT group (Organschaft, § 2 Abs. 2 Nr. 2 UStG), supplies between members are non-taxable internal transactions (Innenumsätze) are treated as internal accounting documents, not invoices and so the mandate does not apply to those intra-group flows.

The deciding factor is the legal relationship between the parties, not the ownership structure.

For example: if a parent company invoices its German subsidiary for shared IT services, management fees or administrative support, the invoice must generally comply with Germany's electronic invoicing requirements, provided the transaction itself is taxable.

On the other hand, transactions that do not require a VAT invoice, such as internal cost allocations that are purely accounting entries, are not treated as e-invoices. This distinction matters more than many organisations expect.

During implementation, finance teams often focus on customer invoices while overlooking intercompany billing. That works until month-end closes begin and internal invoices start following a completely different process from customer invoices. Eventually, someone has to standardise both.

For large corporate groups, it is usually more practical to bring customer invoices and intercompany invoices onto the same compliance framework from the beginning rather than creating separate workflows.

How Multi-Entity Companies Can Comply with Germany's Core E-Invoicing Requirements

1. Choosing the right invoice format

An e-invoice is compliant only if it is issued, transmitted and received in a structured electronic format that satisfies EN 16931. Multi-entity groups in Germany typically standardise on one of: XRechnung (pure-XML, CIUS BR-DE-* rules apply), ZUGFeRD v2.0.1 or later in the BASIC, EN 16931 or EXTENDED profile, Peppol BIS Billing 3.0, or Factur-X. 

Note: Since 1 January 2025, where a ZUGFeRD invoice contains both an XML part and a visual PDF rendition that differ, the XML part is the leading content for VAT purposes.

There is no single format that suits every business. Public sector customers generally require XRechnung. Many private businesses prefer ZUGFeRD because it combines structured XML with a human-readable PDF. Companies already connected to the Peppol network often exchange invoices using Peppol BIS.

For multi-entity groups, the objective should not be to force every subsidiary onto one format. Instead, standardise the underlying data while allowing the platform to generate the format required by each customer.

That approach avoids maintaining multiple invoice creation processes across the organisation.

2. Choosing the right transmission channel

Germany follows a decentralised exchange model. Invoices are exchanged directly between trading partners instead of passing through a central government platform. Businesses may send invoices through Peppol Access Points, EDI networks or email, depending on what the buyer accepts.

This creates another challenge for multi-entity organisations. Different subsidiaries often use different transmission methods because of historical customer relationships. Replacing every existing connection is rarely practical.

Instead, businesses should look for a platform that supports multiple transmission channels through a single interface. Finance teams get one operational view, while customers continue receiving invoices through their preferred channel.

3. Maintaining GoBD-compliant archiving

Generating a compliant invoice is only one part of Germany's requirements. Electronic invoices must be retained in accordance with § 14b Abs. 1 UStG and the GoBD. Following the Viertes Bürokratieentlastungsgesetz (BEG IV, BGBl. I 2024 Nr. 323), the retention period for invoices was reduced from ten to eight years and applies to invoices for which the retention period had not yet expired on 1 January 2025. 

The archive must preserve authenticity of origin, integrity of content and human readability throughout the retention period. Two carve-outs remain relevant: records subject to § 22 UStG continue to require a ten-year retention period, and the correction period under § 15a UStG (e.g. for real estate) may effectively extend the documentation horizon. The updated GoBD requirements are restated in the BMF-Schreiben vom 14. Juli 2025 (BStBl. I 2025, S. 1806).

This becomes more difficult when every subsidiary stores invoices differently. Some maintain local archives. Others rely on ERP storage. Acquired entities may still use legacy document management systems. Over time, these fragmented repositories create unnecessary audit risk. A central archive with entity-level access controls is usually easier to govern and significantly easier to audit.

4. Preparing for Germany's domestic e-reporting

Today's mandate focuses on exchanging structured invoices between businesses. That will not be the end state. Germany's current mandate covers structured invoice exchange only (Stage 1). A domestic digital reporting layer (Stage 2), under which transaction data would be reported to the tax authorities, is expected from 1 July 2030 at the earliest, aligned with the EU's ViDA Digital Reporting Requirements rather than ahead of them. 

No earlier statutory milestone has been published. Businesses that build only for invoice exchange today should nonetheless choose platforms that can be extended to transaction reporting without a system rebuild.

5. Preparing for ViDA's Digital Reporting Requirements in 2030

For groups operating across Europe, Germany's mandate is only one part of a much larger compliance programme. From July 2030, the EU's VAT in the Digital Age (ViDA) package will introduce Digital Reporting Requirements for intra-EU B2B transactions. 

Under ViDA (Council Directive (EU) 2025/516), the e-invoice for an intra-EU B2B transaction must be issued within ten days of the chargeable event. Reporting to the tax authorities is then effectively real-time on the supplier side, as the structured invoice data is transmitted at the point of issuance. The recipient of an intra-EU supply must submit its corresponding report within five days. This regime replaces the existing Zusammenfassende Meldung (ZM), known in EU terminology as the EC Sales List, for transactions in scope.

An implementation that works only for Germany may require another redesign before 2030. That is why many organisations are choosing platforms that can support both current German obligations and future EU-wide reporting requirements from a single technology stack.

How to Evaluate an E-Invoicing Solution for Multi-Entity Companies in Germany

Most businesses evaluating an e-invoicing platform ask the wrong first question. They compare formats supported, implementation timelines or license costs. Those things matter. But they are rarely what causes problems a year after go-live.

The bigger question is this: Will this platform still work when Germany's compliance requirements become more demanding? For multi-entity businesses, changing an e-invoicing platform later is significantly harder than selecting the right one in the first place.

Here are the areas worth evaluating.

1. Can it manage multiple legal entities from one platform?

A good e invoicing solution for multi entity companies should allow each legal entity to maintain its own configuration while giving central finance teams visibility across the group.

You should be able to monitor invoice status, exceptions and compliance centrally without taking operational control away from local finance teams. If every subsidiary requires a separate implementation, separate integrations and separate reporting, the operational cost rises quickly.

2. Does it integrate with different ERP systems?

One entity may use SAP S/4HANA, another SAP ECC, while recently acquired businesses continue using Microsoft Dynamics, Oracle NetSuite or industry-specific systems. Your platform should integrate with all of them without creating a separate compliance project for every ERP.

Even more importantly, regulatory changes should be managed within the e-invoicing platform rather than requiring modifications to each ERP every time the law changes.

3. Does it support every transmission channel?

Germany's decentralised model gives businesses flexibility. Customers may receive invoices through Peppol, EDI or email, depending on their preferred method. That flexibility becomes difficult to manage if every transmission channel operates independently.

Look for a solution that supports all major transmission methods through one platform. Finance teams should have one dashboard, one exception queue and one audit trail regardless of how invoices are exchanged.

4. Can it scale across countries?

Very few multinational businesses stop with Germany. Belgium, France, Poland and other European countries are introducing their own digital reporting and e-invoicing requirements. Outside Europe, many organisations are already complying with mandates in the UAE, Malaysia, India and Saudi Arabia.

Deploying a different platform in every country usually creates more complexity than compliance. A better approach is to choose a platform that supports multiple jurisdictions while allowing country-specific configuration. That reduces implementation effort and gives finance teams a consistent operating model across regions.

5. Does it provide operational visibility after go-live?

Go-live is not the finish line. Invoices fail. Buyer master data changes. ERP updates introduce mapping issues. Government specifications evolve. The platform should make these issues visible before they become month-end surprises.

Look for features such as real-time status tracking, automated validation, reconciliation, exception management and audit trails. These reduce manual follow-ups and help finance teams identify issues early instead of during VAT reporting.

6. Does the provider have proven regulatory expertise?

Technology alone is not enough. Germany's e-invoicing rules will continue evolving as domestic e-reporting develops and ViDA implementation approaches.

An e invoicing solution provider for multi entity companies should have dedicated tax and regulatory expertise, not just software developers. 

Ask practical questions.

• How quickly are regulatory updates delivered?
• Who interprets changes in legislation?
• Will your internal IT team have to build every update?

These answers often tell you more than a product demonstration.

How ClearTax Supports Multi-Entity E-Invoicing Compliance in Germany

Managing multiple entities requires more than invoice generation. It requires consistent compliance across subsidiaries without increasing operational effort.

ClearTax is designed with that objective in mind. ClearTax manages multiple German legal entities through a single platform, each with its own configuration, VAT registration and ERP connection, while giving central finance teams a consolidated view of invoice status, exceptions and audit trails.

Pre-built integrations with SAP, Microsoft Dynamics, Oracle NetSuite and others mean regulatory updates are absorbed at the platform level, not rebuilt per entity. The same platform extends to ViDA-scope jurisdictions across Europe and beyond, removing the need for separate country implementations as your compliance footprint grows.

The result is a platform built not only for Germany's current e-invoicing mandate but also for the reporting obligations that businesses are likely to face over the coming years.

Conclusion

The technology decisions made today will influence how easily businesses adapt to Germany's future e-reporting requirements and the EU's ViDA framework.

The businesses that will find future mandates easier are not necessarily the ones that are implemented first. They are the ones that built a compliance framework that can grow with every new entity, acquisition and regulatory change.