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.
- Treasury Bills & Bonds
- Features
- Review Queue
Review Queue
Record an independent approver's decision on the exact version of each instruction and cash flow.
OverviewReview Decisions Log×
Treasury Bills & Bonds · Review Queue
New
Review Decisions Log
Review decisions
| Parent | Source revision | Decision | Reason | Reviewer | Decided at | |
|---|---|---|---|---|---|---|
| BI-81184 | 350 | Approve | Approve rd-146 | 09 Oct | ||
| BI-19082 | 400 | Return | Reject rd-920 | 14 Oct | ||
| BI-37944 | 570 | Approve | Return rd-905 | 06 Oct | ||
| BI-70934 | 20 | Return | Approve rd-959 | 13 Oct | ||
| BI-92906 | 510 | Approve | Reject rd-986 | 20 Oct |
6 of 6 records
Approve rd-146Review decisions · RD-48187
ApproveParentBI-81184
Source revision350
Decided at09 Oct
What you can do
Approve what was submitted, by someone else
No instruction should leave treasury on one person’s word. A review decision records the outcome (Approve, Reject or Return), the reason, the approver, the time and the version number it applies to. The approver is a different team member from the preparer, in the same entity.
Before approving, the approver checks the mandate, the amount, the value date and that the debit and credit lines balance. If the instruction changes after submission, the earlier decision no longer applies and the new version waits for its own review. Coupon and maturity reconciliations go through the same queue.
How the work is organized
- Approve. The instruction becomes Authorized, or the cash flow Approved, and the decision is kept with its reason.
- Return. The work goes back to the preparer with a reason, for a revised version.
- Reject. The work stops, with the reason recorded.
What to agree during setup
Name the approvers and their deputies, and confirm no one approves their own instruction. Agree the approval limits by amount or instruction type, and what evidence the approver needs: the trade ticket, auction result or board mandate. Decide the turnaround needed to meet bank cut-offs.
Check the handoff on an actual case
A preparer submits an instruction to buy $2,000,000 of a two-year note through a broker-dealer for settlement tomorrow. The Treasury Approver opens the instruction and sees the debit line is on the payroll account, which the mandate does not allow for investments. She returns it with that reason.
The preparer moves the debit to the investment operating account and resubmits. The approver checks the new version, sees the lines balance and the mandate is attached, and approves it. The decision records the version, reason and time, and the earlier return stays in the log.
What your team sees
- Awaiting Action — Instructions waiting at each step, including those in review.
- Cash Flows Awaiting Approval — Submitted coupon and maturity reconciliations for the approver.
- Review Decisions Log — Every decision with reason, approver and version.
Follow the work through
- Instruction to settlement: See where approval sits before submission.
- Coupon and maturity reconciliation: Approve a coupon or maturity against custodian evidence.
Rehearse access with a preparer account before go-live.
What it keeps track of
Data model- Review decisions
- Independent approver decisions recorded against an exact instruction revision.
- Bank instructions
- Typed banking instructions raised by treasury and authorized by an independent approver.
- Security cash flows
- Scheduled coupon and maturity cashflows for held bills and bonds, reconciled against custodian receipt.
- Team members
- Named treasury staff with an authenticated platform identity and role scope.
Who uses it
Permissions- Treasury Approver
- , Treasury Preparer, Admin.
- The Treasury Approver decides.
- The Treasury Preparer prepares and resubmits.
- Admin
- Keeps team members and entity scope current.
Set up Treasury Bills & Bonds your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.