What is checked
- XML schema (XSD). Structure, element order and data types, checked against the unmodified schema files that KoSIT uses: UBL 2.1 for UBL invoices and credit notes, UN/CEFACT CII D16B for CII and ZUGFeRD. The proven libxml2 library runs as WebAssembly in your browser to do this.
- Business rules. Do the contents fit together? Whether the totals add up, every line has a unit code, a reverse-charge invoice carries the buyer’s VAT ID, and an XRechnung includes the Leitweg-ID and a seller contact. EN 16931 rules apply to every e-invoice, the BR-DE rules only to XRechnung.
The validator detects the variant itself: UBL or CII, XRechnung, Peppol BIS, or ZUGFeRD with its profile.
Reading the result
The verdict comes first: no errors, warnings only, or a number of errors. Schema errors follow with their line number, then the business rules that failed. Each message gives the rule ID (such as BR-CO-16), the EN 16931 field number (such as BT-115 for the amount due), a plain explanation, the value found in your file where possible, and what to change. Rules that passed are listed, collapsed, at the end.
Common errors
| Rule | What is behind it |
|---|---|
| BR-DE-15 | The buyer reference is missing. For German public buyers it holds the Leitweg-ID; portals reject invoices without it. |
| BR-CL-23 | The unit is written as text, such as “pcs” or “hrs”. Only codes are allowed: C62 or H87 (piece), HUR (hour), DAY (day). |
| BR-CO-15, BR-CO-16 | Rounding differences between net, VAT, gross and amount due, often because the software rounds per line instead of per VAT rate. |
| BR-DE-18 | An early-payment discount written as free text. XRechnung requires the fixed format #SKONTO#TAGE=14#PROZENT=2.00#. |
| BR-CO-09 | A national tax number in the VAT ID field, or a VAT ID without its country prefix. |
| XSD | Elements in the wrong order, or a decimal comma in amounts. The schema needs 410.55, not 410,55. |
Rules covered
190 rules in total, plus the check digits of every IBAN and a warning for profiles without a full EN 16931 data set.
Mandatory content and structure (EN 16931) (57)
BR-01, BR-02, BR-03, BR-04, BR-05, BR-06, BR-07, BR-08, BR-09, BR-10, BR-11, BR-12, BR-13, BR-14, BR-15, BR-16, BR-17, BR-18, BR-19, BR-20, BR-21, BR-22, BR-23, BR-24, BR-25, BR-26, BR-27, BR-28, BR-29, BR-30, BR-31, BR-32, BR-33, BR-36, BR-37, BR-38, BR-41, BR-42, BR-43, BR-44, BR-45, BR-46, BR-47, BR-48, BR-49, BR-51, BR-52, BR-53, BR-54, BR-55, BR-56, BR-57, BR-61, BR-62, BR-63, BR-64, BR-65
Calculation and consistency rules (EN 16931) (15)
BR-CO-03, BR-CO-04, BR-CO-09, BR-CO-10, BR-CO-11, BR-CO-12, BR-CO-13, BR-CO-14, BR-CO-15, BR-CO-16, BR-CO-17, BR-CO-18, BR-CO-19, BR-CO-20, BR-CO-26
VAT categories S, Z, E, AE, K, G, O (60)
BR-AE-01, BR-AE-02, BR-AE-05, BR-AE-06, BR-AE-07, BR-AE-08, BR-AE-09, BR-AE-10, BR-E-01, BR-E-02, BR-E-05, BR-E-06, BR-E-07, BR-E-08, BR-E-09, BR-E-10, BR-G-01, BR-G-02, BR-G-05, BR-G-06, BR-G-07, BR-G-08, BR-G-09, BR-G-10, BR-IC-01, BR-IC-02, BR-IC-05, BR-IC-06, BR-IC-07, BR-IC-08, BR-IC-09, BR-IC-10, BR-IC-11, BR-IC-12, BR-O-01, BR-O-02, BR-O-05, BR-O-06, BR-O-07, BR-O-08, BR-O-09, BR-O-10, BR-O-11, BR-O-12, BR-S-01, BR-S-02, BR-S-05, BR-S-06, BR-S-07, BR-S-08, BR-S-09, BR-S-10, BR-Z-01, BR-Z-02, BR-Z-05, BR-Z-06, BR-Z-07, BR-Z-08, BR-Z-09, BR-Z-10
Code lists (8)
BR-CL-01, BR-CL-03, BR-CL-04, BR-CL-14, BR-CL-16, BR-CL-17, BR-CL-23, BR-CL-25
Decimal places (18)
BR-DEC-01, BR-DEC-02, BR-DEC-05, BR-DEC-06, BR-DEC-09, BR-DEC-10, BR-DEC-11, BR-DEC-12, BR-DEC-13, BR-DEC-14, BR-DEC-16, BR-DEC-17, BR-DEC-18, BR-DEC-19, BR-DEC-20, BR-DEC-23, BR-DEC-24, BR-DEC-27
XRechnung (German CIUS) (32)
BR-DE-1, BR-DE-2, BR-DE-3, BR-DE-4, BR-DE-5, BR-DE-6, BR-DE-7, BR-DE-8, BR-DE-9, BR-DE-10, BR-DE-11, BR-DE-14, BR-DE-15, BR-DE-16, BR-DE-17, BR-DE-18, BR-DE-19, BR-DE-20, BR-DE-21, BR-DE-22, BR-DE-23-a, BR-DE-23-b, BR-DE-24-a, BR-DE-24-b, BR-DE-25-a, BR-DE-25-b, BR-DE-26, BR-DE-27, BR-DE-28, BR-DE-30, BR-DE-31, BR-DE-TMP-32
What it does not do
This is a pre-check, not the official KoSIT validator. The rules are re-implemented in code; no Schematron engine runs in the browser. Not checked are, among others: the remaining EN 16931 rules (such as BR-CO-05 to BR-CO-08 on allowance reasons, some code lists, categories L and M, IGIC and IPSI), the XRechnung extension (BR-DEX) and procurement variant (BR-DE-CVD), Peppol BIS’s extra rules, ZUGFeRD’s profile-specific schemas, the PDF/A-3 wrapper of a ZUGFeRD file, and whether the invoice is correct for tax purposes. A clean result here means the most common reasons for rejection are absent, not that the file meets every rule.
Frequently asked questions
Is this the official KoSIT validator?
No. KoSIT’s official tool is a Java program that runs the complete Schematron rules. This page validates in your browser against the same XML schemas and re-implements the most common EN 16931 and XRechnung rules in its own code. That catches the typical errors, but it is a pre-check. If you need a binding result, for instance in a dispute with a customer, also run the KoSIT validator.
Is my invoice uploaded?
No. Validation runs entirely in your browser. Only program code and the official schema files are fetched from this website; your invoice never leaves your computer. Many online validators send the file to a server instead.
My invoicing software says “valid”, this page shows errors. Who is right?
Look at the rule ID, for example BR-CO-16 or BR-DE-15. Each message names the field and the value from your file, so you can check the finding in the XML. Some programs only check the schema or an older rule version. When in doubt, the KoSIT validator decides.
What is the difference between an error and a warning?
Errors are rules that EN 16931 or XRechnung make mandatory (“shall”). German public-sector portals usually reject invoices with such errors. Warnings are “should” rules or recommendations, such as a missing delivery date; they rarely lead to rejection but are worth fixing.
Can I check ZUGFeRD and Factur-X invoices?
Yes. Drop the PDF and the embedded XML is checked. Whether the PDF itself meets PDF/A-3 is not checked here. The MINIMUM and BASIC WL profiles and ZUGFeRD 1.0 do not carry a full EN 16931 data set; they only get the basic checks and a clear warning.
Which XRechnung version does it check against?
XRechnung 3.0.2, using the rules of KoSIT’s validator configuration of 31 August 2026, with the UBL 2.1 and UN/CEFACT CII D16B schemas. According to KoSIT, XRechnung 3.0 stays valid until at least 31 July 2027; the final XRechnung 4.0 is expected in spring 2027.
I am a supplier outside Germany. Why does my invoice need a Leitweg-ID?
German public buyers route incoming e-invoices by the Leitweg-ID, which goes into the buyer reference (BT-10). XRechnung makes BT-10 mandatory (rule BR-DE-15). Ask your customer for it; it is usually on the purchase order.
Sources
- Validator-Konfiguration XRechnung 3.0.2, Release 2026-08-31 (XSD UBL 2.1 und CII D16B, Schematron EN 16931 und XRechnung)KoSIT auf GitHub, 02.09.2026
- KoSIT Validator (offizielles Prüfwerkzeug, Open Source)KoSIT auf GitHub
- XRechnung – Versionen und BundlesKoSIT / xeinkauf.de
- EN 16931 – Validierungsartefakte (Schematron-Regeln BR-*, BR-CO-*)CEN/TC 434 und Europäische Kommission, GitHub
- Revised European standard on eInvoicing EN 16931-1:2026Europäische Kommission, 30.03.2026
- ZUGFeRD – häufige Fragen (Dateiname, PDF/A-3, Validierung)FeRD
Last reviewed: