What the files are
Our e-invoice generator writes each example in your browser when you press its button, with the code it writes your own invoices with. Each case comes three ways:
- XRechnung UBL: XRechnung 3.0 in UBL 2.1 syntax, an Invoice or, for the credit note, a CreditNote.
- XRechnung CII: the same content in UN/CEFACT Cross Industry Invoice syntax.
- ZUGFeRD PDF: a PDF/A-3 file with the invoice laid out on A4 pages in German, and the CII invoice attached as factur-x.xml in the EN 16931 profile (COMFORT in ZUGFeRD's terms) for the recipient's software.
The XRechnung files carry what KoSIT's rules ask for on top of EN 16931: a buyer reference (a Leitweg-ID here), a seller contact with name, phone and email, an electronic address for each party (email addresses) and the payment details. The companies, VAT IDs and IBANs are made up, with check digits that pass.
What each case shows
- Invoice at 19 % and 7 %: three lines at two rates, so the VAT breakdown (BG-23) has two groups.
- Small business (§ 19 UStG): every line in category E (exempt) with the exemption reason (BT-120) and the seller's tax number (BT-32) in place of a VAT ID, which then also identifies the seller.
- Reverse charge: category AE with the seller's and the buyer's VAT IDs (BT-31, BT-48).
- Intra-community supply: category K with the buyer's VAT ID, the delivery date and the delivery country.
- Export outside the EU: category G, without a VAT ID for the buyer.
- Credit note: type code 381 (BT-3), naming the invoice it corrects (BT-25). In German VAT law that is a Rechnungskorrektur; a Gutschrift is an invoice the buyer issues.
- Advance payment and Skonto: the amount paid in advance (BT-113) and the cash discount in BT-20 as
#SKONTO#TAGE=10#PROZENT=2.00#, the coded form XRechnung asks for. - Discounts and shipping: allowances and a charge on the whole invoice (BG-20, BG-21), each with its VAT category and rate.
- Monthly maintenance: a billing period (BG-14) in place of a delivery date, with a contract and a project reference.
- SEPA direct debit: payment means 59 with the creditor ID (BT-90), the mandate reference (BT-89) and the debited account (BT-91).
- With an attachment and a logo: a timesheet as a PDF inside the invoice (BT-125), and the seller's logo on the PDF, which no e-invoice format has a field for.
Using them
To find what your own invoice does differently, check it in the validator with the XRechnung profile: each finding names its rule, with a page on what it checks. To see an example as its recipient would, open it in the e-invoice viewer. To turn one into an invoice of your own, open the file in the e-invoice generator and change the seller, the buyer and the lines.
Questions
Are these real invoices?
No. The companies, VAT IDs and IBANs are made up, and the invoices are dated October 2026. They are for comparing and testing, not for paying.
Which XRechnung version are they?
XRechnung 3.0 (customization ID urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0), checked with the XRechnung rules 2.6.0 and the EN 16931 rules 1.3.16, as in the KoSIT configuration of 31 August 2026.
UBL or CII: which one do I need?
Either: both are XRechnung with the same data, and public portals and German invoicing software take both. CII is the syntax inside ZUGFeRD, so software that reads ZUGFeRD reads XRechnung CII too.
Does the ZUGFeRD PDF count as an e-invoice?
Yes. The XML inside follows EN 16931, and ZUGFeRD from version 2.0.1 in this profile meets the German VAT rules for an e-invoice. The MINIMUM and BASIC WL profiles do not.
Where are KoSIT's own test files?
In KoSIT's XRechnung test suite on GitHub (itplr-kosit/xrechnung-testsuite), with many technical cases. The validator's XRechnung profiles load one of them as their example.
Other tools
- XML formatter: Pretty-print or minify XML, keeping text, CDATA and comments as written.
- XML viewer: Read a document as a tree you can fold, search and copy XPaths from.
- XPath tester: Evaluate XPath 3.1 against a document and see each match with its line.
- XSD generator: Infer an XML Schema from sample documents, checked against them.
- XML from XSD: Generate a sample XML document from a schema, validated against it.
- XSLT transformer: Run XSLT 1.0, 2.0 or 3.0 on a document and see the result, the messages and the files it writes.
- XML diff: Compare two XML documents as trees: changed, added and removed elements, attributes and text.
- XML to JSON converter: Convert XML to JSON, with arrays where an element repeats or wherever its XSD allows.
- JSON to XML converter: Convert JSON to XML: @keys become attributes, arrays repeated elements.
- XML to CSV converter: Turn a repeating element into CSV rows: invoice lines, products, records.
- XML to PDF converter: Save any XML as a PDF to read, print or attach: indented, coloured, with line numbers.
- E-invoice viewer: Read an XRechnung, ZUGFeRD, Factur-X or Peppol invoice as a document, and save it as a PDF.
- ZUGFeRD validator: Check a ZUGFeRD or Factur-X PDF: the XML inside against its profile's rules, and the PDF around it.
- XRechnung validator: Check an XRechnung in UBL or CII against EN 16931 and KoSIT's XRechnung rules before you send it.
- UBL validator: Check a UBL invoice, order or any other UBL 2.1 document against its OASIS schema, and the business rules of the profile it names.
- Peppol validator: Check a Peppol BIS Billing 3.0 or PINT invoice against the OpenPeppol rules before your access point sends it.
- P7M viewer: open a .p7m file: Open a signed .p7m file: the PDF, invoice or document inside it, and who signed it.
- E-invoicing mandate in Germany: do I have to?: Find out whether your invoices in Germany must be e-invoices in 2026, 2027 and from 2028.
- Factur-X examples: Example Factur-X invoices of every profile and of the French reform, as XML and as PDF.
- Leitweg-ID check: Check the form and the check digits of a Leitweg-ID, the address of a German public buyer.
- Peppol lookup: Check whether a company is registered in Peppol, under which ID, and which invoices it can receive.
- XML validator: check a document against XSD, DTD, RelaxNG or Schematron, up to 1 GB.