Germany E-Invoicing 2026: Where the Mandate Stands

Sixteen months into Germany's B2B e-invoicing rollout, reception has been mandatory since January 1, 2025 and Phase 2 — mandatory sending for businesses above €800,000 annual revenue — is roughly eight months away. The framework hasn't changed; the operational reality has.

This post was originally published in January 2025. It has been substantially updated in May 2026 to reflect what's actually live, what's coming, and what changed in the meantime.

The current state (May 2026)

• Reception is mandatory for every German VAT-registered business and has been since January 1, 2025. PDF-only invoices are not compliant.
• Sending becomes mandatory for businesses with annual revenue above €800,000 from January 1, 2027, and for all businesses from January 1, 2028.
• Accepted formats: XRechnung (UBL or CII syntax), ZUGFeRD 2.x (hybrid PDF/XML), and Peppol BIS Billing 3.0.
• Current XRechnung version: 3.0.2. KoSIT publishes specification updates regularly; check /country/germany for the latest version-in-force.
• Validation engine of record: KoSIT (Koordinierungsstelle für IT-Standards). Federal portals run KoSIT validation against XRechnung CIUS rules on top of EN 16931.

What changed in 2026

A few items worth flagging if you haven't been tracking the EU regulatory firehose:

• EN 16931 v1.3.16 Schematron (April 10, 2026) — the underlying European standard shipped a non-backward-compatible update. ERP pipelines running pre-1.3.16 Schematron may produce invoices that pass locally but fail at access-point validation. Update your validation artefacts.
• Peppol G2 → G3 certificate hard cutover (April 1, 2026) — the Peppol G2 trust chain was revoked. Any access point that hadn't migrated to G3 PKI is now offline. Check with your service provider.
• XRechnung specification updates — KoSIT continues to publish revisions. Always validate against the current effective version, not the one your codebase was built against.

For a real-time view of what's changing across the EU, the Invoice Navigator changelog tracks every regulatory update, deadline shift, and format release.

The full timeline

Phase 1 — Reception (live since January 2025)

Every German VAT-registered business must be technically capable of receiving e-invoices. In practice this means:

• Software that can ingest both standalone XML (XRechnung UBL/CII) and PDF/A-3 with embedded XML (ZUGFeRD 2.x). Many ERPs only support one path; that gap causes silent failures in production.
• Mapping invoice data — totals, VAT breakdowns, references — into your accounting system.
• Archiving received invoices in a tamper-evident, audit-ready format for ten years (GoBD-compliant).

If you're still receiving invoices via PDF email attachments only, you have a compliance gap.

Phase 2 — Sending for large businesses (January 2027)

From January 1, 2027, businesses with annual revenue exceeding €800,000 must send structured e-invoices for all domestic B2B transactions.

A few sharp edges worth understanding now, eight months out:

• The threshold applies per entity, not per group. Multi-entity organizations need per-entity compliance tracking; you cannot consolidate at group level for the threshold test.
• The Wachstumschancengesetz allows EDI continuity during the transition, but only if both parties agree. Don't assume EDI exemption in your pipeline logic — confirm it with each counterparty.
• B2G has been live since November 2020 via the ZRE portal (Zentraler Rechnungseingang). XRechnung is the primary B2G format. If you already invoice the federal government, you've already done the heavy lifting.

Phase 3 — Full mandate (January 2028)

From January 1, 2028, all businesses regardless of size must send structured e-invoices. There is no announced exemption for micro businesses.

Accepted formats

Germany accepts any format compliant with EN 16931:

XRechnung

The German national CIUS (Core Invoice Usage Specification), XRechnung adds approximately 147 country-specific business rules on top of EN 16931. It's the most commonly used format for B2G and is now widely used in B2B as well. Two syntaxes are valid: UBL and UN/CEFACT CII.

The most common XRechnung rejection causes are payment-related — BT-49 (Payment Means Code) and BT-10 (Buyer Reference) drive the top failure modes. If you're building a sender, validate against KoSIT before transmit.

ZUGFeRD 2.x

ZUGFeRD is a hybrid format that embeds structured CII XML inside a PDF/A-3 document. The PDF stays human-readable; the embedded XML stays machine-processable. ZUGFeRD profiles EN 16931 and Extended are fully EN 16931 compliant. Profiles MINIMUM, BASIC WL (without lines), and BASIC are not — they exist for narrower use cases (mostly Factur-X interop with France).

If you have customers transitioning from PDF invoicing to structured e-invoicing, ZUGFeRD is the lowest-friction starting point: their AP team still gets a human-readable PDF, your finance system gets the XML.

Peppol BIS Billing 3.0

For cross-border or pre-existing Peppol participants, BIS Billing 3.0 invoices are accepted. The Peppol network handles transmission via access points; routing uses the Peppol Participant Identifier scheme. Germany supports Peppol via the federal access point as well as private access point providers.

If you're not already on Peppol, you don't need to register specifically for the German mandate — but Peppol is the path of least resistance for ViDA cross-border requirements from 2030 onward.

What about cross-border?

The German B2B mandate applies to domestic transactions between German VAT-registered parties. But:

• Cross-border invoices into Germany may increasingly be requested in EN 16931 format by buyers' AP automation.
• The EU's ViDA directive mandates intra-EU B2B e-invoicing from July 2030. Building XRechnung-compatible sending capability now puts you in a defensible position for the EU-wide step.
• Using Peppol for both domestic Germany and EU cross-border is operationally simpler than running two parallel paths.

How to prepare for January 2027

1. Audit your current state

• What formats can your AP system receive? Both XML and ZUGFeRD?
• What formats can your AR system send? XRechnung in at least one syntax?
• How are you archiving received invoices? GoBD-compliant for 10 years?
• Are your suppliers already sending structured invoices? Track which ones, in what format, on what cadence.

2. Update your software stack

For Phase 2 (sending), your stack must be able to:

• Generate EN 16931-compliant XRechnung (preferably both UBL and CII; some access points still favor one over the other)
• Validate before send — catching rejections before they hit the access point saves real money in operational overhead
• Handle remediation when fields are missing or malformed — and never modify financial fields silently
• Produce an audit trail of what was sent, when, and what changed during validation

3. Communicate with counterparties

If you're above €800K and your counterparties are below, they may not be sending you structured invoices yet. Confirm what each large counterparty is doing — they might already be sending to you in 2026 voluntarily, which is good practice for your AP system.

4. Decide your Peppol position

You don't strictly need Peppol for the German mandate, but:

• If you have any EU customers outside Germany, Peppol is the path of least resistance for ViDA 2030.
• If you're a software vendor or ERP integrator serving German B2B, Peppol-readiness is a buyer requirement increasingly often.
• If you're purely domestic, Germany's federal access point is sufficient.

FAQ

Do I need to send e-invoices in Germany right now?

No. Sending is not mandatory until January 1, 2027 for businesses with annual revenue above €800,000, and January 1, 2028 for all businesses. Reception, however, has been mandatory since January 1, 2025 — every German VAT-registered business must already be capable of receiving structured e-invoices.

Can I still receive PDF invoices from German suppliers?

You can accept PDFs from suppliers not yet required to send structured e-invoices, since the sending mandate is phased by revenue tier. But every German VAT-registered business should already be capable of receiving structured invoices in EN 16931 format. Conservative approach: treat structured XML as the default and PDFs as a transitional fallback.

What German e-invoice formats are accepted?

Three EN 16931-compliant formats: XRechnung (UBL or CII syntax), ZUGFeRD 2.x (hybrid PDF/A-3 with embedded CII XML), and Peppol BIS Billing 3.0. The current XRechnung version is 3.0.2; KoSIT publishes specification updates regularly, so always validate against the current effective version.

Is Peppol mandatory in Germany?

No. Peppol is one accepted transmission channel; email and other electronic channels are also valid. But Peppol-readiness is the path of least resistance for cross-border EU mandates and the ViDA 2030 directive, so most ERP vendors building German support are also building Peppol support.

What's the penalty for non-compliant German e-invoices?

For B2G submissions, non-compliant invoices are rejected by the ZRE portal — payment delays follow. For B2B, the Wachstumschancengesetz did not specify direct administrative fines, but non-compliant invoices may not qualify for VAT deduction by the recipient. Enforcement is expected to tighten as the Phase 2 sending mandate takes effect in January 2027.

How does Germany's €800K threshold for Phase 2 work?

The threshold applies per legal entity, not per group. Multi-entity organizations need per-entity revenue tracking — you cannot consolidate at group level for the threshold test. The Wachstumschancengesetz also allows EDI continuity during the transition, but only when both parties agree. Confirm EDI exemption with each counterparty rather than assuming.

Validate before you send

Before processing or transmitting an e-invoice, validate it against the EN 16931 standard plus XRechnung CIUS rules. The free Invoice Navigator validator checks:

• XML structure validity
• EN 16931 business rules (BR-01 through BR-65)
• XRechnung CIUS rules (BR-DE-* and country-specific)
• ZUGFeRD profile validation (Minimum, Basic WL, Basic, EN 16931, Extended)
• Peppol BIS Billing 3.0 specific rules (PEPPOL-EN16931-R*)

Stay updated

German and EU e-invoicing regulations are not static. The KoSIT specification, EN 16931 Schematron, and Peppol artifacts all release updates that affect what's accepted and what gets rejected. Bookmark the Invoice Navigator changelog to track regulatory updates as they happen, and the Germany country guide for the current state of formats, validation engines, and mandate phases.