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.
- Treasury Operations
- Implementation and migration
How a Treasury Operations rollout works
Start with one legal entity and two banks for one month your preparers, approvers and analysts can reconcile together.
Agree the operating boundary
The app runs counterparties and accounts, bank instructions, independent authorization, settlement evidence, treasury deals and bank reconciliation. Bank connectivity, trading platforms, market data, risk analytics, cash forecasting and the general ledger remain connected systems. Your approvers decide authorizations; Proto prepares information and configuration for review.
Map the source data
Gather entities, counterparties with eligibility, accounts with provider identifiers, opening balances, open instructions and deals, and sample statements.
Configure a bounded pilot
Pilot one legal entity and two banks for one month. Run every instruction and deal through approval, submission, confirmation and reconciliation.
Rehearse the exceptions
A preparer must not approve their own instruction. A timed-out submission must be held as Pending and never resubmitted automatically. A statement entry with a different amount must stay an exception. A confirmed instruction must be corrected only through an approved compensating instruction.
Reconcile and release
Compare confirmed movements and closing balances with the bank portals. Obtain sign-off from the Treasury Manager and the approvers, keep an export of the source and agree the rollback window before cutover.
What the customer provides
- Legal entities with time zone and base currency, and the users for each team member.
- Counterparties with codes, contacts and eligibility notes.
- Treasury accounts with provider, external account identifier, currency and opening balance.
- Open instructions and deals, and sample statements and confirmations from each bank.
Changing it afterwards
Use Proto to prepare changes on a branch. Review the changed fields, affected permissions, import mappings and reports with their owners. Replay the pilot’s exception cases before release. Past decisions keep the revision they were made on.
Set up Treasury Operations your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.