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.
- Neobank Backend
- Features
- Provider execution
Provider execution
Track authorized instructions through submission and verified provider outcome.
OverviewConfirmed Instructions×
Neobank Backend · Provider execution
New
Confirmed Instructions
Bank instructions
| Record number | Subject | Status | Confirmed at | Amount USD | Counterparty | |
|---|---|---|---|---|---|---|
| BI-48434 | Confirmed bi-105 | Confirmed | 08 Oct | 820 | FC-9389 | |
| BI-21978 | Confirmed bi-303 | Confirmed | 13 Oct | 30 | FC-6023 | |
| BI-55962 | Confirmed bi-548 | Confirmed | 27 Oct | 650 | FC-6789 | |
| BI-69732 | Confirmed bi-322 | Confirmed | 18 Oct | 800 | FC-5206 | |
| BI-90518 | Confirmed bi-991 | Confirmed | 16 Oct | 300 | FC-2867 |
6 of 6 records
Confirmed bi-105Bank instructions · BI-48434
ConfirmedConfirmed at08 Oct
Amount USD820
CounterpartyFC-9389
What you can do
Run the work
A reviewed instruction is ready to be sent to its banking provider. The preparer records the provider identifier once submission occurs and follows the case while provider confirmation is outstanding. A confirmation or settlement record is checked before the instruction is marked confirmed. Submission starts from an authorized instruction. Treasury Preparer records the provider instruction identifier and retains an operation receipt for the action. A submitted or pending instruction remains open while the provider response is outstanding. Confirmation requires provider evidence marked verified and typed as a confirmation or settlement; a statement or an unverified event does not settle the case.
How the work is organized
- Submit reviewed scope. Compare the authorized revision with the amount and account lines sent to the provider.
- Keep the provider reference. Record its instruction identifier and the operation receipt under the parent case.
- Verify the outcome. Link the provider event to the instruction and check its type and verified flag before confirmation.
What to agree during setup
Agree which provider event establishes confirmation and who verifies it. Set the source for statements, confirmations, settlements and corrections. Choose how the team handles a provider response that arrives after the requested value date or repeats an earlier event identifier. Agree who receives the provider response and who verifies its event identifier, type and status. Rehearse a delayed response and a repeated event. Compare the receipt with the recorded provider identifier before any investigation of an interrupted action.
Check the handoff on an actual case
Send an authorized rehearsal instruction through the configured provider connection. Record the resulting provider identifier. Keep one case pending until verified evidence arrives, then compare its amount and occurrence date with the instruction and inspect the operation receipt for the action. Ask the next person to find the parent case and explain its status from the linked records. If a receipt is unclear, compare its claimed effects with persisted records before closing the investigation. If the provider sends a correction after confirmation, retain both events on the instruction. The team can then inspect the order of events and the verified flag before deciding what follow-up is needed.
What your team sees
- Provider Pending Instructions — Find submitted and pending cases awaiting provider evidence.
- Confirmed Instructions — Trace completed cases to their provider event and confirmation date.
Follow the work through
See provider outcome for the provider handoff and bank reconciliation for the movement that follows.
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.
- Financial counterparties
- Banks, custodians and settlement counterparties eligible for banking instructions.
Who uses it
Permissions- Treasury Preparer
- Owns preparation and provider follow-up.
- Independent Treasury Approver
- Makes independent decisions.
- Auditor
- Reviews the resulting evidence in assigned scope.
- App Administrator
- Maintains organization membership and configuration.
Set up Neobank Backend your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.