Skip to content

XRechnung generator

An XRechnung for German public bodies, with every required field checked before you download.

E-invoice format
Invoice details
Your business
Bill to
Items
  1. $0.00
Sales tax rates

Each item uses one of these; choose it on the item under "Sales tax". Sales tax depends on your state, county and city, so type the combined rate that applies to this sale.

  • Sales tax % used by 1 item

Also on each item's list, with no rate to set: No tax.

Notes and payment
Saved on this device (0)

Every invoice you download is kept here, in this browser only.

Clearing your browser's site data deletes these. Export a backup to keep a copy.

How to use XRechnung generator

  1. Choose XML syntax. Select XRechnung (CII) or XRechnung (UBL) at the top of the editor depending on your buyer's portal requirements.
  2. Enter supplier details. Fill in your business name, street, city, postcode, VAT or tax number, IBAN, and the required seller contact person, phone, email, and electronic address.
  3. Add buyer and Leitweg-ID. Enter the buyer's address and electronic address, then paste their Leitweg-ID or order reference into Buyer reference.
  4. Verify checks and download. Add net line items with VAT rates, resolve any red items in the live checklist, and click Download XML.

Everything you type stays in this browser on your device. Nothing is uploaded, and your saved details are never sent anywhere.

How to create an XRechnung 3.0 XML invoice locally

Suppliers billing German federal, state, and municipal agencies must submit structured XML conforming to XRechnung 3.0 rather than plain PDF attachments. The format implements EU Directive 2014/55/EU on Electronic Invoicing, which requires public contracting authorities across Europe to receive EN 16931 compliant bills.

Every exported file carries the official customization identifier urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0 and builds locally in your browser with 0 bytes uploaded. For domestic PDF billing outside public portals, you can also create standard German EUR invoices with 19% or 7% VAT in the same workspace.

Understanding Leitweg-ID routing and Buyer reference rules

German public agencies assign a hyphenated Leitweg-ID so central intake gateways like ZRE and OZG-RE forward invoices to the right budget office. Entering that code under Buyer reference satisfies German business rule BR-DE-15.

Private B2B buyers who request XRechnung without holding a public Leitweg-ID usually supply a cost center, vendor number, or purchase order ID instead. Placing a meaningful buyer reference prevents automated routing holds at the receiving ERP gateway.

Since January 2025, German B2B e-invoicing reforms also require domestic businesses to be able to receive structured electronic invoices. Transition rules for issuing structured XML vary by turnover and tax status, so verify your exact filing timeline before submitting.

Public-sector suppliers face stricter rules because federal agencies already mandate structured XML without paper or plain-PDF fallbacks. Preparing your seller profile once inside local storage lets you generate compliant repeat bills whenever a new public tender milestone closes.

Choosing between CII D16B and UBL 2.1 XML syntax

XRechnung is a semantic standard rather than a single XML schema, allowing suppliers to export either UN/CEFACT Cross Industry Invoice (CII D16B) or OASIS Universal Business Language (UBL 2.1). Selecting XRechnung (CII) or XRechnung (UBL) switches the element tree while preserving identical EN 16931 totals.

As documented on the KoSIT XRechnung 3.0 Official Specification Portal, German portals accept both syntaxes, though some ERP receivers prefer one over the other. Both formats enforce strict element ordering, so generating them from a typed schema tree avoids manual tag typos.

If a private buyer wants a visual PDF alongside machine-readable XML, switch to a hybrid ZUGFeRD PDF/A-3 invoice instead.

Format option Underlying schema Visual PDF layer Typical German use case Primary portal target
XRechnung (CII) UN/CEFACT CII D16B None (pure XML) Federal and state B2G suppliers ZRE, OZG-RE, Peppol
XRechnung (UBL) OASIS UBL 2.1 None (pure XML) Cross-border and Peppol-ready B2G Peppol, municipal portals
ZUGFeRD / Factur-X CII D16B in PDF/A-3b Yes (PDF/A-3b) German and French B2B billing Email and ERP intake
Peppol BIS 3.0 OASIS UBL 2.1 None (pure XML) EU and Belgian B2B networks Peppol access points

How live BR-DE checks prevent portal rejection

Public intake portals reject malformed XML immediately when mandatory contact fields, electronic endpoints, or VAT breakdowns are missing. The sidebar runs checkEInvoice() in real time as you type, flagging errors before you click Download XML.

Fixing missing BT-34, BT-49, and seller contact errors

XRechnung 3.0 enforces seller contact name (BR-DE-5), phone (BR-DE-6), email (BR-DE-7), and both BT-34 seller and BT-49 buyer electronic addresses. Because the OpenPeppol BIS Billing 3.0 Specification shares this endpoint model, supplying an email address with scheme EM satisfies both German and Peppol routing checks.

Net-only line pricing and ISO 13616 IBAN verification

EN 16931 enforces net unit prices per line item and checks arithmetic within a 0.01 currency tolerance across BR-CO-10 through BR-CO-16. The validator also runs an ISO 13616 mod-97 check on your IBAN (BR-DE-23) so transposed bank digits trigger an instant warning.

After downloading, you can inspect generated XML fields as a human-readable invoice to confirm every tax category and line total before portal upload.

Tip: Never type negative unit prices on discount lines (BR-27); use a negative quantity or issue a dedicated credit note instead.

Statutory compliance, archiving, and validation boundaries

Structured XML invoices must satisfy German commercial and tax retention rules just like paper bills. Under the German VAT Act § 14 UStG, suppliers must ensure authenticity of origin, integrity of content, and legibility throughout the statutory retention period.

Why pre-download checks do not replace KoSIT Schematron

Our browser checks cover the core EN 16931 arithmetic, VAT category, and BR-DE field rules that cause most rejections, but they are not a full KoSIT Schematron validation engine. When submitting to a federal portal for the first time, run the exported XML through your buyer’s test validator as well.

Testing a sample invoice before your first live submission catches portal-specific routing preferences, such as whether a municipal office expects Peppol endpoint schemes or custom purchase order tags. Saving validated supplier defaults in browser storage prevents repeat typos on monthly retainers.

Non-tax-advice disclaimer and German § 14 UStG obligations

This generator is provided for operational convenience and does not constitute certified tax, accounting, or legal advice. Statutory VAT rates, exemption clauses, and e-invoicing mandates evolve regularly, so confirm your tax classification and archiving setup with a qualified accountant or tax authority. If you also send visual PDFs to private clients, create German GiroCode SEPA payment QR codes for faster bank transfers.

Questions

What is a Leitweg-ID and where do I find it?

A Leitweg-ID is the structured routing code issued by German federal, state, and municipal agencies so incoming e-invoices reach the right department. Public buyers list it in their tender award letter or contract; enter it under Buyer reference.

What is the difference between XRechnung and ZUGFeRD?

XRechnung is a pure XML file without a visual PDF page, required by most German public-sector portals. ZUGFeRD / Factur-X is a hybrid PDF/A-3 file that embeds structured XML inside a readable invoice PDF for B2B billing.

Should I choose CII or UBL syntax for XRechnung?

Both UN/CEFACT CII and OASIS UBL are official XRechnung 3.0 syntaxes under the KoSIT specification. Choose the format your buyer's portal specifies; if the buyer gives no preference, CII is widely used in Germany while UBL aligns closely with Peppol.

Is client invoice data uploaded to external servers?

No. XML serialization, BR-DE validation, and IBAN check-digit verification run completely inside your browser tab with zero bytes sent over the network. Saved profiles remain in local browser storage.

Does XRechnung 3.0 allow gross prices with VAT included?

No. EN 16931 requires net unit prices per line item and calculates VAT per tax category and rate in the summary breakdown. Enter net prices before VAT so line sums and tax totals pass arithmetic rules BR-CO-10 through BR-CO-15.

Do the built-in checks guarantee portal acceptance without tax advice?

The live checklist catches missing required fields and arithmetic errors before download, but it is an operational convenience rather than full KoSIT Schematron validation or certified tax advice. Confirm statutory VAT wording and portal rules with a qualified accountant or tax authority.

Updated