Transaction evidence packs

What is in a pack

Evidence packs assemble transaction facts, screening outcomes, adjudication decisions, and related metadata your organization captured during processing. They are generated from live workflow data — not manually pasted summaries.

What you see in the workspace

The Evidence workspace is the regeneration surface. The callouts on the figure below name the four areas you use to produce or review a pack.

• Sidebar — Evidence is selected; the workspace stays separate from Transactions so audits land here, not in the operator queue.
• Evidence Packs header — workspace title plus any degraded-state banner if storage is misconfigured.
• Regenerate by transaction ID — paste a transaction UUID (not the order number) and run; produces a fresh pack from stored workflow data.
• Existing pack list — every prior pack for your org, newest first; click to inspect or re-download.

1234

1. 1Sidebar — Evidence selected
2. 2Evidence Packs header
3. 3Regenerate by transaction ID
4. 4Existing pack list

When to regenerate

• An auditor or customer requests proof for a specific transaction ID.
• You need to verify what the system recorded at decision time.
• A prior download expired or you need a fresh bundle after supplemental review.

Reading a pack

A regenerated pack mirrors what Trade stored at the moment of decision. The sections you will see match the transaction detail page and the approvals decision rationale; pack contents are derived, not authored. If a section is empty, the upstream workflow did not produce that data — never edit a pack to fill a gap.

Limits and fail-closed behavior

Evidence reflects what Trade stored for your organization. If intake was incomplete, screening did not run, or a decision was never recorded, the pack will show those gaps — that is intentional fail-closed transparency. Trade does not invent missing screening results, backfill absent decisions, or paper over upstream data quality issues.