How to Create an XRechnung
Public authorities in Germany do not accept PDF invoices: federal, state, and municipal buyers require an XRechnung, a pure XML document following EN 16931 plus the German CIUS rules. The generator above produces exactly that file. Fill in the form once, add the Leitweg-ID, and download an XRechnung that passes the checks the portals run on submission.
The Leitweg-ID: the one field that trips everyone up
Every XRechnung to a public buyer must carry the recipient's Leitweg-ID in the buyer reference (BT-10). It identifies the authority's inbox on the invoice platform and follows the pattern {authority-id}-{optional-suffix}-{check-digit}. You get it from the contracting authority, usually with the order or in the contract; ask for it before you invoice, because a missing or malformed Leitweg-ID is the most common reason an XRechnung bounces.
What else the XRechnung requires
Beyond the usual EN 16931 core (parties, line items, VAT breakdown, payment details), the German CIUS expects an electronic address for both parties, a seller contact with phone or email, and payment via one of the permitted means codes. The form above carries all of these fields, and the generated XML is validated against the CIUS rules before you download it.
Invoicing a company instead of an authority?
Then you do not need an XRechnung. For B2B invoices the practical German format is ZUGFeRD: a normal-looking PDF with the same structured data embedded inside:
- Create a ZUGFeRD invoice instead
- Validate an existing XRechnung file
- Open and read an XRechnung you received
- Read the full XRechnung format guide with sample files
ZRE, OZG-RE, or Peppol: how the file reaches the authority
Federal authorities receive through the ZRE portal, most states through OZG-RE or their own platforms, and a growing number accept delivery over the Peppol network. The XML is identical in all three cases; only the transport differs. Premium accounts can send the finished XRechnung via Peppol directly from this page.