Treasury automation authority

Reserve shared limit atomically and require dual approval above threshold

01 / Operational model

Who acts, and what changes?

Principal and authority origin

A cash-management agent. Board-approved treasury policy and named liquidity task.

Consequential action

Initiate an intercompany transfer.

02 / Action-time control

Make the requested effect testable.

Entity pair, account, amount, daily aggregate limit and segregation of duties. Reserve shared limit atomically and require dual approval above threshold.

OriginBoard-approved treasury policy and named liquidity task
RequestInitiate an intercompany transfer
DecisionEvaluate and enforce before effect

03 / Evidence and responsibility

Permission, execution, and outcome are separate.

Limit ledger, approver identities, transfer decision and bank-confirmed posting.

Treasury policy, bank controls and financial reconciliation remain customer-owned.

Primary source

Check the governing material.

Architecture discussion

Map one consequential action from origin to observed outcome.

Request a Conversation