My invoice was rejected
Payment is delayed, and the error message makes no sense.
Check the invoice →E-INVOICE VALIDATORA rejected e-invoice
A rejected e-invoice
can delay payment.
Know before sending whether your file meets the receiving system’s rules. If a check fails, see what is wrong, where it is and how to fix it in plain words.
New to this? Explained in 30 seconds
XML is a text file with labelled fields, such as an invoice amount.
One broken label can stop the recipient from reading your file.
This tool checks the file against the selected rules.
Correct the reported fields and check again before sending.
EXAMPLE INVOICE RESULTinvoice.xml
Buyer reference is missing
Correct the field before you send it.
Buyer reference
BuyerReference · BR-DE-15Ask your buyer for the reference and add it in your invoice software.
European invoice rules passedGerman rules found the missing buyer reference.
Only a fictional example is sent for this check.
This was a fictional invoice. Check your own now →My XML shows an error
The system refuses your file, but the message does not tell you what to fix.
Find the file error →Our DORA register is due
The regulator rejects your list of IT suppliers, and the deadline is close.
Check the register →Tested against 41,053 official test cases · Your uploaded file is deleted after the check · Made by Daniel
Catch the errors before your customer does.
A required reference is missing.
BR-DE-15 reports a missing buyer reference in a German invoice. Ask your customer which reference to use. A German public body may provide a routing reference called a Leitweg-ID.
BR-DE-15: Read the rule guideThe VAT category code is wrong.
BR-CL-18 flags codes outside the allowed VAT categories. It catches an export code such as STANDARD where an official category code belongs.
BR-CL-18: Read the rule guideThe totals don’t add up.
BR-CO-15 checks that the total including VAT equals the net total plus VAT. The result points to the amounts to correct.
BR-CO-15: Read the rule guideYour invoice software uses the wrong format.
BR-DE-21 checks whether your file declares the right invoice format. Choose the rules for your invoice date. The result names the version used.
BR-DE-21: Read the rule guide41,053checks against official test cases
100%passed
Every check matched its expected result, including invoices designed to fail. Every invoice result names the rule version used.
- Invoice rules
- XML & XSD
Checked · sources checked hourly
For a signed invoice, ask your signature provider to confirm that the signature is valid. Certificate check details.
After correcting the errors, send your invoice and keep the recipient’s acceptance response.
On finding an invoice problem too late
“I did run into this and only found out after the damage was done. Would have been great to have this earlier.”
Check an e-invoice.
Choose the country or format your recipient requires. The matching tool opens with those rules selected.
(the European standard for invoice information) · (a standard format for business documents) / (a standard format for electronic invoices)
E-invoice validator →Other file checks
Find broken labels, check required fields or make a file easier to read. You can also work with several linked rules files.
</>
Explore XML tools →Use your own file rules. Open developer details for supported versions and automated checks.
Your choice is remembered only in this browser.
BUILT FROM EXPERIENCE
Built by Daniel Haket
Daniel spent more than 20 years in banking and trade finance, including Deutsche Bank, leading operations and transformation. He built XSDHub to help teams find the file errors that hold up invoices and payments.
Meet DanielXML & XSDOpen the XML & XSD workbench
Check a document against your schema, then follow the reported errors. XML checks run on your device; sending a file for an advanced check requires your permission.
Find the field that stops your file.Check file layouts and totals. Keep related rule files together or repeat checks automatically.
Explore all features ↓Schematron example
One self-written numeric assertion: total equals the sum of items. Good: total 5. Deliberately failing: total 6. Edit your own rules in the existing schema / rule editor.
The example fills the document and rules. Choose Validate XML and give permission before sending it.
Only supplied assertions are checked. No country or package conformity. XPath 1.0 / XSLT 1.0 only; DTDs, external documents and includes are blocked. Missing response context stays unknown.
How to try this ruleAdvanced engines & multi-file projects
Generate example XML
Find & replace
order.xml
order.xsd
XSD 1.0 on your device · advanced checks available
No files selected
Lexical repair
↳
READY WHEN YOU ARE
Find the error before you send the file.
A file error can stop an import. Load an example or add your file and its rules to find what needs fixing.
See all file checks
Fix one file or check several together.
Start free, without an account. Add Pro for batches and cloud storage, or Team for a shared workspace.
01FREE
Validate with confidence
Check XML syntax and XSD 1.0 on your device. Choose an advanced check for other schema or business rules; sending a document requires your permission.
Example: catch an invalid invoice date or a total that breaks a Schematron rule.
02FREE · CLOUD WITH PRO / TEAM
Work with complete projects
Open XSD files, a folder or ZIP. Resolve includes and imports, switch file tabs and see a dependency graph. Import public HTTPS schemas and dependencies as an explicit snapshot.
Save five revisions on this device and export project or ZIP backups. Pro and Team add cloud projects with up to 50 versions.
03FREE
Find the problem. Make the fix.
Format XML, search and replace text, jump to reported lines and read explanations alongside validation errors. Export the result as JSON.
Example: “Expected a value of at least 1; found 0” helps you identify the constraint that failed.
04FREE
See which file fields are required
Generate a starting XML document and validate it before using it. Compare schema structure across versions saved on this device and explore file dependencies.
Structural comparisons show changes; they do not certify compatibility. Complex examples may need manual editing.
05PRO / TEAM
Check a whole batch
Validate multiple XML files in one run: up to 25 on Pro or 100 on Team. Review per-file results and export a JSON report.
XML documents can be up to 10 MB each. For advanced XML checks, send up to 10 files per request with your permission; usage limits apply.
06FREE API · DOCUMENTED LIMITS
Catch file errors before each export
Use the HTTPS validation API, Python CLI or downloadable GitHub Actions starter to check XML in your development workflow.
Sending a document requires your permission. Review the API usage limits and service coverage in Developers before connecting your workflow.
Your files stay with you
Find broken labels, make the file easier to read and check its layout on your device. The layout check uses XSD 1.0 rules. Projects saved on this device stay in this browser.
You choose what leaves your device
Sending a document for checking requires your permission. Importing a public schema contacts the website that publishes it. Cloud saving uploads schemas when you choose Save; it does not save XML documents.
Clear limits: 10 MB per XML document · 1 MB per schema · 100 schemas / 10 MB per project · 20 files per public HTTPS import. Schematron uses XPath 1.0; DTDs and private-network imports are blocked.
XML STANDARDS
Beyond invoices
Reports for your regulator
DORA: check your list of IT suppliers
DORA register rejected with 805 or 807? Find the source cell before you resubmit.
DAC7 platform reporting validatorYOUR FILES, YOUR CHOICE
Check files without uploading them.
Find broken labels and check the agreed file layout in your browser. Other checks send a file only with your permission. Each XML file can be up to 10 MB.
Save (the agreed layout of a file) projects on this device, or choose cloud storage with Pro or Team. Cloud saving stores schemas, not XML documents. For a schema with linked files, import a complete project before checking.
Read the processing details or see rules, versions and limits.
GROW WITH YOUR WORKFLOWOne file today.
One file today.
Your whole team tomorrow.
Check one file free. For repeated work, compare plans for several files, saved rules and shared team work.
Free · Pro from US$9
Check several files in one go.
Pro from US$9/month. Team from US$29/month.
Save two months with annual billing.
Technical details
Check files automatically in your own software.
File layout checks, calculation rules and automatic checks. See the developer details.