Algorithmic stablecoins: which rights and risks should inform the accounting treatment?
For a finance team preparing IFRS reporting, the label “algorithmic” does not determine the ledger account. Identify the asset held, enforceable rights and available exit arrangements. The stabilisation mechanism describes how the protocol works; the accounting conclusion must address the company’s actual position.
Separate the mechanism from any claim
Start with a dated record: protocol version, token address, quantity controlled, issuance and burn terms, assets received on conversion and the party obliged to deliver them. Keep the contractual terms and their legal analysis alongside the technical description.
Established guidance: IAS 32 paragraph 11 includes, among other assets, contractual rights to receive cash or another financial asset from another entity. Paragraph 13 explains what constitutes a contract and does not invariably require a written agreement. Execution through a smart contract therefore still requires identifying the parties, obligations and enforceability.
BECTRA analysis: a formula targeting a reference price does not, by itself, establish a redemption claim. If conversion delivers another token, examine that asset and the full set of rights; do not automatically treat its delivery as a dollar payment. A separate guarantee also needs analysis within its own scope.
Apply the 2019 decision within its boundaries
The June 2019 IFRIC agenda decision addresses a subset of cryptocurrencies with three cumulative characteristics, including the absence of a contract between the holder and another party. It concludes that IAS 2 applies to holdings for sale in the ordinary course of business, with IAS 38 applying when IAS 2 does not.
This reasoning does not classify every algorithmic stablecoin by name. First document whether the position has the characteristics examined and whether another Standard applies. IAS 38 excludes financial assets and assets within another Standard’s scope; its scope is not an elective accounting policy.
Test the exit separately from carrying value
Hypothetical case: an IFRS-reporting group holds 100,000 tokens, each targeting USD1. An exit scenario uses a USD0.92 price and fees of 1% of gross proceeds. Gross proceeds are USD92,000, fees USD920 and estimated net receipts USD91,080. The shortfall against the USD100,000 reference is USD8,920.
The calculation describes a liquidity scenario before translation into the functional currency. It establishes neither a USD100,000 receivable nor a USD8,920 impairment entry. Accounting for a difference depends on classification and the applicable measurement model. For an IAS 2 holding, distinguish ordinary requirements from the measurement exception for qualifying commodity broker-traders; using an exchange does not establish that status.
BECTRA deliverable: a classification and scenario record
Rights — identify the obligor, asset due, access conditions and restrictions enforceable against the holder.
Mechanism — document dependencies on another token, price inputs, available liquidity and powers to amend or suspend the protocol. These are BECTRA review questions to verify for the particular arrangement.
Conclusion — connect each fact to IFRS guidance, support the classification, then address measurement and disclosures separately. Identify missing evidence and its owner; an unverified technical assumption remains an open matter.
The record addresses the holder’s IFRS reporting. Statutory accounts, taxation and regulatory permission to hold or use the token require separate analysis in the relevant jurisdictions.
Conclusion
The useful decision is a classification grounded in documented rights and use, supported by a reproducible exit scenario. The algorithm and target price inform the assessment; they cannot settle it alone.
Further reading
Sources
Normative review on 29 October 2026: IFRS Foundation 2026 issued texts and the June 2019 IFRIC decision within its scope. Case and file methodology: BECTRA analysis. Amendments’ application dates depend on the reporting period; these sources do not establish a new rule specific to algorithmic stablecoins.
Comments