XRechnung is Germany’s Core Invoice Usage Specification (CIUS) for structured electronic invoices. It defines invoice content and business rules; it is not an exchange network. Public-sector buyers can require a particular portal or Peppol route in addition to the XRechnung format, while Germany’s B2B VAT e-invoice rules are a separate scope question.
At a glance
- What it is: Structured e-invoice (EN 16931 compliant XML); public-sector issuing standard in Germany
- Formats: XRechnung 3.0.2 (CIUS using UBL or CII syntax); delivery channel is a separate buyer or mandate requirement
- SAP scope: SD billing, FI invoices, tax codes, customer master data (Leitweg-ID)
- Key risk: Rejected invoices, payment delays, manual correction work
- Related mandate(s): Germany structured B2B e-invoicing (mandatory from 1 Jan 2027 / 1 Jan 2028)
Executive Summary
| Mandate name | Germany XRechnung |
|---|---|
| Current status | XRechnung 3.0.2 is the production baseline verified on 10 July 2026. Buyer-specific B2G routing and identifier requirements must still be confirmed. |
| Who is affected | Suppliers invoicing German public-sector buyers that require XRechnung, subject to the buyer’s federal, state or local rules. Germany’s B2B VAT-format obligation must be assessed separately. |
| Business risk | Rejected invoices, payment delays, and manual correction work. |
| SAP impact | SD billing, FI invoice data, customer master data, tax codes, XML output, and validation. |
| Recommended next step | Confirm affected invoice flows and XML output requirements. |
What Is the Requirement?
XRechnung specifies a German CIUS of EN 16931 and supports the UBL and UN/CEFACT CII syntaxes defined by the specification. The invoice must satisfy XRechnung business rules and the recipient’s identifiers. Version 4.0 should not be described as the current production baseline unless KoSIT publishes it as such.
Format, Channel and Legal Scope Are Separate
- Format: XRechnung is a CIUS and validation rule set, currently version 3.0.2.
- Syntax: the structured invoice can use the supported UBL or CII syntax.
- Channel: Peppol, a government portal or another buyer-approved route transports the invoice; Peppol is not the XRechnung format.
- B2G: the public buyer determines portal, routing identifier and submission details.
- B2B: Germany’s VAT-law structured e-invoice requirements and transition dates must be assessed separately from public procurement.
Business Impact for Finance and Tax Teams
Teams need invoice data that passes recipient or platform validation and remains traceable to SAP source documents.
How This Impacts Your SAP Environment
- Billing output must generate valid structured invoice data.
- Customer master data and tax fields must support required XML fields.
- Validation errors need correction workflow and ownership.
How S4FN Supports SAP Compliance
S4FN can review SAP invoice data, XRechnung mapping assumptions, validation workflow, and technical prerequisites.
Primary Source and Verification
Verified on: 10 July 2026. Confirm the current KoSIT release and the recipient’s B2G routing rules before implementation.
Review XRechnung Readiness in SAP
Discuss XML output, invoice scenarios, and SAP integration approach with S4FN.
