Currency control of crypto-FEA after July 1, 2026, turns from a relatively flexible practice into a strictly monitored system: businesses will have to buy digital currency through licensed intermediaries, store it in a Russian digital depository, pay only on verified foreign platforms, and prepare documents in advance for the bank, tax authorities, and Rosfinmonitoring.
The key pillar of the new model is federal bill No. 1194918-8 on digital currency and digital rights. Its logic is simple: the state removes cryptocurrency settlements from the anonymous zone and integrates them into an infrastructure similar to the securities market. An intermediary appears between the company and the asset, and the banking transaction itself becomes part of a controlled chain.
For foreign economic activity, this means the end of familiar schemes with unverified exchangers, personal wallets, and informal OTC services. Russia is building a framework where money, digital assets, and documents must be visible at every stage. This is especially important for companies that purchase goods in China or other jurisdictions and use stablecoins instead of classic currencies like the US dollar.
How the Crypto-FEA Infrastructure Is Changing
The new system rests on three elements: licensed Russian intermediaries, a digital depository, and verified foreign platforms. A company that wants to use cryptocurrency in foreign economic settlements will no longer be able to simply buy USDT through a random online digital currency exchange service and send it to a partner’s non-custodial wallet.
Several settlement routes are usually found in crypto-FEA:
- direct transfer of digital currency to a foreign partner’s wallet — a familiar but risky scheme, which the new model effectively removes from the legal framework;
- purchase of an asset through an intermediary — rubles are sent from the corporate account to a licensed broker or digital asset exchange;
- settlement through a Russian digital depository — tokens first go to the company’s address-identifier, and only then are sent to the counterparty;
- payment with stablecoins, such as USDT — convenient for settlements with suppliers, but requires verification of the address, platform, and transaction documents.
The first level of control is the purchase of the asset. Rubles are transferred from the corporate bank account to the account of a licensed broker or digital asset exchange that has the required status or is included in the Bank of Russia’s register. This gives the Central Bank the ability to see the start of the operation: where the money came from, who bought the asset, and in what amount.
The second level is the Russian digital depository. Every company operating under the new regime opens a special address-identifier in it. Purchased tokens cannot be sent to the personal wallet of a director, employee, or foreign supplier. They must go from the intermediary’s address to the company’s address in the depository. Assets, client addresses, and fund movements are recorded there.
A technical detail is important here: the digital depository’s servers must be physically located in Russia. This makes the data accessible to regulators and turns the depository into the central node of legal crypto-asset ownership for FEA purposes.
The third element is the payment recipient. Transfers in favor of a foreign counterparty are allowed only to their account or address opened on a legal foreign platform. The supplier must pass business verification, and the platform itself must comply with international anti-money laundering and counter-terrorism financing requirements, including FATF standards.
New Payment Route
- The company transfers rubles from its corporate bank account to a licensed Russian broker or exchange.
- The intermediary transfers digital currency, such as USDT, and then the asset is transferred to the company’s address-identifier in the Russian digital depository.
- Further transfer to the counterparty is made only from the depository address and only to the verified address of the foreign partner on a legal foreign platform.
This route removes anonymity. The purchase, storage, and transfer are visible not only to the bank but also to the Bank of Russia and Rosfinmonitoring. A direct payment to a personal or anonymous wallet of a foreign partner after July 1, 2026, will be considered a violation. From July 1, 2027, when new penalty provisions come into force, such actions may result in administrative liability, and in some cases — the risk of criminal prosecution under the proposed Article 171.7 of the Criminal Code of the Russian Federation.
A separate ban concerns crypto loans without an authorized intermediary. The legislator considers lending in the digital environment a source of systemic risk, so such operations are taken outside the permissible framework. For businesses, this means less freedom in financial maneuvering, but more predictability for regulators.
The technical issue of fees in public blockchains remains unresolved. Transferring USDT on the TRC-20 network requires TRX, and on the ERC-20 network — ETH. These native tokens are not stablecoins and may not be included in the list of digital currencies allowed by the Bank of Russia for corporate and non-qualified participants. If there is no TRX or ETH at the address-identifier, the transfer may technically fail. A likely solution is to give the digital depository the right to debit the client’s rubles and automatically convert them into native tokens to pay the fee. While this is not regulated, companies will have to consider the risk that the final payment may hang due to lack of gas.
Registering a Contract: What Companies Should Do
The main mistake is to think that settlement in digital currency removes the transaction from currency control. In practice, the opposite happens: control becomes cross-checked. A single operation can be simultaneously monitored by the bank, the Bank of Russia, Rosfinmonitoring, and the Federal Tax Service.
From January 11, 2025, the updated version of Bank of Russia Instruction No. 181-I applies to contracts where settlements are made with digital rights — digital financial assets and utilitarian digital rights. For operations with digital currency, including USDT, Bitcoin, and other decentralized assets, a separate group of codes was previously introduced: 99 080, 99 081, 99 082, 99 083, and 99 085. The basic rules of currency control and amount thresholds apply the same as for settlements in ordinary foreign currency.
- An import contract must be registered if the obligation amount is from 3 million rubles. For smaller amounts, it is usually enough to inform the bank of the operation code.
- An export contract is registered for amounts from 10 million rubles. If the contract is below this threshold, registration is not required, but the bank has the right to request the contract, invoice, and other documents.
Step-By-Step Algorithm
- Immediately after signing the contract, recalculate its amount in rubles at the official Bank of Russia rate on the date of conclusion. If imports exceed 3 million rubles and exports 10 million rubles, prepare documents for the bank.
- Submit the signed contract, invoice, and supporting documents to the bank. After verification, the bank will assign a unique number to the contract. This usually takes no more than one business day after submitting the application.
- Use the correct operation code. For settlements in USDT, Bitcoin, and other digital currencies, use codes 99 080–99 085. For digital rights — a separate group 99 040–99 049. Do not mix them: an incorrect code may lead to the bank refusing to accept the certificate and fines under Article 15.25 of the Administrative Code of the Russian Federation.
- After fulfilling obligations, prepare confirmation. If the goods are imported, cleared by customs, or received by the counterparty, and the digital currency is debited from the depository account, within 15 business days after the end of the month of fulfillment, you must submit a certificate of supporting documents.
- Attach primary documents to the certificate: acts, goods and transport waybills, customs declarations, invoices, as well as a statement from the Russian digital depository showing the debit or credit of USDT to the address specified in the contract.
Late submission of the certificate is a separate violation. It is better to keep the deadlines in mind:
- Up to 10 days late: part 6.1 of Article 15.25 of the Administrative Code of the Russian Federation, the fine depends on the length of the delay.
- From 10 to 30 days late: part 6.2 of Article 15.25 of the Administrative Code of the Russian Federation, the risk arises due to violation of the certificate submission deadline.
- More than 30 days late: part 6.3 of Article 15.25 of the Administrative Code of the Russian Federation, the violation is considered more prolonged and may have more serious consequences.
Common Mistakes That Lead to Fines
- Failure to register an import contract from 3 million rubles or an export contract from 10 million rubles.
- Incorrect operation code: for example, confusing codes for digital currency 99 080–99 085 and codes for digital rights 99 040–99 049.
- Missing the deadline for submitting the certificate of supporting documents after fulfilling obligations.
- Sending digital currency directly to a personal or anonymous wallet of a foreign partner.
- Failure to attach primary documents and a statement from the Russian digital depository to the certificate.
To reduce the risk of violations, companies should establish a simple procedure in advance:
- maintain a register of FEA contracts with cryptocurrency settlements;
- monitor the 3 million and 10 million ruble thresholds for each contract and additional agreement;
- check the operation code before sending documents to the bank;
- prepare the certificate and primary documents immediately after fulfilling obligations;
- store depository statements together with the contract, invoices, and transport documents.
Special attention should be paid to payment accumulation. The 3 million and 10 million ruble thresholds are calculated at the Bank of Russia rate on the date of the contract or additional agreement that changes the obligation amount. If the rate changes after signing and the amount in rubles formally increases, this does not in itself create a retroactive obligation to register the contract. But if the parties sign an additional agreement to increase the supply or, under a framework contract, payments in total exceed the threshold, registration becomes mandatory from the moment of exceeding.
A practical solution is to maintain an internal register of all FEA contracts with cryptocurrency settlements within the company. For each contract, you need to automatically track the total amount of payments, prepare documents in advance when approaching the threshold, and recalculate each additional agreement at the Bank of Russia rate on the signing date. Exchange rate differences are important for tax accounting, but not for retrospective currency control.
Why Dirty Cryptocurrency Is More Dangerous Than a Late Certificate
The most serious risk in crypto-FEA is not a mistake in the certificate form or an incorrectly chosen operation code. The main threat is the origin of the asset. The blockchain is public and immutable: every coin stores its movement history, and it is impossible to delete this history.
If a company buys tokens through a dubious OTC service or P2P platform, it may receive an asset with a problematic past. The coin may have passed through a sanctioned mixer, participated in a fraudulent scheme, been linked to an exchange hack, or shadow segments of the Internet. The buyer may not know this, but the risks will transfer to them.
The first scenario is asset freezing by the issuer. For example, if Tether detects a connection between the address and activities prohibited by international sanctions, including OFAC lists, the issuer may freeze the address. The recipient will not gain access to USDT, the goods will not be shipped or the shipment will be delayed, and the money will be stuck in digital space.
The second scenario is blocking the operation by a Russian bank under Federal Law 115-FZ on anti-money laundering and counter-terrorism financing. Banks are increasingly using crypto analytics, including Rosfinmonitoring’s Transparent Blockchain service. The pilot implementation in credit institutions was completed in December 2025, and in 2026 integration into the national anti-money laundering system is underway.
If the analytical tool detects a connection between the transaction and a suspicious address, the bank is obliged to stop the operation. In practice, the problem is rarely limited to one payment. Settlement and foreign currency accounts of the company in this bank are often blocked, making it impossible to pay suppliers, salaries, and taxes. Unblocking the account requires explanations, documents, and time.
Sanctions related to Russia’s invasion of Ukraine have increased banks’ sensitivity to such operations. The United States of America and other jurisdictions actively use sanction lists, and traces of interaction with addresses from these lists can cause problems even when the company did not intend to violate the rules.
How to Reduce the Risk of Blocking
- Request from the foreign partner not just a wallet, but an address-identifier on a specific licensed platform.
- Obtain a written guarantee that the address has passed business verification, is not linked to mixers, and is not included in sanction lists.
- Before payment, check the address history and asset movement chain using available analytical tools.
- Prepare a protective dossier in advance: contract, invoices, correspondence with the supplier, tax reporting, staffing schedule, internal order on cryptocurrency accounting policy, and statements from the digital depository.
A ready dossier helps to quickly respond to requests from the bank or Rosfinmonitoring. Without it, the company risks spending weeks gathering confirmations while the account remains blocked.
The more transparent the payment route and the more complete the transaction documents, the lower the risk that the inspection will turn into a long account block.
How to Draw Up a Contract So the Bank Will Accept It
Cryptocurrency in Russian law is considered property, not a legal means of payment. Therefore, payment for goods with stablecoins under civil law logic is similar to barter: one party transfers goods, the other — a counter asset in the form of digital currency. The bank and customs will evaluate the contract through this lens.
- The contract must specify the asset: not an abstract payment in cryptocurrency, but the transfer of digital currency — Tether USDT tokens on the TRC-20 network. The parties must explicitly recognize such a transfer as proper fulfillment of the counter obligation.
- The recipient’s details must be specified: the supplier’s address-identifier on a specific licensed platform. It is also worth including a guarantee that the address is not linked to mixers, sanction lists, and complies with FATF requirements.
- The price is better tied not to a fixed formula of 1 USDT equals 1 US dollar, but to the market quote on the selected platform at a specific time in Moscow on the day the tokens are debited from the buyer’s address in the digital depository, with conversion to rubles at the Bank of Russia rate.
- The contract must allocate the risk of AML blocking. If after crediting to the recipient the asset is frozen under anti-money laundering procedures, this should not release the supplier from the obligation to ship the goods if the blockchain transaction has received a sufficient number of confirmations and has become irreversible.
Such conditions reduce the risk of disputes with the bank, customs, and tax authorities. Any discrepancy between the contract and the depository statement may lead to refusal to process the operation or additional requests.
Taxes: Where Unexpected Income Arises
The VAT situation is relatively clear. Operations involving the sale of digital currency are not recognized as subject to VAT. Therefore, when transferring USDT to pay for goods, VAT is not charged on the sale of the digital currency itself. But this does not cancel VAT on imported goods: it is paid in the usual manner.
The main tax risk is related to profit tax. Since settlement with stablecoins is essentially considered barter, the company recognizes income or loss from the disposal of digital currency. The base is determined according to Article 282.3 of the Tax Code of the Russian Federation, effective from January 1, 2025.
The example is simple. The company bought 100,000 USDT at 90 rubles per token and spent 9 million rubles. If on the payment date the market value of one USDT increased to 95 rubles, the total asset volume is already valued at 9.5 million rubles. The difference of 500,000 rubles becomes non-operating income and is taxed at a profit tax rate of 25%. If the rate falls, a non-operating loss arises.
To avoid claims, companies should approve an internal order in advance on the method for determining the digital currency quote. The document should specify the chosen exchange, time zone, exact time of price fixing, and method of asset write-off — FIFO or by unit cost. For the bank and tax authorities, the absence of such a procedure is a red flag.
The rules are also becoming stricter for individuals. The key parameters are:
- Available assets: from 2026 only the most liquid coins from the Bank of Russia’s list.
- Purchase limit: approximately 300,000 rubles per year through one intermediary.
- Personal income tax: 13% on annual income up to 2.4 million rubles and 15% on the excess.
- Profit calculation: the difference between proceeds from the sale and confirmed purchase expenses.
Adaptation Plan for 2026–2027
The period from July 1, 2026, to July 1, 2027, is a transition window for businesses using digital currency in foreign economic settlements. From July 1, 2027, the Administrative and Criminal Codes will come into force, providing for large fines and criminal liability for violations of currency control and illegal organization of cryptocurrency turnover.
- Inventory all settlement schemes. P2P exchangers, garage OTC services, and transfers to personal Trust Wallet or MetaMask wallets of foreign counterparties should be phased out. The legal route should look like this: Russian licensed intermediary, Russian digital depository, verified foreign platform on the counterparty’s side.
- Rewrite contracts. They must include a precise asset description, recipient’s address-identifier, address purity guarantees, market price formula, and AML blocking risk allocation rules.
- Set up internal currency control. Check contracts for approaching the 3 million and 10 million ruble thresholds, train accounting and FEA managers to work with UNC, operation codes, and certificate submission deadlines.
- Create a counterparty verification system. Before payment, you need to confirm the partner’s verification on a legal platform and analyze the risk of the address being linked to sanction mixers or other suspicious assets.
- Form protective dossiers on key suppliers. The package should include contracts, primary documents, correspondence, tax reporting, internal orders, and digital depository statements.
- Monitor legislative changes. Bill No. 1194918-8 may still be amended, especially regarding limits, the list of permitted coins, and transitional rules. Any change will require revision of processes and contracts.
The new model does not prohibit crypto-FEA, but makes it transparent and document-heavy. Companies that restructure payment routes, contracts, tax accounting, and counterparty checks in advance will have a chance to operate without blocks. Those who continue to use gray schemes risk not only fines but also a complete shutdown of settlement accounts.
{
“@context”: “https://schema.org”,
“@type”: “Article”,
“about”: [
{
“@type”: “Thing”,
“name”: “cryptocurrency”
},
{
“@type”: “Thing”,
“name”: “foreign economic activity”
},
{
“@type”: “Thing”,
“name”: “currency control”
},
{
“@type”: “Organization”,
“name”: “Bank of Russia”
},
{
“@type”: “Place”,
“name”: “Russia”
},
{
“@type”: “Place”,
“name”: “China”
},
{
“@type”: “Place”,
“name”: “United States of America”
},
{
“@type”: “Thing”,
“name”: “sanctions related to Russia’s invasion of Ukraine”
}
]
}
