What is checked
- The schema: UBL 2.1 Invoice or CreditNote, or UN/CEFACT CII D16B, the two syntaxes XRechnung 3.0 allows.
- The EN 16931 rules (1.3.16): totals that add up (BR-CO-15), the VAT breakdown per category, required business terms.
- KoSIT's XRechnung rules (XRechnung 3.0.2, rules 2.6.0): the BR-DE rules, such as the buyer reference that carries the Leitweg-ID (BR-DE-15), the seller's contact (BR-DE-2) and the payment instructions (BR-DE-1), and the BR-DEX rules of the XRechnung Extension.
- The levels of the KoSIT validator's configuration for the scenario the invoice declares (XRechnung, Extension or CVD): a few code list rules are warnings there, and its "information" level shows as a warning.
Each finding names its rule, its line and the element it points at; a rule's page gives the German message in English and says how to fix it.
UBL, CII or ZUGFeRD
XRechnung is the German CIUS of EN 16931: the same invoice content in either syntax, UBL or CII, with the specification identifier (BT-24) urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0. The validator reads it and picks the matching rules, the Extension's too. A ZUGFeRD PDF of the XRECHNUNG profile carries an XRechnung in CII as xrechnung.xml: drop the PDF and the XML is taken out and checked the same way, with the PDF around it. Public authorities take XRechnung through their portals (ZRE, OZG-RE, the federal states' own) or Peppol; under the B2B mandate, businesses can send it to one another too.
When it fails
Fix the first errors first: the business rules run only once the schema check passes, and later findings often follow from earlier ones. A missing or wrong Leitweg-ID is the most common reason a public authority's portal refuses an invoice: the Leitweg-ID check tests its check digits. To write an XRechnung that passes, the e-invoice generator makes one in UBL or CII and checks it before download; the XRechnung examples are valid files to compare against, and the e-invoice viewer shows one as the recipient sees it.
Questions
Is my invoice uploaded?
No. The file is read and checked in your browser, with the same engine and rules as our API. Nothing is sent anywhere.
Is this the KoSIT validator?
No, but it runs the same rules: KoSIT's published XRechnung Schematron and the CEN EN 16931 rules, at the levels of the KoSIT validator configuration. Every week the results are compared with the KoSIT validator on the XRechnung test suite.
Which XRechnung versions are supported?
XRechnung 3.0 (3.0.1 and 3.0.2), the version in force, in UBL and CII, invoices and credit notes, and the XRechnung Extension. An older 2.x invoice is checked against the 3.0 rules, and BR-DE-21 warns about its specification identifier.
What is the difference from a ZUGFeRD invoice?
An XRechnung is XML only; a ZUGFeRD invoice is a PDF with the XML inside. Both are e-invoices under the German mandate. The ZUGFeRD validator checks the PDF as well.
Can I check many invoices at once?
Yes: in the validator, drop a folder or a zip and each document is checked with the profile it names. The API and CLI do the same in a build.
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.
- 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.
- XRechnung examples to download: Example XRechnung and ZUGFeRD invoices to download, one for each common case.
- 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.