LuaBill · Documentation

Create an XRechnung

XRechnung is structured invoice data. LuaBill generates CII XML and a separate PDF view for people to read.

Complete the structured fields

Select XRechnung under Files and output for an invoice, credit note or cancellation invoice. Use structured plain-text company names, postal addresses and item descriptions. Supply actual invoice numbers, dates, quantities, unit codes, currency, tax categories and the VAT treatment that applies.

XRechnung needs the buyer reference, seller contact information and electronic addresses with their scheme identifiers. For public-sector buyers, use the Leitweg-ID or reference supplied by the recipient. An ordinary purchase order number is not automatically a valid Leitweg-ID. Tax identifiers and exemption reasons depend on the selected VAT scenario.

Fill in the invoice form →

Generate and read the validation result

Prepare LuaLaTeX and Java 17+, save the project and create PDF/XML. LuaBill validates the XML and publishes result files only after the required stages succeed. A generation error leaves diagnostic logs available instead of presenting the failed attempt as a valid new invoice.

LuaBill 0.1.31 includes Mustang 2.26.0 with a verified local overlay for EN 16931 CII 1.3.17 and XRechnung Schematron 2.6.0, for specification 3.0.2. The original JAR and official rule files remain unchanged. Installed versions are visible in Help and recorded with validation output; a newer technical release alone does not establish a new legal obligation.

  • .validation.xml: the Mustang validation report.
  • .validation-rules.xml: the additional EN 16931 rule report.
  • .validation-info.json: rule versions, hashes and validation-stage information.

Send XML and retain the evidence

Send the generated .xml through the channel accepted by the recipient. The separate PDF is a visual view and does not turn into an XRechnung simply because it accompanies the XML.

Shared document notes are included in the XML; supported LaTeX in those notes remains source text. Introductory text, imported PDF-only comments, stamp and signature images belong to the visual output. Inspect the data your recipient will actually receive and retain the issued files with their validation reports.

Compare with ZUGFeRD →Resolve validation errors →
← Back to documentation