Bank-deposit-backed stablecoins: does the nature of reserves determine their IFRS classification?

59 minutes ago

3 min read

A French company preparing IFRS reporting receives a statement that a stablecoin’s reserves are held in bank deposits. This helps assess backing and liquidity risk. It does not by itself make the company’s tokens its own bank deposit. The closing file should distinguish the issuer’s reserve asset from the holder’s own right.

Start with the asset the company holds

IAS 32 paragraph 11 includes a contractual right to receive cash from another entity within the definition of a financial asset. Paragraph 13 explains the contractual substance of an agreement. Assess the relationship to which the company is a party, rather than only how the issuer invests the proceeds.

Application guidance AG3 explains why a bank deposit is a financial asset of the depositor. When the issuer owns the bank account, do not attribute that right to the token holder without evidence of the holder’s own recourse. A token genuinely representing a deposit and a token merely backed by deposits require different files.

Separate reserve evidence from rights evidence

For reserves, identify the report’s scope, date, asset categories and any restrictions. A report covering the entire issuance does not by itself establish what your company can demand, from whom and on what terms.

For rights, collect the terms applicable to the actual corporate holder: the redemption obligor, beneficiary of recourse, currency and amount due, eligibility conditions, fees, suspension terms and governing law. Resolve material legal uncertainty with competent analysis. Apparently liquid reserves do not turn an uncertain right into an established accounting conclusion.

Distinguish reserve assets from contractual rights.

Worked example: coverage is not a substitute for the contract

Assume a company holds 100,000 tokens each targeting EUR1. The issuer’s report shows EUR1,020,000 of bank deposits against 1,000,000 outstanding tokens: apparent coverage of 102%. This calculation concerns reported reserves. It does not itself create a EUR100,000 bank receivable in the company’s name.

In file A, an enforceable contract establishes the company’s substantive right to receive EUR1 per token from an identified entity, subject to documented conditions. That evidence supports examining financial asset classification. In file B, the company has only a reserve report and an opportunity to resell tokens on a platform. It cannot copy file A’s conclusion: the rights analysis is still incomplete. The 102% ratio is neither a repayment guarantee nor a proposed carrying amount.

Keep two conclusions separate

If the token falls within IFRS 9, measurement requires its own assessment; reserve quality does not automatically determine the measurement category. Presentation as cash or a cash equivalent also requires a separate IAS 7 analysis, including convertibility and risk of changes in value.

The June 2019 IFRIC cryptocurrency agenda decision addresses a subset without a contract between holder and another party. Its IAS 2 or IAS 38 conclusion cannot be applied mechanically to every stablecoin. Assess the instrument’s features and holding purpose before selecting the applicable standard.

A BECTRA closing deliverable

A BECTRA reserve/rights/conclusion record can connect each assertion to dated support: reserve report, terms accepted by the company, recourse analysis where needed, token reconciliation and the consolidation manager’s decision. Separate the normative rule, its application to the facts and unresolved points. For a French entity, this IFRS analysis remains separate from French GAAP and regulatory permission to use the token.

Conclusion

Bank reserves inform the assessment of the issuer’s risk. The holder’s IFRS classification starts with its actual asset and evidenced rights. Bring both sets of evidence into the file without substituting one for the other.