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
- Who it's for
- Treasury teams
Treasury teams
Treasury teams need a consistent way to prepare banking work, separate the decision from preparation and follow the bank's response. The instruction record connects the organization, counterparty, owner, amount and account scope. The review decision and provider evidence make each handoff visible.
How Open Banking API Platform is set up for you
Central treasury
Use the organization and team-member relationships to keep each instruction in the right operating scope. A preparer works assigned drafts while an independent approver decides the submitted revision.
Settlement operations
Keep the eligible settlement counterparty and provider accounts beside the requested movement. Track the provider's instruction identifier until confirmation or settlement evidence is checked.
Audit team
Read the decision, bank evidence, attachment and receipt trail for a specific instruction rather than relying on a summary status alone.
Treasury teams need a consistent way to prepare banking work, separate the decision from preparation and follow the bank's response. The instruction record connects the organization, counterparty, owner, amount and account scope. The review decision and provider evidence make each handoff visible.
Start with one organization and one provider relationship. Register the counterparty and its active financial accounts, then choose a narrow instruction type for the first operating cycle. Agree who prepares, who independently reviews and who follows unresolved provider results. Rehearse an authorized instruction that remains pending until a checked provider event arrives. Include a rejected request so the team can see how the reason stays attached to its source revision.
Once that handoff is clear, add account snapshots and provider movements for reconciliation. The first reconciliation should include a movement that matches exactly and one with a date or amount difference. That contrast helps the team agree how exceptions are investigated. Review the operation receipt with the instruction to confirm that claimed effects can be found in the actual records.
Features to start with
Reconciliation and receipts
Compare provider movements with confirmed instructions and verify each recorded operation.
Financial accounts
Tie provider accounts and balanced debit and credit scopes to each bank instruction.
Independent review
Record who decided, which revision they saw and why they chose the outcome.
Roles on the team
- Auditor
- Read authorized evidence and reports in a scoped, read-only audit view. No record writes and no action execution.
- App Administrator
- Maintain organization configuration and membership. Administrative membership does not confer approval, financial or execution authority and cannot grant an independent reviewer entitlement.
- Independent Treasury Approver
- Review eligible instruction revisions independently and reconcile operational evidence. Approve or reject through guarded actions only; no unrestricted editing of protected or executed records; a reviewer cannot approve their own submission.
- Treasury Preparer
- Prepare assigned operational records and execute eligible reviewed actions. Own organization and draft scope only; accepted, posted and provider evidence is read-only; guarded workflows authorize every transition.
Set up Open Banking API Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.