Stablecoin accounting treatment: is a settlement balance cash, a financial asset or an intangible?

Stablecoin accounting treatment is the question a finance team reaches once the payment problem is solved. The corridor works. Then the controller asks a harder question: what is this balance, and where does it sit in the financial statements? It is not the same under IFRS and US GAAP, and it changes depending on whether the holder has a redemption right against the issuer.

This article sets out the stablecoin accounting treatment questions a payment institution must answer, the standards behind them, and the evidence a settlement wallet needs at close and at audit. It is general information for finance and treasury leaders, not accounting advice on your own facts.

Is a stablecoin balance cash on the balance sheet?

Most teams start by calling it cash. That is usually wrong. Under IAS 7, cash means cash on hand and demand deposits. Cash equivalents are short term, highly liquid investments that are readily convertible to known amounts of cash and subject to insignificant risk of changes in value. A token balance in a wallet you control is neither. It is not a bank deposit.

US GAAP arrives at a similar place by a different route. ASC 305 frames cash and cash equivalents around demand deposits and short term instruments. A token on a public blockchain does not fit that either. So the balance normally sits on its own line, outside cash, and it does not count toward the cash figure a lender, a board or a regulator reads.

A tokenised deposit is a different instrument: a claim on the issuing bank, recorded on a ledger. Keep the two apart in your policy, because classification follows the legal claim and not the technology.

What does IFRS say about stablecoin accounting treatment?

IFRS has no standard written for stablecoins. The closest authoritative guidance is the IFRS Interpretations Committee agenda decision of June 2019 on holdings of cryptocurrencies. It concluded that a cryptocurrency is not cash and not a financial asset. It should be accounted for under IAS 38 Intangible Assets, or under IAS 2 Inventories when it is held for sale in the ordinary course of business.

That decision was written about tokens with no issuer claim behind them. A fiat referenced stablecoin can be different. Where the holder has an enforceable contractual right to receive cash from the issuer, the instrument may meet the IFRS 9 definition of a financial asset. The test is the contract, not the label on the token.

This is where most institutions find the real answer. Can we, as the holder of record, present this token to the issuer and demand fiat? A redeemer with a direct issuer relationship often can. A holder who received the token from a counterparty, with no account at the issuer, often cannot. The first case points toward a financial asset. The second points back to IAS 38.

The choice shows up in the accounts. A financial asset behaves predictably at amortised cost or at fair value through profit or loss. An intangible asset carried at cost cannot be written up above cost, so a recovery after a write down does not flow back through profit the way a treasurer expects.

How does US GAAP treat a stablecoin held for settlement?

The FASB answered part of this in Accounting Standards Update 2023-08, issued in December 2023, which created Subtopic 350-60 and requires in scope crypto assets to be measured at fair value with changes in net income. It applies to fiscal years beginning after 15 December 2024.

Scope is the catch. Subtopic 350-60 reaches an asset only if several criteria are met at once. One of them is that the asset does not provide the holder with enforceable rights to or claims on underlying goods, services or other assets. A fiat backed stablecoin with a contractual redemption right may fail that criterion.

So the fair value model the market associates with that update may not reach your balance at all. Run the scope test on the specific token and the specific holder relationship, document the conclusion, then apply Subtopic 350-60, financial instrument guidance or the residual intangible model, and state in the policy why.

Two further items are worth knowing. The AICPA practice aid on accounting for and auditing of digital assets is non authoritative, but many audit teams work from it. And the SEC Staff Accounting Bulletin No. 122, issued in January 2025, rescinded Staff Accounting Bulletin No. 121, which had required a platform safeguarding customer crypto to recognise a liability and a corresponding asset. For an entity holding tokens for customers, that change affects disclosure rather than custody controls. Capital treatment is separate again, and for a bank it is set by the Basel Committee cryptoasset prudential standard published in December 2022.

Where do fees, conversion spread and a depeg land in the accounts?

A cross border payment that settles on chain creates several small amounts that need a home. Network fees are a transaction cost. Where they relate directly to acquiring the token, there is an argument to capitalise them. Where they are the cost of making a payment, they are an operating expense. Pick one policy and apply it every month.

Conversion spread is usually the larger number. Buying on one side and selling on the other both move value. If the instrument is a financial asset, that movement runs through profit or loss in the normal way. If it is an intangible, a gain only appears on disposal, so the income statement reports a lumpy result even though the economics were continuous.

A depeg is a measurement event, not a new accounting treatment. Under a fair value model the loss appears as it happens. Under the cost model it appears as an impairment once the recoverable amount falls below carrying amount. Decide in advance which trigger you watch and who signs the write down.

Translation is a separate question with the same root. A financial asset is a monetary item, translated at the closing rate. An intangible carried at cost is non monetary, translated at the rate on the transaction date. The classification you chose earlier decides this too.

What does the month end close look like for a settlement wallet?

The close is where accounting treatment meets operations. The wallet is the sub ledger. The chain is the statement. The work is to prove the two agree, and that every movement had an instruction behind it.

• Freeze a cut off. Record the block height and the timestamp you treated as period end, and keep the same confirmation depth every month.
• Pull the full on chain history for every settlement address, including addresses used only once.
• Match each movement to the instruction that caused it by unique end to end reference, so the pacs.008 or pacs.009 and the chain entry carry the same identifier.
• Treat anything unmatched as a break with an owner, a value and an age, not as a note in the file.
• Revalue the balance under your stated policy, and record the rate source and the time you used.
• Produce a statement for the period, in the camt.053 structure if your systems speak it, and reconcile the closing balance to the chain.
• Have a second person who did not move funds sign the reconciliation.

Screenshots from a block explorer are not evidence. An export with no cut off rule is not a statement. If the only record of why a payment moved lives in an operator inbox, the reconciliation is not finished.

What evidence will the auditor ask for?

An auditor tests three things on a token balance: existence, ownership and measurement. Existence is easy: a public chain shows the balance to anyone who looks. Ownership is harder. The balance proves the address holds the tokens. It does not prove your institution controls the address.

Expect a request to demonstrate control, usually by signing a message from the address or moving a small amount on request. Expect questions about who holds the keys, how many signatures a payment needs, and what happens when a signer leaves. Where a third party holds the keys, expect its service report.

Measurement brings back the classification. Have the written policy, the scope analysis behind it, the rate source and the approvals. An auditor can accept more than one defensible answer, but not a different answer each quarter.

The balance on a public chain is the easiest item in the file to verify and the hardest to explain. Classification, proof of control, and the reconciliation that joins a chain entry to a payment instruction are what an audit turns on.

Build the file as you go. A reconciliation produced monthly, signed and stored, costs little. Rebuilt a year later from explorer exports it costs far more and proves less. Settle your stablecoin accounting treatment in writing before the first corridor goes live, not during the first audit.

Where StableNet fits

StableNet, built by SpendTheBits, is a cross border B2B payment and settlement platform for banks, credit unions, licensed money service businesses, exchange houses and remittance fintechs. Settlement runs in regulated stablecoins on public blockchains and completes in minutes with on chain auditability. Because the platform is ISO 20022 native, with pacs.008 customer credit transfers, pacs.009 interbank legs, pacs.002 status reports and pacs.004 returns tracked by UETR, every chain movement carries the reference a reconciliation needs. KYB and KYC onboarding, KYT, sanctions and PEP screening, Travel Rule data and a tamper evident audit trail sit alongside it. That is what turns a wallet balance into a record a finance team can close and an auditor can test.