Stablecoin accounting: classification, measurement, treasury use, controls and depeg risk

Stablecoin accounting for finance and accounting teams. How to account for stablecoins — classification, measurement, treasury use, reconciliation, controls and depeg considerations — under IFRS and US GAAP, with a sub-ledger that keeps every balance reconciled and auditable. This guide covers the treatment and how CryptaCount's crypto sub-ledger automates it.

General information on accounting treatment, not accounting or tax advice. Verify against the applicable standards (IFRS / US GAAP) and your auditor.

What makes stablecoins hard to account for

Stablecoin accounting is the discipline of recording stablecoin holdings and movements correctly: deciding what kind of asset a stablecoin is, how it is measured at each reporting date, how the entity controls and reconciles it, and how to handle the moments when its value departs from its peg. The trap is that stablecoins look like cash — a token nominally worth one unit of a fiat currency, used to settle, hold value and move funds — and the temptation is to wave them through as if they were a bank balance. They generally are not, and treating them as cash without analysis is a classification error that misstates the balance sheet.

The core difficulty is that a stablecoin is a token, not a deposit. Holding it is usually not a contractual right to receive cash from a bank or a regulated payment institution in the way a cash balance is; it is a holding of a digital asset whose value is intended — but not guaranteed — to track a reference currency. Different stablecoins achieve that peg in different ways: some are backed by reserves of fiat and equivalents, some by other crypto collateral, some algorithmically. The backing model affects both the risk profile and the accounting judgement, so 'stablecoin' is not a single accounting category.

The second difficulty is measurement and the peg. Even a well-run, fiat-backed stablecoin is not automatically equal to one fiat unit on the balance sheet. Its market value can sit slightly above or below the peg, and in stress it can depeg materially. An accounting policy that assumes a fixed one-to-one value ignores real value movements that the framework may require to be recognised. Measurement therefore has to be deliberate rather than assumed away.

The third difficulty is volume and reconciliation. Stablecoins are the working capital of on-chain operations: they pay suppliers, receive customer funds, fund DeFi positions and bridge between chains, often in high volume across many wallets. Every one of those movements is an accounting event, and the on-book balance must reconcile to the actual on-chain holding at the cut-off. Keeping that reconciliation tight at scale is precisely what a crypto sub-ledger exists to do.

How the activity maps to the books

The same three decisions govern stablecoins as any other asset: recognition (a receipt or payment of stablecoin is an event to be booked), measurement (at what value the holding sits at period end), and classification (which line it belongs to). The work is to resist the cash shortcut and apply the entity's framework and policy deliberately.

Classification

The first question is whether a stablecoin meets the definition of cash or a cash equivalent, a financial instrument, or — as is common — neither, leaving it presented like other digital assets. Most stablecoins are not cash, because the token is not itself legal tender or a demand deposit at a bank; whether a particular stablecoin carries financial-instrument characteristics depends on the rights it confers, which varies by issuer and structure. Where it is neither, it is generally presented as an intangible asset, or as inventory where the entity trades it. The classification is reasoned from the specific token and the reason it is held, not from the fact that it carries a fiat name.

Measurement under IFRS and US GAAP

Measurement follows classification and the framework. Under IFRS, a stablecoin presented as an intangible or as inventory is measured on the model that classification dictates, and any movement away from the peg is reflected through that model rather than ignored. Under US GAAP, the treatment of in-scope crypto assets has moved toward fair value with changes recognised in net income, and whether a given stablecoin falls inside that scope depends on its characteristics. The practical point is that the carrying value of a stablecoin is a measurement conclusion, not a constant — and the entity needs a documented price source to support it. This is framework-level guidance; confirm the specific treatment against current standards and professional advice.

Treasury use

Many entities use stablecoins as operating treasury — the on-chain equivalent of an operating cash account — to receive revenue, pay vendors and hold short-term working balances. Even where used this way, the accounting policy has to state how the holding is classified and measured, how it is segregated by purpose, and how it is presented between current and non-current where relevant. Treating an operating stablecoin balance as if it were a bank account in the policy, while it sits on the balance sheet as a digital asset, is the kind of inconsistency auditors look for. Treasury use also raises practical questions the policy should answer: which stablecoins are approved for operating balances, what concentration limits apply per issuer, how balances held with custodians and on exchanges are presented separately from self-custodied wallets, and how short-term yield earned on idle stablecoin balances — where the entity chooses to earn it — is recognised as income. Each of these is an accounting choice, not an operational detail, and each leaves a trail a sub-ledger can hold.

Cost basis and gains and losses

Because a stablecoin's value moves around its peg, acquiring and disposing of it can produce real, if small, gains and losses that have to be measured against a cost basis. A stablecoin received at a slight premium and later spent at a slight discount realises a loss; the reverse realises a gain. Across high transaction volumes these small movements aggregate into figures that matter and that an auditor expects to see supported. The basis of each unit is what was effectively paid to acquire it, tracked consistently.

That tracking needs a consistent cost-basis method applied uniformly — FIFO, weighted average or another supported approach — so that each disposal consumes lots in a reproducible order. As an illustrative example, an entity receives 1,000,000 units of a stablecoin valued at 1.002 each (a small premium), carrying them at 1,002,000, and later settles a 1,000,000-unit supplier payment when the token is valued at 0.998, recognising a 4,000 loss on the movement away from and back through the peg (all figures illustrative). At true one-to-one assumed value, that loss would never appear, understating the real cost of holding and moving the asset.

Revaluation and depeg considerations

At each reporting date, stablecoin holdings have to be carried at the value the measurement basis requires, using a documented price source applied consistently — not defaulted to the peg. In normal conditions the adjustment is small. The case that matters is a depeg: an event where a stablecoin's market value diverges materially from its reference currency, whether briefly or persistently. A depeg is a real change in value that the framework may require to be recognised — through fair-value movement or impairment depending on the model — and an accounting process that hard-codes a one-to-one value will simply fail to capture it.

Beyond the mark itself, a depeg or a deterioration in an issuer's backing can be an impairment indicator for stablecoins carried at cost, and a risk-disclosure trigger regardless of measurement model. Concentration in a single issuer, the nature and transparency of the reserves, and redemption mechanics are all matters a reader may reasonably expect the notes to address where the exposure is significant. The discipline is to treat the peg as an assumption to be tested at each close, not a fact to be assumed.

Controls and audit trail

Auditable stablecoin accounting needs an unbroken chain from each reported figure back to the on-chain event behind it, and the controls are sharpened by the high transaction volume. The questions are: has every wallet that holds or moves stablecoins been captured — completeness. Does the on-book balance of each stablecoin reconcile to the actual on-chain holding at the cut-off. Was each holding marked at a documented price at the measurement date. Are issuer concentration and depeg exposure monitored and disclosed where material.

• completeness — every wallet and account that touches stablecoins ingested, with gaps flagged rather than silently missing;
• reconciliation — ledger balances agreed to on-chain holdings at each measurement date, treating any difference as an early warning;
• valuation evidence — the price source and date recorded for each period-end mark, rather than defaulting to the peg;
• issuer and concentration monitoring — exposure by stablecoin and issuer tracked so depeg and backing risks can be disclosed;
• deterministic recomputation — the same inputs always reproducing the same balances so an auditor can re-run the numbers.

Because blockchains are public, the reconciliation runs against an independent source of truth — the chain itself — which is a stronger position than a bank balance that can only be confirmed by a third-party statement. A difference between the ledger and the chain points straight at a missing wallet, an unrecorded settlement or a misclassified movement, and catching it at close keeps it out of the published statements.

How CryptaCount handles stablecoins

CryptaCount is a crypto sub-ledger that sits in front of the general ledger and turns stablecoin activity into accounting records. It ingests on-chain transactions and exchange activity across every wallet and account, recognises each receipt, payment and transfer, and classifies the holding deliberately rather than defaulting it to cash. Each stablecoin is marked at a documented price at the measurement date, so the carrying value reflects the real position around the peg instead of an assumed one-to-one.

On that activity, CryptaCount computes cost basis and gains using a consistent method across high transaction volumes, surfaces issuer and concentration exposure for disclosure, supports impairment and revaluation where a depeg requires it, and posts summarised period journal entries to the general ledger. Every GL balance decomposes back into the individual on-chain movements behind it, so an auditor can select a figure, trace it to the underlying settlements, and confirm each against the public chain. The same engine presents the activity under IFRS or US GAAP and supports DAC8, CARF and MiCA reporting, so an accounting firm, fund administrator or web3 treasury can run stablecoin operations at volume and still close the period from a reconciled, auditable record.