Generated document hash missing
Understand and repair an output whose integrity metadata is missing.
Where to check3 sections
A content hash links a generated file with its document evidence record. If Documents shows No content hash recorded or No hash recorded, that link is unavailable for the affected record. This is an evidence gap; it does not by itself prove the file contents are corrupt.
Where to check
The Generated Reports Archive can show a missing content hash. The proof package builder identifies selectable source documents with No hash recorded. Generated results and the Local Export Log may show a hash when one was recorded. There is no universal Integrity filter or Activity Log on the current Documents screen.
How to resolve it
- Identify the affected record
Confirm organisation, document type, scope, generated timestamp, and document ID. Refresh the relevant Documents area.
- Read the displayed issue
Review the generated record and error. Resolve any named source issue in its owning workflow.
- Generate a new document when available
Use the relevant payslip, report, or statutory workflow. Check whether the new record has a hash.
- Review proof eligibility
Select only hashed source documents for a proof package. If the hash remains absent, keep the original record and escalate with its ID and exact error. Do not enter a hash manually.
What to check
A saved local copy does not repair a missing hash in the generated document record. Verify the replacement document’s scope, format, timestamp, and hash before using it for evidence. A proof package may reject an unhashed input with proof-bundle.output-hash-missing.