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
- Provider evidence
Provider evidence
Separate instruction submission from verified bank confirmation and settlement.
OverviewDraft Instructions×
Open Banking API Platform · Provider evidence
New
Draft Instructions
Review waits for the treasury preparer
| Record number | Subject | Amount USD | Requested at | Counterparty | |
|---|---|---|---|---|---|
| BI-77314 | Draft bi-243 | 280 | 27 Oct | FC-2218 | |
| BI-18852 | Draft bi-111 | 450 | 23 Oct | FC-5480 | |
| BI-12084 | Draft bi-364 | 90 | 12 Oct | FC-8419 | |
| BI-60490 | Draft bi-584 | 210 | 13 Oct | FC-3402 | |
| BI-55253 | Draft bi-860 | 760 | 15 Oct | FC-9202 |
6 of 6 records
Draft bi-243Bank instructions · BI-77314
Amount USD280
Requested at27 Oct
CounterpartyFC-2218
What you can do
Follow the provider outcome
An authorized instruction can be submitted to a banking provider. The provider’s instruction identifier connects the local record to the external request. Until confirmation or settlement evidence is verified, the team keeps the instruction visible as submitted or pending. This avoids treating a successful send as proof that the bank acted on the instruction.
The bank evidence record keeps a line and revision for each provider statement, confirmation, settlement notice or correction. It can retain the provider event identifier, occurrence time and amount. The verified flag tells the team which evidence has passed its check. The attachment record holds supporting documents, their upload time, visibility and uploader. Together these records let an Auditor reconstruct the provider-facing history without relying on a single status label.
How the work is organized
- Submission reference. The instruction retains the provider’s instruction identifier and current status.
- Bank events. The evidence record holds typed provider events, revisions and verification state.
- Supporting files. Each attachment connects a document to the instruction and person who uploaded it.
What to agree during setup
Agree which banking provider connection will submit instructions and how the provider’s instruction identifier returns to the team. Define which evidence types can support confirmation, who verifies them, and how a provider correction affects the running history. A correction should remain visible with the earlier evidence so the reviewer can understand the changed outcome.
Set a rule for attachment visibility. Internal material and shared material have different audiences, so the uploader should choose the correct visibility when adding a document. Decide who follows submitted work each day and how long an unresolved result stays in the provider outcome queue before escalation.
Check the handoff on an actual case
A Treasury Preparer submits an authorized instruction and records the provider reference. The instruction remains in the pending provider outcome list while the team waits. A settlement notice arrives with an event identifier and occurrence date. The Independent Treasury Approver compares that event with the instruction, amount and provider reference, then marks the bank evidence verified when the check succeeds. Only then does the team treat the instruction as confirmed and record its confirmation date. If a later correction arrives, the new bank evidence line points back to the same instruction and remains available for review.
What your team sees
- Pending Provider Outcomes — Submitted instructions still awaiting a verified bank result.
- Verified Bank Evidence — Checked provider events grouped by their parent instruction.
- Authorized Instructions — Work ready for provider submission.
Follow the work through
See provider outcome and account reconciliation for the next handoffs.
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.
- Record attachments
- Supporting documents attached to a banking instruction.
- Operation receipts
- Idempotent operation receipts with stable operation keys and actual effect references.
Who uses it
Permissions- Treasury Preparer
- Submits and follows assigned work.
- Independent Treasury Approver
- Checks provider evidence.
- Auditor
- Reads the event and attachment trail.
Set up Open Banking API Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.