TON in 1C: Crypto Accounting for Russian Businesses (2026)

TL;DR. By mid-2026 Russian businesses that actually receive or hold TON have a working methodology in 1C Accounting 8.3: account 58.05 (or a custom subaccount), exchange rate from a public source, locked in the accounting policy, revaluation at the reporting date for general regime. Tax arises on realisation, not on holding. The base mistake — trying to record crypto off-balance or on account 76: that won’t pass a desk audit. Below is the full mapping with postings for typical scenarios.

This article is the English explainer for the same topic; the Russian version (accessible via the language switcher) goes deeper into Russian-specific paperwork.

Regulatory baseline

By end-2025 the rules settled:

• Crypto = property (Russian Civil Code Art. 128 after 259-FZ amendments).
• Digital currency is not a means of settlement between Russian residents, but allowed as a property asset for external sales.
• Mining is a separate activity registered with the Ministry of Digital since 2024.
• Bookkeeping follows ПБУ 19/02 (PBU 19/02) and Ministry of Finance letter dated 14 March 2024 № 03-03-06/1/22459 (with 2025 clarifications).

Translation: you can account for it, you must account for it, and there’s a working playbook. Below — what that looks like in practice.

Chart of accounts: where to put it

The working pattern (used in most accounting-school materials by 2026):

• 58.05 “Digital financial assets” — for USDT-jetton, BTC, ETH, and TON too (regardless of whether TON formally qualifies as DFA under 259-FZ, bookkeeping it as a financial investment is correct).
• Optionally: 58.05.01 — TON, 58.05.02 — USDT, 58.05.03 — other jettons.

Old-school alternatives — account 76 (“Settlements with debtors”) or 50.04 (“Cash in foreign currency”) — not recommended:

• Account 76 doesn’t methodologically support revaluation.
• 50.04 is for cash; crypto isn’t cash.
• The tax service letters explicitly point at 58.

Accounting policy: what to lock

Before the first posting — update the accounting policy (document “Organisation accounting policy” in 1C → Bookkeeping and tax accounting):

1. Fair-value source. E.g. “TON/RUB rate per CoinGecko (ru.coingecko.com) at the operation time; for exchange operations — actual exchange rate; for P2P — actual trade rate per supporting document”. One source for the whole year, switchable only at year boundary.
2. Revaluation frequency. LLC on general regime — quarterly or annual. LLC on simplified — none. IP — none.
3. Disposal method. FIFO (recommended — easier to justify) or weighted average.
4. Analytics dimension. Per wallet (separate subconto). Convenient: “operational” (hot, for accepting payments), “cold” (long-term holding), “exchange-bybit” (exchange balance).

Typical scenarios with postings

Scenario 1: IP on USN 6% — TON via Crypto Pay from a foreign client

Step 1. Client paid an invoice for 100 USDT (~10,000 ₽ on the date). 1C document: “Other inflow” → “Cash receipt”.

• Dr account: 58.05.02 (USDT)
• Cr account: 90.01 (Revenue)
• Amount: 10,000 ₽
• Subconto (Wallets): “operational-cryptopay”
• Purpose: “Payment for invoice #1234 from client (Telegram ID 12345)”

Step 2. In the IP income ledger — 10,000 ₽ logged as income on payment date. USN 6% = 600 ₽ payable to the budget.

Step 3. Withdrawing USDT on the exchange → converting to rubles → transfer to IP current account.

• Dr 51 (Current account) Cr 58.05.02 — amount actually received in rubles
• If less due to FX/exchange fee — delta: Dr 91.02 Cr 58.05.02

Scenario 2: LLC on general regime — payment for a service, revaluation at 31.12

Step 1. Client pays for a service in TON. Contract: 1000 USD, paid in TON at the date — say 200 TON × 5 USD/TON.

• Dr 62.01 (customer settlements) Cr 90.01 — 100,000 ₽ (at 1 USD = 100 ₽)
• Dr 58.05.01 (TON) Cr 62.01 — 100,000 ₽ (TON received against the receivable)

Step 2. TON sits on your books. On 30.09 the rate dropped, TON = 4 USD. Revalue:

• If 1 TON was on books at 500 ₽ and the rate is 400 ₽ → 20,000 ₽ fall on 200 TON
• Dr 91.02 (other expenses) Cr 58.05.01 — 20,000 ₽

Step 3. On 31.12 rate recovered, TON = 5.5 USD = 550 ₽:

• Dr 58.05.01 Cr 91.01 (other income) — 30,000 ₽

Step 4. 20% profit tax reflects changes through account 91. Meaning: upward revaluation increases tax, downward decreases. So an LLC on general regime with crypto needs a real accountant; for most small businesses USN 6% is much simpler.

Scenario 3: IP on USN ‘income minus expenses’ (15%) — buying TON for resale

If the business model is P2P arbitrage or exchange (buy and sell crypto as goods), USN 15% may be more efficient:

Step 1. Buy 1000 TON at 500 ₽/TON via Bybit P2P:

• Dr 58.05.01 Cr 51 — 500,000 ₽

Step 2. Sell 1000 TON at 550 ₽ via Bybit P2P:

• Dr 51 Cr 90.01 — 550,000 ₽ (income)
• Dr 90.02 Cr 58.05.01 — 500,000 ₽ (expense by FIFO — acquisition cost)

Tax: (550,000 − 500,000) × 15% = 7,500 ₽. Under USN 6% it would be 33,000 ₽ (6% of revenue). Margin < 60% — USN 15% wins.

Document trail: what to keep as primary

A Russian tax service desk audit in 2026 will ask for:

1. Contract with counterparty (free form, can be by email).
2. Service act (for services) / shipping note (for goods).
3. Payment confirmation: webhook payload from Crypto Pay/Wallet Pay as PDF, or tx hash + tonscan.com screenshot showing the transaction to your address.
4. Rate to ruble on payment date — CoinGecko screenshot with timestamp.
5. Accounting policy — current.

Keep everything 5+ years (Russian tax statute of limitations). For safety — 7 years.

Typical mistakes

1. Recording on account 76. Blocks revaluation, throws errors at period close.
2. “Own” rate source. Policy says CoinGecko, you used Binance — formal violation, may pass desk audit, will surface on field audit.
3. No source-wallet analytics. Without per-address subconto you can’t pass inventory.
4. Mixing operational + cold storage in one wallet. 1C-OK, operationally awful — hot key compromise wipes you out.
5. Treating USDT-jetton like just another currency. USDT on TON is a jetton, not currency in 259-FZ terms. Account same as TON but call it out in the policy (“token USDT, issuer Tether, network TON”).

What’s changing in 2026

• Ministry of Finance and the Central Bank published a draft “Methodological guidance on accounting for digital currency” in 2025. Mid-2026 it’s not law yet but actively cited in tax-service letters.
• Automated bank-data exchange on crypto operations in Russia is live — banks see P2P transfers and can request explanations for operations >100,000 ₽/month per individual.
• Mining and crypto exchange require separate registration via the Ministry of Digital. If exchange is your model — registration in the operator registry is required.

Off-the-shelf 1C configurations

By 2026 several industry configurations exist:

• “Cryptocurrency 8” by 1C-Rarus — paid (~30,000 ₽), worth it from 5M ₽/month turnover.
• Free community templates — search “1C Crypto-assets template 2026”.
• Built on standard Accounting 8.3 with 58.05 added — fine for small business.

Under 500,000 ₽/month — standard 1C + two-three new subaccounts + discipline on primary docs handles it without further investment.

”Audit-ready” checklist

• Account 58.05 (or subaccount) added to chart
• Policy updated: valuation method, rate source, revaluation cadence
• Each wallet = separate subconto
• Per operation: counterparty, tx hash, rate screenshot, supporting doc
• 31.12 inventory done, balance screenshots saved
• Tax return (3-NDFL for IP or profit tax for LLC) filed with crypto income
• All primary docs kept 5+ years

Bottom line

Recording TON in 1C isn’t magic or a grey area — by 2026 there’s a working methodology accepted by the Ministry of Finance and tested in practice. The basics: lock rules in the policy, use account 58 (not off-balance or 76), and maintain full primary documentation. For most small businesses USN 6% is simpler than general regime with revaluations; for arbitrage and P2P trading USN 15% beats it when margin is thin.

If TON inflows are personal, not business — see our Taxes on TON in Russia and How to file 3-NDFL for TON guides (RU, available in Russian only).