XML and CII namespace
Well-formed XML, safe parsing and the UN/CEFACT CrossIndustryInvoice :100 namespace.
Free ZUGFeRD 2.5, Factur-X and PDF/A-3 validator
Validate ZUGFeRD XML and its PDF/A‑3 container.
Paste or upload CrossIndustryInvoice XML for business-rule findings, or upload the hybrid PDF to check PDF/A-3 markers, attachment metadata and veraPDF conformance when the full engine is available.
Validate invoice XML free →Supported surface
- ZUGFeRD 2.5 CII XML
- Factur-X profile identifiers
- MINIMUM through EXTENDED
- PDF/A-3 attachment and veraPDF validation
Hybrid-document gate
Validate the complete PDF/A‑3 container.
Upload the original hybrid invoice—not a print-to-PDF copy. Shipment Sentry checks PDF/A-3 metadata, embedded-file and associated-file evidence, then invokes veraPDF when the complete engine is available. The binary is never retained.
- ✓ PDF/A part and conformance declaration
- ✓ Embedded XML and AFRelationship evidence
- ✓ Standard Factur-X/ZUGFeRD attachment naming
- ✓ Complete veraPDF machine-verifiable rules when configured
Direct answer
What this ZUGFeRD validator actually proves.
XML and PDF/A-3 are separate evidence layers. The PDF upload checks container markers and attachment metadata, and runs veraPDF when that engine is installed; without veraPDF it reports the engine gap instead of claiming full conformance. Visual-to-XML equality and every official Schematron assertion still require the complete FeRD/Factur-X package.
Read the FeRD ZUGFeRD / Factur-X specification ↗Rule coverage
Eight layers between “valid XML” and a usable invoice.
Guideline profile
Recognizes MINIMUM, BASIC WL, BASIC, EN16931, EXTENDED and XRechnung identifiers.
Document identity
Invoice number, type code and format-102 issue date.
Seller and buyer
Legal names, postal country codes and profile-sensitive electronic addresses.
Invoice lines
Line IDs, quantities, product names, prices, line totals and VAT categories.
Monetary totals
Line total, tax basis, VAT, grand total, prepaid/rounding and due payable equations.
Profile-aware severity
EN16931 electronic-address omissions block; lower profiles receive a delivery-readiness warning.
Actionable evidence
Every finding includes a stable code, CII location, source and concrete next action.
Visual field guide
See where each failure enters the document.
Three-step workflow
Preflight, repair, certify.
- 1
Choose XML or the hybrid PDF
Use factur-x.xml or ZUGFeRD-invoice.xml for business rules, and the PDF/A-3 upload for container and attachment evidence.
- 2
Repair CII business terms
Fix profile and party identity first, then line and monetary-reconciliation failures.
- 3
Validate the hybrid document
Run the complete ZUGFeRD 2.5 / Factur-X artefacts to test PDF/A-3, attachment metadata and visual/XML equality.
Questions before upload
ZUGFeRD validator FAQ
Can I upload a ZUGFeRD PDF?
Yes. The separate PDF/A-3 upload checks the PDF header, conformance metadata, embedded-file relationship and expected XML attachment name, then uses veraPDF when installed. Visual-to-XML equality remains outside this automated check.
Which ZUGFeRD and Factur-X profiles are recognized?
The preflight recognizes MINIMUM, BASIC WL, BASIC, EN16931, EXTENDED and XRechnung guideline identifiers. Line and endpoint requirements adapt to the detected profile.
Does it validate EN 16931 totals?
It checks the high-value line-net, tax-basis, VAT, grand-total and due-payable relationships within a two-cent tolerance.
Does a 100 score prove the PDF is compliant?
No. The XML score and PDF/A-3 report are separate. Full veraPDF conformance is named explicitly when available, while rendering equality and every official business rule remain separate evidence.
Are invoice files retained?
Anonymous XML is not retained. Signed-in users can explicitly opt into encrypted retention; the default remains off.
Which release does this validator target?
The rule surface is aligned to ZUGFeRD 2.5, whose official FeRD information package was published on 10 June 2026.
One invoice, one clear next action