Germany
XRechnung & ZUGFeRD invoice validation
XRechnung is a pure-XML profile; ZUGFeRD combines PDF and embedded XML. For XRechnung validation, invoices that declare XRechnung are checked with the official KoSIT validator and configuration before they are paid, on every plan. On Invoice Firewall, Invogi validates all five ZUGFeRD 2.5.2 profiles and their PDF/A-3 container against the configured technical profile and rule-set version.
What Invogi checks
Current German checks, stated precisely
Structured-format detection
A declared XRechnung customization identifier is routed automatically, in XML or inside a ZUGFeRD PDF; generic UBL or CII stays on the EN 16931 baseline instead of guessing a German profile.
Official KoSIT validation
The KoSIT validator (1.6.3) with XRechnung configuration 3.0.2 checks syntax, EN 16931 rules, and the German BR-DE rules, including totals and code lists.
On by default
KoSIT validation runs for declared XRechnung invoices on every plan unless an organization owner turns it off; the built-in buyer-reference and payment-instruction checks then still apply.
Evidence on every validation result
Validation results list the official rule identifiers, the validator and configuration versions, and a hash of the exact document checked.
Two formats, one pipeline
XRechnung vs. ZUGFeRD
XRechnung is XML-based and commonly required for invoices to German public-sector buyers. ZUGFeRD is a hybrid PDF/XML invoice — a human-readable document with the same kind of structured data embedded inside it, extracted before any visual OCR fallback.
- XRechnung: XML-based, commonly required for invoices to German public-sector buyers
- ZUGFeRD: hybrid PDF/XML invoice with container, metadata, attachment, schema, and profile-rule checks
- KoSIT validation runs for any invoice that declares an XRechnung customization identifier
Results reflect pinned KoSIT, Factur-X/ZUGFeRD, veraPDF, and Saxon versions. They are technical validation outcomes, not legal or tax certification, and a failed check is flagged for review rather than blocked automatically. Confirm current legal requirements with your own advisors.
FAQ
Common questions
What's the difference between XRechnung and ZUGFeRD?
XRechnung is a pure XML format commonly required for German public-sector invoices. ZUGFeRD is a hybrid format that embeds the same kind of structured XML data inside a human-readable PDF, used more broadly for German B2B invoicing.
Is German e-invoicing mandatory for B2B?
Germany's e-invoicing requirements have moved toward mandatory B2B structured invoicing on a phased timeline. Confirm current deadlines with your own advisors — mandate dates are not stated on this page because they change.
What German profiles does Invogi currently support?
Invoices that declare XRechnung are checked with the official KoSIT validator and XRechnung configuration by default. ZUGFeRD runtime validation covers MINIMUM, BASIC WL, BASIC, EN 16931, and EXTENDED against the configured 2.5.2 technical profile and rule-set version, including PDF/A-3, attachment, XMP, XSD, and Schematron checks. Results are technical validation outcomes, not legal or tax advice.
See it on your own invoices
Start with a free AP recovery audit, then confirm your German profile needs.
Contact us if your decision depends on a particular XRechnung rule or on ZUGFeRD profile validation and we will confirm how it is covered.