ZUGFeRD ToolsZUGFeRD Tools

ZUGFeRD Validator — check ZUGFeRD PDF invoices online

Upload a ZUGFeRD invoice PDF and check it in seconds: embedded XML structure, detected profile, 24 EN 16931 core rules and PDF/A-3 container markers. Free, no sign-up — as a structural and rule pre-check.

By the editorial team ZUGFeRD Tools

  • ZUGFeRD 2.5.2 (FeRD, verified 2026-09-29)
  • XSD schema check for CII XML
  • EN 16931 core rules & totals logic
  • Pre-check — not a full PDF/A archival validation
  • Files are never stored
ZUGFeRD version (FeRD, 2026-08-04)
2.5.2ZUGFeRD version (FeRD, 2026-08-04)
XRechnung, bundle 2026-08-31
3.0.2XRechnung, bundle 2026-08-31
ZUGFeRD profiles
5ZUGFeRD profiles
syntaxes: UBL 2.1 & CII
2syntaxes: UBL 2.1 & CII
EN 16931 rules checked
24EN 16931 rules checked
all tools, no sign-up
€0all tools, no sign-up

Drop your ZUGFeRD PDF here

or choose a file — .pdf, max 3.5 MB

3.5 MB max · Verarbeitung ohne dauerhafte Speicherung

PDF · max. 3,5 MB · nur strukturierte Prüfung, keine Archivkonformität

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.

How to use the ZUGFeRD validator in four steps

  • Upload your ZUGFeRD PDF via drag & drop or the file dialog (max. 3.5 MB, .pdf only).
  • Start the check: the ZUGFeRD validator extracts the embedded XML and validates schema, rules and container markers.
  • Read the result: format, version, profile, syntax and every layer are shown with status and rule coverage.
  • Fix errors: issues appear with rule ID, severity and field reference (e.g. BT-10) — copy them with one click for your accounting team or the sender.

Why a ZUGFeRD validation matters more than ever

As of 2026-09-29 — ZUGFeRD 2.5.2 is the current version (FeRD, published 2026-08-04). Source: ferd-net.de.

According to the Federal Ministry of Finance, German businesses must be able to receive e-invoices since 1 January 2025, with transition periods for sending that can extend to the end of 2027 depending on prior-year turnover. Anyone sending or receiving ZUGFeRD invoices is responsible for machine-readable, rule-compliant data. A ZUGFeRD validator is therefore the first tool of choice: it finds structural errors before tax advisors, customers or authorities do.

Typical defects a ZUGFeRD validator catches early: missing embedded XML, wrong profile URNs, totals that do not add up (line items vs. grand total), incomplete VAT breakdowns, or a PDF that contains the XML but lacks the PDF/A-3 embedding and association markers.

The validation layers of the ZUGFeRD validator in detail

PDF/A container (marker check)

The ZUGFeRD validator verifies that the PDF carries the PDF/A-3 markers: XMP metadata with pdfaid:part 3, an OutputIntent with an ICC profile, the embedded file in the name tree, and the AF (Associated File) association. To be precise: this is a structural marker check, not a full archival conformance test at veraPDF level — and the result report says exactly that.

XML schema (XSD) and EN 16931 rules

The CII instance is validated against the official Factur-X/ZUGFeRD XSD (libxml2). The ZUGFeRD validator then applies a curated subset of the EN 16931 core rules: mandatory fields, invoice date and number, line arithmetic (quantity × price = line net), totals logic and the VAT breakdown.

Not a replacement for professional advice

A passed technical validation does not confirm the factual or tax correctness of an invoice. The ZUGFeRD validator checks structure and rules — whether the content is right remains a human task.

ZUGFeRD validator: common findings and what they mean

FindingLayerMeaning
No embedded XML foundPDF/AThe PDF has no structured invoice data — not a ZUGFeRD invoice.
XSD violationSchemaThe XML does not match the schema; usually a generator bug.
BR-CO-15 totals mismatchEN 16931Gross ≠ net + VAT — amounts are inconsistent.
BR-CO-12 line itemEN 16931Quantity × price does not equal the line net amount.
PDF/A markers missingPDF/AXML present, but the container is not marked as PDF/A-3.

FAQ

Is the ZUGFeRD validator free?

Yes. The ZUGFeRD validator works without sign-up and without a daily limit — the ZUGFeRD validator processes files up to 3.5 MB in memory and never stores them.

Which files does the ZUGFeRD validator accept?

PDF files only (.pdf, application/pdf) — the ZUGFeRD validator takes no XML. Plain XML files belong in the XRechnung validator, which supports UBL 2.1 and UN/CEFACT CII.

Does the ZUGFeRD validator check full PDF/A conformance?

No — and it says so honestly. The PDF/A-3 structural markers are checked (XMP, OutputIntent, AF association, embedded file). A full archival conformance check would require e.g. veraPDF and is not part of this MVP.

Which ZUGFeRD versions are detected?

The ZUGFeRD validator reads the version from the guideline URN of the embedded XML — e.g. ZUGFeRD 2.1, 2.3 or 2.5. The current release is ZUGFeRD 2.5.2 (FeRD, 2026-08-04).

What does “profile EN 16931” in the result mean?

ZUGFeRD defines the profiles MINIMUM, BASIC WL, BASIC, EN 16931 and EXTENDED. The EN 16931 profile carries all mandatory fields of the European e-invoicing standard and is the most common choice for B2B exchange.

Are my invoice data stored?

No. The file is used only for the requested processing and discarded afterwards — no persistent storage of PDF, XML, IBAN, VAT IDs or customer data.

How fast is the ZUGFeRD validator?

Yes. Factur-X is the French counterpart of ZUGFeRD and technically identical (PDF/A-3 + embedded CII XML). The ZUGFeRD validator recognises Factur-X URNs accordingly.

How fast is the ZUGFeRD validator?

Typical invoices are checked within seconds — extraction, schema validation and rules combined. The ZUGFeRD validator runs server-side; your browser only waits for the finished result.

This tool provides technical information and checks. It does not constitute tax or legal advice. A technical validation does not confirm the factual or tax correctness of an invoice. Legal status of the German e-invoicing mandate: BMF FAQ, as of 2026-09-29.