Questions, answered

Click Get started, then use Proto to configure Treasury Operations for your business. Pilot one legal entity and two banks for one month. Run every instruction and deal through approval, submission, confirmation and reconciliation, and compare the results with your bank portals before adding entities.

A Treasury Approver in the same entity who did not prepare it. The decision is Approve, Reject or Return with a reason, against the exact revision.

The instruction is held as Pending and flagged for review. It is not sent again automatically; the settlement officer checks with the bank first.

Only when verified settlement or confirmation evidence from the bank is in.

Yes. Deals are recorded under the instruction that settles them, with instrument, trade date, notional and the counterparty’s confirmation, and complete on verified evidence.

No. Risk limits, market data and ALM analytics stay in your risk systems. Counterparty eligibility is recorded in each counterparty’s eligibility note.

Statement entries are matched exactly to confirmed instructions by provider identifier, amount and date. Anything that does not match becomes an exception to explain.

An instruction not yet sent is cancelled with a reason and kept on record. An instruction already sent or settled is reversed through an approved compensating instruction.

Prepare counterparties, accounts with provider identifiers, opening balances and open instructions. Rehearse one month and reconcile it before extending the migration.

Ordinary manual use has no per-user charge under the platform policy. Imports, integrations, agent execution and other machine work consume prepaid credits; implementation is scoped separately. The pricing page lists the current rates.