Is e-invoicing mandatory in Germany?

Yes. Germany has a phased e-invoicing mandate: B2G (government) invoicing via XRechnung has been mandatory since November 2020. B2B receiving became mandatory for all German businesses on January 1, 2025 — your systems must accept EN 16931-compliant invoices. B2B sending mandates begin January 2027 for businesses with >€800K annual revenue, and January 2028 for all businesses. According to Invoice Navigator's analysis, Germany uses one of the strictest validation rule sets in the EU.

What e-invoice formats does Germany accept?

Germany accepts three EN 16931-compliant formats: XRechnung (UBL), XRechnung (CII), and ZUGFeRD 2.x. For B2G submissions through the ZRE (Zentraler Rechnungseingang) portal, XRechnung is the primary format. For B2B exchange, all three formats are accepted. ZUGFeRD embeds CII XML inside a PDF/A-3 document, making it popular for businesses transitioning from PDF invoicing. The current required version is XRechnung 3.0.2.

Is Peppol available for e-invoicing in Germany?

Yes, Germany participates in the Peppol network. Peppol is used for both B2G and B2B e-invoice exchange. For B2G, the German federal government accepts Peppol delivery alongside the ZRE portal. For B2B, Peppol is increasingly used for cross-border invoicing. Businesses need a Peppol ID and an Access Point to send/receive invoices via the Peppol network. SMP/SML lookup is required for Peppol delivery routing.

What are the penalties for non-compliance with Germany's e-invoicing mandate?

Germany's e-invoicing mandate does not currently specify direct fines for non-compliance. However, businesses that cannot receive EN 16931-compliant invoices (mandatory since January 2025) risk supply chain disruption — trading partners may be unable to send invoices. For B2G, non-compliant invoices are rejected by the ZRE portal. From 2027/2028 when sending becomes mandatory, businesses that continue sending non-structured invoices may face VAT deduction issues, as tax authorities will increasingly rely on structured data for audits.

What is Germany's e-invoicing timeline?

Germany's e-invoicing rollout follows four phases: (1) November 2020 — B2G mandatory via XRechnung for federal suppliers, (2) January 2025 — B2B receiving mandatory for all German businesses (must accept EN 16931 invoices), (3) January 2027 — B2B sending mandatory for businesses with >€800K annual revenue, (4) January 2028 — B2B sending mandatory for all remaining businesses. Invoice Navigator tracks all German deadlines and validates against XRechnung 3.0.2 rules.

All countries

Country Guide

🇩🇪 E-Invoicing in Germany

MandatoryPeppol

Recently verified: 9 March 2026

Germany requires all businesses to accept structured e-invoices as of January 2025, with mandatory sending phased in from January 2027. This makes Germany's e-invoicing regime one of the most advanced in the EU, covering both B2G (since 2020 via the ZRE portal) and B2B transactions. All invoices must conform to the EN 16931 standard using either XRechnung (UBL or CII syntax) or ZUGFeRD 2.x format.

The B2B mandate rolls out in two phases: businesses with annual revenue above €800,000 must send e-invoices from January 2027, and all remaining businesses follow from January 2028. B2G invoicing has required XRechnung via the Zentraler Rechnungseingang (ZRE) portal since November 2020. Every invoice must include a Leitweg-ID routing identifier for B2G transactions.

Germany's validation requirements are among the strictest in Europe. XRechnung 3.0.2 adds over 147 CIUS-specific rules on top of the core EN 16931 business rules, and the official KoSIT validation engine is the government's standard for compliance checking. Invoice Navigator's validation engine covers all 147 XRechnung CIUS rules and auto-remediates 89% of the most common German rejection errors, including missing Leitweg-IDs, invalid Scheme IDs, and incorrect date formats.

Non-compliance carries real consequences: invoices that fail XRechnung validation are rejected by the ZRE portal, delaying payment. For B2B transactions, non-compliant invoices may not qualify for VAT deduction. The German Federal Ministry of Finance (BMF) has indicated that enforcement will tighten as the sending mandates take effect.

TL;DR

Germany mandates EN 16931 e-invoicing for all B2B (receiving since Jan 2025, sending from 2027-2028) and B2G (since 2020). XRechnung 3.0.2 with 147+ CIUS rules validated via KoSIT.

Last updated: January 2026

Quick Facts

Format

xrechnung, zugferd, peppol_bis

Next Deadline

Jan 2027

Peppol

Connected

CIUS Rules

147

Auto-Fix

89%

Portal

ZRE (Zentrale Rechnungseingangsplattform) ↗

Compliance

Mandate Status

Phase

Status

Scope

B2G

Live (Nov 2020)

All federal suppliers

B2B receiving

Live (Jan 2025)

All German businesses

B2B sending

Jan 2027

>€800K annual revenue

B2B sending

Jan 2028

All businesses

Technical Specifications

Validation engineKoSIT (koordinierungsstelle-it-standards.de)

Required CIUSXRechnung 3.0.2

Government portalZRE (Zentraler Rechnungseingang)

Routing identifierLeitweg-ID (mandatory for B2G)

PeppolYes — SMP/SML lookup required for Peppol delivery

Accepted formatsxrechnung, zugferd, peppol_bis

Invoice Navigator covers 147 XRechnung 3.0.2 rules. Auto-remediates 89% of top rejection errors.

Practical

Common Rejection Patterns

#1BR-DEX-11Missing third party payment amount. When using third party payment group...Fix guide

#2DE-R-008The element "Buyer city" (BT-52) shall be provided.Fix guide

#3BR-DE-25XRechnung invoice type restrictionFix guide

#4BR-DE-20The Debited Account (BT-91) should contain a valid IBAN for SEPA direct...Fix guide

#5BR-DEX-03Eine Sub Invoice Line (BG-DEX-01) muss genau eine "SUB INVOICE LINE VAT...Fix guide

Invoice Navigator auto-remediates these at pipeline speed. See how →

View all Germany error codes

Implementation Notes

The B2B mandate has three sharp edges that affect pipeline design.

Receiving (live now). Your system must ingest both XRechnung (UBL and CII) and ZUGFeRD 2.x. ZUGFeRD embeds XML in PDF/A-3, so your parser needs to handle both standalone XML and PDF extraction. Many ERPs only support one path — this causes silent failures in production.

Sending phase 1 (Jan 2027, >€800K). The revenue threshold applies per entity, not per group. Multi-entity customers need per-entity compliance tracking. The Wachstumschancengesetz allows EDI continuity during the transition, but only if both parties agree — don't assume EDI exemption in your pipeline logic.

Format specifics that break pipelines. XRechnung CIUS adds rules beyond base EN 16931. The most common failure: BT-10 (Buyer Reference) is mandatory for B2G but handled differently in B2B. If your template uses the same field for both, you'll get rejections on one side. BT-49 (Payment Means Code) validation is strict — the top 5 German rejection errors are all payment-related.

Stay Current