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
- Who it's for
- Custody operations
Custody operations
A custody operations group works with accounts held by external financial counterparties. The account code, external identifier, provider, currency and owner relationship matter when an instruction is prepared. Core Banking System keeps these identities with the instruction's debit and credit scopes, so an approver can inspect the intended accounts before submission and an investigator can locate the same accounts during reconciliation.
How Core Banking System is set up for you
Counterparty setup
The administrator maintains active provider relationships, contacts and eligibility notes for the operating organization.
Account selection
The preparer chooses the correct provider-held account for each direction. An inactive account remains visible in historical work while new requests use current scope.
Dated balances
Provider snapshots retain the ledger and available amounts with their effective date and provider snapshot identifier.
Movement review
Reconciliation items retain the provider event identity and account. Matching requires the confirmed instruction's amount and occurrence date to agree as well.
A custody operations group works with accounts held by external financial counterparties. The account code, external identifier, provider, currency and owner relationship matter when an instruction is prepared. Core Banking System keeps these identities with the instruction's debit and credit scopes, so an approver can inspect the intended accounts before submission and an investigator can locate the same accounts during reconciliation.
Select one custodian and a representative set of active accounts. Verify their external identifiers against the provider's source material before drafting an instruction. Walk an approver through a transfer with balanced account scopes and an attached request. Import a provider snapshot and several movements, including one whose amount matches but account does not. Keep that movement open and document how the team obtains a correction from the provider. Agree who owns master-data changes, because a renamed account must not break the historical chain of instructions and snapshots.
Features to start with
Roles on the team
- 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.
- App Administrator
- Maintain organization configuration and membership. Administrative membership does not confer approval, financial or execution authority and cannot grant an independent reviewer entitlement.
- Auditor
- Read authorized evidence and reports in a scoped, read-only audit view. No record writes and no action execution.
Set up Core Banking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.