Guide
E-Invoicing in Germany
Key formats, routing options, and a practical checklist for sending compliant e-invoices in Germany.
What matters in practice
This Germany guide explains how XRechnung, ZUGFeRD, Leitweg-ID routing, and KoSIT validation work in practice so buyers and suppliers can send invoices without avoidable rejections.
This article treats E-Invoicing in Germany as a practical reference, not just a navigation page. It explains the term or workflow in context, shows why it matters for European e-invoicing, and connects the topic to invoice creation, validation, routing, archiving, and ERP implementation decisions.
Common e-invoice formats
Common e-invoice formats is where the general explanation of E-Invoicing in Germany becomes operational. The section focuses on XRechnung (UBL/CII) and ZUGFeRD / Factur-X, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- XRechnung (UBL/CII)
- ZUGFeRD / Factur-X
Routing & delivery
Routing & delivery connects E-Invoicing in Germany with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding ZRE / OZG-RE and PEPPOL to validating or converting the invoice file.
Common identifiers
Common identifiers is where the general explanation of E-Invoicing in Germany becomes operational. The section focuses on Leitweg-ID (B2G) and VAT ID (USt-IdNr.), so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Leitweg-ID (B2G)
- VAT ID (USt-IdNr.)
Mandate & scope
Germany’s e-invoicing landscape mixes EN 16931-based formats (XRechnung) with delivery via portals and PEPPOL.
Mandate & scope
Mandate & scope is where the general explanation of E-Invoicing in Germany becomes operational. The section focuses on B2G: XRechnung is the standard for invoices to public authorities (federal, state, municipal)…, Syntax: XRechnung typically uses UBL or CII; the receiver/channel decides which is accepted and Routing: public sector workflows often require Leitweg-ID and a buyer reference for internal…, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- B2G: XRechnung is the standard for invoices to public authorities (federal, state, municipal) depending on the recipient’s requirements.
- Syntax: XRechnung typically uses UBL or CII; the receiver/channel decides which is accepted.
- Routing: public sector workflows often require Leitweg-ID and a buyer reference for internal routing.
- B2B: ZUGFeRD/Factur-X is common where a PDF-first workflow is still required.
How to send (practical steps)
How to send (practical steps) is where the general explanation of E-Invoicing in Germany becomes operational. The section focuses on Confirm the recipient channel (ZRE/OZG-RE portal vs PEPPOL) and the accepted syntax (UBL vs CII), Collect routing identifiers (Leitweg-ID, buyer reference, PEPPOL endpoint/participant IDs if… and Export EN 16931-compliant data and validate (schema + business rules / CIUS) before sending, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Confirm the recipient channel (ZRE/OZG-RE portal vs PEPPOL) and the accepted syntax (UBL vs CII).
- Collect routing identifiers (Leitweg-ID, buyer reference, PEPPOL endpoint/participant IDs if applicable).
- Export EN 16931-compliant data and validate (schema + business rules / CIUS) before sending.
- Submit via the chosen channel and store the acknowledgement/receipt for auditability.
Validation & compliance
Validation & compliance is where the general explanation of E-Invoicing in Germany becomes operational. The section focuses on Validate with KoSIT rulesets for the targeted XRechnung version/profile, Ensure code lists are correct (currency, VAT category, units, payment means) and Avoid modeling discounts as negative invoice lines; use allowance/charge structures, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Validate with KoSIT rulesets for the targeted XRechnung version/profile.
- Ensure code lists are correct (currency, VAT category, units, payment means).
- Avoid modeling discounts as negative invoice lines; use allowance/charge structures.
Common pitfalls
Common pitfalls is where the general explanation of E-Invoicing in Germany becomes operational. The section focuses on Missing buyer reference / Leitweg-ID for public sector routing, Address completeness issues (street/city/postcode/country) causing validator rejections and Wrong code list values (VAT category codes, unit codes) that pass internally but fail in KoSIT, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Missing buyer reference / Leitweg-ID for public sector routing.
- Address completeness issues (street/city/postcode/country) causing validator rejections.
- Wrong code list values (VAT category codes, unit codes) that pass internally but fail in KoSIT.
Frequently asked questions
Frequently asked questions answers the practical questions that usually appear after reading the main explanation of E-Invoicing in Germany. The answers focus on When should I use XRechnung in Germany and What should I verify before submitting an invoice and are written to clarify implementation choices quickly.
When should I use XRechnung in Germany?
Use XRechnung for public-sector invoicing when the recipient requires it, and choose the accepted syntax and channel before you send.
What should I verify before submitting an invoice?
Check the buyer reference, Leitweg-ID, party addresses, code lists, and validation results so the invoice can pass routing and business-rule checks.
Official links
Official links connects E-Invoicing in Germany with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding XRechnung (official information), E-Rechnung Bund (ZRE / OZG-RE) and OpenPeppol (PEPPOL network) to validating or converting the invoice file.