Evidence and operations

Keep documents, provider events and operation outcomes attached to their instruction. The record stays with the organization that owns the work. Each handoff has a named owner and a source record that the next person can inspect. This makes the decision and its provider outcome traceable to the same instruction.

• Prepare. Record the operating context and source references before changing the status.
• Decide. Use the appropriate role to check the current revision and supporting evidence.
• Verify. Compare the recorded outcome with the provider event and retain exceptions.

Record attachments identifies a title, file, upload time, visibility and uploading team member. Application evidence records provider event IDs, evidence type, amount, received date and verification. Operation receipts records an operation key, expected revision, result state and effect references. The Operations Overview page highlights recorded exceptions for the team. These records support a read-first check of what an action actually changed.

Agree which organization owns each account and counterparty, who may prepare an instruction and who may independently decide it. Define where provider references, confirmations and balance snapshots arrive. Give each person the minimum scope needed for their role, including what may be shared in attachments. Choose one real account movement for the first rehearsal and retain its provider source identifiers.

The team should also agree when a returned record needs a fresh revision. Provider events can arrive after an internal action, so an operational status should reflect the observed event. Keep the timing and reason for correction on the related record. This helps the next shift understand why an item is still waiting.

When an operation receipt says an instruction was submitted but the provider reference is absent, Treasury Reconciler checks the parent record and the effect references. The receipt moves to needs review with a concrete discrepancy. The team investigates without sending the instruction a second time. A correction keeps earlier verified evidence and the independent decision history available to the Auditor. Walk through the case with the preparer, reviewer and reconciler together. Ask each person to point to the record they used and the event that made the next state valid. Check the same case in an ordinary screen and in the exception list, then verify that an unauthorized actor cannot make the decision.

• Operations Needing Review — Follow the records that need the module’s next action.
• Evidence Pending Verification — Check the subsequent state against its source information.

See the related process and the data model for the record handoff.