Bank instructions

The Treasury Preparer starts with the organization, owner, counterparty, amount and requested date. The record number and subject let a reviewer distinguish one instruction from another when the same counterparty receives similar requests. The value date expresses the intended timing; it does not establish that the provider accepted or settled the work. A draft remains editable within the preparer’s organization scope until it is sent for review.

Each instruction has debit and credit account scopes. For a transfer between provider-held accounts, the preparer identifies both directions and checks that the scoped amounts balance. The selected accounts should be active and belong to the intended provider relationship. When an account or counterparty is no longer eligible, resolve that master data before asking an approver to decide. A plausible total cannot replace the account detail that defines what the instruction will affect.

• Preparation. The preparer owns the draft, its account scopes and attachments until the revision is submitted for review.
• Decision. An independent approver examines that frozen revision and records the reason for approval, rejection or return.
• Provider result. Submission records the provider identifier; confirmation waits for verified provider evidence.

Choose the organization boundary for each team, the provider account identifiers, and who may prepare versus independently approve. Decide how the institution will receive provider confirmations and settlement notices. Keep the external event identifier stable so a repeated notification points to the same evidence. Agree how a correction to an authorized instruction is requested and documented; a local edit should not be treated as a provider reversal.

For example, a treasury team may move funds between two provider-held accounts before a value date. The preparer enters the amount once on the instruction and records matching debit and credit scopes. The approver checks the chosen accounts and the attached request against the frozen revision. Only after authorization does the preparer submit. If the provider returns a pending result, the team keeps the instruction pending until an actual confirmation or settlement notice has been verified.

Rehearse a clean case and a rejected one. In the clean case, compare the authorized amount and account scopes with the provider identifier and subsequent evidence. In the rejected case, retain the decision reason and keep submission unavailable. Then test a repeated submit request with the same operation key; it should lead to the recorded effect rather than creating a second external action. If a confirmed instruction later needs correction, preserve the original provider result and use the guarded correction route.

• My Instructions — Find assigned work and review its current status before requesting a decision.
• Provider Pending Instructions — Follow submitted work by provider reference and value date.
• Confirmed Instructions — Trace accepted outcomes back to the originating instruction.

Read instruction preparation, independent authorization and provider outcome.