When the balance sheet holds a token

A treasury that holds a native token is asked to do something the standards bodies did not write the rulebook for. The asset behaves like inventory in some cases, like a financial instrument in others, like a foreign currency for some transactions, and like none of those things for the most economically meaningful events — issuance, retirement, and the use of the token to settle real-world obligations.

The CFO's job is not to resolve the standards debate. It is to take a position, apply it consistently, document it defensibly, and disclose it so that a reader of the accounts can understand what is on the balance sheet and why.

The asymmetry the classification creates

Under IFRS, a token that does not meet the definition of cash, a financial instrument, or inventory is classified as an indefinite-lived intangible asset under IAS 38. Measurement is at cost, with impairment testing. The treatment understates an appreciating position — there is no upward revaluation — and faithfully records a falling one. Under US GAAP, recent changes have moved towards fair-value accounting for certain crypto-assets, narrowing but not eliminating the asymmetry.

The consequence in practice is that the income statement does not capture the economic value of a rising token position. The economic gain is real. It is invisible to the income statement until realised. A balance sheet that has appreciated materially on a position the auditor cannot allow the entity to mark up is, in narrative terms, the harder story to tell. The CFO must be ready to tell it.

Issued, held, and the question of self-held tokens

A subtlety that confuses many first-time token treasuries: a token held by the issuing entity, where the entity could destroy or re-issue it at will, is not the same asset as a token held by a third party. The economic substance differs, and the accounting reflects that.

Specifically:

• A token held by the issuer that has never been in circulation typically is not recognised on the balance sheet at all. It is closer to authorised-but-unissued share capital than to a held asset.
• A token previously issued and reacquired may, depending on the entity's intentions, be classified analogously to treasury shares, removed from circulation but not derecognised as a balance-sheet line.
• A token held by a subsidiary issued by the parent in a consolidated group is eliminated on consolidation — the group cannot show as an asset something it owes to itself.
• A token issued to a third party who has subsequently delivered it back to the entity in exchange for goods or services is, in substance, the redemption side of the deferred-revenue arrangement the issuance originally created.

Getting each of these patterns right requires the entity's token economics to be documented at a level of detail that most pre-revenue token issuers do not maintain. The remediation cost grows with the volume of transactions. Doing it early is materially cheaper.

Measurement and the cadence problem

Whatever the classification, a token position has to be measured. The measurement choice has three components.

• The price source. Tokens trade on multiple exchanges with non-trivial spreads. The policy must specify which venue, which pair, which time, and what to do when the primary source is unavailable.
• The cadence. Daily? Period-end only? The cadence affects how much volatility the policy injects into the reported numbers and how much work the finance team carries.
• The liquidity adjustment. A position that represents more than a defined percentage of daily traded volume cannot realistically be sold at the screen price. A liquidity-adjusted valuation is more honest about realisable value, particularly for the audit committee discussion.

None of these choices is obvious. All of them have to be documented before they are tested.

Disclosure obligations a token position creates

A material token position drives several disclosure lines that a fiat-only treasury would not generate.

IFRS 7 requires disclosure of the sensitivity of profit or loss to changes in market variables where a financial instrument is held. Where a token is not classified as a financial instrument, an analogous disclosure is still required by users of the accounts who reasonably need to understand the exposure.

Risk disclosure should specify the maximum exposure, the liquidity profile, the custody arrangements, and the controls in place. "Crypto holdings of X" without context is, for most readers of accounts, not a meaningful disclosure.

Where the token is the entity's own native token, additional disclosure of the issuance and retirement patterns, the holders' rights, and any redemption obligations is necessary to give the reader a picture of the underlying economics.

Stress disclosure — what happens to the balance sheet if the token price falls by 30%, 50%, 70% — is increasingly an audit committee expectation. The numbers should be calculated and held, ready for the question, before the question is asked.

What the audit committee actually needs to see

The board-level conversation about a token position benefits from a one-page summary that the CFO refreshes each period:

• Quantity held, in tokens and in fiat at the policy price.
• The classification, the valuation methodology, and any change since last period.
• The custody arrangement and any change to signatories.
• The position as a percentage of total treasury and of total assets.
• The stress sensitivities at three calibrated price levels.
• Any related-party transactions in the token during the period.

The discipline of producing this page makes the audit easier, the diligence easier, and the board conversation honest. None of those qualities is automatic, and all of them are worth the work.

One further point on consistency. Investors and auditors compare the entity's treatment of its token position across periods, and they compare it against peer entities with similar positions. A policy that shifts between periods without a documented reason is read as opportunistic. A policy that lags peer practice without a defensible rationale is read as weak. Neither is a good outcome. The discipline is to choose a defensible treatment, apply it consistently, change it only when the facts or the standards require, and document the rationale when change occurs. The audit committee should be able to read a single paragraph and understand the policy, the rationale, and whether anything has moved.

This sits inside the CFO in blockchain framework. See also on-chain treasury framework and MiCA for the CFO. Lorna writes from practice at IMPT. The verified page records what is and isn't published here.