E-Invoicing in Germany 2025: What Czech companies need to know about new legal and technical requirements

The shift in German e-invoicing standards: What changed and why it matters

Germany has long had a structured approach to invoicing, but 2025 marks a decisive shift toward mandatory e-invoicing based on the EN 16931 standard. The transition is driven by the Growth Opportunities Act ( Wachstumschancengesetz ) and aligns with broader EU VAT directives.

From January 1, 2025, all German B2B companies must be technically capable of receiving electronic invoices.

While there are transitional periods for issuing e-invoices for domestic German entities, the pressure on suppliers—including foreign ones—starts immediately. In practice, Czech companies often assume that because they are foreign entities, these rules do not apply. This is a dangerous oversimplification. While a Czech company without a fixed establishment in Germany may not be statutorily obliged to issue an e-invoice under German VAT law for a cross-border supply, contractual obligations and B2G rules often mandate it.

The problem is not only the technical format but also the coordination between your Czech accounting system, German partner expectations, and compliance frameworks that span two jurisdictions.

Discover how to effectively handle complex international law requirements and how a global network of verified expert lawyers helps you.

What are the core e-invoicing requirements in Germany?

German e-invoicing requirements distinguish between "electronic invoices" (structured data) and "other invoices" (PDF, paper). A compliant e-invoice must:

• Adhere to the EN 16931 standard: The two most common compliant formats are XRechnung (pure XML data, standard for public administration) and ZUGFeRD (a hybrid PDF/A-3 file with embedded XML data).

• Be transmitted electronically: Through email, a web interface, or a specialized network like Peppol.

• Contain mandatory data fields: In addition to standard VAT invoice details, specific structured data fields are required for automated processing.

For Czech companies, the challenge is that standard Czech invoicing software often does not automatically produce output compatible with the German EN 16931 standard.

The cross-border coordination challenge

In an international environment, the issue is rarely just about buying new software. It is about coordinating multiple partners, document formats, and legal interpretations. A typical situation unfolds when your Czech company invoices a German customer for a service using a standard PDF compliant with Czech VAT law. The German customer's procurement system expects a ZUGFeRD or XRechnung file to process the payment automatically.

Your invoice is rejected by their system, payment is delayed, and your finance team is scrambling to understand whether the rejection is a legal issue or a technical one.

In practice, a combination of document centralization, initial clarity on the specific requirement, and involvement of the right tax expert proves effective. This is exactly where it makes sense to have the brief, documents, and technical specifications in one place before incurring costs on wrong solutions.

Practical impacts: costs, delays, and compliance risk

Ignoring the shift in German market standards carries real consequences:

• Payment delays: German partners with automated workflows may deprioritize or technically reject non-structured invoices, extending Days Sales Outstanding by 30–60 days.

• Contractual exclusion: Large German buyers, especially in automotive and logistics, often make e-invoicing a prerequisite for supplier onboarding.

• B2G barriers: If you supply to German public sector entities, e-invoicing via Peppol is generally mandatory, and non-compliance means your invoice is legally invalid.

• Internal inefficiency: Managing manual workarounds for German clients while automating the rest of your billing creates operational risk.

How to approach e-invoicing compliance systematically

Step 1: Audit your current invoicing process

Before implementing changes, understand your current technical capability:

• Does your ERP or accounting software support EN 16931 formats (ZUGFeRD 2.x or XRechnung)?

• Are you currently sending invoices to German public sector entities?

• Which of your German private sector customers have updated their General Terms and Conditions regarding invoicing?

A typical company discovers that while they generate PDFs, they lack the structured XML data required for the German market.

Step 2: Determine your specific obligations

German e-invoicing rules apply differently depending on the nature of your transaction:

• B2G (Public Sector): Mandatory e-invoicing is largely in effect. You must issue XRechnung (or compatible) invoices, often via specific portals.

• B2B (Private Sector) - Cross-Border: Under statutory law, the obligation to issue e-invoices applies to supplies between two German-resident taxable persons. However, if your customer requires e-invoices contractually to optimize their input VAT processing, you must comply to get paid.

• VAT Registration: If your Czech company has a fixed establishment in Germany, you fall directly under the domestic German e-invoicing mandate.

1. Is a pure Czech exporter legally forced by German law to issue e-invoices?
For a standard cross-border supply (e.g., Reverse Charge) where the supplier has no seat in Germany, generally no statutory obligation exists under the German VAT Act. However, the commercial obligation is high, as German buyers will demand it.

2. What format should we choose?
ZUGFeRD is often the best choice for B2B, as it looks like a PDF to humans but contains the XML for machines. XRechnung is typically required for public procurement.

3. Does our Czech tax advisor need to coordinate with a German one?
Yes, particularly to verify if your specific business model creates a permanent establishment or VAT liability in Germany, which would trigger full domestic compliance rules.

Step 3: Select and test a compliant invoicing solution

Contact us via Anywhere.legal to structure your case, as we can help you define whether your need is purely technical or if it involves a review of your VAT status in Germany.

Many modern invoicing solutions now support these standards. Options include:

• ERP upgrades: Systems like SAP, MS Dynamics, or Odoo often have modules for German compliance.

• Middleware or converters: Software that takes your Czech PDF/data and converts it into a valid XRechnung/ZUGFeRD file.

• Peppol network: Connecting to the Peppol network allows you to send invoices directly to the recipient’s system, which is the standard for B2G.

Do not assume your "export" format works. Test a ZUGFeRD or XRechnung file with a validator tool or a friendly German partner before going live.

Step 4: Document transmission and archiving

Even if you are a Czech entity, if you submit to German jurisdiction via contracts or VAT registration, ensure your system logs when the structured data file was sent. The structured XML data is the "original" for tax purposes in Germany, not the visual PDF representation. If you are liable for German VAT, you must adhere to German archiving rules (GoBD) and keep data for 10 years in an immutable format.

Risk and impact table: E-invoicing compliance gaps and solutions

Common implementation mistakes Czech companies make

Treating it as just a "file format" change

Many finance teams assume e-invoicing is just saving a file as XML. In reality, it involves mapping data fields correctly, such as buyer references and VAT codes. If the data inside the XML is wrong, the invoice is technically valid but payment will be rejected by the client’s ERP.

Ignoring the "recipient" requirement

Even if you don't issue e-invoices, if you buy services from Germany, you might receive e-invoices. If your Czech system cannot import or read a German XRechnung, you might miss processing a payable.

Waiting for the "hard" deadline

Companies often wait until the law forces them. Since the statutory law applies to German domestic firms, Czech firms feel safe, forgetting that the market moves faster than the law. Waiting until a key customer rejects a PDF invoice is a costly strategy.

Why systematic approach matters: A practical example

Consider a Czech engineering firm supplying components to a German automotive manufacturer.

The German manufacturer upgrades its SAP system for 2025 and updates its supplier terms to require XRechnung format by Q2 2025.

Without preparation, the Czech firm ignores the requirement, believing German laws don't apply to them. The manufacturer’s portal rejects their standard PDF, and the Czech finance team fails to create a valid manual XML. Payment is delayed by weeks while IT scrambles for a solution, impacting cash flow.

The Czech firm uses Anywhere.legal to consult the new requirement, selects a simple converter tool, and updates their customer master data seamlessly.

The difference is not legal compliance per se, but operational readiness and professional credibility.

Why addressing this systematically through centralized coordination matters

In cross-border situations, the problem is often not only the legal or technical assessment itself but also coordinating multiple countries, multiple inputs, and multiple stakeholders.

Navigating German e-invoicing requires input from IT, tax, and sales departments. This type of coordination is commonly handled via platforms designed specifically for cross-border legal and operational matters, where you can bring together the project brief, documentation of your invoicing requirements, initial technical assessment, and collaboration with both your Czech finance team and a German tax advisor.

Conclusion

German e-invoicing requirements in 2025 create a new digital reality for Czech exporters. While the strict legal mandate to issue e-invoices targets domestic German companies, the commercial and B2G reality forces Czech partners to adapt.

The transition requires more than a software update; it demands a strategic look at how you exchange data with your main export market.

The good news is that the standards are clear, and solutions are available. What matters is starting the process early, involving the right expertise, and centralizing the project so that all stakeholders are aligned.

Need international legal or tax coordination? Get in touch with us via Anywhere.legal.

Frequently asked questions

1. Our Czech accounting software does not offer XRechnung export. What are our options?
You do not necessarily need to change your whole ERP. You can use middleware or a third-party e-invoicing service provider that takes your PDF or data and converts it to a compliant XRechnung or ZUGFeRD format.

2. We are a Czech company with no branch in Germany. Must we issue e-invoices?
Legally, under the German VAT Act, likely no. However, practically, yes—if your German customer requires it for their automated processing or if you sell to the government (B2G). Always check your customer contracts.

3. What is the difference between XRechnung and ZUGFeRD?
XRechnung is a pure XML data file preferred by the public sector, which is hard for humans to read. ZUGFeRD is a PDF with the XML embedded inside it; it looks like a normal invoice but can be processed by machines and is often preferred for B2B.

4. Can we simply email the XML file?
It depends. For B2B, email is often permitted if the parties agree. For B2G, you typically must use specific upload portals or the Peppol network, not email.

5. How long does implementation take?
For a technical converter solution, it can be 2–4 weeks. If you need to integrate directly via Peppol or upgrade an ERP, plan for 2–3 months.

6. Does this affect our VAT filings in Germany?
If you are already registered for VAT in Germany, the shift to e-invoicing implies that the German tax authorities will have easier access to audit your transaction data in the future. Ensure your VAT codes in the e-invoice match your tax returns perfectly.