Is XRechnung the same as ZUGFeRD?

No. XRechnung is pure XML. ZUGFeRD is a PDF with embedded CII XML; its XRECHNUNG profile carries an XRechnung inside the PDF.

Do private companies have to use XRechnung?

No. For B2B any EN 16931 compliant format is allowed — XRechnung, ZUGFeRD (EN 16931 profile or higher) and Peppol BIS 3.0 are all fine.

What is a Leitweg-ID?

The routing identifier of German public authorities. It is placed in the buyer reference (BT-10) and, on Peppol, used as endpoint with scheme 0204.

XRechnung validator for German e-invoices

XRechnung is the German CIUS of EN 16931, mandatory for invoices to the federal government and widely used for B2B. Upload an XRechnung in UBL or CII syntax to check the EN 16931 core rules, calculations and identifiers.

Specification: XRechnung 3.0 (KoSIT)
Syntaxes: UBL 2.1 and UN/CEFACT CII D16B
CustomizationID: urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0
Used for: B2G (mandatory) and B2B

Rules

Drop your e-invoice here

UBL 2.1 · Peppol BIS 3.0 · XRechnung · Factur-X / ZUGFeRD (XML or PDF)

Processed in memory and never stored. PDFs are unpacked in your browser.

What this validator checks for Germany

Detection of the XRechnung 3.0 CustomizationID in UBL and CII
All EN 16931 core business rules (BR-01 … BR-65, BR-CO, BR-S/Z/E/AE)
German VAT number format and check digit
Decimal precision of amounts (max. 2 decimals)
IBAN check digits for SEPA payment instructions

XRechnung national rules

XRechnung adds German rules (BR-DE-*) on top of EN 16931, for example a mandatory seller contact and payment instructions. InvoiceVerify validates the complete EN 16931 core today; the dedicated BR-DE rule set is on our roadmap. For B2G submissions, run the official KoSIT validator as a final check.

UBL or CII?

Both syntaxes are allowed and carry the same information. UBL is more common on Peppol; CII is used by ZUGFeRD/Factur-X tooling. Our report maps both onto the same EN 16931 business terms, so the inspection view looks identical.