E-Invoice Becomes Mandatory: What Companies Need to Do Now

The E-Invoice Requirement Is Coming

From January 1, 2025, electronic invoicing becomes mandatory for B2B business transactions in Germany. This affects practically every company that issues invoices to other businesses — and the regulatory pressure behind this change is significant.

The legal foundation is Germany's Growth Opportunities Act (Wachstumschancengesetz), passed by the Bundesrat in March 2024 after a lengthy legislative process. The act amends Section 14 of the German VAT Act (UStG) and introduces a phased obligation for structured electronic invoicing in domestic B2B transactions. But Germany is not acting in isolation here.

At the European level, the VAT in the Digital Age (ViDA) initiative by the European Commission provides the broader framework. ViDA aims to modernise EU VAT rules by 2030, with digital reporting and e-invoicing as central pillars. Germany's national rollout is therefore part of a larger continental shift toward real-time transaction reporting and digital tax compliance. Countries like Italy (since 2019), France (rolling out through 2027), and Romania have already implemented mandatory e-invoicing for B2B, and the rest of the EU is following. Companies operating across borders should prepare for a pan-European e-invoicing landscape, not just a German one.

The core motivation behind these regulations is straightforward: the VAT gap — the difference between expected and actually collected VAT revenue — costs EU member states an estimated 60 to 70 billion euros per year. Structured e-invoicing makes it far harder to falsify, lose, or delay invoices, and enables tax authorities to cross-check transaction data automatically.

What Is an E-Invoice?

An e-invoice is not simply a PDF sent by email. That distinction is critical and widely misunderstood. A traditional PDF invoice, even one generated by accounting software, is not machine-readable in the regulatory sense. A human or OCR software must extract the data from it — a process that is error-prone and does not satisfy the legal definition.

A compliant e-invoice is a structured data format that can be read, validated, and processed entirely by machines without human interpretation. The two most important standards in Germany are:

XRechnung is the official standard mandated for invoices sent to German public sector clients. It is a pure XML format — there is no visual component embedded in the file itself. While it satisfies legal requirements, displaying an XRechnung to a human reader requires dedicated viewer software. XRechnung is based on the European standard EN 16931 and is maintained by the Coordination Office for IT Standards (KoSIT).

ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) takes a hybrid approach. A ZUGFeRD file is a standard-looking PDF — readable by any PDF viewer — with a structured XML payload embedded inside it. This makes it more practical for businesses that still need human-readable documents in their workflows. The current version is ZUGFeRD 2.1, which is also fully EN 16931-compliant from the "EN 16931" profile level upward.

At the technical level, both XRechnung and ZUGFeRD use one of two underlying XML syntaxes:

• UBL (Universal Business Language): An OASIS standard widely used in Scandinavia and globally, structured as <cac:Invoice> elements.
• CII (UN/CEFACT Cross Industry Invoice): The syntax used by ZUGFeRD and common in Germany and France, structured differently but expressing equivalent data.

Both syntaxes are valid under EN 16931. The choice between them typically depends on your software ecosystem and your trading partners' preferences.

What makes these formats fundamentally different from a PDF is the semantic structure: every data field — invoice number, issue date, VAT amount, line items, bank details — occupies a defined, standardised XML element. An automated system can parse and process the data instantly, without ambiguity, without OCR, and without manual entry.

Which Formats Are Compliant?

The legal benchmark for a compliant e-invoice in Germany is conformance with EN 16931, the European standard for the semantic data model of the core invoice. EN 16931 defines which fields must, should, or may appear in an invoice, and how they must be expressed. Any format claiming compliance must correctly implement this standard.

In practice, compliant formats include:

• XRechnung 3.x (UBL or CII syntax) — the German government's preferred format, required for B2G invoicing via the ZRE (Zentraler Rechnungseingang) portals.
• ZUGFeRD 2.1 (EN 16931 profile and above) — profiles below EN 16931 (such as MINIMUM or BASIC WL) do not satisfy the full legal requirement for B2B mandatory e-invoicing.
• Factur-X (the French equivalent of ZUGFeRD, technically identical from version 2.1 onward) — relevant for cross-border invoicing to French clients.

The KoSIT validator is the authoritative tool for checking whether an XRechnung or ZUGFeRD file is technically compliant. Maintained by KoSIT (Koordinierungsstelle für IT-Standards), it applies the official Schematron rules published by the German government. Running your generated invoices through the KoSIT validator before sending them is strongly recommended — especially during a transition period when receiving systems may reject malformed invoices.

Formats that are not compliant as e-invoices under the new rules include standard PDFs, scanned paper invoices, Word documents, and EDI formats that do not conform to EN 16931 (though legacy EDI arrangements may be subject to transitional provisions). Images of invoices sent via email are explicitly excluded.

Who Is Affected?

Essentially all companies operating in the B2B sector in Germany. The requirement applies when both the issuing company and the receiving company are established in Germany for VAT purposes. Cross-border invoices and B2C (business-to-consumer) invoices are currently outside the scope of the domestic mandate, though ViDA will address cross-border transactions at the EU level by 2028.

The obligation will be rolled out in stages based on company size:

The 2025 receiving obligation is already in effect. This means your accounting system must be capable of ingesting and processing XRechnung or ZUGFeRD files today — regardless of whether you are a micro-enterprise or a large corporation. Refusing to accept an e-invoice from a supplier because your system cannot handle it is not a valid excuse under the law.

The sending obligations give smaller companies more time to prepare, but the timeline is shorter than it may appear when you account for software evaluation, procurement, testing, and staff training.

Consequences of Non-Compliance

Failing to comply with e-invoicing requirements carries real consequences — operational, financial, and reputational.

Tax and legal exposure: An invoice that does not meet the legal format requirements may be considered an invalid invoice under Section 14 UStG. This has direct implications for VAT deduction: your client may be unable to claim input VAT on a non-compliant invoice, which creates friction in business relationships and may trigger tax audits or assessments.

Payment delays and rejected invoices: Public sector clients in Germany (municipalities, federal agencies, state governments) have been rejecting non-XRechnung invoices for B2G transactions since 2020 in most federal states. As B2B requirements take hold, private sector companies will increasingly build automated rejection into their accounts payable systems. A non-compliant invoice may simply bounce back.

Loss of competitive positioning: Companies that can offer seamless e-invoicing to their clients remove a significant friction point in the procurement and payment cycle. Companies that cannot may find themselves deprioritised as vendors — particularly in larger corporate supply chains where procurement teams are optimising for fully automated invoice processing.

Audit risk: The German tax authority (Finanzamt) will have far more visibility into transaction data as e-invoicing scales. Gaps or inconsistencies between submitted invoices and actual transactions will be easier to detect. Companies that delay compliance are also more likely to have disorganised invoice archives, which creates additional exposure during audits.

Fines: While the Wachstumschancengesetz does not introduce specific new fines for e-invoicing non-compliance in the initial phase, general provisions of the tax code apply. Issuing an invalid invoice — or failing to maintain proper records — can result in penalties under Sections 26a and 379 of the German Fiscal Code (AO).

What Do You Need to Do?

1. Check Your System

Can your accounting software process e-invoices in XRechnung or ZUGFeRD format? Many modern systems — DATEV, SAP, Lexware, Sevdesk, Fastbill — already support one or both formats. Often a software update or the activation of a module is sufficient. Check your vendor's documentation and, if in doubt, contact their support team with a specific question: "Can your system generate XRechnung 3.x and ZUGFeRD 2.1 EN 16931-compliant invoices, and can it import and process incoming files in these formats?"

If your current system cannot be extended, this is the moment to evaluate alternatives. A migration now — while the sending obligation is still 12 to 24 months away — is far less stressful than a crisis migration under deadline pressure.

2. Adapt Your Processes

E-invoices require complete and correct master data. Structured XML formats are unforgiving — a missing tax number, an incorrect VAT ID, or an absent Leitweg-ID for a public sector client will cause the invoice to fail validation and be rejected. Work through your customer database and verify:

• Is all customer data current, including legal name, address, and VAT identification number?
• Do you have the Leitweg-ID stored for all public sector clients? (This routing identifier is mandatory for B2G invoicing in Germany.)
• Can your ERP or accounting system export structured invoice data in the required fields, or does it rely on free-text fields that an e-invoice format cannot accommodate?
• Do your invoice templates capture all EN 16931-required fields, including payment terms, buyer reference, and line-item tax categorisation?

3. Validate Before You Send

Before going live with e-invoice generation, validate your output. Use the KoSIT validator (available online at ecosio.com, mustangproject.org, and other platforms) to verify that your generated XML files pass the official Schematron rules. Testing against the validator catches format errors, missing mandatory fields, and incorrect value encoding before your clients or their systems do.

Create a small batch of test invoices covering your most common invoice scenarios — standard domestic sales, partial deliveries, credit notes — and run all of them through validation. Document the results and fix any issues systematically.

4. Train Your Team

Your accounts payable and accounts receivable teams need to understand the new formats. They do not need to read raw XML, but they need to know how to handle incoming e-invoice files, where to store them, how to trigger processing in your system, and what to do when an invoice is flagged as invalid. A short internal training session before the deadlines arrive will prevent confusion and errors under pressure.

The Technical Solution

For companies that want to keep their existing systems but need e-invoice capability — or for software vendors who want to offer e-invoicing to their users — we developed invoice.xhub.io.

Our API enables:

• Creation of XRechnung 3.0.2 and ZUGFeRD 2.1
• AI-enhanced validation according to KoSIT standard
• Integration into existing systems in under 5 minutes
• 100% GDPR compliant on German servers

For Developers: The Complete Technical Guide

Are you a developer looking to integrate e-invoicing into your software? Our comprehensive developer guide (German) includes:

• Code examples for TypeScript, Python, and cURL
• Technical details on UBL vs. CII XML syntax
• Implementation checklist
• Common validation errors and solutions

Frequently Asked Questions About E-Invoicing

Can I still use PDF invoices after January 2025?

For receiving invoices: your system must be able to accept e-invoices from suppliers who send them, but you cannot refuse an e-invoice simply because you prefer PDFs. For sending invoices: PDFs remain acceptable during the transitional period until your sending obligation kicks in (2027 for larger companies, 2028 for all), provided your recipient agrees. However, if your client requests an e-invoice, you must be able to provide one.

Does this apply to small businesses and freelancers?

Yes, the receiving obligation applies to all domestic B2B businesses from January 2025. The sending obligation thresholds (EUR 800,000 revenue for 2027, all companies for 2028) mean that very small businesses have until 2028 to comply with sending requirements, but they must already be able to receive e-invoices today. Additionally, businesses with annual revenue below EUR 800,000 are not granted an indefinite exemption — 2028 is a hard deadline for everyone.

Is a ZUGFeRD invoice always compliant?

Not necessarily. ZUGFeRD has multiple profiles, and not all of them satisfy the EN 16931 requirement. The MINIMUM and BASIC WL profiles are not fully compliant for the mandatory B2B e-invoice. Your invoices must use the EN 16931 profile (previously called COMFORT) or higher — specifically, the EN 16931, EXTENDED, or XRECHNUNG profiles within ZUGFeRD 2.1.

What about cross-border invoices within the EU?

The German domestic B2B mandate applies to transactions where both parties are established in Germany. For invoices to clients in other EU countries, existing rules apply for now. However, the EU ViDA directive will introduce harmonised cross-border e-invoicing and digital reporting requirements, with full implementation expected around 2030. Companies with significant intra-EU business should monitor the ViDA timeline closely.

How long must e-invoices be archived?

The retention period for e-invoices in Germany is ten years, as required by the German Commercial Code (HGB) and the Fiscal Code (AO). E-invoices must be stored in a tamper-proof manner and remain readable throughout the retention period. Cloud-based archiving solutions that guarantee long-term accessibility and audit trails are strongly recommended.

Conclusion

The e-invoice requirement is not an administrative hurdle to minimise — it is the beginning of a fundamental shift in how business transactions are recorded, reported, and audited in Europe. Companies that approach this change proactively will gain faster payment cycles, lower administrative costs, fewer input errors, and a competitive edge in supply chains that increasingly demand automated invoice processing.

The 2025 receiving obligation is already in effect. The 2027 and 2028 sending deadlines will arrive faster than expected once you account for preparation time. The right moment to act is now.

---

Need a quick solution for e-invoices? Try invoice.xhub.io for free.