Russia Approves Bitcoin, Ethereum and USDT Trading: What Accounting Firms and CFOs Must Assess Now
Russia has formally approved the trading of Bitcoin, Ethereum and Tether (USDT) on licensed domestic platforms, while explicitly leaving XRP off the permitted list. The decision, published on 11 August 2026, moves three of the largest digital assets by market capitalisation into a defined regulatory lane inside Russia and raises immediate questions for any accounting firm, auditor or CFO whose clients touch Russian-linked trading activity. Bitcoin accounting and ethereum accounting entries that were previously in a legal grey zone now sit inside a formalised, if internationally contested, framework.
What Russia Has Actually Approved
The approved list covers Bitcoin (BTC), Ethereum (ETH) and Tether (USDT). Each asset is permitted for trading on platforms that operate under Russian licensing requirements. XRP was considered and deliberately excluded, though the precise regulatory rationale for that exclusion has not been published in detail.
The Significance of the Asset Selection
The three approved assets are not arbitrary. BTC and ETH together represent the overwhelming majority of global crypto trading volume. USDT, as the dominant dollar-pegged stablecoin, has long been the settlement layer of choice across many emerging-market crypto corridors, including routes that touch Russia. Approving USDT in particular signals that Russian authorities are prepared to tolerate dollar-denominated digital settlement inside their regulated perimeter, at least on licensed venues.
XRP's exclusion is notable. Ripple's token has been used in cross-border payment corridors globally. Its absence from the approved list may reflect concern about the payment-rail characteristics of the asset or its international banking linkages, but no official explanation has been confirmed at the time of publication.
Licensing and Platform Requirements
Trading must occur on platforms that hold Russian regulatory authorisation. Unlicensed activity remains prohibited, a point reinforced by the earlier Russia FSB crypto exchange enforcement sweep at Moscow City, which targeted operators running outside the licensed perimeter. The new approval list effectively narrows the field: only assets on the permitted list, traded on authorised platforms, operate within the law.
Sanctions Overlap: The Unavoidable Complication
Approving an asset domestically does not dissolve the international sanctions architecture that surrounds Russia. For any firm with non-Russian clients, the approval of USDT trading inside Russia creates a layered compliance problem.
USDT and Sanctions Screening
Tether (USDT) has already been at the centre of international sanctions enforcement actions. The OFAC sanctions involving Shelbit and Aban Tether illustrated how dollar-pegged stablecoin flows can intersect with blocked-party networks. Firms that hold or process USDT on behalf of clients must now contend with an expanded set of Russian-origin transaction vectors that are legal under Russian law but potentially sanctionable under US, EU or UK rules.
The practical risk is not that a licensed Russian platform is itself sanctioned on day one. The risk is that transaction flows involving USDT pass through or touch wallets, addresses or entities already on OFAC's Specially Designated Nationals list or equivalent EU or UK lists. Digital asset accounting software that lacks real-time sanctions screening at the wallet address level is inadequate for this environment.
EU and UK Exposure
European accounting firms and CFOs advising clients who trade on international venues need to assess whether any counterparty leg of a BTC, ETH or USDT transaction could be traced to a Russian licensed platform. Russian regulatory approval does not create a safe harbour under EU Council regulations or UK financial sanctions legislation. The compliance burden remains with the Western-side counterparty.
Bitcoin Accounting and Ethereum Accounting: Classification Under IFRS and Local Standards
For firms handling digital asset accounting for clients with Russian-market exposure, the approval decision has direct implications for how BTC and ETH positions are classified and measured.
IFRS Treatment of Approved but Sanctioned Assets
Under IFRS, the classification of a digital asset typically turns on its contractual characteristics and the holder's business model. BTC and ETH held as investments are generally recognised as intangible assets under IAS 38 or, if held for trading, at fair value through profit or loss under the commodity-broker exemption. Russian regulatory approval does not alter that analysis for a non-Russian entity. What it does change is the liquidity and market-access dimension: if Russian exchange volumes for BTC and ETH are now officially reported, those prices could theoretically be reference data points, but any auditor would need to assess whether a Russian exchange price constitutes an active market price under IFRS 13 given sanctions restrictions on accessing those markets.
Stablecoin Accounting for USDT
Stablecoin accounting for USDT is already complex under both IFRS and US GAAP. USDT is not cash under IAS 7 and does not meet the definition of a financial instrument in the conventional sense, though standard-setters continue to debate this. The Russian approval does not resolve those classification questions. What it does introduce is an additional disclosure consideration: if a client holds USDT that has passed through a Russian licensed platform, the auditor needs to assess whether that creates a contingent liability or requires specific disclosure under IAS 37 or equivalent, given the sanctions overlay.
Under ASC 350-60, the US GAAP framework for crypto assets, the same principle applies. The approved trading status in Russia has no bearing on the measurement methodology, but it does affect the risk disclosures required in financial statements if the entity has material exposure to Russian-origin digital asset flows.
Tax Implications for Cross-Border Structures
Tax teams at accounting firms need to think through several distinct questions arising from this development.
Characterisation of Gains on Approved Assets
Inside Russia, the formalisation of BTC, ETH and USDT trading presumably brings those assets more squarely within Russian tax reporting frameworks for digital financial assets. For non-Russian entities, the tax treatment of gains on BTC, ETH or USDT is unaffected by Russian domestic approval, but the practical risk of unrecognised taxable events increases when clients begin accessing Russian venues believing that local approval confers broader legitimacy.
Transfer Pricing and Intercompany Positions
For multinational groups with Russian subsidiaries or affiliates, the approved trading list raises transfer pricing questions. If a Russian entity can now legally hold and trade BTC, ETH or USDT, intercompany arrangements involving those assets need to be priced at arm's length using observable market data. The question of which reference price to use, given the sanctions restrictions on Western access to Russian exchange data, is one that transfer pricing teams should document carefully.
Withholding and Reporting Obligations
Firms acting as intermediaries or advisers in transactions involving Russian-licensed platforms should review whether any withholding or information-reporting obligations arise in their home jurisdiction. In the UK, for example, HMRC's cryptoasset guidance requires that disposals be reported regardless of the jurisdiction in which the trade executes. Russian regulatory approval does not create a reporting exemption.
Practical Steps for Accounting Firms and CFOs
The Russia approval decision is not a reason to panic, but it is a reason to act. Here is a structured response framework.
Immediate Actions
First, audit your client portfolio for any entity with Russian counterparty exposure in BTC, ETH or USDT. Even indirect exposure through a non-Russian exchange that routes liquidity through Russian venues is worth documenting. Second, ensure that your digital asset accounting software captures the jurisdiction of the executing venue, not just the asset type. An ETH trade is not the same accounting or compliance event regardless of where it settles. Third, review sanctions screening procedures. USDT flows in particular warrant enhanced due diligence given the existing OFAC and EU enforcement record on Russian-linked stablecoin transactions.
Medium-Term Workflow Adjustments
Update client onboarding questionnaires to ask explicitly about Russian-licensed platform usage. Revise engagement letters to clarify the scope of sanctions compliance advice, particularly for clients who may interpret Russian domestic approval as a green light for broader activity. For audit clients, assess whether the Russia approval creates any new going-concern or contingent liability disclosures in the financial statements.
Firms should also revisit their crypto compliance reporting protocols to ensure that Russian-venue transactions are tracked separately in the audit trail, enabling clear documentation if a regulator or sanctions authority requests evidence of due diligence.
What the XRP Exclusion Means in Practice
The deliberate omission of XRP from Russia's approved list has practical consequences for any firm or client that holds XRP and has Russian business relationships. XRP trading on Russian-licensed platforms remains unlicensed activity under the new framework. Clients who hold XRP and are contemplating Russian market access should be advised that the asset sits outside the approved perimeter, creating an additional compliance and legal risk layer on top of the existing sanctions environment.
For accounting purposes, the exclusion does not change the recognition or measurement of XRP under IFRS or GAAP. It does, however, affect the risk profile of any client that holds XRP alongside Russian-linked positions, and that should be reflected in client risk assessments and engagement file documentation.
Source: Decrypt
Frequently Asked Questions
Does Russian regulatory approval of BTC, ETH and USDT affect how we classify those assets under IFRS?
No. Classification under IFRS depends on the asset's contractual characteristics and the holder's business model, not on the domestic regulatory status in any particular jurisdiction. Russian approval has no bearing on whether BTC or ETH is treated as an intangible asset under IAS 38 or at fair value through profit or loss for a non-Russian entity.
Can we use Russian exchange prices as fair value reference data under IFRS 13?
Only with significant caution. IFRS 13 requires that a fair value measurement reflect a price observable in an active market that the entity can actually access. Given that Western entities are broadly restricted from accessing Russian financial markets under sanctions, Russian exchange prices are unlikely to qualify as the primary reference for fair value measurement.
Does the Russian approval of USDT change our OFAC sanctions screening obligations for Tether transactions?
No. OFAC sanctions obligations are determined by US law, not by the domestic regulatory status of a foreign jurisdiction. Any USDT transaction involving a Russian-linked wallet, entity or platform must still be screened against OFAC's SDN list and Russia-related sanctions programmes. Russian approval does not create a safe harbour.
What should we disclose in financial statements if a client holds USDT that passed through a Russian licensed platform?
Firms should assess whether the position creates a contingent liability under IAS 37 (or ASC 450 under US GAAP) given the sanctions overlay. At a minimum, if the exposure is material, a disclosure of the nature and uncertainty of the position is prudent. Auditors should document their assessment of whether the Russian nexus represents a significant risk that requires specific mention in the audit report.
Is XRP on any international approved trading list that might offset Russia's exclusion?
XRP is traded on licensed venues in multiple jurisdictions, including the EU and the UK, where it does not face a blanket prohibition. Russia's exclusion is a domestic regulatory decision specific to the Russian licensed platform framework and does not affect XRP's status elsewhere. However, clients holding XRP who also have Russian business relationships should document that the asset is outside the Russian approved perimeter and cannot legally be traded on Russian licensed platforms.