What is checked
- The XML: the CII schema of the profile and its Schematron rules (MINIMUM, BASIC WL, BASIC, EN 16931 or EXTENDED), with the EN 16931 business rules for the profiles that carry a full invoice, and the KoSIT rules for an invoice of the XRECHNUNG profile. Each finding names its rule, such as BR-CO-15 for totals that do not add up, with the line it is on.
- The attachment: its name (
factur-x.xml, orxrechnung.xmlfor the XRECHNUNG profile), the/AFRelationshipand MIME type PDF/A-3 asks for, and its place in the catalog's associated files. - The metadata: PDF/A-3 declared in the XMP, the Factur-X extension with its DocumentType, file name, version and conformance level, and that level matching the profile the XML names.
- The page text: the invoice number, date, totals and IBAN of the XML looked for in the PDF's text, so a PDF that shows other numbers than its XML is caught. The 15 of 150 corpus invoices that disagree were found this way.
- PDF/A: on request, the PDF goes to our server once for veraPDF, the reference PDF/A validator, and is deleted after the check.
ZUGFeRD and Factur-X profiles
ZUGFeRD 2 (Germany, FeRD) and Factur-X (France, FNFE-MPE) are the same format: a PDF/A-3 that people read, with the invoice attached as UN/CEFACT CII XML for software. The profile says how much of the invoice the XML carries: MINIMUM and BASIC WL only the header and totals, so they are not e-invoices under the German mandate; BASIC the lines too; EN 16931 (COMFORT in ZUGFeRD) the full European standard; EXTENDED more fields on top; XRECHNUNG an XRechnung in CII. The validator reads the profile from the XML's specification identifier (BT-24) and picks the matching rules itself.
When it fails
Fix the first errors first: later ones often follow from them, and the business rules run only once the schema check passes. A finding in the PDF part means the file was put together wrongly, often by a PDF library that attaches the XML without the PDF/A-3 metadata; a finding in the XML part means the invoice data is wrong. To make a ZUGFeRD PDF that passes, the e-invoice generator writes one in the EN 16931 profile and checks it before download; the Factur-X examples have a valid file of each profile.
Questions
Is my invoice uploaded?
No. The PDF is read, the XML taken out and checked in your browser, with the same engine and rules as on our servers. Only the PDF/A check, on its own button, sends the PDF to our server, which deletes it afterwards.
Can I check only the XML?
Yes: drop the factur-x.xml itself. The XML is checked the same way; the PDF checks are left out.
Which ZUGFeRD versions are supported?
ZUGFeRD 2.0, 2.1, 2.2 and 2.3 and Factur-X 1.0 in every profile. ZUGFeRD 1.0, which ZUGFeRD 2 replaced, is opened but only checked for well-formedness, as its schema is not in the catalog.
Is a ZUGFeRD invoice an e-invoice under the German mandate?
From version 2.0.1, in every profile except MINIMUM and BASIC WL, which do not carry a full invoice. See the mandate check for whether your invoices must be e-invoices from 2027.
Is this the official ZUGFeRD validator?
No: FeRD publishes the schemas and Schematron rules, and this page runs them, with veraPDF for PDF/A on request. The rules are the published ones, compared every week with the KoSIT validator and Saxon.
Other tools
- XML formatter: Pretty-print or minify XML, keeping text, CDATA and comments as written.
- XML viewer: Read a document as a tree you can fold, search and copy XPaths from.
- XPath tester: Evaluate XPath 3.1 against a document and see each match with its line.
- XSD generator: Infer an XML Schema from sample documents, checked against them.
- XML from XSD: Generate a sample XML document from a schema, validated against it.
- XSLT transformer: Run XSLT 1.0, 2.0 or 3.0 on a document and see the result, the messages and the files it writes.
- XML diff: Compare two XML documents as trees: changed, added and removed elements, attributes and text.
- XML to JSON converter: Convert XML to JSON, with arrays where an element repeats or wherever its XSD allows.
- JSON to XML converter: Convert JSON to XML: @keys become attributes, arrays repeated elements.
- XML to CSV converter: Turn a repeating element into CSV rows: invoice lines, products, records.
- XML to PDF converter: Save any XML as a PDF to read, print or attach: indented, coloured, with line numbers.
- E-invoice viewer: Read an XRechnung, ZUGFeRD, Factur-X or Peppol invoice as a document, and save it as a PDF.
- XRechnung validator: Check an XRechnung in UBL or CII against EN 16931 and KoSIT's XRechnung rules before you send it.
- UBL validator: Check a UBL invoice, order or any other UBL 2.1 document against its OASIS schema, and the business rules of the profile it names.
- Peppol validator: Check a Peppol BIS Billing 3.0 or PINT invoice against the OpenPeppol rules before your access point sends it.
- P7M viewer: open a .p7m file: Open a signed .p7m file: the PDF, invoice or document inside it, and who signed it.
- XRechnung examples to download: Example XRechnung and ZUGFeRD invoices to download, one for each common case.
- E-invoicing mandate in Germany: do I have to?: Find out whether your invoices in Germany must be e-invoices in 2026, 2027 and from 2028.
- Factur-X examples: Example Factur-X invoices of every profile and of the French reform, as XML and as PDF.
- Leitweg-ID check: Check the form and the check digits of a Leitweg-ID, the address of a German public buyer.
- Peppol lookup: Check whether a company is registered in Peppol, under which ID, and which invoices it can receive.
- XML validator: check a document against XSD, DTD, RelaxNG or Schematron, up to 1 GB.