XRechnung Validator
Upload a UBL 2.1 or CII XML file and validate it against XRechnung 3.x, the German CIUS (Core Invoice Usage Specification) for EN 16931. The validator runs both the EN 16931 base rules and the German-specific BR-DE extension rules.
Generate a validator-passing XRechnung invoice
SealDoc generates an XRechnung 3.0-compliant invoice — including all required BR-DE fields — and validates it instantly. Download the PDF/A-3B and inspect the embedded CII XML.
No account required. Not persisted. Rate-limited per IP.
Drop an XRechnung UBL or CII XML here
PDF or XML, up to 10 MB. Drag and drop or click to choose.
No account required. Files are auto-deleted within 24 hours. Only a hashed IP is stored for rate-limiting.
What is XRechnung?
XRechnung is Germany's national CIUS (Core Invoice Usage Specification) for the EN 16931 European invoice standard. It is a pure XML format — unlike Factur-X, it does not embed XML inside a PDF.
XRechnung is available in two syntaxes: UBL 2.1 (OASIS Universal Business Language) and CII (UN/CEFACT Cross Industry Invoice). Both syntaxes carry identical data.
XRechnung is mandatory for all invoices to German federal authorities (B2G) since 2020, and accepted as an alternative to ZUGFeRD for B2B invoicing since the Wachstumschancengesetz took effect.
Version 3.0 introduced stricter validation and additional BR-DE rules. The most common breaking change was the addition of BR-DE-2 (seller tax number mandatory) for all invoice types.
German-specific rules (BR-DE)
BR-DE-1 The document type code must be 380 (invoice) or 381 (credit note).
BR-DE-2 The seller's tax registration number (BT-32) is mandatory.
BR-DE-3 The buyer's reference (BT-10, Leitweg-ID) is mandatory for B2G invoices.
BR-DE-14 Each line item must carry a net amount (BT-131).
BR-DE-16 Payment means must specify a German bank account (BG-17/BT-84/BT-85).
BR-DE-17 Delivery information (BG-13) is mandatory.
German e-invoicing mandate timeline
B2G mandatory (federal)
All invoices to German federal authorities must be XRechnung via Peppol. Central government only.
B2B receive obligation
All German VAT-registered businesses must be technically able to receive structured e-invoices (XRechnung or ZUGFeRD). Sending is still optional for most.
B2B send obligation (large)
Businesses with over €800k annual turnover must send structured invoices. Plain PDFs are no longer accepted.
B2B send obligation (all)
All German VAT-registered businesses must send structured e-invoices. Plain PDFs not accepted for any B2B invoice.
Exceptions
Invoices under €250, public transport tickets, and invoices to non-VAT-registered buyers remain exempt from structured format requirements.
10 years retention
HGB §257 and AO §147 require 10-year retention for invoices. SealDoc enforces this automatically via the BUSINESS_7Y and ARCHIEFWET_20Y retention policies.
Generate and validate XRechnung invoices via API
The SealDoc API generates XRechnung-compliant invoices from JSON. The output is a sealed, RFC 3161-timestamped PDF/A-3 with an embedded CII XML attachment that passes XRechnung 3.x validation.
// Validation result example
{
"status": "pass",
"profile": "XRechnung 3.0 (UBL)",
"findingsCount": 0,
"findings": []
}