DVEI Peppol e-Invoice Validation
Know an e-invoice will be accepted before you send it
Australia is moving invoicing onto the Peppol network, and a structured e-invoice that breaks the PINT A-NZ rules gets rejected downstream — after it has left your system. DVEI checks it first: upload a UBL invoice or credit note and get back every problem, named, with the rule it breaks and the exact element it lives in.
Live on RapidAPI. Subscribe on the marketplace — authentication and billing are handled there, so a key is all you need.
{
"conformant": false,
"summary": { "errors": 1, "warnings": 1, "rules_checked": 36 },
"issues": [
{
"rule": "DVEI-R026",
"aligned_with": "EN 16931 BR-CO-10",
"severity": "error",
"message": "Lines sum to 149.00, document says 150.00.",
"location": "cac:LegalMonetaryTotal/cbc:LineExtensionAmount"
}
],
"document": {
"specification": "PINT A-NZ Billing",
"totals": { "payable": "165.00" }
}
}What comes back, and what it means
- conformant
- True only when nothing of error severity fired. The single answer to "can I send this?"
- rule
- A stable DVEI identifier you can branch on, log, and hold us to across versions.
- aligned_with
- The EN 16931 or Peppol PINT rule the check corresponds to, so a finding can be traced back to the standard rather than taken on trust.
- severity
- error means a compliant receiver may reject the invoice. warning means recommended practice, or a check where rounding conventions differ.
- location
- The UBL element path, so a fix goes straight to the right line instead of starting a search.
The rule list is public
A second endpoint returns the full catalogue of rules the validator applies — 36 of them, each with its identifier, the standard rule it aligns with, its severity, and a description. What is and isn't checked is never a mystery, and a report can only ever cite a rule from that list.
Deterministic, not inferred
No model and no network call sits in the validation path. Structure, mandatory content, ABN checksums, tax categories, and the arithmetic — line sums, tax-exclusive and tax-inclusive totals, payable amounts, computed with decimal precision — are all code. The same document always produces the same report, byte for byte.
A validator, not an Access Point
DVEI does not send, receive, or store e-invoices, and is not a Peppol Access Point. It reads a document in memory, answers, and forgets it. Hostile XML — external entities, entity-expansion bombs — is refused outright rather than parsed.
What DVEI guarantees
Every line below is checkable rather than asserted — that is the whole point of the brand.
- Deployed to its own production origin
- 36 rules implemented, 32 automated tests
- Hostile-XML handling verified against XXE and entity expansion
- OpenAPI specification generated from the running app
Start using DVEI
Plans, quotas, and rate limits are on the listing itself, so what you read there is always what you are billed — we never restate prices here where they would go stale. There is a free tier to try it on your own documents first. Processing supplier invoices as well? DVAP extracts, validates, fraud-checks, and PO-matches them on the same engine, with the accuracy published.