e-Rechnung Inbox
Start for free
Validate XRechnung

Validate XRechnung and read it – instead of XML guesswork.

The public XRechnung validator checks uploaded XRechnung files (UBL or CII) and ZUGFeRD/Factur-X invoices in the EN 16931 profile with the KoSIT validator against the EN 16931 and XRechnung rules. The validator's XRechnung configuration does not cover other ZUGFeRD profiles such as BASIC or EXTENDED; for those we only show our pre-check. For errors you see what is wrong and what to ask the supplier — with a plain-language explanation for selected rules, otherwise with the validator's original message. The file is processed for this one check only and is not stored. The tool also shows the invoice content in readable form: seller, line items, amounts and bank details.

Updated:

The file is processed for this check only and is not stored.

Checked with the KoSIT validator

The uploaded e-invoice is checked with the KoSIT validator in its XRechnung configuration: XML schema, EN 16931 business rules and national XRechnung rules. It covers XRechnung and the EN 16931 profile, also as ZUGFeRD/Factur-X.

Sum and tax logic

Among other things, the EN 16931 business rules check whether the total equals net plus VAT and whether the tax amount matches the taxable amount and rate.

Plain-language explanations

For selected rules such as BR-CO-15 we explain what is wrong and what to ask the supplier. For all other rules we show the validator's original message.

Honest status

Valid, with notes, invalid or not an e-invoice. If the validator cannot be reached right now or does not cover the profile, we say so instead of showing an unchecked “valid” or “invalid”.

What is checked

  • Format detection: XRechnung (UBL or CII) or ZUGFeRD/Factur-X with embedded XML

  • Pre-check by e-Rechnung Inbox: readable XML, supported XRechnung profile identifier and typical structural errors in tax and payment data

  • KoSIT validator (XRechnung configuration) for XRechnung and the EN 16931 profile: XML schema, EN 16931 business rules (BR-…) and national XRechnung rules (BR-DE-…)

  • Other profiles (e.g. ZUGFeRD BASIC or EXTENDED): pre-check only, no result from the KoSIT validator

  • Result with rule identifier and original message, with a plain-language explanation for selected rules

  • ZUGFeRD/Factur-X PDF: comparison of invoice number, gross amount and payment IBAN between the visible PDF and the embedded XML, shown as a note; the XML part is what counts

Common questions about XRechnung validation

What does the public XRechnung validator check?
It detects the format and checks XRechnung and e-invoices in the EN 16931 profile with the KoSIT validator against the XML schema, the EN 16931 business rules and the XRechnung rules. The result is valid, with notes, invalid or not an e-invoice — or “check not possible right now” if the validator does not respond, and “profile not covered by the KoSIT validator” if its XRechnung configuration does not check the profile (for example ZUGFeRD BASIC or EXTENDED).
Is the uploaded file stored?
No. The file is processed for this one check only and is sent to our own checking services for it (the KoSIT validator, plus an isolated PDF environment for PDFs). It is not saved in a database or file storage and is discarded after the check.
Can I also validate a ZUGFeRD PDF?
Yes. The validator accepts XML and PDF files, detects whether they contain a structured e-invoice and checks the contained XML with the KoSIT validator if it uses the EN 16931 profile. For other ZUGFeRD profiles such as BASIC or EXTENDED the validator's XRechnung configuration has no test scenario; we then show only our pre-check.
Does the tool notice when the PDF and the XML of a ZUGFeRD invoice differ?
It compares three values: for ZUGFeRD/Factur-X PDFs the tool checks the invoice number, gross amount and payment IBAN in the visible PDF against the embedded XML. It detects a difference when the value in the PDF sits next to a usual label (such as "Rechnungsnummer", "Gesamtbetrag" or "IBAN"); otherwise it shows "not found in the PDF" or "Not checkable". For direct debits the IBAN is not compared. Scanned PDFs without readable text cannot be checked. A difference is a note, not a legal assessment: the structured XML part is what counts for the e-invoice, and the supplier should correct a PDF that differs. If the IBAN differs, only pay after checking with the supplier on a phone number you already know.
Does the check replace my own review of the invoice?
No. The technical check supports, but does not replace, your own review of the invoice.

Receive invoices regularly?

Use a dedicated invoice inbox to receive, check and archive invoices and prepare DATEV CSV exports. The file checked here is not transferred automatically.

This website uses cookies to improve your experience and analyze traffic. You can decline individual categories at any time. Privacy Policy