Germany · XRechnung: e-invoice formats and rules

Use this page to choose the Germany · XRechnung check, identify the fixed package and follow diagnostic examples before sending an invoice to its recipient.

Formats and syntax

XRechnung represents a German invoice as UBL or CII XML with national restrictions on the European model. ZUGFeRD, equivalent to Factur-X in the paired releases, combines a readable PDF with structured CII data. The Federal Ministry of Finance distinguishes accepted structured formats and excludes the MINIMUM and BASIC-WL ZUGFeRD profiles from its stated B2B format conditions. A PDF containing invoice-looking text is not enough to establish the required structured information.

Rules XSDHub applies

The XRechnung selection in XSDHub uses EN 16931 artefacts 1.3.16 with XRechnung 3.0.2 and national Schematron rules 2.6.0. Both UBL and CII use the corresponding schema layer before business rules run. These are pinned application versions, not a promise to track every KoSIT release automatically. For a ZUGFeRD container, use the separate Factur-X validator and its declared-profile checks instead of feeding the whole PDF to the XML form.

Who this affects

KoSIT describes XRechnung as the standard used for invoices to public contracting bodies: B2G means that your customer is a public authority. The Ministry of Finance FAQ separately explains German domestic B2B invoicing and transitional provisions. Receiver routing, exceptions and the required submission channel need checking against those sources and your contract. Technical validation does not decide your tax status or whether a particular public recipient has registered your business.

Common errors to investigate

What XSDHub checks / what it does not
CheckXSDHub coverage
XML structure and fixed rulesEN 16931 1.3.16 + XRechnung 3.0.2 / Schematron 2.6.0
Certification and legal acceptanceNot provided
Government portal submissionNot provided
PeppolNot supported yet

Working with the result

Export the syntax that the German customer accepts, choose XRechnung explicitly and review both schema failures and business-rule findings. Keep routing references in the source invoice system so that the next export preserves them. Passing XML can still be rejected by a receiving portal for registration or delivery reasons. The related German guides explain these distinctions without presenting XSDHub as a government-certified submission service.

Need batches or an API?

Check an invoice for free

Start Pro Start Team · Pricing · API documentation

Official sources · checked 5 November 2026

E-invoicing by country · English rule guide