From January 1, 2025, all German B2B companies must be technically capable of receiving electronic invoices.
Although transitional periods apply for issuing e-invoices to domestic German entities, the pressure on suppliers—including foreign ones—begins immediately. In practice, Czech companies often assume that these rules do not apply to them as foreign entities. This is a dangerous oversimplification. While a Czech company without a permanent establishment in Germany may not be legally obliged to issue an e-invoice for cross-border transactions under German VAT law, contractual obligations and B2G rules often require it.
The issue is not just the technical format, but also the coordination between your Czech accounting system, the expectations of your German partner, and the compliance framework across two jurisdictions.
What are the Main Requirements for E-invoicing in Germany?
German e-invoicing requirements distinguish between “electronic invoices” (structured data) and “other invoices” (PDF, paper). A compliant e-invoice must:
Comply with EN 16931 standard: The two most common compliant formats are XRechnung (pure XML data, standard for public administration) and ZUGFeRD (hybrid PDF/A-3 file with embedded XML data).
Be transmitted electronically: Via email, 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 generate output compatible with the German EN 16931 standard.
The Challenge of Cross-Border Coordination
In an international environment, it's not just about buying new software. It's about coordinating multiple partners, document formats, and legal interpretations. A typical situation arises when your Czech company invoices a German customer for a service using a standard PDF, which complies with Czech VAT law. However, the German customer's purchasing system expects a ZUGFeRD or XRechnung file for automatic payment processing.
Your invoice is rejected by their system, payment is delayed, and your finance team struggles to figure out whether it's a legal or technical problem.
In practice, a combination of document centralization, initial clarity on the specific requirement, and involvement of the right tax expert proves effective. This is where it makes sense to have the brief, documents, and technical specifications in one place before incurring costs on incorrect solutions.
Start your case directly on Anywhere.legal for effective document preparation and detailed mandate definition.
Practical Implications: Costs, Delays, and Risk of Non-Compliance
Ignoring the shift in German market standards has real consequences:
Payment delays: German partners with automated workflows may deprioritize or technically reject unstructured invoices, extending the time for accounts receivable collection by 30–60 days.
Contractual exclusion: Large German buyers, especially in the automotive and logistics industries, often make e-invoicing a condition for supplier inclusion.
B2G obstacles: If you supply German public institutions, e-invoicing via Peppol is generally mandatory, and non-compliance means your invoice is legally invalid.
Internal inefficiencies: Managing manual solutions for German clients while automating the rest of invoicing creates operational risk.
How to Systematically Approach E-invoicing Compliance
Step 1: Audit your existing invoicing process
Before implementing changes, understand your current technical readiness:
Does your ERP or accounting software support EN 16931 formats (ZUGFeRD 2.x or XRechnung)?
Do you currently send invoices to German public sector entities?
Which of your German private customers have updated their general terms and conditions regarding invoicing?
A typical company will find that while it generates PDFs, it lacks the structured XML data required for the German market.
Step 2: Determine your specific obligations
German e-invoicing rules vary depending on the nature of your supply:
B2G (public sector): Mandatory e-invoicing is largely already in effect. You must issue XRechnung (or compatible) invoices, often through specific portals.
B2B (private sector) - cross-border: Legally, the obligation to issue e-invoices applies to transactions between two taxable persons established in Germany. However, if your customer contractually requires e-invoices to optimize the processing of their input VAT deduction, you must comply to get paid.
VAT registration: If your Czech company has a permanent establishment in Germany, you fall directly under the domestic German mandatory e-invoicing regime.
1. Is a purely Czech exporter legally forced by German regulations to issue e-invoices? For standard cross-border transactions (e.g., Reverse Charge), where the supplier is not established in Germany, there is generally no legal obligation under German VAT law. However, commercial pressure is high because German buyers will demand it.
2. Which format should we choose? ZUGFeRD is often the best choice for B2B because it looks like a PDF to humans but contains XML for machines. XRechnung is usually required for public procurement.
3. Does our Czech tax advisor need to coordinate with a German one? Yes, especially to verify whether your specific business model creates a permanent establishment or VAT liability in Germany, which would trigger the full domestic compliance regime.
Step 3: Select and test a compliant invoicing solution
Contact us via Anywhere.legal and structure your case; we'll help you determine if your request is purely technical or if it also involves reviewing your VAT status in Germany.
Many modern invoicing solutions now support these standards. Options include:
ERP upgrade: 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, a standard for B2G.
Don't assume your “export” format will work. Before going live, test your ZUGFeRD or XRechnung file using a validation tool or a cooperative German partner.
Step 4: Document transmission and archiving
Even if you are a Czech entity, if you enter German jurisdiction through contracts or VAT registration, ensure your system records when the structured data file was sent. Structured XML data is the “original” for tax purposes in Germany, not the visual PDF. If you are subject to German VAT, you must comply with German archiving rules (GoBD) and retain data for 10 years in an unalterable form.
Common Implementation Mistakes Made by Czech Companies
Treating it as just a “file format” change
Many finance teams assume e-invoicing just means saving a file as XML. In reality, it involves correctly mapping data fields like buyer references and VAT codes. If the data within the XML is incorrect, the invoice is technically valid, but the client's ERP will reject it for payment.
Ignoring the “recipient” requirement
Even if you don't issue e-invoices, if you purchase services from Germany, you may receive e-invoices. If your Czech system cannot import or read German XRechnung, you might overlook the processing of the liability.
Waiting for a “hard” deadline
Companies often wait until they are legally forced to comply. Because the legal obligation applies to domestic German companies, Czech companies feel secure and forget that the market moves faster than the law. Waiting until a key customer rejects a PDF invoice is a costly strategy.
Why a systematic approach is important: a practical example
Imagine a Czech engineering company supplying components to a German car manufacturer.
The German manufacturer upgraded their SAP system for 2025 and updated supplier terms to require XRechnung format from Q2 2025.
Without preparation, the Czech company ignores the requirement, believing German laws don't apply to them. The manufacturer's portal rejects their standard PDF, and the Czech finance team cannot create a valid manual XML. Payment is delayed for weeks while IT frantically searches for a solution, impacting cash flow.
The Czech company uses Anywhere.legal to consult on the new requirement, chooses a simple conversion tool, and seamlessly updates their customer data.
The difference lies less in legal compliance itself and more in operational readiness and professional credibility.
Why It's Important to Tackle This Systematically Through Centralized Coordination
In cross-border situations, the problem is often not just the legal or technical assessment itself, but also the coordination of multiple countries, multiple inputs, and multiple stakeholders.
Navigating German e-invoicing requires input from IT, tax, and business departments. This type of coordination is typically handled through platforms designed specifically for cross-border legal and operational matters, where you can combine project briefs, documentation for your invoicing requirements, initial technical assessment, and collaboration with your Czech finance team and German tax advisor.
Conclusion
Germany's e-invoicing requirements in 2025 create a new digital reality for Czech exporters. Although the strict legal obligation to issue e-invoices targets domestic German companies, commercial and B2G realities compel Czech partners to adapt.
The transition requires more than just software updates; it demands a strategic perspective on how you exchange data with your main export market.
The good news is that standards are clear, and solutions exist. The important thing is to start early, engage the right experts, and centralize the project so that all stakeholders are aligned.
Need international legal or tax coordination? Contact us via Anywhere.legal.
Frequently Asked Questions
1. Our Czech accounting software does not offer XRechnung export. What are our options? You don't necessarily need to change your entire ERP. You can use middleware or a third-party e-invoicing service provider that takes your PDF or data and converts it into a compliant XRechnung or ZUGFeRD format.
2. We are a Czech company without an office in Germany. Do we have to issue e-invoices? Legally, under German VAT law, probably not. Practically, however, yes — if your German customer requires it for their automated processing or if you sell to the state (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 difficult for humans to read. ZUGFeRD is a PDF with embedded XML; it looks like a regular invoice but can be processed by machines and is often preferred in B2B.
4. Can we simply send an XML file by email? It depends on the situation. For B2B, email is often allowed if the parties agree. For B2G, you usually have to use specific upload portals or the Peppol network, not email.
5. How long does implementation take? For a technical conversion solution, it can be 2–4 weeks. If you need direct integration via Peppol or an ERP upgrade, plan 2–3 months.
6. Will this affect our VAT returns in Germany? If you are already VAT registered in Germany, the shift to e-invoicing means that German tax authorities will have easier access to audit your transaction data in the future. Ensure your VAT codes in the e-invoice accurately match your tax returns.
Find out everything Anywhere can do – with a tailored demo from our team.
Discover what Anywhere can do — with a tailored demo from our team.
