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.
- Open Banking API Platform
- Features
- Independent review
Independent review
Record who decided, which revision they saw and why they chose the outcome.
OverviewReview Queue×
Open Banking API Platform · Independent review
New
Review Queue
Approval conditions
| Record number | Subject | Revision | Amount USD | Owner | Counterparty | |
|---|---|---|---|---|---|---|
| BI-55373 | Review bi-281 | 160 | 340 | FC-4084 | ||
| BI-72698 | Review bi-650 | 410 | 800 | FC-9124 | ||
| BI-18046 | Review bi-192 | 380 | 40 | FC-5239 | ||
| BI-94355 | Review bi-518 | 130 | 20 | FC-6613 | ||
| BI-59917 | Review bi-588 | 490 | 430 | FC-7675 |
6 of 6 records
Review bi-281Bank instructions · BI-55373
Revision160
Amount USD340
CounterpartyFC-4084
What you can do
Decide on a specific revision
Independent review centers on the instruction as it stood when it entered the queue. The decision record keeps the source revision, reviewer, decision, time, reason and operation key. This makes an approval or rejection traceable to a person and a specific state of the work. A change to the instruction after review has to be checked against that decision basis before the team relies on it.
The Independent Treasury Approver is separate from the Treasury Preparer. The review handoff should prevent someone from authorizing their own submission. The App Administrator manages membership and configuration, but that administrative role is not itself financial approval authority. Keeping those responsibilities distinct matters when the same small team administers the application and prepares banking work.
How the work is organized
- Queue. The review list exposes the instruction number, revision, amount, owner and counterparty.
- Decision. review decisions holds approval, rejection or return with a required reason.
- Effect. An operation receipt can connect the guarded action to the resulting instruction state.
What to agree during setup
Identify eligible independent reviewers for each organization and agree how to replace an absent reviewer. Decide what evidence a reviewer must see for an instruction: account scope, counterparty eligibility, requested date and supporting attachments may all matter. Define what a return means operationally and who changes the draft before another review. The decision reason should be specific enough for an Auditor to understand the outcome later.
Agree how an unexpected revision is handled. A reviewer who saw an earlier amount should not approve a later amount by relying on the prior decision. The team’s review procedure needs to compare the submitted revision with the current instruction and preserve the result of every attempted decision.
Check the handoff on an actual case
A preparer sends a settlement instruction to review. Its amount and account scope are visible with the current revision. The Independent Treasury Approver checks the counterparty and supporting record, then chooses approval, rejection or return and records the reason. Approval moves the instruction into authorized work only for that revision. If the preparer changes the instruction while review is underway, the team stops and checks the revision again. The Auditor later reads the decision time, person and reason beside the instruction and receipt rather than inferring approval from a status label alone.
What your team sees
- Review Queue — Instructions awaiting an independent decision with revision and owner in view.
- Authorized Instructions — Approved work ready for the provider handoff.
- Receipt Exceptions — Guarded actions whose recorded effects need attention.
Follow the work through
See instruction authorization for the review sequence and access roles for the authority split.
What it keeps track of
Data model- Review decisions
- Independent approver decisions recorded against a frozen instruction revision.
- Bank instructions
- Typed banking instructions moving through authorization, submission and confirmation.
- Team members
- Preparers, approvers, auditors and administrators working in the organization.
- Operation receipts
- Idempotent operation receipts with stable operation keys and actual effect references.
- Record attachments
- Supporting documents attached to a banking instruction.
Who uses it
Permissions- Independent Treasury Approver
- Decides the submitted revision.
- Treasury Preparer
- Supplies the instruction and evidence.
- Auditor
- Traces the decision; App Administrator maintains membership without taking the financial decision.
Set up Open Banking API Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.