Skip to content
Vouchline for Assets by RETEK

Evidence for auditors and offline verification

What to give the auditor

On the Evidence tab, every campaign and every leaver settlement has one main file: the campaign report or the leaver certificate (PDF). That is what the auditor reads. It ends with the final hash of the decision log.

The other files are for an auditor who wants to check the data or the hashes:

FileWhat it is for
Evidence package (JSON)Every decision and log entry as stored. The offline verifier checks this file.
Assets (CSV)One row per asset with its owner and decision.
Decision log (CSV)Every sealed entry with its hash.
Corrections for Assets (CSV)Owner changes, missing or retired assets, and assets with no owner, ready for an Assets import.

Names of people and assets are read from Jira and Assets when a file is created; the app itself stores identifiers only.

The Evidence tab shows five records per page, newest first, with filters for campaigns, leaver settlements and open records.

Verify without the app

  1. Download verify-package.mjs (also on the Evidence tab).
  2. With Node.js 18 or newer, run node verify-package.mjs "Evidence package - 28 Oct 2026.json". No network and no access to Jira are needed.
  3. Compare the final chain hash it prints with the one in the PDF you received earlier.

The script checks five things: every hash in the chain; numbering without a gap and nothing after the closing entry; that every decision shown on an item equals its last log entry; that the closing totals equal the decisions before them; and that the snapshot header matches the seal in the first entry.

What it cannot tell you: that the data in Assets was true when it was scanned, or that a package was not rebuilt from scratch by someone with access to the app's storage. That is why the final hash in a report you already hold is the anchor.