On-chain treasury: a CFO's framework

The treasury function exists to make sure the business never runs out of money. That definition is intact. What has changed is the set of instruments the function is allowed, expected, or required to hold to perform it. A balance sheet that includes a native token, a stablecoin position, or any other on-chain asset is not a balance sheet that needs a new treasury function. It is a balance sheet that needs a treasury policy adequate to the assets it actually holds.

Most policies are not. They were written for cash, deposits, money market funds, and a thin layer of FX hedging. They presume a counterparty for every position and a banking system that catches errors. On-chain assets do not behave that way. The framework below is what a senior finance leader uses to bring an on-chain treasury inside the same discipline that governs the rest of the balance sheet.

The treasury function the new asset class is testing

Three properties of on-chain assets stress-test a conventional treasury policy. Settlement is fast and final. Custody is cryptographic rather than contractual. Pricing is continuous and venue-dependent. None of these properties are bad. They are simply not what existing policy was written to handle.

The mistake is to treat the gap as a technology problem. It is a controls problem with technology dependencies. The CFO who delegates the entire question to the engineering team will get a custody arrangement that works operationally and fails audit. The CFO who delegates it to the auditors will get a controls memo that does not survive contact with a live transaction.

Four questions that resolve most edge cases

Before any document is drafted, four questions narrow the policy space considerably.

• What is the asset for? A token held to fund retirement events, a stablecoin held to settle international payables, and a native token held as a reserve asset are three different positions with three different policies. Collapsing them into a single "crypto holdings" line will produce a policy that fits none of them.
• Who controls it? If the answer is a single individual with a hardware wallet, the policy must say so, the audit committee must know, and the succession plan must exist. If the answer is a multi-signature arrangement or a qualified custodian, the document must specify the signing thresholds, the custodian's standing, and the reconciliation cadence.
• What is the liquidity profile? A position that represents more than a defined percentage of daily traded volume is not liquid at its mark-to-market price. The treasury must know what it can realise, in a stress, on a defined day. That number, not the screen price, is the working assumption.
• What is the classification? Intangible asset, inventory, financial instrument, cash equivalent. The accounting answer drives the disclosure, the valuation cadence, and what happens to earnings when the price moves. The classification cannot be decided after the position is taken.

Classification before policy

The accounting classification of a digital asset is not a presentation choice. It determines whether the position can be revalued upward, how impairment is tested, and what disclosures attach to it. A token classified as an indefinite-lived intangible asset under IAS 38 sits at cost with downside-only adjustments. A stablecoin classified as a cash equivalent under IAS 7 — if the facts support it — behaves like a deposit. A token held for sale in the ordinary course of business is inventory under IAS 2.

The right sequence is to analyse the specific facts against the applicable standard, document the reasoning, and agree the classification with the auditors before the position is material. Retrofitting a classification after a covenant calculation has been published is not a path that ends well.

Custody is a treasury control, not an IT one

The on-chain world has a single, uncomfortable property: the holder of the private key is the holder of the asset. There is no third-party custodian who can be subpoenaed into surrendering the position. There is no chargeback. There is no "hold" instruction. Whoever can sign can move the asset, immediately, irreversibly.

That property pushes custody into the treasury policy. The framework must specify the custody model — proprietary keys, qualified custodian, multi-signature, hardware security modules — the signing thresholds for transactions above defined amounts, the reconciliation cadence between on-chain balances and the accounting record, and the incident response procedure for a suspected compromise. The CFO owns this jointly with the security function. Pretending it is an IT matter is how treasuries lose assets.

Liquidity, concentration, and the discipline of a floor

Two disciplines do most of the work in keeping an on-chain treasury solvent under stress.

The first is concentration. A maximum allocation to any single token, including the entity's native token, must be specified and tested. Self-imposed limits matter because the alternative is that the limit is imposed by a forced sale at the worst possible price.

The second is a liquid-asset floor. The treasury must hold sufficient liquid, non-volatile assets — fiat, regulated stablecoins where the policy permits, treasury bills — to cover a defined period of operating expenditure regardless of what the token position is worth. The floor is not a function of the screen price. It is a function of the runway the business has chosen to defend.

What the framework actually produces

A working on-chain treasury framework gives the finance team a decision rule rather than a debate, gives the board a position it can read in one page, and gives the auditors a document they can rely on. It does not predict the price. It does not require the CFO to become a trader. It does require her to know, at any point, what the entity owns, who controls it, what it is worth, and what would happen if it halved overnight.

This piece is one entry in the CFO in blockchain framework. The companion pieces on when the balance sheet holds a token and stablecoin treasury management deepen specific elements. Lorna writes from practice at IMPT, and the verified page sets out what is and isn't published here.