E‑Rechnungs-StudioE-invoice validation: find issues fast and reduce rejection risk
Technical validation checks whether your e-invoice is structurally and semantically consistent before submission. It helps find common causes of rejection, such as missing mandatory fields, inconsistent totals, invalid code values, or incomplete references, but it cannot guarantee tax recognition or recipient acceptance.
Already have a file? Validate and review 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.
Use this correction workflow for your own outgoing invoice. For an incoming supplier invoice, use the results to diagnose the problem and ask the issuer for a proper correction; do not treat your edited copy as the supplier’s corrected invoice. See the receiving guide.
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.