1. Home
  2. Documents
  3. E-Invoice Validator (EN 16931)

E-Invoice Validator (EN 16931)

Check pasted XRechnung or Factur-X XML rule by rule, with the skipped rules listed.

Runs in your browser · No upload
Checks European (German, French …) e-invoices: EN 16931, XRechnung, Factur-X and Peppol. This is not Korea’s electronic tax invoice system (Hometax) and cannot check those.
This check does not replace official validators such as KoSIT. It covers only part of the rules listed below, so a file can pass here and still be rejected by the recipient. Not legal or tax advice.
No errors in the rules checked. This does not mean it passes an official validator.

Document summary

Syntax
CII (CrossIndustryInvoice)
Profile
XRechnung
Number
RE-2026-0042
Type code
380
Currency
EUR
Lines
3
VAT breakdowns
2
Total without VAT
1239.80
Total VAT
229.59
Total with VAT
1469.39
Amount due
1469.39

Findings

Findings
LevelRuleMessageWhere
NotePROFILEAn XRechnung identifier was found, so the BR-DE rules were checked as well.
Rules checked

These rules are implemented. Rule ids and criteria were transcribed from the Schematron of the EN 16931 validation artefacts (1.3.17) and the XRechnung validator configuration (3.0.2).

Mandatory items (EN 16931 BR-01 to BR-16, BR-CO-18)
  • BR-01~05 CustomizationID, number, issue date, type code, currency
  • BR-06~11 Seller and buyer name, address and country code
  • BR-12~15 Presence of totals BT-106, 109, 112 and 115
  • BR-16, BR-CO-18 At least one line and one VAT breakdown
  • BR-21~28, BR-CO-04 Line id, quantity, unit, net amount, item name, price (not negative), line VAT category
  • BR-31~38, BR-45~49 Document-level allowance/charge amount, category, reason; VAT breakdown fields; payment means code
Totals and VAT arithmetic (BR-CO-10 to BR-CO-17)
  • BR-CO-10~13 BT-106 = sum of lines, BT-107/108 = allowance/charge sums, BT-109 = BT-106 − BT-107 + BT-108
  • BR-CO-14, 15 BT-110 = sum of breakdown taxes, BT-112 = BT-109 + BT-110
  • BR-CO-16 BT-115 = BT-112 − BT-113 + BT-114
  • BR-CO-17 Breakdown tax = taxable × rate ÷ 100 (differences below 1.00 are tolerated like the official rule, with a warning)
  • BR-DEC-* Amounts have at most 2 decimals
VAT categories (BR-S, Z, E, AE, IC, G, O, IG, IP)
  • -01 A VAT breakdown exists for each used category (exactly one for non-S)
  • -02, -03, -04 Seller/buyer VAT identifiers required per category for lines, allowances and charges (forbidden for O)
  • -05, -06, -07 Line/allowance/charge rate: S above 0, Z/E/AE/K/G equal 0, O no rate
  • -08, -09 Breakdown taxable = lines + charges − allowances of the same category and rate (1.00 tolerance for S); zero tax for exempt types
  • -10 Exemption reason: required for E/AE/K/G/O, forbidden for S/Z
  • BR-IC-11, 12 Delivery date (or period) and deliver-to country for category K
  • BR-O-11~14 Category O cannot be mixed with other categories
Code lists and formats (BR-CL, BR-CO)
  • BR-CL-01, 04, 05, 06, 14, 15 Type, currency, country and VAT point codes
  • BR-CL-16, 17, 18, 22, 23, 25 Payment means, VAT category, VATEX, unit codes, electronic address scheme
  • BR-62, BR-63 Electronic addresses carry a scheme identifier
  • BR-CO-03, 09, 19, 26, BR-29, BR-53, BR-57, BR-61 VAT point exclusivity, VAT id prefix, period fields, seller identifier, period order, accounting currency, deliver-to country, account id
  • DATE, CURRENCY, NUM Date format and calendar validity, currency attribute match, number format (checks without a rule number)
XRechnung 3.0 extra rules (only when the CustomizationID is XRechnung)
  • BR-DE-1~11, 14~17 Payment instructions, seller contact (name, phone, email), city and post code, buyer reference, type code limit
  • BR-DE-19, 21, 27, 28 IBAN check digits for SEPA, XRechnung 3.0 identifier, phone and email format
  • PEPPOL-EN16931-R001, R005, R008, R010, R020, R120 Process id (BT-23), accounting currency, no empty elements, mandatory electronic addresses, line amount ≈ quantity × price (warning)
Not checked

The items below are not verified by this tool. Use an official validator before you submit anything.

  • XML Schema (XSD) validation: element order and the full syntax structure
  • Syntax rules UBL-SR-*, UBL-CR-*, UBL-DT-*, CII-SR-*, CII-DT-*
  • BR-17 to BR-20 (payee and tax representative details), BR-30, BR-35, BR-39 to BR-44, BR-50 and BR-51 and other optional-group details
  • BR-CO-05 to BR-CO-08 and BR-CO-20 to BR-CO-24 (reason code/text consistency, line-level allowances and charges)
  • Reason-code lists BR-CL-19/20 and identifier-scheme lists BR-CL-10/11/21/26
  • Attachments, item attributes and classifications (BR-52, BR-54, BR-64, BR-65 …), preceding invoice references (BR-55, BR-DE-26)
  • XRechnung BR-DE-18 (Skonto text), BR-DE-20, 22, 23, 24, 25, 30, 31, BR-DEX-*, CVD and extension rules
  • Most Peppol BIS rules (only R001, R005, R008, R010, R020 and R120 are read). Use a Peppol validator for Peppol delivery
  • Factur-X/ZUGFeRD per-profile XSDs (MINIMUM and BASIC WL apply only part of the BR rules), PDF/A-3 conformance and the PDF attachment structure
  • National extra rules (Italy SDI, France Chorus Pro, Poland KSeF …) and tax-law judgement

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.

  1. Paste the invoice XML into the box or load it with Open an XML file. UBL Invoice, UBL CreditNote and CII CrossIndustryInvoice are read.
  2. Results appear as soon as you paste. Load a valid sample and Load a sample with errors show you what the output looks like.
  3. 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.
  4. 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.

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.

Can't find the tool you need?

Tell us what you want to do. We build the most requested tools first.