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.
- Core Banking System
- Features
- Independent review
Independent review
Record an independent decision against the instruction revision under review.
OverviewInstructions for Review×
Core Banking System · Independent review
New
Instructions for Review
Bank instructions
| Record number | Subject | Status | Amount USD | Revision | Counterparty | |
|---|---|---|---|---|---|---|
| BI-13346 | Review bi-739 | Review | 810 | 340 | FC-7726 | |
| BI-19038 | Review bi-901 | Review | 280 | 390 | FC-4464 | |
| BI-99314 | Review bi-825 | Review | 130 | 190 | FC-5040 | |
| BI-48071 | Review bi-327 | Review | 360 | 570 | FC-9274 | |
| BI-30598 | Review bi-562 | Review | 760 | 60 | FC-4951 |
6 of 6 records
Review bi-739Bank instructions · BI-13346
ReviewAmount USD810
Revision340
CounterpartyFC-7726
What you can do
Decide on the submitted revision
An instruction enters review with its owner, counterparty, amount, account scopes and supporting material available for the decision. The Independent Treasury Approver checks the exact revision being presented. The guarded authorization action verifies the organization and app scope as well as the reviewer’s independence from the submission. A reviewer who prepared the request cannot simply switch screens or use an administrator account to approve their own work.
The decision record keeps the reviewer, decision, time, source revision and reason. An approval authorizes the reviewed instruction; a rejection leaves the reason for the preparer to address. A returned request can be corrected and submitted as a new revision. The earlier decision remains part of the history, so a later amount or account change does not inherit an approval from an older version.
How the work is organized
- Queue. The approver reads instructions whose status is Review and checks the underlying account and evidence records.
- Decision. The guarded action records Approve, Reject or Return with the reviewer and reason for the frozen revision.
- Receipt. The resulting operation receipt ties the action to a stable key and the instruction effect.
What to agree during setup
Assign active approvers to the right organizations and decide who covers absences without allowing self approval. The App Administrator may maintain membership, but administrative setup does not grant the independent reviewer entitlement. Decide what evidence an approver expects for each instruction type and how the preparer will make corrections after a return. The rules should hold through the app interface and any connected action endpoint.
A practical case is a same-day provider instruction where the amount matches the attached request but the credit account points to a different provider-held account. The approver returns the request with a precise reason. The preparer corrects the account scope and requests a new decision. The system should not retain the old approval as authority for the revised instruction. The reviewer examines the new revision and records a new decision before submission can proceed.
Check the handoff on an actual case
Rehearse approval, rejection and return with two distinct team members. Compare the reviewed revision with the current instruction revision before and after a preparer edit. Confirm that the decision row exists before the authorized or rejected outcome is persisted. Check the receipt’s key, expected revision and effect references. Repeat the same action to confirm it does not create a second decision or change a protected result. Give the Auditor a read-only view of the same history and verify that audit access cannot execute the action.
What your team sees
- Instructions for Review — Open the submitted instruction and inspect the revision before deciding.
- Receipts Needing Review — Investigate an action whose claimed effect needs checking.
Follow the work through
What it keeps track of
Data model- Bank instructions
- Typed banking instructions moving through authorization, submission and confirmation.
- Review decisions
- Independent approver decisions recorded against a frozen instruction revision.
- Operation receipts
- Idempotent operation receipts with stable operation keys and actual effect references.
- Team members
- Preparers, approvers, auditors and administrators working in the organization.
- Record attachments
- Supporting documents attached to a banking instruction.
- Instruction accounts
- Debit and credit account scopes that make an instruction balanced.
Who uses it
Permissions- Independent Treasury Approver
- Makes the decision.
- Treasury Preparer
- Supplies and corrects the request.
- Auditor
- Reviews the trail.
- App Administrator
- Maintains membership without deciding the instruction.
Set up Core Banking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.