Board reporting for a Bitcoin treasury should answer one question: is the holding operating within the limits and controls the board approved? The right KPIs cover the position, headroom against limits, execution quality, custody health and the effectiveness of controls. Each needs a clear definition, a source and a threshold, so directors see exceptions rather than raw data.
External disclosure is a different exercise, covered in communicating a Bitcoin strategy to investors. This article is about what the board and its committees should see internally.
Principles for Bitcoin treasury board reporting
- Report against the policy. Every limit in the treasury policy should have a matching KPI.
- Show thresholds, not just numbers. Use a simple status, such as within limit, approaching limit, or breach.
- Keep it stable. Use the same KPIs, definitions and order every period. Changing the format makes trends harder to see and can look selective.
- Separate value from control. Market value moves are reported, but the board's main concern is whether controls are working.
- One page first. A single summary page, with detail in an appendix.
Position KPIs
These describe what the company holds.
- Bitcoin held (units). The most stable measure of the position, unaffected by price.
- Cost basis. Total cost, using the method stated in the policy.
- Fair value at period end. Using the policy's pricing source and time.
- Unrealised gain or loss. Fair value less cost.
- Movement in the period. Purchases, sales, fees and transfers, in units and value, reconciled from opening to closing.
The roll-forward ties to the accounting records and to the disclosures required under ASU 2023-08 where it applies. See Bitcoin disclosure requirements.
Limit and liquidity KPIs
These show whether the company is inside its approved boundaries.
- Holding as a share of treasury assets, measured on the policy basis, against the limit.
- Cash floor cover, in months of operating costs, against the minimum.
- Largest single-custodian share of holdings.
- Peak pre-funded exposure to any one liquidity provider during the period.
- Drawdown from cost, against the trigger levels in the policy.
Report headroom as well as the level. "Holding is 3.8% against a 5% limit" is more useful than "3.8%".
Execution KPIs
For periods with trading activity, the board should see whether trades were well executed.
- Number and size of trades.
- Number of quotes obtained against the policy minimum.
- Execution cost against a stated benchmark, such as a reference price at the time of the order. See slippage and market impact.
- Settlement time from trade to receipt in custody.
- Settlement exceptions, such as delays or failed transfers.
Custody and control KPIs
These are often left out, and they are the ones most likely to reveal a developing problem.
- Reconciliation status. Whether holdings agreed to custodian statements and on-chain records at period end, and the number of unresolved differences.
- Access review. Date of the last review of signers and portal users.
- Recovery test. Date of the last successful recovery or continuity test.
- Whitelist changes. Number of addresses added or removed, all with dual approval.
- Screening alerts. Number raised and how they were resolved. See sanctions screening.
- Provider reviews. Any provider overdue for its scheduled due diligence review.
- Policy exceptions and breaches. Number open, with age.
- Security incidents and near misses.
Include the date of the last recovery test on the summary page. It is the single number that best tells a board whether the company could actually access its Bitcoin if a key person or provider became unavailable.
A one-page summary layout
The table below shows an illustrative layout. Figures and thresholds are placeholders for each company to set in its own policy.
| KPI | This period | Threshold | Status |
|---|---|---|---|
| Bitcoin held (units) | [X] | n/a | Information |
| Holding as % of treasury assets (cost) | [X]% | Limit [Y]% | Within limit |
| Cash floor cover (months) | [X] | Minimum [Y] | Within limit |
| Largest custodian share | [X]% | Maximum [Y]% | Approaching limit |
| Drawdown from cost | [X]% | Trigger [Y]% | Within limit |
| Quotes obtained on trades above threshold | [X] of [Y] | All trades | Breach: 1 trade |
| Unresolved reconciliation differences | [X] | Zero | Within limit |
| Days since last recovery test | [X] | Maximum 365 | Within limit |
| Open policy exceptions | [X] | Zero over 30 days | Within limit |
Below the table, add three short items: what changed, any breach and its resolution, and any decision the board is asked to make.
Frequency and audience
| Audience | Frequency | Content |
|---|---|---|
| CFO and treasury | Monthly | Full KPI set and appendix |
| Audit or risk committee | Quarterly | Summary page, exceptions, risk register changes |
| Full board | Quarterly or each meeting | Summary page and any decisions required |
| Board, ad hoc | On trigger | When a policy trigger or breach occurs |
Align the timing with the month-end close so the figures match the accounts. If the treasury is small and inactive, a shorter report is fine, but keep the control KPIs.
Keeping the report reliable
- Name a preparer and a reviewer, from different teams.
- Source every KPI from a system or document, not a manual estimate.
- Link each KPI to its policy clause and to the related entry in the Bitcoin risk register.
- Keep prior reports so trends can be checked by internal audit.
How The Bitcoin World helps
We design board and committee reporting packs for Bitcoin treasuries, mapped to the company's policy limits and controls, as part of our corporate treasury work. Execution and custody are carried out by licensed third-party institutions.