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
- Provider outcomes
Provider outcomes
Keep provider references, evidence and operation receipts with the instruction.
OverviewAuthorized instructions×
Financial Risk Management · Provider outcomes
New
Authorized instructions
Submission waits for the treasury preparer
| Record number | Subject | Status | Amount USD | Revision | Counterparty | |
|---|---|---|---|---|---|---|
| BI-12220 | Authorized bi-523 | Authorized | 550 | 480 | FC-9520 | |
| BI-87193 | Authorized bi-351 | Authorized | 20 | 90 | FC-8258 | |
| BI-16760 | Authorized bi-467 | Authorized | 500 | 310 | FC-6557 | |
| BI-94260 | Authorized bi-156 | Authorized | 70 | 280 | FC-8542 | |
| BI-28376 | Authorized bi-323 | Authorized | 470 | 80 | FC-5931 |
6 of 6 records
Authorized bi-523Bank instructions · BI-12220
AuthorizedAmount USD550
Revision480
CounterpartyFC-9520
What you can do
Treat the provider response as its own event
An Authorized banking instruction can be submitted to a provider. The banking instruction record keeps the provider instruction identifier and the current status. The bank evidence register holds statements, confirmations, settlement notices and corrections related to that instruction. These records let the team distinguish a request it sent from a result the provider actually confirmed.
For an instruction submitted late in the day, a provider identifier may arrive before settlement evidence. Treasury Preparer records the identifier and follows the instruction while it is Submitted or Pending. A confirmation or settlement event with a provider event identifier, occurrence date and verified flag gives Independent Treasury Approver a basis to accept the outcome. A provider message that only acknowledges receipt should not make the instruction Confirmed.
How the work is organized
- Submission. Keep the provider reference on the instruction and the attempt in an operation receipt.
- Observation. Add provider evidence with its event identity, type, amount, time and verification result.
- Completion. Compare recorded effects with the receipt before treating an operation as completed.
The operation receipt records a stable operation key, expected revision, action and result state. It also retains effect references or a failure reason. When a request times out, the team can inspect the existing receipt and provider reference before trying again. A retry should resolve the original attempt rather than creating a second financial effect. Needs review identifies a concrete discrepancy that someone must investigate.
What to agree during setup
Identify the provider source for confirmations and settlement notices. Decide which events count as verified evidence and who checks that determination. Agree how corrections are recorded without deleting the earlier provider event. Preserve the event identifier and occurrence date in a consistent format so reconciliation can compare it with the related instruction.
Set ownership for uncertain provider responses. A technical transport success is different from a confirmed financial outcome. A failed receipt and a pending provider instruction should lead to investigation of the existing request, not an immediate new submission. Decide when Treasury Preparer escalates to Independent Treasury Approver and what Auditor needs to see later.
Check the handoff on an actual case
Take an Authorized instruction and submit it through the agreed provider connection. Record the provider identifier. Check that the provider acknowledgement leaves the instruction in a waiting status. Add a verified confirmation with the correct amount and occurrence date, then inspect the status and linked evidence. The owner should be able to trace the same record number from preparation through the provider event.
Rehearse an uncertain response. Leave its receipt Pending until the actual local effect is checked. If the claimed effect is absent or inconsistent, record needs review with the discrepancy. Do not issue another provider request simply because the receipt has not yet been marked Completed. This case tests the difference between an attempted operation and a verified one.
What your team sees
- Provider outcome queue — Submitted and pending instructions with the provider identifier available for follow-up.
- Receipts needing review — Attempts whose recorded effects need inspection or correction.
Follow the work through
See provider outcome, receipt verification and integrations.
What it keeps track of
Data model- Bank instructions
- Typed banking instructions moving through authorization, submission and confirmation.
- Bank evidence
- Provider statements, confirmations, settlement notices and corrections for an instruction.
- Operation receipts
- Idempotent operation receipts with stable operation keys and actual effect references.
- Review decisions
- Independent approver decisions recorded against a frozen instruction revision.
- Reconciliation items
- Source-identified provider movements matched against banking instructions.
Who uses it
Permissions- Treasury Preparer
- Follows the provider reference and collects evidence.
- Independent Treasury Approver
- Can inspect the verified outcome.
- Auditor
- Inspects the operation and evidence trail.
- App Administrator
- Maintains access and provider setup.
Set up Financial Risk Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.