Crypto Treasury KPIs: The Five-to-Seven That Govern, Not Decorate

Most crypto treasury dashboards fail the same way: thirty metrics, none of them acted on. Governance comes from the few numbers that answer solvent? liquid? within policy? This guide is that focused set — and why their targets are yours to set, not ours to assert.

TL;DR

• Keep the headline set small (~5-7 strategy-linked KPIs) — thirty metrics govern nothing.
• Core KPIs: runway / days cash, liquidity coverage, concentration vs policy limits, realised vs unrealised, mark-to-market volatility.
• Thresholds are organisation-set, not universal crypto rules — bands here are illustrative.
• MTM volatility matters under fair value (ASU 2023-08) — value/earnings move with price.
• KPIs are the instrument panel for the policy — an out-of-band KPI is a policy exception.
• Feeds the board report; built on reconciled accounting.

Few, or none get used

Common treasury-dashboard guidance: keep the headline set small — on the order of five to seven metrics tied directly to strategy and risk. A dashboard with thirty numbers governs nothing because no one acts on it. The discipline is choosing the handful that answer "are we solvent, liquid, and within policy?" — not maximising metric count. More KPIs is worse governance, not better.

The core set

Together: solvency, liquidity, policy adherence, risk. That is the whole job.

Thresholds are yours, not universal

General corporate finance offers rules of thumb (minimum days-cash bands, liquidity-coverage ranges). Those are organisation- and risk-tolerance-specific and must not be asserted as crypto standards. A treasury sets its own thresholds in policy from its runway needs, volatility tolerance, and obligations. The KPI is the measure; the target is a policy decision. Any band quoted in a guide (including this one) is illustrative, never a rule.

Why MTM volatility is a KPI

Under fair-value accounting (in-scope crypto under ASU 2023-08) and at portfolio level, the treasury's reported value and earnings move with crypto price every period. A volatility KPI tells the board how exposed the reported position is to price swings — informing covenant headroom and risk tolerance. Without it, the board sees a number without knowing how much it can move — the realized-vs-unrealized distinction made into a governance metric.

KPIs are the policy's instrument panel

Concentration-vs-limits, runway, liquidity-coverage KPIs are direct readings of whether the policy's limits and liquidity floor are met. An out-of-band KPI is a policy exception, not just a number — it should trigger the same escalation as a breach. KPIs without a policy to measure against are decoration; a policy without KPIs is unenforceable. They only work as a pair.

Practical guidance

1. Cap the headline set at ~5-7 strategy-linked KPIs.
2. Track the core five: runway, liquidity coverage, concentration-vs-limits, realised/unrealised, MTM volatility.
3. Set thresholds in policy — do not import a generic band as a crypto rule.
4. Treat an out-of-band KPI as a policy exception — escalate.
5. Build KPIs on reconciled accounting — not raw balances.
6. Feed them into the board report; review targets periodically.

How vendor tools support treasury KPIs

Cryptio and Request Finance compute treasury metrics from reconciled positions. Confirm the tool measures concentration against your policy limits and realised vs unrealised distinctly, and lets you set your own thresholds — a fixed, vendor-default KPI band is not your policy.

How Wag3s helps

Wag3s Ledger computes the core treasury KPIs — runway, liquidity coverage, concentration against your policy limits, realised vs unrealised, MTM volatility — from reconciled, audit-trailed positions, with organisation-set thresholds and out-of-band exception flags feeding the board report. See the Ledger product page and the Wag3s for accountants page.

Further reading

• Crypto Treasury Board Reporting
• Crypto Treasury Accounting Policy
• Crypto Treasury Segregation of Duties
• Stablecoin Treasury Policy
• Realized vs Unrealized Gains in Crypto
• Crypto Treasury Yield Strategy

Sources

• Treasury-dashboard best practice: keep the headline set focused (~5-7 strategy-linked KPIs); core liquidity metrics = days cash / runway, liquidity coverage (liquid assets vs outflows)
• KPI thresholds are organisation- and risk-tolerance-specific (general corporate-finance rules of thumb exist but are not universal crypto standards — bands illustrative, set in policy)
• MTM volatility relevant under fair-value accounting (ASU 2023-08) and at portfolio level; KPIs are the measurement layer for the treasury policy (out-of-band = policy exception)