How to use
Please note first: this tool checks e-invoice XML exchanged with European customers (EN 16931, XRechnung, Factur-X, Peppol). Korea’s electronic tax invoice (Hometax and National Tax Service transmission) is a different system and cannot be checked here. And it does not replace official validators such as KoSIT. It verifies only the rules described below, so a file can pass here and still be rejected by the recipient’s system. This is not legal or tax advice.
- Paste the invoice XML into the box or load it with Open an XML file. UBL Invoice, UBL CreditNote and CII CrossIndustryInvoice are read.
- Results appear as soon as you paste. Load a valid sample and Load a sample with errors show you what the output looks like.
- In the results table read the rule number, the message and the location in the XML, then fix the file. Even with zero errors, read the “Not checked” section below.
- To build an invoice from scratch use the E-Invoice Creator, which runs these same rules right after generation.
Rules that are checked
Rule ids and criteria were transcribed from the Schematron of the European Commission’s EN16931 validation artefacts 1.3.17 and the KoSIT XRechnung validator configuration 3.0.2. Expand Rules checked in the tool for the full list.
| Area | Rules | What is verified |
|---|---|---|
| Mandatory items | BR-01 to BR-16, BR-CO-18 | Specification id, number, issue date, type code, currency, seller and buyer name, address and country, four totals, at least one line and one VAT breakdown |
| Lines | BR-21 to BR-28, BR-CO-04 | Line id, quantity, unit, net amount, item name, price (not negative), line VAT category |
| Totals | BR-CO-10 to BR-CO-16 | Sum of lines = BT-106, BT-109 = BT-106 − BT-107 + BT-108, BT-112 = BT-109 + BT-110, BT-115 = BT-112 − BT-113 + BT-114 |
| VAT amounts | BR-CO-17, BR-S-08, BR-S-09 | Breakdown tax = taxable × rate ÷ 100; taxable = lines + charges − allowances of the same category and rate |
| Categories | BR-S, Z, E, AE, IC, G, O, IG, IP | Rate per category, exemption reason, seller and buyer VAT ids, breakdown present |
| Codes | BR-CL-01, 04, 06, 14, 16, 17, 22, 23, 25 | Type, currency, country, payment means, VAT category, VATEX, unit and electronic address scheme |
| Formats | DATE, CURRENCY, NUM, BR-DEC | Date format, amount currency attribute, number format, 2 decimals |
| XRechnung | BR-DE-1 to 11, 14 to 17, 19, 21, 27, 28 | Payment instructions, seller contact, city and post code, buyer reference, type code limit, IBAN check digits |
| Peppol | R001, R005, R008, R010, R020, R120 | BT-23, accounting currency, no empty elements, mandatory electronic addresses, line amount ≈ quantity × price |
XRechnung rules apply only when the CustomizationID is an XRechnung identifier; for an unknown identifier the tool says that only base EN 16931 rules were checked. Profiles without lines and VAT breakdown, such as Factur-X MINIMUM and BASIC WL, skip the rules that do not apply.
VAT tolerance
The official rules tolerate a difference below 1.00 for the tax amount (BR-CO-17, BR-S-09) and for the standard-rate taxable amount (BR-S-08). In 1.3.17 the UBL rule rejects a difference of exactly 1.00 while the CII rule accepts it. This tool follows the same criterion but shows a warning whenever the tax differs from the exact value, because other validators can be stricter.
| Case | Result |
|---|---|
| 1,000.00 × 25% = 250.00, tax 250.00 | pass |
| same, tax 250.99 | pass (warning possible) |
| same, tax 251.00 | BR-CO-17 error in UBL, warning in CII |
| same, tax 252.00 | error in both syntaxes |
Common errors and their causes
| Rule | Usual cause | Fix |
|---|---|---|
| BR-CO-15 | Total with VAT differs from total without VAT plus tax, e.g. 1,000.00 + 190.00 but 1,200.00 | Set the total with VAT to 1,190.00 |
| BR-CO-13, 14 | A total was edited by hand while lines and tax stayed | Re-add line amounts and breakdown taxes |
| BR-S-08 | A rate group’s taxable amount differs from the sum of that rate’s lines | Regroup lines by category and rate and recompute |
| BR-E-10, BR-AE-10 | Exempt or reverse charge without a reason | Add reason text (BT-120) or a VATEX code (BT-121) |
| BR-DE-15 | No buyer reference (Leitweg-ID etc.) | Fill BT-10 |
| BR-DE-2, 5, 6, 7 | Seller contact name, phone or email is missing | Fill BG-6 |
| PEPPOL-EN16931-R001 | No business process id (BT-23) | urn:fdc:peppol.eu:2017:poacc:billing:01:1.0 |
| BR-CL-23 | A word such as “pcs” used as the unit code | A UN/ECE Rec. 20 code (C62, H87, HUR …) |
| BR-61 | Credit transfer (30, 58) without an account | Enter the IBAN in BT-84 |
Not checked
This tool does not verify the following. Use an official validator before you submit anything.
- XML Schema (XSD) validation and syntax rules (UBL-SR, UBL-CR, CII-SR …)
- Payee and tax representative details (BR-17 to BR-20), attachments, item attributes and classifications, preceding invoice references
- Reason code/text consistency (BR-CO-05 to 08), line-level allowances and charges, some identifier scheme lists
- XRechnung Skonto text (BR-DE-18), direct debit and card payment details (BR-DE-20, 23 to 25, 30, 31), extension and CVD rules
- Most Peppol rules, per-profile Factur-X XSDs, PDF/A-3 conformance and national extra rules
Frequently asked questions
If a file passes here, will the KoSIT validator pass it too?
That cannot be guaranteed. Only some rules are implemented and XSD validation is not run, so the official validator can still report errors. Conversely, an error here is usually rejected by the official validator under the same rule.
Can it check a Korean electronic tax invoice XML?
No. The National Tax Service’s standard XML has a different structure and is reported as an unsupported document.
What is the difference between an error and a warning?
An error is a violation that the official rules treat as fatal. A warning is something the official rules allow but that differs from the exact value, or a recommendation. A note describes the scope of the check.
Is it fine if the XML contains personal data?
The XML is processed in your browser and is not sent to a server. Even so, avoid pasting real transaction data on a shared computer.
What if the file is big?
Files up to 5 MB are checked. A larger input shows a message.
Related tools
The XML Validator checks the syntax of ordinary XML against an XSD and the XML Formatter lays out long XML for reading. To attach the XML to a PDF use PDF to Factur-X E-Invoice. The XML you enter is processed in your browser and never sent to a server.