Compliance
Compliance you can hand to an auditor.
Generating a compliant e-invoice is not the hard part. Proving it is.
Two artifacts have to survive inspection: the PDF and the XML inside it. We validate them with two separate third-party tools, deliberately kept apart so that neither vouches for the other.
veraPDF 1.28.1 — the reference PDF/A validator — checks the document against PDF/A-3 B.
Mustangproject's ZUGFeRDValidator 2.17.0 checks the invoice XML against XSD and then the EN 16931 Schematron rules.
We run the XML check twice: once on the file we generate, and once on the file extracted back out of the PDF we deliver. The second run is the one that matters — it tests what your recipient actually receives, not what we intended to send. Both are versioned tests, and they fail the build when they fail.
Three forms, one engine
| For | What you get | |
|---|---|---|
| Compliance Engine | software vendors, integrators | the generation and validation component, with its proof suite |
| Invoice | small and mid-size businesses | a complete invoicing application, hosted |
| Accounting Portal | accounting firms | one portal, every client separated, agent-assisted preparation |
Ask for the validation dossier.
Validator versions, what each one checks, and the test that would fail if we broke it.