Evidence and audit

An instruction can carry uploaded documents, provider evidence, independent decisions and operation receipts. These records serve different purposes. An attachment keeps the document title, type, visibility, uploader and upload time. Bank evidence keeps the provider event, occurrence time, amount, evidence type and verified state. A review decision records the reviewer, source revision, decision and reason. An operation receipt records the action, stable key, expected revision, result state and effect references. Reading them together explains what happened without treating one record as proof of every step.

The Auditor has scoped, read-only access. The App Administrator can maintain membership but cannot convert that administrative power into approval authority. The Treasury Operations Lead follows exceptions and compares receipts with the effects they claim. Verified provider evidence and prior review decisions must remain available when a correction or cancellation is considered. A provider effect should not be assumed reversed because a local instruction is edited.

• Documents. Attach support to the parent instruction with the appropriate visibility.
• Provider events. Record source identifiers and verification separately from submitted requests.
• Operation effects. Check that a completed receipt corresponds to real persisted records.

Set who can mark provider evidence verified, what source identifier is required, and when a document may be shared beyond the operations team. Define who investigates a receipt marked Failed or needs review, including how to compare its effect references with actual instruction, decision and evidence rows. A repeated request with the same operation key should point to the same effect. The team must know whom to contact at the provider when a settlement notice conflicts with a local record.

An approver authorizes an instruction and the receipt says the operation completed. The Auditor reads the receipt’s operation key and expected revision, then finds the corresponding review decision, instruction status and recorded reason. Later, a provider confirmation arrives with an event identifier. The operations lead verifies the evidence and checks the instruction’s provider reference before marking it Confirmed. If the receipt claims a decision that is absent, the discrepancy is recorded for review; the team does not issue a second provider instruction to repair a local evidence gap.

• Verified provider evidence — Provider events that have been checked against their parent instruction.
• Receipts needing review — Claimed effects that require a record-by-record check.

See evidence verification and instruction lifecycle.