Factur-X / ZUGFeRD validator
Check a Factur-X or ZUGFeRD 2 invoice, as a PDF or its XML, against the rules for its profile.
- Version 1
- Checked against 2 published cases
Check an invoice now
Free, no sign-up, 5 invoices a day. Files up to 900 KB, XML or Factur-X PDF. The file is checked in memory and is not stored.
What it checks
Takes the PDF (base64) or the CII XML. From a PDF the embedded factur-x.xml, zugferd-invoice.xml or xrechnung.xml is read, with the profile the PDF's XMP metadata names. The profile comes from the guideline ID (BT-24): MINIMUM, BASIC WL, BASIC, EN 16931 and EXTENDED use the Factur-X 1.09.2 / ZUGFeRD 2.5 schema and Schematron for that profile; XRECHNUNG uses KoSIT's rules.
- PDF/A-3 conformance of the PDF itself is not checked: only the embedded invoice and the Factur-X XMP metadata are read.
- ZUGFeRD 2.0 guideline IDs are checked against the current rules for the same profile, with a warning. ZUGFeRD 1.0 is not supported.
Rules used
- Factur-X 1.09.2 / ZUGFeRD 2.5 schemas and Schematron (FNFE-MPE and FeRD), as distributed with Mustang, version 1.09.2
- KoSIT validator configuration for XRechnung 3.0.2, version 2026-08-31
A check shows whether the invoice passes the official rule sets listed, at the versions listed. It is not legal or tax advice, and passing does not promise that a tax authority or buyer will accept the invoice. See the terms.
Use it from your code
jq -Rs '{xml: .}' ferd-en16931-einfach.xml |
curl https://api.curatedapi.com/v1/validate/einvoice/factur-x \
-H "Authorization: Bearer $CURATEDAPI_KEY" \
-H "Content-Type: application/json" \
--data-binary @-
{
"validator": "einvoice/factur-x@1",
"result": {
"valid": true,
"scenario": "Factur-X EN 16931",
"document_type": "UN/CEFACT CII",
"specification_id": "urn:cen.eu:en16931:2017",
"errors": 0,
"warnings": 0,
"notices": 0,
"error_rules": [],
"checks": [
{
"check": "XML syntax",
"passed": true
},
{
"check": "Factur-X 1.09.2 EN 16931 schema",
"passed": true
},
{
"check": "Factur-X 1.09.2 EN 16931 rules",
"passed": true
}
],
"messages": [],
"messages_truncated": false,
"profile": "EN 16931",
"pdf": null
},
"rules": [
{
"name": "Factur-X 1.09.2 / ZUGFeRD 2.5 schemas and Schematron (FNFE-MPE and FeRD), as distributed with Mustang",
"version": "1.09.2",
"url": "https://github.com/ZUGFeRD/mustangproject/tree/1d633ab612856527d536a709ed53bedd2a4ea98c/validator/src/main/resources"
},
{
"name": "KoSIT validator configuration for XRechnung 3.0.2",
"version": "2026-08-31",
"url": "https://github.com/itplr-kosit/validator-configuration-xrechnung/releases/download/v2026-08-31/xrechnung-3.0.2-validator-configuration-2026-08-31.zip"
}
]
}
MCP tool validate_einvoice_factur_x at https://mcp.curatedapi.com.
Inputs, results and errors in the API reference.
Other validators
Check every invoice before it is sent
Run the same check from your invoicing app or ERP, one POST per invoice, before the file goes to the customer or the Peppol network. The answer lists every rule it breaks.
Free for up to 200 invoices checked a month. 10,000 invoices checked a month cost $9.00 on the Starter plan.