XRechnung 3.0 Invoice (UBL)
The German e-invoice in UBL syntax, checked against the UBL 2.1 schema, the EN 16931 rules and the XRechnung rules (BR-DE-*).
About
XRechnung is the German CIUS of EN 16931, required for invoices to the German public sector and one of the formats accepted under the German B2B e-invoicing mandate. KoSIT publishes its rules as Schematron.
The XRechnung rules add the buyer reference that carries the Leitweg-ID (BR-DE-15), seller contact details, payment information and other German requirements on top of EN 16931.
E-invoicing in Germany: the rules in short and how to check an invoice →
Good to know
- Rules run only when the document matches the schema. Documents over 50 MB are checked against the schema only.
- Rule levels follow the KoSIT validator configuration (2026-08-31) for the scenario the document declares (XRechnung, Extension or CVD): a few code list rules are warnings there, a few line rules errors. Its "information" level is shown as a warning.
- The example is from the XRechnung test suite by KoSIT (Apache License 2.0).
Files
14 files · 2.7 MB-
maindoc/UBL-Invoice-2.1.xsd main
-
common/UBL-CommonAggregateComponents-2.1.xsd
-
common/UBL-CommonBasicComponents-2.1.xsd
-
common/UBL-CommonExtensionComponents-2.1.xsd
-
common/UBL-QualifiedDataTypes-2.1.xsd
-
common/UBL-UnqualifiedDataTypes-2.1.xsd
-
common/UBL-ExtensionContentDataType-2.1.xsd
-
common/CCTS_CCT_SchemaModule-2.1.xsd
-
common/UBL-CommonSignatureComponents-2.1.xsd
-
common/UBL-SignatureAggregateComponents-2.1.xsd
-
common/UBL-SignatureBasicComponents-2.1.xsd
-
common/UBL-xmldsig-core-schema-2.1.xsd
-
common/UBL-XAdESv132-2.1.xsd
-
common/UBL-XAdESv141-2.1.xsd
The validator loads all of these with their folder structure, so includes and imports resolve as published.
Business rules
Schematron · run in this orderThe rules run after the schema check, only when the document matches the schema, and in your browser like the schema check (with SaxonJS by Saxonica). Each finding names its rule, such as BR-CO-15, and the line it points at; each rule has a page with what it checks.
Example document
01.02a-INVOICE_ubl.xml · 6.4 KB · passes the schema and the rules
In CI and from code
The same schema by its name, xrechnung-3-ubl, through the API.
npx @xmlvalid/cli validate "**/*.xml" --schema xrechnung-3-ubl
- uses: xmlvalid/validate-action@v1
with:
files: "**/*.xml"
schema: xrechnung-3-ubl
api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
-H "Authorization: Bearer $XMLVALID_API_KEY" \
-F document={{ $schema->example ?? 'document.xml' }} -F schema=xrechnung-3-ubl
Free accounts get 100 API validations a month. On Pro, a URL monitor can check a published document against this schema every hour and email you when it breaks. More CI setups