E-Invoicing Obligation Germany 2026: Everything You Need to Know
Table of Contents
Germany's e-invoicing obligation is no longer a future concern. Since January 1, 2025, every B2B company operating in Germany must be able to receive structured electronic invoices. Starting in 2027, sending e-invoices becomes mandatory too.
If your business sells to or buys from German companies, you need to understand these rules. Failure to comply means fines of up to EUR 5,000 per violation, jeopardized VAT deductions, and strained business relationships.
This pillar guide covers everything: the legal basis, deadlines, approved formats, exemptions, and a concrete 5-step action plan to get your business ready.
Key Takeaways
The 6 facts you need to know about Germany's e-invoicing obligation:
1. Since Jan 1, 2025: all B2B businesses in Germany must be able to receive e-invoices.
2. From Jan 1, 2027: businesses with prior-year revenue above EUR 800,000 must send e-invoices.
3. From Jan 1, 2028: all businesses must send e-invoices, regardless of revenue.
4. Accepted formats must comply with EN 16931 (XRechnung, ZUGFeRD Comfort/Extended).
5. Plain PDF invoices do not qualify as e-invoices under the law.
6. The legal basis is the reformed Section 14 UStG, amended by the Growth Opportunities Act.
What Is Germany's E-Invoicing Obligation?
Germany's e-invoicing obligation (Ger: E-Rechnungspflicht) is the legal requirement for businesses to issue, transmit, and receive invoices in a structured electronic format. It was introduced through the Growth Opportunities Act (Wachstumschancengesetz), which became law on March 22, 2024.
Legal Basis
The core provision is the reformed Section 14 UStG (Value Added Tax Act). The new version introduces two categories:
- Electronic invoice (E-Rechnung): An invoice issued, transmitted, and received in a structured electronic format that enables automated processing. The format must comply with the European standard EN 16931.
- Other invoice (sonstige Rechnung): Everything else, including paper invoices and plain PDF files.
Critical distinction: A PDF attached to an email is not an e-invoice under German law. Only machine-readable, structured formats compliant with EN 16931 meet the legal definition.
Why Did Germany Introduce This Mandate?
Germany is following the EU-wide push toward digital tax administration. Key drivers:
- Combating VAT fraud (EU VAT gap: approximately EUR 60 billion annually)
- Preparing for the EU's ViDA initiative (VAT in the Digital Age)
- Increasing efficiency in invoice processing
- Tax simplification through automated verification
Timeline: All Deadlines 2025 to 2028
| Date | Obligation | Who Is Affected |
|---|---|---|
| Jan 1, 2025 | Receiving mandate: All domestic B2B businesses must be able to receive e-invoices | All businesses based in Germany |
| Jan 1, 2027 | Sending mandate (Phase 1): Businesses with prior-year revenue > EUR 800,000 must issue e-invoices | Businesses > EUR 800K revenue |
| Jan 1, 2028 | Sending mandate (Phase 2): All businesses must issue e-invoices | All businesses, regardless of revenue |
Who Must Receive and Send E-Invoices?
Receiving Mandate (Active Since Jan 1, 2025)
Every domestic business engaged in B2B transactions, where a VAT invoice obligation exists, must be able to receive e-invoices. Key points:
- No specific receiving system is prescribed by law.
- A simple email inbox is sufficient.
- Recipients must be able to process and archive the invoice in compliance with GoBD.
Sending Mandate (From Jan 1, 2027 / Jan 1, 2028)
- From 2027: Businesses with prior-year revenue exceeding EUR 800,000
- From 2028: All remaining businesses
Who Is Specifically Affected?
The mandate applies to all VAT-taxable supplies between domestic businesses (B2B):
- Corporations (GmbH, AG, UG)
- Partnerships (OHG, KG, GbR)
- Sole proprietors and freelancers
- Associations and foundations with commercial activities
Practical tip: Even small businesses using the Kleinunternehmerregelung must be able to receive e-invoices. They are only exempt from the sending mandate.
Which Formats Are Accepted?
Not every electronic format qualifies. The e-invoice must conform to the European standard EN 16931.
| Format | Type | EN 16931 Compliant? | Accepted? |
|---|---|---|---|
| XRechnung | Pure XML | Yes | Yes |
| ZUGFeRD (EN 16931 / Comfort profile or higher) | Hybrid (PDF + XML) | Yes | Yes |
| ZUGFeRD Basic, Basic WL, Minimum | Hybrid (PDF + XML) | No | No |
| Plain PDF | Image-based | No | No |
| Paper invoice | Analog | No | Impermissible in B2B from 2028 |
Exemptions at a Glance
Main exemptions:
- Small-amount invoices up to EUR 250 (Section 33 UStDV)
- Travel tickets and public transport receipts (Section 34 UStDV)
- VAT-exempt supplies under Section 4 Nos. 8 to 29 UStG
- Sales to end consumers (B2C) — outside the scope
- Cross-border transactions — the mandate applies only to domestic B2B supplies
Transitional Rules 2025 to 2028
Phase 1: Jan 1, 2025 to Dec 31, 2026
- Receiving: Mandatory for all domestic B2B businesses
- Sending: Not yet mandatory. Paper invoices remain permitted.
- Condition for PDF invoices: The recipient must consent to receiving an "other invoice" in electronic form.
Phase 2: Jan 1, 2027 to Dec 31, 2027
- Receiving: Still mandatory for all
- Sending: Businesses with prior-year revenue > EUR 800,000 must issue e-invoices
- EDI procedures: EDI invoices remain permissible until Dec 31, 2027, provided invoice data can be correctly extracted
Phase 3: From Jan 1, 2028
- Receiving and sending: Mandatory for all domestic B2B businesses
- No revenue threshold applies
- No EDI exception anymore (unless the EDI format complies with EN 16931)
- Paper and PDF invoices are no longer permissible in domestic B2B
B2B vs. B2G vs. B2C Differences
| Criterion | B2B | B2G | B2C |
|---|---|---|---|
| E-invoicing mandate | Yes (receiving 2025, sending 2027/2028) | Yes (federal level since 2020) | No |
| Legal basis | Section 14 UStG | E-Invoicing Ordinance (ERechV) | — |
| Required format | EN 16931 | XRechnung (preferred) | No required format |
| Transmission channel | Email, Peppol, portal, EDI | Peppol, ZRE/OZG-RE | Freely chosen |
| Archiving obligation | 10 years (GoBD) | 10 years (GoBD) | 10 years (GoBD) |
What Changed Under the Growth Opportunities Act?
Section 14 UStG: Old vs. New
| Aspect | Old Section 14 UStG | New Section 14 UStG |
|---|---|---|
| Invoice definition | Paper or electronic (with consent) | Distinguishes between "e-invoice" and "other invoice" |
| Electronic invoice | Any electronic format with recipient consent | Only EN 16931-compliant formats |
| Recipient consent | Required for every electronic invoice | Not required for e-invoices |
| Format requirement | No specific standard | EN 16931 |
Before: The invoice recipient had to consent to receiving an electronic invoice. Now: The e-invoice is the default — the recipient must consent to receiving an "other invoice" instead.
Technical Requirements
EN 16931: The European Standard
EN 16931 defines a semantic data model for the core elements of an electronic invoice. It specifies mandatory fields, optional fields, and syntaxes.
In Germany, two syntaxes dominate:
- XRechnung — Germany's national standard (XML-based, no visual document)
- ZUGFeRD (v2.0.1+, EN 16931 profile or higher) — hybrid format (PDF/A-3 with embedded XML)
Transmission Channels
All permissible:
- Email (with the e-invoice as an attachment)
- Peppol network
- Web portals of the recipient
- AS4 protocol
- Direct API integration (e.g., via Complyance)
Archiving
E-invoices must be archived in compliance with GoBD:
- Retention period: 10 years
- Immutability must be guaranteed
- The structured format (XML) must be archived, not just the visual representation
Action Plan: 5 Steps to Compliance
Step 1: Assess Your Current State
- How many invoices do you send and receive per month?
- What systems do you currently use?
- Have you already sent B2G e-invoices?
- What was your prior-year revenue?
Step 2: Choose Your Format and Transmission Channel
- XRechnung for B2G and tech-savvy recipients
- ZUGFeRD Comfort/Extended for broad B2B use
- Transmission via email, Peppol, or API
Step 3: Select Software or Upgrade Existing Systems
Check whether your current accounting or ERP software supports e-invoicing. If not, you need a solution that can generate, validate, and integrate.
Step 4: Adapt Processes and Test
- Switch invoice creation to e-invoice output
- Test receiving workflows
- Verify archiving processes
- Train your team
Step 5: Go Live and Monitor
- Roll out e-invoicing gradually across all B2B partners
- Monitor error rates
- Collect feedback from business partners
Penalties for Non-Compliance
Direct Consequences
- Fines of up to EUR 5,000 per violation of invoicing requirements (Section 26a UStG)
- Jeopardized input VAT deduction for the invoice recipient
- Issues during tax audits
Indirect Consequences
- Business partners may reject non-compliant invoices
- Reputational damage
- Higher process costs
Do/Don't
| Do | Don't |
|---|---|
| Start your assessment now | Wait until the last minute |
| Ensure e-invoice receiving capability immediately | Ignore or reject incoming e-invoices |
| Use EN 16931-compliant formats | Use ZUGFeRD Basic or plain PDF |
| Evaluate and test software early | Go live without testing |
| Train your team | Treat this as a purely technical project |
| Set up GoBD-compliant archiving | Archive e-invoices only as printed PDFs |
| Evaluate Peppol as a transmission channel | Rely exclusively on email delivery |
| Inform your business partners early | Assume all partners are already ready |
Conclusion: Act Now
Germany's e-invoicing obligation is binding law. The receiving mandate is already active, and the sending mandate is approaching fast. Businesses that act now secure legal certainty, more efficient invoice processing, and readiness for the EU-wide ViDA initiative.
Related posts
Frequently Asked Questions
The receiving mandate has been active since January 1, 2025. The sending mandate starts on January 1, 2027, for businesses with prior-year revenue above EUR 800,000, and on January 1, 2028, for all businesses.
Partially. Small businesses using the Kleinunternehmerregelung (Section 19 UStG) must be able to receive e-invoices. Since they do not charge VAT, they are exempt from the sending obligation.
No. A plain PDF file does not qualify as an e-invoice under Section 14 UStG. A ZUGFeRD PDF (EN 16931 / Comfort profile or higher) does qualify because it contains embedded XML data.
XRechnung is a pure XML format with no visual representation. ZUGFeRD is a hybrid format: a PDF/A-3 document with an embedded XML file.
Fines of up to EUR 5,000 per violation may be imposed (Section 26a UStG). A non-compliant invoice can affect the invoice recipient's input VAT deduction.
During the transition period until the end of 2026, yes. From 2027, only if your revenue is below EUR 800,000. From 2028, paper invoices are no longer permissible in domestic B2B.
E-invoices must be archived for 10 years in GoBD compliance. This means: immutable, machine-evaluable, and in the original format (XML).
Complyance is an API-first e-invoicing platform that integrates into your existing systems. The platform generates, validates, and transmits e-invoices in XRechnung and ZUGFeRD formats, supports Peppol transmission, and provides GoBD-compliant archiving.
About the Author
Swathy
Content Marketer
I’m a Content Marketer at Complyance, focused on e-invoicing. Over the years, I’ve created a wide range of content, including blog posts, whitepapers, and product guides, which have supported Complyance’s growth across markets such as the UAE and EU regions. My goal is to deliver content that is comprehensive, clear, accurate, and easy to understand, no matter how complex the topic.
