← Factur-X Validator

Factur-X, ZUGFeRD, XRechnung and EN 16931, explained simply

Four names that look interchangeable but aren't. Here's how they fit together — and what to check before you send an invoice.

Short version: EN 16931 is the rulebook. Factur-X / ZUGFeRD and XRechnung are specific formats that implement it. A hybrid invoice is a PDF with the structured data attached inside.

EN 16931: the common rulebook

EN 16931 is the European standard that defines a core invoice data model — a list of business terms (the "BT" numbers you see in validation output, like BT-1 for invoice number) and rules about which are mandatory and how amounts must add up. It exists so that an invoice issued in one country can be understood and processed automatically in another. Any compliant format must carry at least the EN 16931 core fields.

Factur-X and ZUGFeRD: two names, one hybrid format

Factur-X and ZUGFeRD are essentially the same thing under different branding — Factur-X is the French name, ZUGFeRD the German one. The defining trait is the hybrid invoice: a visual PDF/A-3 that a human reads, with a machine-readable XML invoice embedded as an attachment. The XML follows CII (Cross Industry Invoice) syntax.

There are several Factur-X profiles — MINIMUM, BASIC WL, BASIC, COMFORT, EN 16931, EXTENDED. Higher profiles carry more fields. The profile is declared in BT-24 (the guideline ID), e.g. urn:factur-x.eu:1p0:basic.

XRechnung: Germany's public-sector format

XRechnung is the format required for invoices to German public authorities. It is XML-only (no visual PDF requirement) and comes in two syntaxes: UBL and CII. It is built on EN 16931 with a few German-specific extensions. Because it shares the core model, the same fundamental field checks apply.

CII vs UBL syntax

SyntaxRoot elementUsed by
CIICrossIndustryInvoiceFactur-X, ZUGFeRD, XRechnung-CII
UBLInvoiceXRechnung-UBL, many other EU formats

They describe the same invoice in different XML structures. Our validator auto-detects which one you've pasted and checks the equivalent fields in each.

Mandatory fields worth checking first

Before worrying about the ~200 detailed Schematron rules, make sure the core fields are present and consistent:

The most common rejection causes are a missing guideline ID, a currency/date in the wrong format, and totals that don't reconcile. Run your invoice through the validator to catch these in seconds.

Free tool, honest limits

Our validator runs entirely in your browser — nothing is uploaded. It checks a practical core subset: mandatory fields, amount consistency, line items and VAT syntax. It is not a certified EN 16931 conformance checker; for legal filing or formal acceptance, confirm with an official validator or your platform's acceptance test.