About the E-Invoice Validator
Before you send an electronic invoice, you want to know that it will not be rejected. This tool reads a UBL or CII invoice XML file, the formats behind PEPPOL, XRechnung, Factur-X and ZUGFeRD, and runs quick checks based on common rules of the European standard EN 16931 and PEPPOL BIS 3.0. It reports missing required fields, wrong dates and codes, sums that do not add up, VAT amounts that do not match their rate and IBANs that fail the checksum, each with the rule number and a plain explanation. The file is read in your browser and never uploaded. It is a quick check, not the official rule set.
Updated October 2026
How to use the E-Invoice Validator
- 1Press Select XML invoice and choose the invoice file, or paste the XML into the box.
- 2Read the summary: invoice number, seller, buyer, date and amount.
- 3Look at the list of problems and checks. Each has a rule code and a plain explanation.
- 4Fix the problems in the program that created the invoice and check again.
- 5Use the official validator of your country or customer for the final test.
Why validate before sending
A rejected e-invoice means delays and sometimes late-payment problems. Most rejections come from a handful of mistakes: a missing seller identifier, a country written as a full name, a total that is off by a cent, VAT calculated per line instead of per rate, or a missing buyer reference. A quick check at your desk catches these before the invoice leaves.
What is checked
The tool verifies that the main required fields are present, that dates and currency codes are valid, that every line has a quantity, unit, name and net price, that line amounts equal quantity times price, and that totals, VAT breakdown and amount due are consistent. It also tests the IBAN checksum and warns about a missing buyer reference or payment information.
- Required fields: number, date, type code, currency, parties, lines
- Calculations: line sums, VAT per rate, totals, amount due
- Formats: dates, currency and country codes, VAT number shape, IBAN checksum
What is not checked
The XML schema, the full set of schematron rules, code lists beyond the common ones, country-specific rules, attachments, allowances and charges at document level and credit note rules are not part of these quick checks. For a binding result, use the official validator or the service of your access point.
Reading the results
A green message means that none of the quick checks failed. A red message lists the problems, each with a rule code. Yellow items are hints. Fix problems at the source, in the system that makes the invoice, rather than editing the XML by hand, because other parts of the file may depend on the same numbers.
Phone and computer
On a phone, choose the XML file from your files or paste its text. On a computer, you can drop the file or paste it. Results appear immediately and update as you edit the pasted XML.
Good to know
A file that is not well-formed XML is reported first, because nothing else can be checked until it opens. Amounts are compared with a tolerance of one cent, as rounding can differ slightly between systems. Your invoice stays on your device, which matters for customer data. Check the file here before you send it, and fix problems in the source. Use the E-Invoice Creator to build a new invoice, the XML E-Invoice to PDF tool for a readable copy, and the XML Formatter to tidy tags so errors are easier to spot. The IBAN Validator checks the bank account number.
Features
- Reads UBL Invoice and CII CrossIndustryInvoice
- Required fields and format checks
- Sums, VAT and totals cross-checked
- IBAN checksum test
- Rule codes with plain explanations
- Private: nothing leaves your browser
Frequently asked questions
Is this the official validator?
No. It is a quick check of common EN 16931 and PEPPOL rules. The official validators also run schema and schematron tests with many more rules, and each country or network can add its own. Use this to catch the usual mistakes early.
Which files can I check?
UBL 2.1 invoices, as used on PEPPOL and in XRechnung, and CII CrossIndustryInvoice files, as used in Factur-X and ZUGFeRD. Credit notes are not supported. A PDF with embedded XML must be extracted first.
What do the rule codes mean?
Codes like BR-CO-15 are rule numbers from the European standard. BR rules are about required content, and BR-CO rules are about calculations that must add up. The message next to each code explains it in plain words.
My invoice shows problems but my software says it is fine. Why?
Your software may be checking with a different rule set or none at all. A mismatch of sums, a missing country code or a missing seller identifier is a problem for most receivers.
What is the difference between a problem and a check?
A problem is something the standard requires or a sum that does not add up, and a receiver is likely to reject it. A check is a hint, for example that the buyer reference is missing, which only some receivers require.
Is my invoice uploaded?
No. The XML is read and checked in your browser.