Provider evidence

After authorization, a bank instruction can be submitted to its provider. The treasury team records the provider’s instruction identity and follows its status while waiting for a verifiable outcome. A submitted request is still different from a confirmed movement. Confirmation depends on evidence from the bank or custodian, not merely a successful send attempt.

Bank evidence can include statements, confirmations, settlement notices and corrections. Each item remains attached to the instruction with its event identity, occurrence time, amount and verification state where available. Supporting attachments remain available to explain why the team issued the original request. Together, these records let a reviewer trace the intended instruction to the provider’s response.

• Submission state. Authorized, submitted and pending requests remain distinct while the provider outcome is unresolved.
• Evidence lines. Provider records retain their type, event identity and verification result with the parent instruction.
• Final confirmation. The team uses verified confirmation or settlement evidence before marking the request confirmed.

A correction is another piece of evidence in the history. It should not erase the earlier statement or decision. The instruction’s provider identity helps the team compare messages from the same transaction without confusing two requests of equal amount.

Identify each provider’s transport and the fields it returns for instruction identity, confirmation and settlement. Agree which evidence types can establish confirmation and who verifies them. Decide how event identities are deduplicated when a provider sends the same notice twice. Keep the original occurrence date and amount so reconciliation can use the provider’s actual movement rather than a screen update time.

Set a procedure for a provider rejection or an uncertain transmission. Treasury should inspect both the provider response and the local operation receipt before considering another attempt. For authorized-scope corrections, preserve the prior provider evidence and review history. A local edit cannot by itself reverse an effect already accepted by the provider.

An approved instruction is sent to a bank. The preparer records the provider instruction identity and waits in the pending queue. A confirmation arrives with an event identity and amount. The team links it to the original instruction, verifies the evidence and then marks the instruction confirmed. The auditor can inspect the original approval, provider identity and evidence line in one trail.

Repeat the rehearsal with a settlement notice that has a different amount. The team should keep it visible for investigation rather than treating a provider message as automatic proof of the requested amount. Also replay the same provider event to check that duplicate delivery does not create another financial effect.

• Provider Outcomes Pending — Submitted and pending instructions awaiting provider evidence.
• Verified Bank Evidence — Provider evidence items marked verified, including statements, confirmations, settlements and corrections.

Read provider outcome and account reconciliation.