Skip to main content
← All use cases
Use case

XRechnung without rejections: invoice in, compliant XRechnung out — in seconds

The E-Invoicing Validator checks every invoice against EN 16931 and the German XRechnung 3.0.2 (the official KoSIT rules, configuration 2026-01-31): every fired violation with its field (BT/BG) and the fix, then the schema-valid UBL 2.1 XML plus an audit report as a PDF. Grounded in the official rules, with open fields honestly marked 'TO COMPLETE'.

Book a demo All use cases
EN 16931
validated against the official KoSIT rules (XRechnung 3.0.2)
UBL 2.1
schema-valid XML + audit-report PDF, Peppol-ready
Seconds
validated instead of days of ping-pong
Demo in German, English and Spanish
The starting point

Faulty e-invoices get rejected by the recipient — and the ping-pong costs days. An invoice has to be valid against EN 16931 and the German XRechnung 3.0.2 before it leaves the building.

How it works
1

Invoice in

You hand over the invoice — in seconds instead of days of ping-pong.

2

Checked against the official rules

Validated against EN 16931 and XRechnung 3.0.2; every violation with its BT/BG field and the fix.

3

Compliant XRechnung out

Schema-valid UBL 2.1 XML plus an audit-report PDF, Peppol-ready.

The outcome
EN 16931
validated against the official KoSIT rules (XRechnung 3.0.2)
UBL 2.1
schema-valid XML + audit-report PDF, Peppol-ready
Seconds
validated instead of days of ping-pong
Grounded in

Grounded in EN 16931, the German XRechnung 3.0.2 (KoSIT rules, configuration 2026-01-31) and UBL 2.1.

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.