Loading

XRechnung creation guide

What to prepare before you create an XRechnung

XRechnung is structured XML based on EN 16931. Use this page when you are issuing a new invoice from data fields instead of converting an existing PDF. The generated file still needs recipient-specific details and a final review before submission.

Where XRechnung fits

For German public-sector buyers and many German e-invoicing workflows, XRechnung is a pure XML invoice. German B2B e-invoicing rules distinguish structured e-invoices from ordinary PDFs, so start from the structured data your recipient expects.

Leitweg-ID and delivery route

Public-sector recipients usually provide the Leitweg-ID. Put it in BuyerReference BT-10 and confirm whether the recipient wants direct XML, Peppol, an OZG-RE/ZRE-style portal, or another portal upload.

XRechnung, ZUGFeRD or PDF

Use XRechnung when the recipient expects a machine-readable XML invoice. Use ZUGFeRD or Factur-X when a hybrid PDF/A-3 file with embedded XML is accepted. A normal PDF alone is not a structured e-invoice.

Validate before sending

Schema validity is only the first check. Review BR-DE and XRechnung business rules, tax logic, mandatory references and recipient-specific routing before treating the XML as ready.

Required invoice data

A valid file depends on complete invoice data, not just totals. Prepare these values before generating XML.

  • Seller and buyer legal names, addresses, VAT or tax identifiers where applicable.
  • Invoice number (BT-1), issue date (BT-2), currency (BT-5), payment terms and due date.
  • Line items with descriptions, quantities, units, net unit prices, VAT categories and rates.
  • Totals that reconcile: line net amounts, tax basis, VAT totals, allowances or charges, and payable amount.
  • BuyerReference BT-10 is required for XRechnung; for German public-sector recipients it is usually the Leitweg-ID.
  • Delivery or project references your recipient or portal requires, such as order number, contract reference or electronic address.

Before you download

  1. 1Confirm the recipient accepts XRechnung and which syntax or portal they require.
  2. 2Enter invoice data at line level instead of relying only on summary totals.
  3. 3Add BuyerReference BT-10 before generation; use the Leitweg-ID when the German public-sector recipient provides one.
  4. 4Review validation warnings and regenerate after any material edit.
  5. 5Keep a readable copy and the final XML in your accounting records.

Helpful related pages

Convert a PDF to XRechnungUse this route when you already have a source PDF and need extraction, review, and XML generation.->Validate XRechnung XMLCheck the generated XML before sending it to a recipient or portal.->Understand Leitweg-IDReview how the Leitweg-ID maps to BuyerReference BT-10 for German public-sector invoices.->XRechnung field referenceUse the resource hub for BT/BG fields, standard context, and implementation notes.->Compare ZUGFeRD outputUse the hybrid route when the recipient accepts PDF/A-3 with embedded XML.->

Create XRechnung FAQ

Can I create XRechnung without a PDF?

Yes. This flow is for issuing a new invoice from structured fields. If you already have a PDF invoice, use the PDF to XRechnung converter instead so the source document can be extracted and reviewed.

Is BT-10 always required?

BuyerReference BT-10 is required for XRechnung in this flow. For German public-sector recipients it is usually the Leitweg-ID supplied by the recipient; for other recipients use the buyer reference they require.

Does this replace legal or tax review?

No. The tool helps structure and validate invoice data, but the issuer remains responsible for the business facts, tax treatment, recipient routing and final submission.

Invoice-Converter.comIC

Create XRechnung from Scratch

Validation Results