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.
- Mobile Banking App Backend
- Features
- Accounts and counterparties
Accounts and counterparties
Keep the banking organizations, eligible counterparties and provider accounts in scope.
OverviewActive Financial Accounts×
Mobile Banking App Backend · Accounts and counterparties
New
Active Financial Accounts
Financial accounts
| Account code | Provider | External account ID | Currency | Owner | Active | |
|---|---|---|---|---|---|---|
| AC-390 | PRV-339 | EAI-647 | USD | FC-6472 | Yes | |
| AC-824 | PRV-680 | EAI-307 | EUR | FC-7297 | Yes | |
| AC-686 | PRV-564 | EAI-860 | GBP | FC-5734 | Yes | |
| AC-708 | PRV-107 | EAI-990 | CAD | FC-9728 | Yes | |
| AC-809 | PRV-250 | EAI-289 | JPY | FC-7342 | Yes |
6 of 6 records
AC-390Financial accounts · FA-54563
USDProviderPRV-339
External account IDEAI-647
OwnerFC-6472
ActiveYes
What you can do
Establish the account directory
The treasury team needs to know which organization owns a request, which counterparty handles it and which provider-held accounts are available. The directory links organizations to financial counterparties and counterparties to accounts. Account codes, external account identities, provider names and currencies help a preparer select the intended account before an instruction reaches review.
The App Administrator maintains organizational membership and the counterparty directory. A counterparty’s eligibility note records the basis for using it. Active flags distinguish current choices from historical ones. Historical instructions should continue to point to their original parties even when a counterparty or account stops accepting new work.
How the work is organized
- Organization scope. Each organization has a code, currency and time zone for its treasury work.
- Counterparty directory. Banks, custodians and settlement parties carry contact and eligibility details within an organization.
- Provider accounts. Each account belongs to a counterparty and has a provider identity, currency and active state.
Dated provider snapshots add a separate view of the account’s recorded ledger and available balances. They are observations at a point in time, not permission to submit a bank instruction. The team can inspect how a balance changed without overwriting an earlier provider snapshot.
What to agree during setup
Choose a clear owner for organization and counterparty maintenance. Agree how provider account identities will be checked before activation and how changes to a bank destination will be reviewed. Define which team members can see account details for each organization. Review time zones when using provider dates so a movement is compared with the intended calendar day.
Agree how snapshots arrive from each provider and how repeated snapshot identities are handled. Keep the source identity and as-of date with each observation. If an account becomes inactive, decide how existing reconciliation work is completed while preventing new instructions from using it.
Check the handoff on an actual case
The administrator adds an eligible banking counterparty to an organization, with its contact and eligibility note. A provider-held account is linked to that counterparty, with its account code, external identity and currency. A preparer selects the account for a new instruction and confirms it belongs to the expected organization and counterparty. The approver sees the same account scope when reviewing the instruction.
Next, an account snapshot arrives for that account. The reconciliation analyst compares its as-of date and balances with the prior snapshot and any open provider movements. Test an inactive account in a second case: it remains visible for audit and reconciliation, but should not be chosen for new work.
What your team sees
- Active Financial Accounts — Provider accounts available for current treasury scope.
- Current Counterparties — Eligible banking parties and their organizational ownership.
Follow the work through
What it keeps track of
Data model- Organizations
- Banking organizations whose treasury operations are run in this app.
- Financial counterparties
- Banks, custodians and settlement counterparties eligible for banking instructions.
- Financial accounts
- Provider-held financial accounts owned by a counterparty.
- Account snapshots
- Dated provider balance snapshots for a financial account.
- Team members
- Preparers, approvers, auditors and administrators working in the organization.
- Exchange rates
- Read-only effective exchange rates for this app.
Who uses it
Permissions- App Administrator
- Maintains organizations, counterparties and membership.
- Treasury Preparer
- Selects eligible accounts for instructions.
- Reconciliation Analyst
- Reads snapshots and account movements.
- Auditor
- Inspects historical scope.
Set up Mobile Banking App Backend your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.