Stablecoin Chart of Accounts: Why It Is Not a Cash Account

The most common stablecoin accounting error is the most intuitive one: it tracks a dollar, so it goes in the cash account. For accounting, a stablecoin is generally not cash — it is a crypto-asset whose classification follows the same framework analysis as any token. This guide structures the accounts so the balance sheet is right, hedged, because the classification is an auditor judgement.

TL;DR

• A typical stablecoin is generally not cash and often not a cash equivalent — not legal tender, different terms/risks from a bank deposit.
• It is commonly analyzed as a crypto-asset under the applicable framework, like other tokens.
• Booking it in cash overstates cash and hides it from crypto disclosures and the right measurement model.
• Structure it as its own crypto-asset accounts (asset + wallet axes, realized/unrealized) — not a fixed-at-par cash line.
• Depeg risk is part of why it isn't cash — carrying amount/impairment/fair value per the model.
• Framework-, instrument-, and jurisdiction-specific auditor judgement. Not accounting advice.

Behaves like a dollar ≠ is cash

Despite being designed to track a fiat value, a typical stablecoin is usually not cash and often not a cash equivalent for accounting: it is not legal tender, and its terms and risks differ from a bank deposit. It is commonly analyzed as a crypto-asset under the applicable framework, the same way other tokens are (see stablecoin accounting treatment). "Behaves like a dollar" is an economic intuition, not the classification — an auditor judgement on the specific instrument.

Why it matters

Putting stablecoins in the cash account is exactly the kind of misstatement an auditor looks for. The CoA should keep them out of cash unless a specific analysis concludes otherwise.

How the chart of accounts should handle them

Typically as their own crypto-asset accounts within the same classification framework used for other tokens (intangible, financial asset, or another treatment per the facts/framework), with the asset and wallet mapping axes applied as for any crypto (see chart of accounts design). Separating stablecoins from volatile crypto for management analysis is fine — but separation ≠ treating them as cash. Auditor-confirmed.

Depeg is part of the reason

A stablecoin can deviate from its reference value, so its carrying amount and any impairment or fair-value change are accounted for under the applicable model, not assumed at par. The CoA therefore needs the same realized/unrealized structure as other crypto (see realized vs unrealized gain accounts), not a fixed-at-par cash line. Treatment of a deviation is framework-specific, auditor-confirmed.

Not one global rule

The general "not cash" position is widely applicable, but the precise classification and measurement depend on the framework (IFRS, US GAAP, French ANC) and the specific stablecoin's terms, and regulatory context such as the EU MiCA regime affects related obligations. The CoA follows the applicable framework's conclusion for that instrument, auditor-confirmed — not a single global rule.

Practical guidance

1. Keep stablecoins out of the cash account by default.
2. Classify them under the same framework as other crypto-assets.
3. Use their own crypto-asset accounts with asset/wallet axes.
4. Apply realized/unrealized structure — depeg means not fixed at par.
5. Separate for analysis if useful — but that is not "cash".
6. Confirm the instrument's treatment with your auditor — framework-/instrument-specific; not accounting advice.

How vendor tools handle stablecoins

Cryptio and Bitwave can map stablecoins to dedicated crypto-asset accounts rather than cash and apply the configured measurement. Confirm the tool does not default stablecoins into cash — the tool applies the mapping; whether a stablecoin is cash, a cash equivalent, or a crypto-asset is an auditor judgement.

How Wag3s helps

Wag3s Ledger maps stablecoins to dedicated crypto-asset accounts (asset + wallet axes, realized/unrealized), not the cash line, with an audit trail and ERP export — while the classification of a specific stablecoin under the applicable framework stays auditor-confirmed. See the Ledger product page.

Further reading

• Stablecoin Accounting Treatment
• Crypto Chart of Accounts Design
• Crypto Asset Account Classification
• Crypto Realized vs Unrealized Gain Accounts
• Stablecoin Payment Reconciliation
• Crypto CoA: GAAP and IFRS Mapping

Sources

• A typical stablecoin is generally not cash and often not a cash equivalent for accounting (not legal tender; terms/risks differ from a bank deposit); commonly analyzed as a crypto-asset under the applicable framework like other tokens
• Booking stablecoins as cash overstates cash and removes them from crypto disclosures and the correct measurement model — keep in dedicated crypto-asset accounts (asset + wallet axes, realized/unrealized) unless a specific analysis concludes otherwise
• Depeg risk means carrying amount/impairment/fair-value change must follow the applicable model, not par; separation for management analysis is not the same as cash classification
• Precise classification/measurement is framework- (IFRS/US GAAP/French ANC), instrument-, and jurisdiction-specific (MiCA context); auditor-confirmed — not a single global rule, not accounting advice