Accounting for Tether (USDT)

Stablecoins look simple — a token worth a dollar — but they're one of the trickiest things to classify, because the redemption right behind a fiat-backed stablecoin changes the accounting. This page explains how USDT is treated, why it's a judgment call, and how CryptaCount handles it.

General information, not accounting or tax advice. Stablecoin classification is unsettled and judgment-based — confirm the right treatment for your facts with your auditor or advisor.

Why USDT isn't treated like Bitcoin

The crypto fair-value standard (ASC 350-60 under US GAAP) only covers assets that give the holder no enforceable claim on an underlying asset. A fiat-backed stablecoin like USDT, where the holder may have a right to redeem for underlying reserves, generally falls outside that scope — so it usually isn't measured at fair value the way BTC or ETH are.

How USDT is classified

There's no authoritative accounting guidance specific to stablecoins, so classification requires documented judgment. In practice:

• If there's an enforceable redemption right, USDT may be analysed under financial-instrument guidance (e.g. as a receivable).
• If redemption isn't enforceable, it's more likely an intangible asset (under ASC 350-30 / IAS 38), carried at cost with impairment rather than at fair value.
• Many preparers default to intangible treatment unless there's a clear legal analysis supporting financial-asset classification.
• It's not automatically cash or a cash equivalent — stablecoins generally fail those criteria due to counterparty and redemption risk, though standard-setters are actively developing guidance on stablecoin cash-equivalent treatment.

Crypto accounting under US GAAP → · Crypto accounting under IFRS →

Regulatory note

Under the EU's MiCA, a single-currency stablecoin is an E-Money Token (EMT), and a stablecoin's regulatory status in your market can affect how it's treated. MiCA →

Tax and cost basis

For tax, USDT is still property in most jurisdictions — so swapping or spending it can be a disposal with a (usually small) gain or loss against its cost basis. Used for payments or treasury, that means tracking the basis and movement of every unit. Cost-basis methods →

How CryptaCount handles USDT

• Tags USDT with its stablecoin and classification attributes (including peg and regulatory class)
• Applies the measurement treatment you've determined with your advisor, consistently
• Tracks cost basis and movement across high-volume payment and treasury flows
• Posts journal entries to your ERP with a full audit trail

See the sub-ledger → · Crypto assets → · USD Coin (USDC) →

General information, not accounting or tax advice. Stablecoin treatment is unsettled — verify with your auditor or advisor.

Recognition and initial measurement of a USDT position

A fiat-backed stablecoin enters the books when the entity obtains control of the tokens, initially measured at the cost given to obtain them. In the ordinary case where a unit is acquired at or close to its peg, that cost will sit near par, but the accounting does not assume par - it records what was actually paid, including any fees, in the functional currency at the transaction date. The reason this matters is that the classification decision sitting behind a stablecoin shapes both how it is later measured and where it appears, and that decision turns on the nature of the holder's claim. Establishing the right classification at recognition, and documenting the judgment, is therefore more consequential for USDT than for a pure crypto asset like Bitcoin, where the classification is more settled.

Because there is no authoritative accounting guidance specific to stablecoins, the recognition decision is a documented judgment rather than a lookup. The existing page above sets out the core fork: where an enforceable redemption right exists, USDT may be analysed under financial-instrument guidance; absent that, it is more likely an intangible asset carried at cost with impairment. Whichever way the judgment lands, it should be recorded with its reasoning, applied consistently, and revisited as guidance develops - and the underlying movements should be captured granularly in the sub-ledger so the position can be re-cut if the treatment changes.

Par value, peg, and subsequent measurement

Stablecoins invert the measurement problem that dominates Bitcoin and Ethereum accounting. Because USDT is designed to track a unit of fiat, the remeasurement question is usually not about large price swings but about whether, and how, small deviations from the peg are recognised. If USDT is treated as an intangible asset under a cost-and-impairment approach, a fall below the carrying amount could prompt an impairment assessment, while a rise back toward par may not be recognised in the same way - the asymmetry that characterises cost-and-impairment models. If instead it is analysed as a financial instrument such as a receivable, the measurement follows that guidance, which may treat the holding differently again. The practical point for an accounting team is that the peg does not eliminate measurement work; it changes its character from tracking volatility to monitoring deviation and redemption risk.

An illustrative example clarifies the par-value mechanics. Suppose an entity holds USDT recorded at a cost of 100 units, intended to track 100 of fiat. If the token trades persistently below par - say an effective value of 98 - an intangible-asset treatment might require considering whether the carrying amount should be written down, whereas a brief, immaterial deviation that reverts to par would generally not. If the token is instead a receivable backed by an enforceable redemption right, the assessment centres on recoverability of that claim rather than on a market price. These figures are purely illustrative and are used only to show that the trigger for any adjustment depends on the classification, not on the token simply being labelled a stablecoin.

Cost basis, gains and losses in the books

Even though USDT hovers near par, it is not treated as cash for accounting, which means moving it is not a non-event the way spending cash is. Each time USDT is swapped, spent, or converted, the disposal is matched against the cost basis of the units involved under the adopted cost-basis method, and any small difference between proceeds and basis is a realised gain or loss. Individually these differences are usually tiny, but across a high-volume payments or treasury operation they accumulate into figures that have to be recorded accurately rather than waved away. The accounting challenge with stablecoins is therefore rarely the size of any single gain - it is the volume of movements, each needing a clean basis and a traceable journal entry, so that the books reconcile to the wallets at period end.

A particular trap in high-volume stablecoin flows is the internal transfer: moving USDT between wallets the entity itself controls is not a disposal and creates no gain or loss, yet if the two legs are not matched, an automated process can mistake one leg for a sale and invent a phantom result. Distinguishing genuine disposals from internal movements is therefore a prerequisite for the realised figures to mean anything, and it is one of the first things an auditor will probe in a payments-heavy USDT book. The same care applies to fees paid in USDT, which are themselves small disposals matched against a lot, and to conversions between USDT and other assets, where the USDT leg and the other leg each have to be recognised on the correct side rather than netted into a single ambiguous entry.

Balance-sheet classification and presentation

Where USDT appears on the balance sheet follows directly from the classification judgment, and getting it right protects the integrity of the liquidity picture. It is not automatically cash or a cash equivalent - stablecoins generally fail those criteria because of counterparty and redemption risk - so defaulting it into cash would overstate liquidity and mislead a reader, even though standard-setters are actively considering stablecoin cash-equivalent questions. Depending on the judgment reached, USDT is presented within crypto or digital assets, within intangible assets, or, where a financial-asset analysis holds, as a receivable. The presentation should be accompanied by disclosure of the classification basis and the judgment behind it, because a reader cannot otherwise tell why a dollar-pegged token sits where it does. Regulatory status can also bear on the picture: under the EU's framework a single-currency stablecoin is treated as an e-money token, which may inform classification in some markets - a point covered on the existing page and worth confirming against current rules.

Controls and audit trail for a stablecoin position

Stablecoin controls share the crypto-asset fundamentals - reconciliation, completeness, deduplication - but shift the emphasis toward classification consistency, peg monitoring, and high-volume reconciliation. An auditor will want to see that the chosen treatment was applied to every unit without drift, that any peg deviations were assessed against the measurement policy, and that the large population of payment and treasury movements reconciles cleanly to the wallets without internal transfers being mistaken for disposals.

• Consistent classification - the determined treatment applied to every USDT unit and revisited only through a documented change, never silently varied.
• Peg-deviation monitoring - material or persistent departures from par assessed against the measurement policy rather than ignored.
• High-volume reconciliation - large payment and treasury flows tied back to wallet balances at period end.
• Internal-transfer flagging - movements between the entity's own wallets excluded from disposal calculations.
• Classification and valuation provenance - the judgment, its reasoning, and each value preserved with an immutable change history.

How CryptaCount handles USDT in the sub-ledger

CryptaCount tags USDT with its stablecoin and classification attributes - including peg and regulatory class - and applies the measurement treatment the firm has determined with its advisor, consistently across every unit. It tracks cost basis and movement across high-volume payment and treasury flows in one reconciled sub-ledger, matches disposals under the chosen cost-basis method, and posts every journal entry to the ERP with a full audit trail. Because the classification, the basis tracking, and the balance-sheet position all flow from the same reconciled records, the accumulation of many small stablecoin movements stays accurate and traceable rather than dissolving into an unexplained variance at period end.

If USDT tracks a dollar, why is moving it an accounting event?

Because USDT is not cash for accounting purposes. Each swap, payment, or conversion is a disposal matched against the cost basis of the units involved, and any small difference between proceeds and basis is a realised gain or loss. Individually tiny, these accumulate across a high-volume operation and have to be recorded accurately.

How does the classification judgment change USDT's measurement?

Decisively. As an intangible asset under cost-and-impairment, a fall below carrying amount may prompt a write-down while a recovery may not be recognised symmetrically. As a financial instrument such as a receivable, the focus shifts to recoverability of the redemption claim. The peg itself does not settle the question - the nature of the holder's claim does. Confirm the treatment with your auditor.

Can we present USDT within cash on the balance sheet?

Generally no. Stablecoins are not automatically cash or cash equivalents and typically fail those criteria due to counterparty and redemption risk, so presenting USDT within cash would overstate liquidity. It is shown within crypto or digital assets, intangibles, or as a receivable depending on the judgment, with disclosure of the basis.

What makes stablecoin accounting hard if the price barely moves?

Volume and judgment, rather than volatility. The classification is unsettled and requires documented reasoning, and a payments or treasury operation generates a very large population of movements that each need a clean basis and a traceable entry. The difficulty is keeping all of that reconciled and consistent at scale.