Reserve Policy

Overview

Reserve Policy is the documented framework governing the purpose, composition, liquidity, custody, limits, use, and oversight of financial reserves. It sets governance and risk rules; the reserve itself is the pool of assets held under those rules.

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

When Reserve Policy informs a trade, payment, or treasury decision, teams should retain legal entity, account or wallet, asset and currency, liability, availability state, valuation time, policy limit, decision owner, and resulting ledger entry. Each update should have an effective time and source, allowing later events to amend the position without erasing the earlier state.

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

A reliable review of Reserve Policy starts with the specific distinction in the definition: It sets governance and risk rules; the reserve itself is the pool of assets held under those rules. This prevents a related quote, balance, order status, or provider response from being treated as proof of the final economic outcome.

Control evidence for Reserve Policy should cover entity, account, asset, liability, availability state, valuation time, policy limit, owner, and ledger effect. The definition also indicates that in production, teams should define the authoritative record, identifiers, ownership, lifecycle rules, and evidence used to confirm the outcome. Keeping these details together makes later reconciliation and performance comparison possible without rewriting the original record.

The main control tests should cover stale positions, hidden restrictions, concentration, mismatched currencies, unavailable funds, valuation error, and unrecorded liabilities. Both normal and stressed scenarios matter because an apparently available price, balance, venue, or settlement route may fail when the transaction is actually attempted.