Crypto & IFRS 9: When Is It a Financial Instrument (and When Not)

People reach for IFRS 9 when they see crypto on the balance sheet, but typical spot crypto does not belong there. A financial asset needs a contractual right to cash, and holding Bitcoin gives no such right, so spot crypto lands in IAS 38 instead. The genuine IFRS 9 cases are narrower: crypto derivatives and tokens whose terms create financial-instrument rights. This article maps that scope boundary, which is the call that decides whether an exposure runs at fair value through profit or loss or sits as an intangible. The default intangible treatment is covered in the IAS 38 hub.

The scope boundary in brief

• Typical spot crypto such as BTC generally lacks a contractual right to cash, so it falls outside IFRS 9 and is accounted under IAS 38 (or IAS 2 for broker-traders).
• Crypto derivatives (futures, options, certain swaps) and tokens carrying contractual cash or financial-asset rights can be in IFRS 9 scope, often at fair value through profit or loss.
• Contractual substance decides it, not the label "crypto".
• IFRS 9 (FVPL through profit or loss) and IAS 38 (cost or revaluation, surplus to OCI) produce materially different statements.
• Stablecoins with redemption or claim terms may shift the analysis; it is instrument-specific.
• This is not the same as US GAAP (ASU 2023-08). Scope is a terms-specific auditor judgement, and this is not accounting advice.

Typical spot crypto: generally not IFRS 9

A financial asset broadly requires a contractual right to receive cash or another financial asset; holding a typical cryptocurrency gives no such contractual right against another party, so spot crypto generally falls outside IFRS 9 and is accounted as an intangible (IAS 38) — or inventory (IAS 2) for broker-traders (see crypto asset account classification). A general characterization; the specific-token conclusion is an auditor judgement on its terms.

When crypto can be in IFRS 9

The key is contractual substance, not the "crypto" label — a terms-specific auditor judgement, not a default.

Why the boundary matters

The same economic exposure can produce very different financial statements depending on which applies — so the scope determination is the consequential decision, settled with the auditor before the chart of accounts is finalized.

Stablecoins

Some stablecoins have redemption/claim terms that look more like a contractual right than a typical cryptocurrency, which can push the analysis toward a financial-asset or other treatment rather than a plain IAS 38 intangible — though they are generally still not cash (see stablecoin chart of accounts). Instrument-specific, auditor-confirmed, not one rule.

Not the same under US GAAP

US GAAP uses different financial-instrument and crypto guidance, including ASU 2023-08 for in-scope crypto at fair value through net income, so the IFRS 9 vs IAS 38 framing does not map one-to-one. Contractual substance driving classification is broadly shared, but standards and outcomes follow the entity's actual framework (see IFRS vs GAAP for crypto), auditor-confirmed.

Practical guidance

1. Default typical spot crypto out of IFRS 9 → IAS 38 (confirm on terms).
2. Test derivatives and contractual-right tokens for IFRS 9 scope.
3. Decide on contractual substance, not the "crypto" label.
4. Settle scope before the CoA — IFRS 9 FVPL vs IAS 38 changes everything.
5. Analyse stablecoins on their specific terms — possibly different.
6. Confirm scope with your auditor — terms-specific; not accounting advice.

Choosing a tool for the IFRS 9 / IAS 38 split

Because a portfolio can contain both spot holdings (IAS 38) and derivatives or right-bearing tokens (IFRS 9), the subledger has to apply two treatments side by side. If you are evaluating one — Cryptio and Bitwave can apply either treatment once configured — confirm it can:

• apply an IFRS 9 fair-value-through-profit-or-loss treatment and an IAS 38 cost-or-revaluation treatment;
• configure the treatment per instrument, so a derivative and a spot holding are not forced onto one basis;
• record the instrument terms that drive the scope determination;
• keep an audit trail of the treatment applied to each instrument.

The tool applies the chosen treatment; whether an instrument is in IFRS 9 scope is an auditor judgement on the contractual terms.

How Wag3s fits in

Wag3s Ledger records instrument terms and movements so an IFRS 9 (FVPL) or IAS 38 treatment can be applied and evidenced per instrument with an audit trail. The IFRS 9 versus IAS 38 scope determination turns on the contractual substance and stays an auditor judgement; Ledger supplies the per-instrument figures and trail that support it. See the Ledger product page.

Further reading

• Crypto Asset Account Classification
• IAS 38 Crypto as an Intangible Asset
• Crypto Held as Inventory (IAS 2)
• Stablecoin Chart of Accounts
• Crypto & IFRS 13 Fair Value Measurement
• IFRS vs GAAP for Crypto

Sources

• IFRS — IFRS 9 Financial Instruments: the scope and classification of financial instruments, and the fair-value-through-profit-or-loss measurement that can apply to crypto derivatives and tokens carrying contractual cash or financial-asset rights.
• IFRS — IAS 32 Financial Instruments: Presentation: the financial-asset definition (a contractual right to receive cash or another financial asset) that typical spot crypto does not meet.
• IFRS — IAS 38 Intangible Assets and IAS 2 Inventories: where spot crypto is accounted when it falls outside IFRS 9 (intangible by default, inventory for broker-traders).
• FASB — Accounting Standards Update 2023-08, Subtopic 350-60: the US-GAAP guidance for in-scope crypto, which does not map one-to-one onto the IFRS 9 / IAS 38 framing. Scope is a terms-specific auditor judgement; this is not accounting advice.