What does the ZUGFeRD validator check?
The ZUGFeRD validator splits your uploaded invoice into the two layers every ZUGFeRD file is made of: the visual PDF and the embedded structured XML invoice. First, the ZUGFeRD validator searches the embedded files of the PDF for the Factur-X/ZUGFeRD XML payload. If that structure is missing, the file is an ordinary PDF, not a ZUGFeRD invoice — an important distinction, because unstructured PDFs no longer qualify as e-invoices under German tax law since 1 January 2025 (BMF FAQ).
Once the XML is found, the ZUGFeRD validator identifies the syntax (UN/CEFACT CII), the profile (MINIMUM, BASIC WL, BASIC, EN 16931 or EXTENDED) and the claimed version. The file then runs through several validation layers: XSD schema validation of the CII instance, the EN 16931 business rules including full totals arithmetic, and the PDF/A-3 container markers such as XMP metadata, OutputIntent and the AF association of the embedded file.
The result is transparent: you see exactly which layers were executed, passed or skipped — including rule IDs such as BR-CO-15 and BT field numbers. The ZUGFeRD validator never claims conformance it has not actually checked. That honesty is the working principle: a check that overstates its coverage is worse than no check at all.