Provider evidence

execution evidence holds a provider event reference, occurrence date, amount, evidence type and verification status under the parent instruction. Statements, confirmations, settlements and corrections have distinct types. The instruction also retains the provider instruction ID, so operators can navigate from the local request to the outside response.

• Record. A submitted instruction may still be awaiting provider confirmation. The team reviews the evidence and marks it verified only after it matches the provider response. A local status should reflect that review. Attachments can hold supporting documents with Internal or Shared visibility and the uploader identified.
• Decision. Before the first operating cycle, agree which provider message counts as confirmation, who verifies it and how corrections are retained. Also decide the permitted visibility of attachments. A provider connection and its authentication must be configured for the actual counterparty.
• Evidence. Keep the original event, later correction and attachment uploader visible so the team can reconstruct the provider sequence.

Agree which provider message counts as confirmation, who checks the source event and how corrections are retained. Set the attachment visibility before documents are shared. Configure the provider connection for the actual counterparty, then rehearse an acknowledgement that has no confirming evidence. The analyst should keep the instruction open until a verified confirmation or settlement event exists. Use a correction sample to test that earlier evidence remains available to the Independent Finance Reviewer.

A provider sends a confirmation for an instruction and later sends a correction. Operations Analyst records both events rather than replacing the first. The correction keeps its own event reference and occurrence date. Independent Finance Reviewer can compare both events with the instruction and its operation receipt before deciding whether the downstream position remains sound. At handoff, the next operator should see the provider instruction ID, each event ID, its type and occurrence date, and the verification result. They can compare the original confirmation with a later correction without losing either source. The operation receipt explains an attempted submission separately from the provider evidence that establishes its outcome. If those records disagree, keep the case open for source clarification.

• Unverified provider evidence — Check source events that have not yet been verified.
• Pending provider response — Find submitted or pending instructions and follow their provider references.

Follow instruction review, provider confirmation and account reconciliation to see how this work joins the next stage.