ZUGFeRD ToolsZUGFeRD Tools

XRechnung — the German XML format for e-invoices

What is an XRechnung and how do you validate or display one? XRechnung is the XML-based German format for electronic invoices built on EN 16931 — the standard in public-sector traffic and the second pillar of commercial exchange. Here you find the explanation, validator and viewer.

By the editorial team ZUGFeRD Tools

  • Current: XRechnung 3.0.2 · Bundle 2026-08-31
  • Syntaxes: UBL 2.1 and UN/CEFACT CII
  • CIUS with BR-DE rules (incl. Leitweg-ID)
  • KoSIT validator reference: 1.6.3
ZUGFeRD version (FeRD, 2026-08-04)
2.5.2ZUGFeRD version (FeRD, 2026-08-04)
XRechnung, bundle 2026-08-31
3.0.2XRechnung, bundle 2026-08-31
ZUGFeRD profiles
5ZUGFeRD profiles
syntaxes: UBL 2.1 & CII
2syntaxes: UBL 2.1 & CII
EN 16931 rules checked
24EN 16931 rules checked
all tools, no sign-up
€0all tools, no sign-up

What is an XRechnung?

An XRechnung is an electronic invoice as a pure XML file. Unlike ZUGFeRD, XRechnung does without a visual PDF layer: the invoice consists entirely of structured data. XRechnung is thus the consistently machine-readable way to exchange electronic invoices — the recipient’s software processes line items, taxes and totals directly.

Technically, XRechnung is a CIUS (Core Invoice Usage Specification) based on the European standard EN 16931: the same semantic invoice data, supplemented by German rules — the BR-DE rules. Two syntaxes are allowed: OASIS UBL 2.1 and UN/CEFACT CII. Receiving an XRechnung requires software that processes at least one of them.

XRechnung is used mainly in traffic with public bodies: federal authorities accept invoices via portals such as the ZRE (Zentrales Rechnungseingangsportal) or OZG-RE, increasingly via PEPPOL. In parallel, XRechnung establishes itself in commercial exchange as a structured second route next to ZUGFeRD.

The structure of an XRechnung: XML instead of PDF

An XRechnung starts with the CustomizationID (UBL) or GuidelineID (CII) — the URN identifying the file as an XRechnung of the respective release. Then follow the familiar blocks: invoice header with number and date (BT-1, BT-2), seller and buyer with addresses and VAT ID, the line items with quantity, price and tax rate, the VAT breakdown and the totals up to the payable amount (BT-115).

The special feature is the Leitweg-ID (BT-10): this recipient reference is mandatory in every XRechnung via rule BR-DE-15. For authorities it is documented in the tender; it ensures the invoice reaches the right office in the recipient’s system.

Because XML is hard to read unaided, the viewer belongs to XRechnung practice: it renders the file as a familiar invoice. The viewer on this page works entirely in the browser — and honestly notes that displaying is not validating.

XRechnung versions: 3.0.2 is current

As of 2026-09-29 — XRechnung 3.0.2, bundle 2026-08-31, KoSIT validator 1.6.3. Source: xeinkauf.de / KoSIT.

The current release is XRechnung 3.0.2 with the technical bundle of 2026-08-31; the reference validator is the KoSIT validation software in version 1.6.3. XRechnung 4.0 so far exists only as a pre-release and is not the active standard — pages presenting 4.0 as “current” are wrong.

The version history runs from 1.2 through the widely spread 2.x series to the current 3.x line. Older files still appear in daily practice; good tools read the release from the file instead of guessing it.

ReleaseStatusNote
3.0.2currentBundle 2026-08-31, validator 1.6.3
3.0 / 2.4 / 2.3 / 2.2 / 2.1in circulationstill widespread
4.0pre-releasenot the active standard
1.2outdatedpredates the EN 16931 CIUS structure

Receiving, validating, displaying an XRechnung

Receive and validate

Received XRechnungen should be validated before booking — at the latest when senders or systems change. The XRechnung validator checks well-formedness (with XXE protection), syntax detection, the XSD schema for CII, the EN 16931 core rules and the BR-DE rules including the Leitweg-ID. The result names rule IDs and honestly states which layers ran.

Display and process

For reading, the XRechnung viewer serves: select the XML and the invoice appears — with invoice and XML views. Authority processes continue with upload routes (ZRE, OZG-RE or PEPPOL); for commercial booking, the accounting system imports the XML directly.

XRechnung in the context of the e-invoicing mandate

The tax-law e-invoicing mandate requires structured, machine-readable invoices: since 1 January 2025, domestic businesses must be able to receive e-invoices; issuing has transition periods that can run to the end of 2027 depending on prior-year turnover (BMF FAQ, as of 2026-09-29).

XRechnung and ZUGFeRD are the two ways to meet this requirement in the German market. Which is right for a given case depends on the recipient — the comparison on the ZUGFeRD vs XRechnung page helps decide. For the tax assessment of your case the usual applies: professional advice beats rules of thumb.

FAQ

What is an XRechnung?

An XRechnung is an electronic invoice as a pure XML file based on EN 16931 — supplemented by German BR-DE rules. It is the standard in public-sector traffic (B2G) and is also used in commercial exchange.

Which file format does an XRechnung have?

An XML file — usually with the .xml extension. There is no PDF layer; the invoice consists entirely of structured data.

What is the difference between XRechnung and ZUGFeRD?

XRechnung is pure XML with German CIUS rules (typically B2G); ZUGFeRD is a PDF with embedded XML (typically B2B). Both build on EN 16931 — the comparison page has the details.

Which syntaxes exist for XRechnung?

Two: OASIS UBL 2.1 (Invoice document) and UN/CEFACT CII (CrossIndustryInvoice). Both are allowed; the validator and viewer on this site support both.

What is the Leitweg-ID and where do I get it?

The Leitweg-ID (BT-10) is the recipient reference mandatory in every XRechnung (BR-DE-15). Authorities document it in the tender or portal; it identifies the responsible office of the recipient.

Which XRechnung version is current?

XRechnung 3.0.2 with the technical bundle of 2026-08-31; the reference is KoSIT validator 1.6.3. XRechnung 4.0 is only a pre-release (as of 2026-09-29).

How do I submit an XRechnung to an authority?

Via the routes specified by the recipient: the Zentrale Rechnungseingangsportal (ZRE), OZG-RE or PEPPOL. The file must comply with the rules beforehand — the validator helps avoid rejections up front.

Can I print an XRechnung as a PDF?

For reading, yes — the viewer produces a readable display. Legally, the XRechnung remains the XML file; a printout is no longer an e-invoice.

This site provides technical information and does not constitute tax or legal advice. Legal status of the e-invoicing mandate: BMF FAQ, as of 2026-09-29.