In short
XRechnung 3.0.2 is in force and stays valid until at least 31 July 2027. XRechnung 4.0, based on EN 16931-1:2026, exists only as a preliminary specification (15 September 2026); the final version and its validation artefacts are expected in spring 2027. For German B2B, XRechnung is one accepted e-invoice format: receiving is required since 1 January 2025, issuing from 2027 (prior-year turnover above €800,000) and 2028 (everyone).
How XRechnung works
An XRechnung is an XML file that follows the EN 16931 data model, plus the German rules on top. You can write it in either of the two EN 16931 syntaxes:
The file declares itself as XRechnung in the specification identifier (BT-24), and KoSIT’s validator then applies three layers: the XML schema, the EN 16931 business rules, and the German BR-DE rules.
What the BR-DE rules add
The XRechnung 3.0.2 configuration contains 31 BR-DE rules. The ones senders run into most:
- BR-DE-15: the buyer reference (BT-10) must be present. For public buyers this is their Leitweg-ID; for other buyers, the reference they ask for, such as an order number.
- BR-DE-2, -5, -6, -7: a seller contact group with name, telephone and e-mail address (BT-41 to BT-43). BR-DE-27 and BR-DE-28 check that the phone has at least three digits and the e-mail has a valid shape.
- BR-DE-3, -4, -8, -9: seller and buyer city and post code.
- BR-DE-1: payment instructions (BG-16) are mandatory; BR-DE-23 to -25 tie them to the payment means code (transfer, card, direct debit).
- BR-DE-14 and BR-DE-16: every VAT breakdown states its rate, and the seller’s VAT ID or tax number is present when VAT applies.
- BR-DE-18: cash discount (Skonto) terms follow a fixed text format.
- BR-DE-21: the specification identifier (BT-24) must name XRechnung.
Where public-sector invoices go
- Federal authorities: the OZG-RE platform, by web form, upload, e-mail or Peppol. The former ZRE platform has been merged into it.
- Länder and municipalities: their own portals or Peppol; the buyer tells you which, together with the Leitweg-ID.
Why XRechnung matters
Public sector: e-invoices required since 2020
Suppliers to the German federal administration have had to send e-invoices since 27 November 2020. The federal portal checks them against XRechnung or another standard that meets EN 16931. Länder and municipalities set their own rules.
B2B: one accepted format among several
For invoices between German businesses, the law asks for an e-invoice that meets EN 16931, not for XRechnung specifically. ZUGFeRD from version 2.0.1 also counts, except its MINIMUM and BASIC WL profiles. The dates (§ 27 (38) UStG):
| Date | What applies |
|---|---|
| 1 January 2025 | Every business must be able to receive e-invoices. |
| Until 31 December 2026 | Anyone may still send paper, or another electronic format if the recipient agrees. |
| 1 January 2027 | Businesses whose total turnover in the previous year was above €800,000 must issue e-invoices. |
| Until 31 December 2027 | Businesses at or below €800,000 may still send paper or other formats; EDI may continue with the recipient’s consent. |
| 1 January 2028 | Everyone issues e-invoices for domestic B2B supplies. |
Invoices up to €250, tickets and invoices from small businesses under the Kleinunternehmer rule may always be sent in another form (BMF letter of 15 October 2025).
Versions: 3.0.2 now, 4.0 next
XRechnung 3.0 has been in force since 1 February 2024. KoSIT made no normative release in summer 2026, so 3.0 stays in force until at least 31 July 2027. The current bundle is 3.0.2 (Summer 2026 bugfix of 31 August 2026; visualisation fix of 13 October 2026). XRechnung 2.3 has been out of force since 1 February 2024.
XRechnung 4.0 is built on the revised European standard EN 16931-1:2026. KoSIT published a preliminary specification on 15 September 2026 and states it is not meant for production use. The final 4.0 bundle, with schematron, validator configuration and test suite, is expected in spring 2027; it depends on CEN’s validation artefacts for the 2026 standard, which are not published yet. KoSIT plans a gradual transition and has not announced dates. The 2017 and 2026 editions of EN 16931-1 may be used in parallel until March 2029.
What that means for you
- Senders: keep producing XRechnung 3.0.2 and validate against the current KoSIT configuration. Nothing in 4.0 can be implemented against an official validator yet.
- Receivers: accept 3.0.x for at least the period to 31 July 2027, and plan to read 4.0 files once KoSIT publishes the transition dates.
We check XRechnung 3.0.2 files with the official KoSIT validator. Check an XRechnung.
How to get started
Step 1: Find out what your buyer needs
Public buyers usually require XRechnung and give you a Leitweg-ID and a submission channel. Business customers must be able to receive e-invoices that meet EN 16931, so XRechnung and ZUGFeRD both work.
Step 2: Fill the German mandatory fields
Buyer reference (BT-10), seller contact name, phone and e-mail, both addresses with city and post code, payment instructions, and your VAT ID or tax number. These are the fields behind most BR-DE rejections.
Step 3: Create and check the file
Export XRechnung 3.0.2 from your invoicing software, or convert an invoice with our converter, then check it with the KoSIT validator before you send it.
Sources
Facts checked against these sources on 3 November 2026.
Further reading
- What is ZUGFeRD?Hybrid PDF/XML format
- XRechnung vs ZUGFeRDWhich format to use
- Germany E-Invoicing GuideFull requirements
- What is EN 16931?The EU standard
- E-Invoicing DeadlinesAll mandate dates
- Validate your XRechnungFree check with the KoSIT validator
- Convert PDF to XRechnungAI-assisted PDF → XRechnung 3.0.2 (UBL or CII)
- PDF in XRechnung umwandelnDeutsche Konvertierungs-Landing (KI-gestützt)
- XRechnung erstellen (Deutsch)Vier Wege zur konformen XRechnung
Questions
- Which XRechnung version applies now?
- XRechnung 3.0, current bundle 3.0.2. It has been in force since 1 February 2024 and stays in force until at least 31 July 2027. XRechnung 4.0 exists only as a preliminary specification (15 September 2026); the final version is expected in spring 2027.
- Is XRechnung mandatory for German businesses?
- XRechnung itself is not; an e-invoice that meets EN 16931 is. Every business must be able to receive e-invoices since 1 January 2025. Issuing becomes mandatory on 1 January 2027 for businesses with prior-year turnover above €800,000 and on 1 January 2028 for all. XRechnung and ZUGFeRD (from 2.0.1, except MINIMUM and BASIC WL) both qualify.
- What changes with XRechnung 4.0?
- XRechnung 4.0 moves to the revised European standard EN 16931-1:2026. The preliminary specification of 15 September 2026 describes the new data model, but the validation artefacts are not published yet, so it cannot be used in production. KoSIT plans a gradual transition and has not announced dates.
- What's the difference between XRechnung and ZUGFeRD?
- XRechnung is a pure XML file. ZUGFeRD is a PDF/A-3 with the invoice data embedded as CII XML. Both meet EN 16931 for German B2B. Federal authorities accept ZUGFeRD in its XRECHNUNG profile. Compare XRechnung vs ZUGFeRD
- What is a Leitweg-ID?
- The routing identifier of a German public-sector buyer. It goes into the buyer reference (BT-10), and the buyer gives it to you. Rule BR-DE-15 rejects an XRechnung without a buyer reference.
- Which syntax should I use, UBL or CII?
- Both are valid XRechnung and both are checked by the same KoSIT configuration. UBL is common where Peppol is used; CII is the syntax inside ZUGFeRD.