Do you revalue stablecoin balances at month end?

The answer depends on a decision you made earlier: how the balance is classified. There is no revaluation rule for stablecoins as a category, because stablecoins are not a category in US GAAP. Classification drives measurement, and measurement drives what you do at close.

Three classifications, three different month-end procedures.

If it is a cash equivalent: nothing to revalue

A cash equivalent is carried at face. One USDC is one dollar on the balance sheet, every period, and there is no remeasurement step.

The only close procedure is existence and completeness: confirm the on-chain balance matches the ledger, and that every movement in the period is recorded. That is reconciliation, not revaluation.

This is the simplest outcome and it is one reason companies argue for the classification. Whether it is available to you is covered in is USDC a cash equivalent under US GAAP.

If it is a financial asset: assess credit loss, not market price

Classified as a receivable under ASC 310, the balance is carried at amortized cost. You are not marking to market, because the asset is a claim for a fixed number of dollars, not a traded position.

What you do owe each period is an expected credit loss assessment under ASC 326. The question is not "what is USDC trading at" but "is there a risk the issuer fails to redeem at par." For a fully reserved issuer publishing regular attestations, the answer is usually that the expected loss is immaterial, and you document that conclusion.

It is still a judgment, and it is one that should be revisited rather than rolled forward blindly. The inputs are reserve composition, attestation recency, concentration of reserves in any single custodian or bank, and the issuer's redemption record under stress. Circle publishes reserve composition and attestation reports; other issuers publish on different schedules with different asset mixes.

A practical close step: record the attestation date and reserve composition you relied on. If the assessment is ever challenged, the question will be what you knew at the balance sheet date.

If it is an intangible: test for impairment, and watch the trough

This is where month-end gets genuinely dangerous.

Under ASC 350-30, an indefinite-lived intangible is carried at cost less impairment and tested whenever events or changes in circumstances indicate the carrying amount may not be recoverable. A stablecoin trading below par is exactly such an event.

Two features of that model catch finance teams out.

The test is triggered by events in the period, not just the closing price. If USDC traded at $0.92 on the 14th and recovered to $1.00 by the 31st, the depeg happened. A balance that looks fine at the reporting date may still require an impairment recognised at the lower value observed during the period. Your auditor will ask what the asset did between the dates, not only where it ended.

Impairment cannot be reversed. ASC 350-30 is one-way. Once written down, the carrying amount stays down even after the peg fully recovers. You carry a permanent book loss on an asset that is economically worth a dollar.

The March 2023 Silicon Valley Bank weekend is the reference case. USDC traded as low as roughly $0.87 before returning to par within days. Holders on the intangible model recognised impairments at the trough that they were prohibited from reversing. Holders on cash equivalent or receivable models did not.

If you are on the intangible model, build a price-monitoring step into close rather than only a balance check. You need intraperiod lows, not just period-end values.

What every classification needs: a clean reconciliation

Whatever the measurement model, close requires proving the balance is real and complete. On-chain assets make this both easier and harder than a bank account.

Easier, because the balance is independently verifiable. Anyone with the address can confirm it against a block explorer at a given block height, which is stronger evidence than a bank confirmation.

Harder, because the chain does not know what your invoices are. A wire carries a reference field; a token transfer carries an address, an amount and a hash. Matching that to an invoice is work that has to happen somewhere, and if it does not happen as the payment settles it has to be rebuilt later from timestamps and amounts. We cover the mechanics in how to reconcile an on-chain payment to an invoice.

A workable month-end sequence for stablecoin balances:

1. Pull the balance at a fixed block height for each address, and record the height. "As of 31 October" is ambiguous on a chain that produces blocks continuously; a block number is not.
2. Agree the movement between opening and closing balance to recorded transactions. Unexplained deltas are usually gas, dust or an unrecorded transfer.
3. Confirm address ownership is still documented for every address in the balance. See how to prove a wallet belongs to your company.
4. Apply the measurement step your classification requires: nothing, credit loss assessment, or impairment test.
5. Record what you relied on, including attestation dates and any intraperiod price observations.

Does the treasury size change the answer?

Not the accounting, but it changes how much the accounting costs you.

At small balances, an impairment on the intangible model is an annoyance. At meaningful treasury size it distorts reported results in a way that is hard to explain to a board, because the loss is real on the books and absent from the bank.

If stablecoins are a working capital instrument rather than a speculative position, that asymmetry is a good reason to work through whether the receivable or cash equivalent classification is available to you, and to document it properly. Stablecoin treasury for startups covers the broader float question.

FAQ

Do you have to revalue USDC at month end?

Only if your classification requires it. As a cash equivalent, no, it is carried at face. As a financial asset under ASC 310, you assess expected credit loss rather than market value. As an indefinite-lived intangible under ASC 350-30, you test for impairment whenever indicators exist, including a depeg during the period.

Does a stablecoin depeg create an accounting loss if the peg recovers?

Under the intangible model, yes, and it is permanent. ASC 350-30 impairment cannot be reversed, so a token that dipped and recovered within the same period can still leave a write-down on the books. Under cash equivalent or receivable classification, a temporary depeg does not produce the same result.

What price do I use for the impairment test?

The fair value at the measurement date, supported by observable market data. Because the test is triggered by indicators arising during the period, you also need intraperiod price observations rather than only the closing price. Document the source and timestamp of whatever price you use.

Do I need to mark stablecoins to market each period?

Not under any of the three classifications. Fair value through net income applies to crypto assets inside ASU 2023-08, and fiat-backed stablecoins are excluded from that standard because holders have redemption rights against the issuer.

What is the right balance date for an on-chain asset?

Use a block height rather than a wall-clock time, and record it. Chains produce blocks continuously, so a timestamp alone does not identify a single verifiable state. A block number lets anyone reproduce your balance exactly.

What should you do next?

Write down which classification you are on and what close procedure it requires. If you are on the intangible model and hold meaningful balances, add intraperiod price monitoring to close before the next depeg rather than after it.

Plaitr posts every transaction to the ledger as it settles, so the reconciliation step at close is a check rather than a rebuild. See auto accounting.

This article describes accounting standards and is not accounting advice.