E‑Rechnungs-StudioE-invoice validation: find issues fast and avoid rejections
Validation ensures your e-invoice is technically and semantically consistent before submission. In practice, most rejections come from missing mandatory fields, inconsistent totals, invalid code values, or incomplete references. This guide explains these patterns and shows how to resolve them efficiently.
Already have a file? Validate, view, and correct it now.
The E‑Rechnung Validator supports both XRechnung and ZUGFeRD workflows: upload existing files, inspect XML in the viewer, understand errors and mandatory fields, and iterate until the invoice is ready to send.
What validation checks
- XML structure and mandatory fields.
- Codes, value ranges, and references.
- Totals, rounding, VAT logic, and consistency between header and line items.
Typical errors and mandatory-field gaps
1) Missing mandatory fields
Required party data, payment terms, line descriptions, or tax details are often incomplete or only present in the visual PDF.
2) Totals and VAT inconsistencies
Rejections often result from mismatched line sums, tax breakdowns, or rounding differences.
3) Missing recipient references
Purchase order references, project identifiers, or contract numbers may be mandatory in recipient workflows.
Viewer: inspect XML and read the preview
A validator is most useful when you can compare structured XML and a readable preview in one place. The viewer helps you identify whether data is only visible in the document view or truly present in the invoice XML that recipient systems process.
Correct quickly with plain-language change requests
Instead of editing XML manually, request changes in plain language, review the updated preview, validate again, and export the updated invoice. This short loop is usually the fastest way to clear mandatory-field and consistency issues.
New validator workflow for existing files
The validator page accepts existing XRechnung XML and ZUGFeRD PDF files. It can extract XML from ZUGFeRD, show XML and preview side by side, apply plain-language correction requests, validate again, and export the updated invoice.
Start here: E‑Rechnung Validator.
FAQ
What is an e-invoice validator?
An e-invoice validator checks whether XRechnung or ZUGFeRD files are technically and semantically consistent. It verifies mandatory fields, totals, VAT logic, and required references before submission.
Can I validate and view an XRechnung XML file?
Yes, you can upload an existing XRechnung XML file, validate it, and inspect the structured XML. You also get a readable preview to compare invoice data and document output.
Can I validate a ZUGFeRD PDF and extract the XML?
Yes, you can upload a ZUGFeRD PDF that already contains embedded invoice XML. The XML is extracted for validation, viewer inspection, and preview generation.
Why are e-invoices rejected?
Common rejection reasons are missing mandatory fields, inconsistent totals, invalid VAT values, and unsupported code values. Missing recipient references can also trigger rejection.
How can I fix errors and mandatory fields quickly?
Use plain-language change requests: describe the correction, review the updated preview, and validate again. This loop is usually faster than manual XML editing for common issues.
Do I need to register?
No, you can start without registration. Upload, validate, view, correct, and export your updated invoice directly in the tool flow.