Generate invoice document

Hex-encoded SHA-256 of the returned document bytes (the base64-decoded data). Empty string when no document was produced (422). NOT stable across calls for PDF outputs — the PDF carries a creation timestamp and document ID, so two calls with an identical payload yield two different values. Use it to verify the file you received; use payloadHash for idempotent filenames and duplicate detection.

Hex-encoded SHA-256 of the canonical JSON of the invoice you sent (object keys sorted recursively, undefined members dropped). Identical invoice data → identical value, on every call. Present on 200 and 422 responses. Use it as the key for idempotent file names and to recognise a document you already generated.

Embedded XML content (for hybrid PDF formats like ZUGFeRD/Factur-X). The PDF/A-3 in data already contains this XML; it is exposed here for convenient display/inspection.

Spec-conformance verdict on the generated document — present only when the request set validate: true (which makes the call count as 2 units). Same shape as the /:countryCode/:format/validate response, plus status. Fed from the self-check of the same run — no second check.

The ZUGFeRD / Factur-X version and profile the document was actually written in — the requested ones, or the defaults (2.4 / 1.08, EN16931) when none was sent. Absent for formats without a version selector (XRechnung, UBL, …).

Validation errors (if any)

Validation warnings (if any). SELF_CHECK_INCOMPLETE means a rulebook of our conformance self-check could not be applied (missing, not loadable or failed while running): the document was not fully checked against it. It is a warning, never a 422 — the document was not found to be wrong.