XRechnung validator (KoSIT rules)
Check an XRechnung 3.0 invoice the way German public buyers do, with KoSIT's official validator configuration.
- Version 1
- Checked against 3 published cases
Check an invoice now
Free, no sign-up, 5 invoices a day. Files up to 900 KB. The file is checked in memory and is not stored.
What it checks
Uses KoSIT's validator configuration for XRechnung unchanged: its scenarios choose the rules from the document's type and specification ID, then the UBL or CII schema, the EN 16931 rules and the XRechnung rules (BR-DE-…) run, with KoSIT's custom levels. The decision is KoSIT's: valid means no error.
- Checked against KoSIT's XRechnung test suite: every published test invoice is accepted.
Rules used
- KoSIT validator configuration for XRechnung 3.0.2, version 2026-08-31
A check shows whether the invoice passes the official rule sets listed, at the versions listed. It is not legal or tax advice, and passing does not promise that a tax authority or buyer will accept the invoice. See the terms.
Use it from your code
jq -Rs '{xml: .}' xrechnung-01.01a-invoice-ubl.xml |
curl https://api.curatedapi.com/v1/validate/einvoice/xrechnung \
-H "Authorization: Bearer $CURATEDAPI_KEY" \
-H "Content-Type: application/json" \
--data-binary @-
{
"validator": "einvoice/xrechnung@1",
"result": {
"valid": true,
"scenario": "EN16931 XRechnung (UBL Invoice)",
"document_type": "UBL Invoice",
"specification_id": "urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0",
"errors": 0,
"warnings": 0,
"notices": 1,
"error_rules": [],
"checks": [
{
"check": "XML syntax",
"passed": true
},
{
"check": "XML Schema for UBL 2.1 Invoice",
"passed": true
},
{
"check": "Schematron rules for EN16931 (UBL)",
"passed": true
},
{
"check": "Schematron rules for Invoice - CIUS XRechnung (UBL)",
"passed": true
}
],
"messages": [
{
"rule": "BR-DE-TMP-32",
"level": "information",
"message": "[BR-DE-TMP-32] Eine Rechnung sollte zur Angabe des Liefer-/Leistungsdatums entweder BT-72 \"Actual delivery date\", BG-14 \"Invoicing period\" oder in jeder Rechnungsposition BG-26 \"Invoice line period\" enthalten.",
"check": "Schematron rules for Invoice - CIUS XRechnung (UBL)",
"location": "/Q{urn:oasis:names:specification:ubl:schema:xsd:Invoice-2}Invoice[1]"
}
],
"messages_truncated": false
},
"rules": [
{
"name": "KoSIT validator configuration for XRechnung 3.0.2",
"version": "2026-08-31",
"url": "https://github.com/itplr-kosit/validator-configuration-xrechnung/releases/download/v2026-08-31/xrechnung-3.0.2-validator-configuration-2026-08-31.zip"
}
]
}
MCP tool validate_einvoice_xrechnung at https://mcp.curatedapi.com.
Inputs, results and errors in the API reference.
Other validators
Check every invoice before it is sent
Run the same check from your invoicing app or ERP, one POST per invoice, before the file goes to the customer or the Peppol network. The answer lists every rule it breaks.
Free for up to 200 invoices checked a month. 10,000 invoices checked a month cost $9.00 on the Starter plan.