ZUGFeRD ToolsZUGFeRD Tools

XRechnung validator — validate XRechnung XML online

Upload an XRechnung XML file: the XRechnung validator checks well-formedness, the EN 16931 core rules and the BR-DE rules — XSD schema validation runs for CII syntax, while for UBL files this layer is skipped and shown as such. Free, no sign-up, as a pre-check.

By the editorial team ZUGFeRD Tools

  • XRechnung 3.0.2 · Bundle 2026-08-31
  • KoSIT validator reference: 1.6.3
  • CII: XSD + rules · UBL: rules without XSD
  • Pre-check — not a full KoSIT validator
  • Nothing is stored
ZUGFeRD version (FeRD, 2026-08-04)
2.5.2ZUGFeRD version (FeRD, 2026-08-04)
XRechnung, bundle 2026-08-31
3.0.2XRechnung, bundle 2026-08-31
ZUGFeRD profiles
5ZUGFeRD profiles
syntaxes: UBL 2.1 & CII
2syntaxes: UBL 2.1 & CII
EN 16931 rules checked
24EN 16931 rules checked
all tools, no sign-up
€0all tools, no sign-up

Drop your XRechnung XML here

or choose a file — .xml, max 1 MB

1.0 MB max · Verarbeitung ohne dauerhafte Speicherung

XML · max. 1 MB · UBL 2.1 und UN/CEFACT CII

What does the XRechnung validator do?

The XRechnung validator takes your XML file apart before anyone else does. The file is parsed safely first — with active XXE protection and no DTD or entity resolution. The XRechnung validator then detects the syntax: OASIS UBL 2.1 (Invoice) or UN/CEFACT CII (CrossIndustryInvoice). Both syntaxes are allowed in the XRechnung CIUS.

Next, the XRechnung validator reads the CustomizationID or GuidelineID to determine whether the file claims the XRechnung 3.0 CIUS. The validation layers then run in sequence: well-formedness, the XSD schema (for CII against the official schema via libxml2), the EN 16931 business rules with full arithmetic, and finally the BR-DE rules of the German CIUS — first of all BR-DE-15, the Leitweg-ID (BT-10), which is mandatory in B2G traffic.

Every result states which layers were actually executed. For UBL files the honest note applies: well-formedness and rules run in full, while the XSD layer is only available for CII in this build and is marked as skipped.

The XRechnung validator in four steps

  • Upload the XML: drop the XRechnung as .xml via drag & drop (max. 1 MB).
  • Validate: syntax detection, schema, EN 16931 and BR-DE rules run automatically.
  • Read the result: version, syntax, profile and every layer appear with status and rule coverage.
  • Fix errors: problems such as a missing Leitweg-ID (BR-DE-15) show rule ID and BT field — copyable for the sender.

Why validate an XRechnung? Because authorities do

As of 2026-09-29 — XRechnung 3.0.2 with bundle 2026-08-31 is current; XRechnung 4.0 is a pre-release and not the active standard. Source: xeinkauf.de.

XRechnung is the format for invoices to German federal authorities and, increasingly, states and municipalities. Files submitted through portals such as ZRE (Zentrales Rechnungseingangsportal) or OZG-RE pass the KoSIT validation — with reference validator 1.6.3 and the technical bundle from 2026-08-31. A file that fails there is rejected.

That is exactly why the XRechnung validator pays off before submission: it finds the most common rejection reasons up front — a missing Leitweg-ID, a wrong CustomizationID, totals that do not add up, or EN 16931 rule violations — saving you the round trip through the authority. Every XRechnung you validate here is one round trip you may not need.

The XRechnung validator is deliberately transparent about its rule coverage: it checks a curated subset of the EN 16931 core rules and BR-DE rules. For formal approval in a B2G process, validation with the official KoSIT validator remains authoritative. Until then, the XRechnung validator catches the errors that cause most rejections.

The XRechnung validator: layers in detail

Well-formedness and XXE protection

The XRechnung validator rejects DTD and entity declarations outright and parses the file without network access — a deliberate defence against XXE attacks and billion-laughs resource exhaustion.

XSD schema and EN 16931 rules

CII instances are checked against the official schema; on both syntaxes the EN 16931 core rules then run: mandatory fields, invoice number, line arithmetic, totals and the VAT breakdown with cent-level tolerance.

BR-DE rules of the German CIUS

The BR-DE subset focuses on BR-DE-15 (Leitweg-ID/BT-10 present and well-formed) and BR-DE-2 (seller VAT ID or tax number). The result names the rule coverage explicitly — no claims about checks that did not happen.

XRechnung validator: typical findings at a glance

FindingRuleMeaning / fix
Leitweg-ID missingBR-DE-15Add the Buyer Reference (BT-10) — mandatory in B2G.
Totals mismatchBR-CO-15Gross ≠ net + VAT; check the amounts in the file.
XSD violationSchemaStructure wrong or incomplete; check the generator.
VAT category missingBR-CO-06A line category does not appear in the breakdown.
Unknown root elementParseNeither UBL Invoice nor CII — probably not an XRechnung.

FAQ

Is the XRechnung validator free?

Yes — the XRechnung validator works without sign-up, without a daily limit and without persistent storage, and the XRechnung validator processes every file in memory and discards it after the response. Free applies to each XRechnung validator run you start here.

Which files does the XRechnung validator accept?

XML only (.xml, application/xml, text/xml) up to 1 MB — the XRechnung validator takes nothing else. PDF files belong in the ZUGFeRD validator, which extracts and checks the embedded XML; the XRechnung validator deliberately takes no PDFs at all, so responsibilities stay perfectly clear whenever you validate XRechnung data here.

Does the XRechnung validator replace the KoSIT validator?

No. The KoSIT validator with bundle 2026-08-31 remains the formal reference, especially for B2G submissions. The XRechnung validator here checks a documented subset (schema, EN 16931 core rules, selected BR-DE) and the XRechnung validator shows exactly what was checked in every single result.

What is the difference between UBL and CII?

The XRechnung validator supports both syntaxes allowed in XRechnung: OASIS UBL 2.1 serialises the invoice as an Invoice document, UN/CEFACT CII as a CrossIndustryInvoice. The XRechnung validator detects both automatically and reports the syntax, so the XRechnung validator lets you validate XRechnung files in either flavour here.

Why is the XSD layer skipped for my UBL file?

The schema check in this build uses the official CII schemas via libxml2. No UBL schema is bundled — the layer is therefore honestly marked as “skipped” when you validate UBL XRechnung files, while well-formedness and all rules still run in full.

Which XRechnung version is current?

XRechnung 3.0.2 with the technical bundle from 2026-08-31 (KoSIT validator 1.6.3) is current. XRechnung 4.0 exists only as a pre-release and is not the active standard.

Where do I find my customer’s Leitweg-ID?

One file per run — batch validation is deliberately outside the MVP so that every result maps to exactly one file. The Leitweg-ID (BT-10) is assigned by the recipient; for federal authorities it is documented in the tender documents or portal. The XRechnung validator reports a missing or malformed Leitweg-ID via BR-DE-15 and spares you the most common rejection when you validate XRechnung files at any authority.

This tool provides technical information and checks. It does not constitute tax or legal advice. A technical validation does not confirm the factual or tax correctness of an invoice. As of 2026-09-29.