Crypto, Going Concern & Subsequent Events: When Volatility Hits the Audit

Most balance-sheet items barely move between the reporting date and the day the accounts are signed. A crypto-heavy one can swing materially in that window — and that single fact makes two audit areas live that are otherwise routine: the going-concern assessment (where liquidity leans on a volatile treasury) and events after the reporting period (the adjusting versus non-adjusting split). This guide is about how crypto volatility specifically reaches those two judgements: when a price drop is a disclosure note, when it is something graver, and where it crosses into going concern. The conclusions are the auditor's, so the framing here is deliberately hedged.

The two judgements in brief

• If liquidity or solvency depends materially on volatile crypto, the going-concern assessment must consider a significant adverse move (runway, obligations). Holding volatile assets alone is not the problem; concentration plus thin fiat runway is.
• Subsequent events split two ways: an adjusting event is evidence of a condition that existed at year-end (adjust the figures); a non-adjusting event reflects a condition that arose after (disclose if material, do not adjust).
• A post-year-end price move is typically non-adjusting — disclosed if material, not a reason to restate the year-end carrying amount.
• It can be adjusting where it reveals a condition that already existed at year-end (for example an already-impaired holding). The classification is fact-specific.
• This is most acute for crypto-treasury entities but relevant to any material crypto holder.
• Going-concern and subsequent-events conclusions are fact-specific auditor judgements. This is not accounting or audit advice.

Crypto and going concern

If an entity's liquidity or solvency depends materially on crypto whose value is volatile, the going-concern assessment must consider how a significant adverse move would affect the ability to continue operating — the liquidity runway and the obligations that fall due (this ties into crypto treasury KPIs and board reporting). Holding volatile assets alone is not a going-concern problem; a treasury concentrated in crypto with limited fiat runway is exactly the dependency the assessment must address. The conclusion is a fact-specific auditor judgement.

Adjusting vs non-adjusting events

A crypto price movement after year-end is typically non-adjusting, because it reflects after-period conditions — disclosed if material, not a reason to restate the year-end carrying amount. The classification is fact-specific and auditor-confirmed.

A post-year-end price drop

Generally a post-reporting-date price change is non-adjusting, so the year-end carrying amount (measured under the applicable model) is not changed for it. If material, it is disclosed so users understand the post-period position, and in severe cases it can interact with going concern. Restating the year-end balance for an after-period move is usually wrong; evaluating it for disclosure and going concern is right. The call is auditor-confirmed.

When it is adjusting

It can be adjusting where after-period information provides evidence about a condition that already existed at the reporting date — for example, confirming a counterparty or holding was already impaired or unrecoverable at year-end, as opposed to a fresh market move afterwards. The distinction is whether the event reveals a year-end condition or a new one. That is a fact-specific auditor judgement, not a blanket "crypto events are always non-adjusting" rule.

Not only crypto-treasury companies

This is most acute for crypto-treasury entities, but any entity with material crypto holdings has potential subsequent-events disclosure and, if dependency is significant, going-concern considerations. Crypto's volatility and near-continuous trading make the movement between the reporting date and the authorization date more likely to be material than for many traditional assets. Materiality and treatment are auditor judgements on the facts.

Practical guidance

1. Assess going concern against crypto dependency — concentration + thin runway is the risk.
2. Classify after-period events adjusting vs non-adjusting on whether they reveal a year-end condition.
3. Treat post-year-end price moves as typically non-adjusting — disclose if material, don't restate.
4. Watch for genuinely adjusting events (already-impaired/unrecoverable at year-end).
5. Apply this to any material crypto holder, not just treasuries.
6. Confirm going-concern and subsequent-events conclusions with your auditor — fact-specific; not accounting/audit advice.

How vendor tools support these judgements

Cryptio and Bitwave provide the period-end and post-period holdings and price data that informs the going-concern and subsequent-events analysis. The tool provides the data; whether an event is adjusting, and the going-concern conclusion itself, are auditor judgements under the applicable framework.

Where Wag3s fits

Wag3s Ledger records period-end and post-period holdings and price movements with timestamps and an audit trail, so the subsequent-events and going-concern analysis rests on evidenced figures rather than reconstruction. It documents the movement; the adjusting versus non-adjusting classification and the going-concern conclusion stay with the auditor. See the Ledger product page.

Further reading

• Crypto Treasury KPIs
• Crypto Treasury Board Reporting
• Crypto Asset Disclosure Notes
• Crypto Asset Account Classification
• Crypto Impairment vs Fair Value Accounting
• Crypto Audit Readiness

Sources

• AICPA & CIMA — Statement on Auditing Standards No. 132, The Auditor's Consideration of an Entity's Ability to Continue as a Going Concern: the US going-concern audit requirement, including separate conclusions on the going-concern basis and on substantial doubt.
• IAASB — International Standard on Auditing (ISA) 570 (Revised), Going Concern: the international going-concern standard the auditor applies where a treasury depends on volatile crypto.
• IAASB — Basis for Conclusions: ISA 560, Subsequent Events: the auditor's responsibilities for events between the reporting date and the date the financial statements are authorized.
• The adjusting versus non-adjusting accounting classification itself sits in IAS 10 (Events after the Reporting Period) under IFRS and ASC 855 (Subsequent Events) under US GAAP; the materiality, classification, and going-concern conclusions remain fact-specific auditor judgements and this article is not accounting or audit advice.