
When does IFRS 9 apply to a stablecoin?
An Ivorian subsidiary in an IFRS-reporting group receives 400,000 stablecoin units to pay suppliers. The token targets USD1, but only an approved customer of the issuer may request redemption. The subsidiary uses a trading platform. Before calculating amortised cost or fair value, the controller must answer a more basic question: what contractual right does the subsidiary hold, and against which entity?

IFRS 9 does not apply merely because an asset moves on a blockchain or targets a stable value. The instrument must first qualify as a financial asset under IAS 32 and then fall within IFRS 9’s scope. The file should make that path reproducible.
Start with the right, not the reported reserves
IAS 32 includes a contractual right to receive cash or another financial asset from another entity within the definition of a financial asset. The contract should identify the obligor, the performance due, the exercise conditions and the owner of the right. Reserves described as deposits or government securities may inform issuer risk; they do not necessarily give the holder rights over those assets.
The controller collects the issuer terms, the platform agreement, evidence identifying the account holder, transfer restrictions and the redemption process. The review distinguishes a direct right against the issuer, a claim against an intermediary and a mere ability to sell the token to a third party. The third case does not by itself create a contractual right against a future buyer.

The June 2019 IFRIC agenda decision does not end this review. It addresses a subset of cryptoassets that, among other characteristics, does not give rise to a contract between the holder and another party. A stablecoin with a demonstrated contractual right may therefore fall outside that specific fact pattern.
Cross the IFRS 9 threshold through two checks
First, does the asset meet the definition of a financial asset? If the subsidiary can require an identified counterparty to deliver cash or another financial asset, the file records the legal basis and conditions of that right. If only the intermediary is the issuer’s creditor, the relevant analysis is the subsidiary’s right against the intermediary, not the intermediary’s separate right.
Second, is that right within IFRS 9’s scope? The IFRS Foundation’s overview explains that IFRS 9 governs classification and measurement of financial assets and liabilities and that an entity recognises an instrument when it becomes party to its contractual provisions. Recognition is therefore not automatically triggered by the technical appearance of tokens at an address; the operational transfer must be reconciled with the effective contractual rights.
A positive scope conclusion opens the IFRS 9 analysis. It does not determine the measurement category. The business model and contractual cash-flow characteristics are later steps. IFRS-012 to IFRS-014 will address SPPI, the business model and the choice among amortised cost, FVOCI and FVTPL. This file stops at the scope threshold so that it does not pre-empt those conclusions.
Separate direct custody from a platform account
In the case, 250,000 units sit in a wallet controlled by the subsidiary, but the issuer’s terms reserve redemption to approved customers. The other 150,000 units appear in a platform account that promises delivery of tokens or money under its own terms.
The first lot is not automatically a receivable from the issuer because the subsidiary controls the keys. Technical control demonstrates access to the token; it does not establish the obligor or a payment obligation. The second lot may create a right against the platform, but its nature depends on the agreement: delivery of tokens, payment of money, custody with restitution, or another arrangement.
The deliverable therefore contains one record per lot. Each record connects the holder, counterparty, asset due, due date, conditions and supporting evidence. When evidence is missing, the conclusion remains open. A missing document is never treated as evidence that no contract exists.
Worked case: quantify exposure without deciding classification
At year-end, the observable price is USD0.992 per token. The directly held lot is worth USD248,000 and the platform account USD148,800, for a total of USD396,800. The difference from the USD400,000 reference amount is USD3,200.

This calculation supports reconciliation and risk review. It proves neither a USD400,000 receivable, nor a successful SPPI assessment, nor a USD3,200 accounting loss. If IFRS 9 applies, measurement will depend on the supported category; if it does not, another Standard must be identified. The controller separately records the price, source, timestamp, market depth and exit costs.
For a West African subsidiary, the file also records the functional currency, exchange rate and local constraints relevant to the transaction. Those matters affect entries, treasury and compliance; they do not replace the IFRS analysis of the contractual right.
BECTRA deliverable: IFRS 9 scope memorandum
The memorandum uses a six-column matrix: lot, applicable contract, obligor, performance due, IAS 32 conclusion and IFRS 9 scope conclusion. An appendix holds dated terms, balance confirmations, wallet-control evidence and legal approvals.
A reviewer should be able to reproduce the reasoning without knowing the token’s brand. If the contract changes, the intermediary is replaced or redemption becomes available, the matrix identifies which conclusion must be reopened. This discipline prevents an outdated classification from remaining in the closing file.
Conclusion
IFRS 9 applies to a stablecoin when the holder has a financial asset within its scope. That assessment begins with a demonstrated contractual right linked to a counterparty. A target price, reserve composition, wallet control or market liquidity is not sufficient on its own.
The useful work is to document each lot, contract and obligor before addressing SPPI, the business model and measurement. A dated scope memorandum gives the finance director and reviewer a clear boundary between established facts, analysis and open questions.
Further reading
Sources
Official sources reviewed on 12 November 2026. The 2019 IFRIC decision is applied within the fact pattern it describes; this article does not conclude on a named token without its current contracts.
• IFRS Foundation, IFRS 9 Financial Instruments: https://www.ifrs.org/issued-standards/list-of-standards/ifrs-9-financial-instruments/
• IFRS Foundation, IAS 32 Financial Instruments: Presentation: https://www.ifrs.org/issued-standards/list-of-standards/ias-32-financial-instruments-presentation/
• IFRS Interpretations Committee, “Holdings of Cryptocurrencies”, IFRIC Update, June 2019: https://www.ifrs.org/news-and-events/updates/ifric/2019/ifric-update-june-2019/
• IFRS Foundation, Annual Improvements to IFRS Accounting Standards—Volume 11, July 2024, effective for annual periods beginning on or after 1 January 2026: https://www.ifrs.org/news-and-events/news/2024/07/iasb-issues-annual-improvements-ifrs-accounting-standards/




Comments