Problems·HTTP 422

invalid-invoice

The invoice cannot produce a valid Peppol document.

What it means

A conversion never returns an invalid document. This invoice would have broken the rules listed in findings, and errors maps each one to the JSON field that caused it.

What to do

Fix the fields named in errors. Each finding links to its rule's page.

Extra members

errors

Messages keyed by the JSON path of the field at fault.

findings

The rules the document would have broken, in the same shape as a validation report's findings.

Example

Sent as application/problem+json (RFC 9457). Branch on type, which is stable. Never branch on title or detail, which are prose and may change.

{  "type": "https://www.einvoicing.dev/problems/invalid-invoice",  "title": "The invoice cannot produce a valid Peppol document.",  "status": 422,  "detail": "…",  "errors": "…",  "findings": "…"}