Skip to main content
← All use cases
Use case

Check before you send: upload an existing e-invoice, get findings and a validation report in seconds

The E-Invoice Validator checks an existing XML or PDF invoice with pinned validator engines against EN 16931, XRechnung 3.0 and ZUGFeRD/Factur-X: every fired rule with its field (BT/BG) and a correction hint, plus a validation report. It generates no replacement invoice, sends nothing, does no Peppol delivery and does not archive the file — it is discarded after the check.

Book a demo All use cases
EN 16931
checked by pinned engines (KoSIT, Mustang)
BR · BR-DE
every fired rule with its field, a correction hint and a report
0
archived invoices: the file is discarded after the check
The starting point

Faulty e-invoices get rejected by the recipient — and the back-and-forth costs days. Checking the invoice technically beforehand lets you find the errors yourself and correct them in your own system.

How it works
1

Upload the invoice

Upload an existing XML or PDF invoice, or select one from Documents.

2

Checked by pinned engines

KoSIT and Mustang check against EN 16931, XRechnung 3.0 and ZUGFeRD/Factur-X; every fired rule with its BT/BG field and a correction hint.

3

A report, not a replacement invoice

A validation report with engine version and input hash, generated in the browser. You correct the invoice in your own system; nothing is sent or archived.

The outcome
EN 16931
checked by pinned engines (KoSIT, Mustang)
BR · BR-DE
every fired rule with its field, a correction hint and a report
0
archived invoices: the file is discarded after the check
Grounded in

What is real: the validator engines (the KoSIT validator with the official XRechnung configuration, Mustang for ZUGFeRD/Factur-X), the rule IDs and the correction hints. The result is technical conformance — not a tax or legal assessment, and no proof that this format was required.

Book a demo

See it on your own use case.

30 minutes, scoped to your industry, frameworks and integrations. You leave with a concrete scenario — not a sales loop.