These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Financial Risk Management
- Features
- Banking instructions
Banking instructions
Prepare a scoped instruction and follow its authorization and provider status.
OverviewDraft instructions×
Financial Risk Management · Banking instructions
New
Draft instructions
Approval conditions
| Record number | Subject | Status | Amount USD | Requested at | Owner | |
|---|---|---|---|---|---|---|
| BI-12479 | Draft bi-723 | Draft | 560 | 06 Oct | ||
| BI-55273 | Draft bi-451 | Draft | 540 | 25 Oct | ||
| BI-64732 | Draft bi-529 | Draft | 860 | 12 Oct | ||
| BI-61971 | Draft bi-902 | Draft | 90 | 03 Oct | ||
| BI-66085 | Draft bi-563 | Draft | 550 | 17 Oct |
6 of 6 records
Draft bi-723Bank instructions · BI-12479
DraftAmount USD560
Requested at06 Oct
CounterpartyFC-9253
What you can do
Give each instruction a clear owner
Treasury Preparer starts with the organization, owner and eligible counterparty. The instruction records its subject, requested date, amount and revision. Debit and credit account scopes show which financial accounts the request affects. The counterparty and accounts should be checked before the instruction is sent for review; changing either after a decision changes the basis of that decision.
An instruction for a transfer between provider accounts gives the team a concrete case. The preparer identifies the account on each side, records the intended amount, and attaches the supporting request. If the accounts or amount disagree with the request, the preparer resolves the discrepancy while the instruction is still a draft. The owner can then explain the transaction without asking an approver to infer it from a subject line.
How the work is organized
- Prepare. Record the organization, counterparty, owner, amount and account directions while the instruction is in Draft.
- Review. Move a complete instruction into Review and retain its revision for the independent decision.
- Follow through. Keep the provider instruction reference and outcome with the original record through confirmation.
The status separates a prepared instruction from one authorized by a reviewer. Submitted and Pending describe work awaiting a provider result. Confirmed belongs to an outcome supported by verified provider evidence. A rejected instruction remains visible with its decision history; it is not silently recycled as though it had never been reviewed.
What to agree during setup
Agree which organizations own the instructions, who may prepare for each organization and which counterparties are eligible. Decide how the team verifies account identity and debit or credit direction before review. Set a convention for the subject and record number so an operator can find the instruction from a provider reference or a supporting document. The preparer should know which changes require a new review of the current revision.
Also agree who supplies provider status and how that status is checked. The instruction can retain a provider identifier, but the team must distinguish a submission acknowledgement from a confirmation or settlement event. A second attempt after an unclear response needs its original operation key and receipt checked before anyone submits again.
Check the handoff on an actual case
Use a real transfer request in a rehearsal. Ask Treasury Preparer to create the instruction, record both account directions and attach the source request. Ask Independent Treasury Approver to compare the amount, accounts and counterparty with the evidence, then record a decision on that revision. Follow the provider reference through the Submitted and Pending stages. Finish only when the evidence supports Confirmed and the operation receipt points to the effect that actually persisted.
Run a second case with a changed amount after review. The reviewer should see the new revision and decide on its current evidence. A prior approval must not silently authorize a changed instruction. Keep the earlier decision and attachments available so Auditor can reconstruct why the transaction was released.
What your team sees
- Instruction status board — Instructions grouped by status so the owner can separate drafts, review work and provider follow-up.
- Provider outcome queue — Submitted and pending instructions with the provider reference beside the amount and counterparty.
Follow the work through
See instruction review, provider outcome and implementation.
What it keeps track of
Data model- Bank instructions
- Typed banking instructions moving through authorization, submission and confirmation.
- Instruction accounts
- Debit and credit account scopes that make an instruction balanced.
- Financial accounts
- Provider-held financial accounts owned by a counterparty.
- Financial counterparties
- Banks, custodians and settlement counterparties eligible for banking instructions.
- Record attachments
- Supporting documents attached to a banking instruction.
- Review decisions
- Independent approver decisions recorded against a frozen instruction revision.
- Operation receipts
- Idempotent operation receipts with stable operation keys and actual effect references.
Who uses it
Permissions- Treasury Preparer
- Owns preparation and provider follow-up.
- Independent Treasury Approver
- Decides the reviewed revision.
- Auditor
- Reads the instruction and its evidence.
- App Administrator
- Maintains organizational membership without acting as the financial approver.
Set up Financial Risk Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.