Which validator for XRechnung and ZUGFeRD fits?
There are many free tools for checking e-invoices. They differ in the rule set they check against, what happens to your file and whether they check more than the format. Here are the criteria, and we say openly what our validator can and cannot do.
How to choose a validator
A validator should check against EN 16931 and the German XRechnung rules (BR-DE). The most reliable option is the official KoSIT validator, which German public administration also uses for incoming invoices.
XRechnung is a pure XML file, ZUGFeRD and Factur-X are PDF files with embedded XML. A useful validator accepts both and extracts the XML from the PDF itself.
Invoices contain bank details and customer data. Check whether the file is stored after validation and where the servers are located.
A validator reports rule identifiers such as BR-DE-15 or BR-CO-25. It helps if every identifier comes with a plain-language explanation, because you need it when talking to the supplier.
A formally valid invoice can still be manipulated. Pure format validators do not compare the bank details. Anyone who pays incoming invoices should have this check as well.
What our validator does
Official KoSIT validator
We check with the KoSIT validator against EN 16931 and the German XRechnung rules, in both the CII and UBL syntax.
XRechnung, ZUGFeRD, Factur-X
XRechnung as an XML file, and ZUGFeRD and Factur-X as a PDF with embedded XML. Each format has its own page: the XRechnung validator and the ZUGFeRD validator.
Three free checks per day
No account and no email address needed. A free account raises the quota and adds bank change detection, an IBAN vault and a check history.
Not stored without an account
When you check without an account, the file is processed only for the check and discarded afterwards. Processing takes place on servers in Germany.
Rules in plain language
In the free account and via the API, the check names the violated rules with identifier and official text. The public check tool only shows the number of violations. The error code reference explains every identifier.
IBAN matching
We compare the IBAN visible in the PDF with the embedded data, verify the check digits and match the IBAN country against the issuer's location. This is no guarantee of authenticity, but pure format validators lack this check.
Want to see it with your own case? We will show you in a free online demo.
What a validator does not do
Valid does not mean genuine
A validator checks structure and rules, not whether the invoice comes from the right sender. Swapped bank details only stand out if they are compared with the embedded data or known supplier data.
Copy instead of original
If a ZUGFeRD PDF is saved again, printed or scanned, it looks unchanged but loses the embedded XML. The check then reports "not an e-invoice". Always check the original file.
The sender fixes errors
Only the issuer can correct formal errors, by issuing a corrected invoice. The validator shows what is missing, it cannot change the invoice.
A PDF sent by email is not an e-invoice
An ordinary PDF without embedded XML is a picture of an invoice. A validator cannot find an e-invoice in it, no matter what the invoice looks like.
Price
Checking in the browser is free three times a day, without an account. A free account raises the quota. Checking incoming invoices via the API costs 2 credits per invoice. Credits start at EUR 9.00 net for 100 credits, they do not expire, and you get 10 free credits to start.
Questions about your case? Write to us and we will reply personally.
Frequently asked questions: e-invoice validator
Which validator is the right one for XRechnung and ZUGFeRD?
One that checks with the official KoSIT validator against EN 16931 and the German XRechnung rules and accepts both formats. For incoming invoices it also matters whether the file is stored and whether the bank details are matched. Our validator meets these points and is free three times a day without an account.
Where can I check a received e-invoice for free?
At sichere-erechnung.de/pruefen, without an account and without an email address. You upload the file and see whether it complies with EN 16931 and whether the visible IBAN matches the embedded data.
How do I recognise a trustworthy online validator?
By the rule set it names (KoSIT validator, EN 16931, BR-DE), a clear statement on storage and server location, and error messages that come with a rule identifier and explanation. If any of this is missing, ask before uploading invoices with bank details.
Is a valid check result enough to pay an invoice?
No. A valid result only means that structure and rules are correct. The format check does not tell you whether the invoice is genuine and the bank details are right. Our IBAN matching detects the most common manipulation, swapped bank details, but does not replace your approval.
Can I integrate the check into my accounting?
Yes, via the POST /v1/check API, for example to check every incoming invoice before it is booked. It costs 2 credits per invoice and stores the result in the check history. Details are in the documentation.
Further reading
Check incoming invoices before you pay
Start for free, 10 transactions included. No credit card.
Get started