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.
- Core Banking System
- Features
- Provider accounts
Provider accounts
Maintain provider-held account identities and the counterparties behind them.
OverviewActive Provider Accounts×
Core Banking System · Provider accounts
New
Active Provider Accounts
Financial accounts
| Account code | Provider | External account ID | Currency | Owner | |
|---|---|---|---|---|---|
| AC-444 | PRV-521 | EAI-697 | USD | FC-5286 | |
| AC-301 | PRV-329 | EAI-565 | EUR | FC-5756 | |
| AC-363 | PRV-645 | EAI-918 | GBP | FC-8403 | |
| AC-354 | PRV-120 | EAI-965 | CAD | FC-2654 | |
| AC-588 | PRV-138 | EAI-157 | JPY | FC-6806 |
6 of 6 records
AC-444Financial accounts · FA-61818
USDProviderPRV-521
External account IDEAI-697
OwnerFC-5286
What you can do
Keep the account scope usable
Financial accounts identify the provider, external account identifier, account code, currency and counterparty owner. They are the account scopes selected on a banking instruction and the account anchor for snapshots and reconciliation movements. The Active value determines whether an account remains available for new operational work. Historical instructions and evidence still need to point to the same account after it becomes inactive.
Financial counterparties carry the name, code, contact and eligibility note for a bank, custodian or settlement relationship. The App Administrator maintains the organization and its counterparties. The Treasury Preparer uses that setup when preparing an instruction. The counterparty on the instruction should correspond to the provider-held accounts used for its debit and credit scopes. A familiar account code alone is insufficient when the external account identifier or owner differs.
How the work is organized
- Organizations. The administrator keeps each operating organization active with its currency and time zone.
- Counterparties. The administrator records eligible relationships and contact details before preparers use them.
- Accounts. The team tracks active provider-held accounts, their external identifiers and their dated balance snapshots.
What to agree during setup
Identify the source of truth for each provider account identifier and the person who can confirm changes to it. Agree how inactive accounts are treated in new instructions and how historical movements remain visible. Decide the provider cadence for dated snapshots; a balance from a prior date should be shown with its date rather than presented as the current position. Set the organization’s currency and time zone before importing provider events, since date comparison is important to reconciliation.
For example, a treasury group may have two accounts at one custodian and another at a settlement bank. The preparer selects the correct accounts by their external identifiers and checks the currencies and owner relationship. An account snapshot captures the provider’s ledger and available amounts as of its recorded date. If a later provider movement is attributed to the wrong account, reconciliation keeps it as an exception until the account identity is corrected from source evidence.
Check the handoff on an actual case
Import a small set of counterparties and active accounts, then prepare an instruction that uses both debit and credit scopes. Trace each scope to its account and owner. Mark one account inactive and confirm it no longer appears in the new-work selection while prior instructions and snapshots remain inspectable. Compare two dated snapshots for one account; the team should be able to tell which balance belongs to which provider snapshot identifier and date. Review who can edit the master records and who may only view them.
What your team sees
- Active Provider Accounts — Check account identities and currencies before assigning them to an instruction.
- Reconciliation Exceptions — See movements whose account or other matching evidence needs attention.
Follow the work through
Read instruction preparation and bank reconciliation.
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.
- Instruction accounts
- Debit and credit account scopes that make an instruction balanced.
- Reconciliation items
- Source-identified provider movements matched against banking instructions.
- Exchange rates
- Read-only effective exchange rates for this app.
Who uses it
Permissions- App Administrator
- Maintains organization and counterparty setup.
- Treasury Preparer
- Uses accounts for draft instructions.
- Independent Treasury Approver
- Checks account scope during review.
- Auditor
- Inspects historical balances and relationships.
Set up Core Banking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.