This guide explains how to assess, record, and report stablecoins under your company’s applicable accounting framework. Before posting entries, identify the token’s contractual rights, the purpose for holding it, and whether your reporting uses IFRS, US GAAP, or another local standard; classification depends on those facts, not the “stablecoin” label.
What You’ll Need
- Your applicable reporting framework and accounting policies, including materiality thresholds.
- Token terms, issuer documentation, redemption arrangements, reserve disclosures, and custody or exchange agreements.
- Transaction records showing dates, token quantities, fees, counterparties, and the business purpose of each transfer.
- Reliable valuation evidence, bank and custodian statements, wallet records, and controls for access to private keys.
- An accountant familiar with your reporting framework and, where relevant, legal or tax advice. Accounting presentation and tax treatment are not necessarily the same.
Step-by-Step
- Confirm the framework and reporting purpose. Establish whether the financial statements follow IFRS Accounting Standards, US GAAP, or local rules, and which entity owns the tokens. Document whether the holding is for payments, treasury management, trading, customer activity, or another purpose. Review any sector-specific requirements and existing policies before deciding how to account for it.
- Identify what the token legally and economically represents. Read the issuer terms and determine who can redeem tokens, against whom, in what currency, at what amount, and subject to what conditions. Check whether the token gives a contractual claim to cash, a claim on a reserve, an interest in assets, or no enforceable claim against the issuer. Consider restrictions, redemption delays, fees, suspension rights, and whether rights differ by holder or jurisdiction. A stated one-to-one peg alone does not establish that the token is cash or a cash equivalent.
- Assess classification under the applicable standard. Under IFRS, a cryptocurrency holding will often be assessed under IAS 2 if held for sale in the ordinary course of business, including by a commodity broker-trader, or otherwise under IAS 38 as an intangible asset. However, contractual rights may mean a particular token falls under another standard, such as financial-instrument guidance; assess the facts rather than applying a blanket rule. Under US GAAP, evaluate the current accounting requirements for crypto assets and whether the asset meets their scope and exclusions. A token that creates an enforceable right to cash may require a different analysis. Record the reasoning and obtain technical accounting advice for material holdings.
- Set initial recognition and measurement. Record the asset when the company obtains control or otherwise meets the applicable standard’s recognition conditions. Use the measurement basis required by the classification: this may be transaction-date fair value, cost, or another prescribed amount. Include or expense transaction costs according to the relevant standard and the nature of the transaction. Keep the source for the exchange rate or fair-value measurement, and distinguish the token’s quoted market price from the amount actually redeemable after fees or restrictions.
- Record the transaction with a complete audit trail. For a purchase, document the date, quantity, consideration, fees, and valuation source; debit the appropriate asset account and credit cash or the payable account. For a payment to a supplier, record settlement using the carrying amount or measurement required by policy, recognize any resulting gain or loss where applicable, and record the related expense or liability settlement. For a transfer between wallets owned by the same entity, do not treat it as a sale merely because the address changed; record network fees separately and retain evidence of ownership and control.
- Apply subsequent measurement and impairment rules. At each reporting date, follow the standard and policy selected for that classification. Depending on the asset and framework, this may require cost less impairment, fair value with changes in profit or loss, or another measurement approach. Do not assume that a stable peg prevents impairment or fair-value changes. Investigate depegging, reduced redemption access, issuer distress, reserve concerns, market illiquidity, and sanctions or withdrawal restrictions. Recognize losses and reversals only as permitted by the relevant standard.
- Reconcile holdings and cut off transactions. Reconcile wallet balances and custodian statements to the general ledger at each close. Confirm token quantities using appropriate on-chain records, while checking that addresses belong to the entity and that records cover all wallets. Review transactions around period-end for correct dates, fees, pending transfers, and settlement status. Investigate unmatched items promptly and document any estimates or valuation adjustments.
- Assess cash-flow, presentation, and disclosure requirements. Decide whether the asset qualifies as cash or a cash equivalent only after applying the framework’s definition and considering its liquidity, purpose, redemption terms, and value risk. Do not classify it as cash simply because it is pegged to a currency. Present it in the appropriate balance-sheet category and assess required disclosures about measurement, accounting policy, risks, restrictions, fair-value inputs, and material balances. Consider whether customer-held tokens are assets, liabilities, or both under the specific arrangements.
- Approve the policy and maintain controls. Have the controller or finance lead approve a written policy covering classification, valuation sources, fees, reconciliation, impairment indicators, custody, and disclosure. Separate transaction approval from reconciliation where practical, restrict key access, maintain recovery procedures, and retain evidence under the company’s record-retention policy. Reassess the analysis when token terms, redemption arrangements, standards, or business use changes.
Common Mistakes
- Assuming all stablecoins are cash, cash equivalents, or financial assets because they target a currency.
- Relying on marketing statements about reserves instead of evaluating enforceable holder rights and redemption mechanics.
- Using a one-dollar value automatically at every reporting date, even when the market price, liquidity, or redemption access has changed.
- Recording internal wallet transfers as disposals, or omitting network fees and transaction-date evidence.
- Confusing accounting measurement with tax reporting, or applying one jurisdiction’s guidance to another framework.
- Failing to disclose significant judgments, restrictions, valuation uncertainty, or custody risks when required.
Tips
- Maintain a token-by-token assessment file; different tokens marketed as stablecoins may have materially different legal rights.
- Use a consistent, documented valuation hierarchy and specify what to do when a usual market or data source is unavailable.
- Keep quantity records separate from valuation records so a price change cannot obscure a wallet reconciliation difference.
- Include the controller, treasury, legal, and tax teams in the review, but document each team’s distinct conclusion.
- For material holdings or unclear rights, obtain a written technical accounting analysis before finalizing the statements.
Troubleshooting
The token trades below its peg: Check whether redemption is available to your company, whether the quoted market is liquid, and whether the price difference reflects fees or restrictions. Preserve evidence, reassess measurement and impairment under the applicable standard, and escalate material changes for review.
Issuer terms are unclear or unavailable: Do not infer a redemption right from a website description. Request current legal terms and supporting evidence from the issuer or custodian. If the rights cannot be established, document the uncertainty and consult technical accounting and legal advisers before selecting a classification.
Wallet records do not match the ledger: Confirm the correct network and token contract, identify transfers in transit, check fees and duplicate imports, and verify address ownership. Reconcile to independent custodian records where available; do not plug the difference without evidence.
No reliable closing price is available: Apply the framework’s measurement requirements and your approved valuation policy. Evaluate whether observable transactions are orderly and relevant, document any adjustment or estimation method, and disclose significant uncertainty when required.
Frequently Asked Questions
Are stablecoins cash equivalents?
Not automatically. Assess the applicable definition, purpose, liquidity, redemption rights, and exposure to changes in value. A peg alone is insufficient.
Are stablecoins treated the same under IFRS and US GAAP?
No. Standards, scope, and presentation can differ. Determine the reporting framework and analyze the token’s rights and use under its requirements.
How should a company record a stablecoin payment?
Record the underlying purchase or liability settlement, the token’s relevant carrying or transaction-date value, and any required gain, loss, or fee. Retain the transaction evidence.
Can a stablecoin lose value for accounting purposes?
Yes. Market discounts, impaired redemption, issuer problems, or restrictions may affect measurement even when the token is designed to maintain a peg.
What evidence should be retained?
Keep transaction and wallet records, valuation sources, issuer terms, custody statements, fee details, reconciliation work, and the documented classification decision.
Does accounting treatment determine tax treatment?
No. Tax rules can differ from financial reporting rules. Check the requirements in each relevant jurisdiction with a qualified tax adviser.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Multi-Asset Trading Platforms: Why They’re Essential
- Creality K3 4-Nozzle 3D Printer: 4.8s Swap?
- Notepad Remove Duplicate Lines: 3 Simple Ways
- API Security Checklist: A Backend Dev’s Guide
- Storefront Hero Images: Desktop vs. Mobile Versions
- McAfee Mobile Security Antivirus: Does It Work?