Treasury Mandate

Overview

Treasury Mandate is the formally approved statement of a treasury function’s objectives, permitted activities, asset universe, risk limits, authorities, and reporting duties. It defines what treasury may do and under which constraints, while individual procedures explain how approved activities are executed.

Treasury Mandate is closely connected to Treasury Risk Management, Reserve Policy, and Crypto Allocation. These concepts can appear in the same workflow, but they represent different records, decisions, controls, or stages.

Treasury Mandate can appear in the same workflow as Treasury Risk Management, Reserve Policy and Crypto Allocation, but the records should remain separately identifiable. A relationship between them does not prove that pricing, execution, settlement, custody, or accounting has completed.

The practical boundary of Treasury Mandate follows directly from its definition: It defines what treasury may do and under which constraints, while individual procedures explain how approved activities are executed. A system should therefore keep the market observation, operational action, and final financial result as separate records when they occur at different times.

Teams applying Treasury Mandate should retain entity, account, asset, liability, availability state, valuation time, policy limit, owner, and ledger effect. A further point from the source definition is that in production, teams should define the authoritative record, identifiers, ownership, lifecycle rules, and evidence used to confirm the outcome. These fields help distinguish an expected timing difference from a real pricing, execution, liquidity, or settlement break.

Risk review should test for stale positions, hidden restrictions, concentration, mismatched currencies, unavailable funds, valuation error, and unrecorded liabilities. Exceptions should remain open until the evidence supports closure, and any manual adjustment should record its reason, approval, and resulting financial effect.