Check any XRechnung 3.x e-invoice against the official KOSIT schematron — both UBL and CII syntax variants supported. Free, no signup, instant results with the exact rule ID (BR-DE-*, CII-DE-*, EN 16931) for every error.
Drag and drop or pick the XML file — either UBL (Invoice / CreditNote) or CII (CrossIndustryInvoice). The validator auto-detects the syntax from the root element and CustomizationID URN.
2
Run EN 16931 + XRechnung 3.x rules
The validator runs the underlying EN 16931 European norm followed by all XRechnung-specific rules (BR-DE-*, CII-DE-*, profile constraints) using the official KOSIT schematron release.
3
Read the detailed report
Errors and warnings come back with the exact KOSIT rule ID, the XPath location in the document, and a plain-English description, so you know exactly what to fix and where.
What the XRechnung validator checks
EN 16931 European norm
Full EN 16931 ruleset: mandatory fields (BT-*), business rules (BR-*), calculation chain (BR-CO-*), VAT category logic (BR-S-*, BR-Z-*, BR-E-*, BR-AE-*, BR-K-*, BR-G-*, BR-O-*) and decimal-precision rules (BR-DEC-*).
XRechnung-specific rules
All BR-DE-* (UBL) and CII-DE-* (CII) constraints required by German federal and state public-sector buyers. Includes mandatory Leitweg-ID (BR-DE-1), valid German VAT identifiers, banking details for SEPA, and the German- specific date and currency formats.
UBL and CII syntax both supported
UBL XRechnung (used by PEPPOL access points and modern e-invoicing software) and CII XRechnung (UN/CEFACT Cross Industry Invoice, used by SAP Document Compliance, DATEV and ZUGFeRD tooling) are both detected and routed to the right pipeline automatically.
XSD schema validation (UBL)
UBL 2.1 schema-level checks catch structural errors before the business rules ever run — wrong element order, missing required types, namespace mistakes, invalid enumeration values from the official UBL code lists.
Why XRechnung validation matters
Since 27 November 2020, every supplier invoicing a German federal public-sector buyer must send the invoice as XRechnung. Most German federal states extended the same requirement to state and municipal contracts over the following years. Submitting a non-compliant invoice through ZRE (Zentrale Rechnungseingangs- plattform des Bundes), OZG-RE or any state portal results in immediate rejection — no human review — and the payment clock does not start until you resubmit a passing invoice.
The aiDoks XRechnung validator uses the same official schematron files distributed by KOSIT (Koordinierungsstelle für IT-Standards) that the government portals use. If aiDoks says "valid", your invoice passes at the portal. If aiDoks reports errors, every rule comes with the exact ID (e.g. BR-DE-15 for the Leitweg-ID, BR-CO-13 for tax-total mismatch) so the next iteration is fast.
Common XRechnung validation errors
BR-DE-1 — The Buyer reference (Leitweg-ID) is missing. German federal/state buyers always send a Leitweg-ID with the order — it must be repeated in the invoice's cbc:BuyerReference (UBL) or ram:BuyerReference (CII).
BR-DE-15 — Buyer contact information is incomplete. XRechnung requires either an electronic address or a postal address — most validators require both.
BR-DE-21 — Specification identifier missing or wrong. The CustomizationID must be urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0.
BR-CO-15 — Total payable amount mismatch. Sum of line totals + charges - allowances must equal the payable amount, rounded to 2 decimal places.
BR-S-08 — Standard-rated VAT but rate is missing. Add the correct VAT rate to the relevant cac:TaxCategory / ram:CategoryTradeTax element.
Beyond XRechnung: PEPPOL, Factur-X, EN 16931 and more
The aiDoks validator is a single tool for every major European e-invoice format. Upload a PEPPOL BIS 3.0 invoice, a Factur-X / ZUGFeRD PDF, a plain EN 16931 CII document or an Estonian e-arve XML and the tool auto-detects the format and applies the right validation pipeline. Useful if you exchange invoices across multiple EU markets or operate in both PEPPOL and XRechnung corridors.
XRechnung validator: FAQ
Mis on XRechnung ja kes peab seda kasutama?
XRechnung on saksa CIUS (Core Invoice Usage Specification) standardile EN 16931. Alates 27. novembrist 2020 peavad kõik Saksa föderaalse avaliku sektori tarnijad saatma arveid XRechnung-vormingus; paljud Saksa liidumaad ja omavalitsused nõuavad seda ka osariigi ja kohaliku tasandi hangetes. Validaator kontrollib nii UBL- kui CII-süntaksit uusimate XRechnung 3.x reeglite suhtes — sama reeglikomplekt, mida kasutab ametlik KOSITi validaator.
Mida XRechnung-validaator kontrollib?
Käivitatakse järjest kaks reeglikihti: aluseks olev Euroopa norm EN 16931 (BR-CO-*, BR-S-*, BR-DEC-* jt) ja seejärel XRechnung-spetsiifilised reeglid (BR-DE-*, CII-DE-* ja profiilipiirangud). XSD-skeemi kontroll toimub UBL-arvete puhul, täielik Schematron-valideerimine toimub nii UBL kui CII puhul. Vead tagastatakse täpse KOSITi reegli ID ja arusaadava kirjeldusega.
Kas validaator toetab nii UBL- kui CII-XRechnung?
Jah. Toetatud on nii UBL-XRechnung (kasutavad PEPPOL pääsupunktid ja moodne e-arvete tarkvara) kui ka CII-XRechnung (UN/CEFACT Cross Industry Invoice, kasutavad SAP Document Compliance, DATEV ja ZUGFeRD/Factur-X tööriistad). Süntaks tuvastatakse automaatselt.
Kas XRechnung-validaator on tasuta ja kas mu arve andmed salvestatakse?
Validaator on tasuta ja ei nõua kontot. Teie arve-XML saadetakse töötlemiseks aiDoksile, valideeritakse mälus ja seda ei säilitata pärast vastust. Me ei logi ega salvesta arvete sisu.
Kuidas erineb see ametlikust KOSITi validaatorist?
aiDoksi validaator kasutab samu ametlikke XRechnung-Schematron-faile, mida levitab KOSIT — reeglikate on identne. Erinevus: moodne veebiliides saksa/inglise/prantsuse/eesti/läti/leedu/hispaania keeles, lohistamine-ja-kukutamine üleslaadimine, kohesed tulemused, automaatne vormingu tuvastamine ja üks tööriist kõigile vormingutele.
Millist XRechnungi versiooni toetatakse?
XRechnung 3.x (praegune põhiversioon). Validaator tarnitakse uusima stabiilse KOSITi Schematroni väljalaskega ja seda uuendatakse iga uue KOSITi versiooni avaldamisega.