Export an evidence pack

When you would do this

When an auditor, a bank, a regulator or your own board asks you to evidence a specific payment. One transaction, one file, everything in it.

Steps

1. Go to Operation › Ledger.
2. Find the transaction and open it.
3. Under Documents, select Evidence Pack.
4. The pack downloads as a single compressed file.

You can also download the Receipt on its own, or the attached Invoice if there is one.

What is in the pack

Receipt. The transaction summary.

Transaction details. Amount, asset, network, source wallet, destination, counterparty, timestamps and the on-chain reference.

Risk dossier. Every compliance check that ran, what each found, and the overall verdict, exactly as it stood when the decision was made.

Audit trail. Who created the payment, who resolved any flags and what they wrote, who signed, and when each of those happened.

Policy snapshot. The rules that were in force at the moment the payment was created, not the rules in force today. This matters: if you have since changed your thresholds, the pack still shows what applied at the time.

Documents. Every file uploaded against the transaction, such as invoices and approval evidence.

Manifest and proof hash. A list of every file in the pack with a fingerprint of each, plus a single hash covering the manifest. Anyone can recompute those fingerprints and confirm nothing in the pack has been altered since it was generated.

What to expect

The pack is generated when you request it, from stored records. It is not assembled from anything editable, and generating it twice gives you the same content.

For a batch payment, the pack covers the batch and its recipients.

Any member of your team can generate one, including Viewers.

How to give it to an auditor

Send the file as it is. Do not unpack it, rename files inside it, or re-zip it: that breaks the fingerprints and removes the thing that makes it evidence rather than a folder.

If they ask how they can trust it, point them at the manifest and the proof hash.

Common problems and what they mean

The pack has no documents folder. Nothing was uploaded against that transaction. If your policy required a document, check whether the payment predates that policy.

The risk dossier looks thin. The payment passed without flags, so there was less to record.

The policy snapshot does not match your current policies. Correct. It shows what was in force at creation time.

You need many transactions at once. Use the ledger export instead. See "Export records for your auditor or accountant".