Treasury Exposure

Overview

Treasury exposure is the financial and operational risk created by assets, liabilities, counterparties, currencies, networks, custodians, settlement delays, and liquidity commitments held or managed by an organization’s treasury function. For teams linking Treasury Exposure to Net Exposure, limits, independent pricing, concentration monitoring, liquidity assumptions, stress testing, and breach escalation should be documented and reconciled to source records. Within Treasury Exposure, and especially at the boundary with Position, analysis should distinguish gross, net, realized, unrealized, liquid, restricted, and stressed values and preserve the valuation time and source.

The workflow for Treasury Exposure commonly touches Net Exposure and Position. Documenting those handoffs keeps duplicate events, delayed updates, and manual corrections for Treasury Exposure traceable to the correct object.

Measurement for Treasury Exposure should begin with a documented scope and valuation time. When Treasury Exposure interacts with Net Exposure, assets, liabilities, derivatives, reserves, pending settlements, fees, and contingent obligations may require different price sources, liquidity assumptions, legal treatment, and settlement horizons. In the relationship between Treasury Exposure and Position, gross, net, realized, unrealized, and stressed views answer different questions and should not be combined without explaining offsets and dependencies.

For Treasury Exposure, crypto-related positions need representation-level detail. When Treasury Exposure interacts with Net Exposure, native assets, wrapped tokens, exchange balances, stablecoin claims, bridge-issued assets, and custodied holdings can share a ticker while carrying different counterparties and exit paths. In the relationship between Treasury Exposure and Position, records should retain venue, network, contract, custodian, issuer, maturity or unlock conditions, collateral, and the rate used for reporting.

Controls for Treasury Exposure should define ownership, limits, independent pricing, conservative haircuts, concentration thresholds, stress scenarios, approval levels, and breach escalation. When Treasury Exposure interacts with Net Exposure, reconciliation should connect reported exposure to ledgers and external statements, while scenario analysis should test correlated failures such as depeg, exchange suspension, bridge outage, network congestion, and unavailable collateral.

Treasury Exposure can appear in the same workflow as Treasury and network congestion, but the records should remain separately identifiable. A relationship between them does not prove that pricing, execution, settlement, custody, or accounting has completed.