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

A crypto-heavy balance sheet can move materially between the reporting date and the day the accounts are signed. That makes two quietly important areas live: going concern (a treasury leaning on volatile crypto) and events after the reporting period (adjusting vs non-adjusting). This guide is how crypto volatility reaches these judgements, hedged, because they are the auditor's call.

TL;DR

• If liquidity/solvency depends materially on volatile crypto, the going-concern assessment must consider a significant adverse move (runway, obligations) — holding volatile assets alone isn't a problem; concentration + thin fiat runway is.
• Subsequent events: adjusting = evidence of a year-end condition (adjust); non-adjusting = after-period condition (disclose if material, don't 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 if it reveals a condition that already existed at year-end (e.g. an already-impaired holding) — fact-specific.
• Most acute for crypto-treasury entities but relevant to any material crypto holder.
• Going-concern / subsequent-events conclusions are fact-specific auditor judgements. Not accounting/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 affects the ability to continue operating — liquidity runway and obligations (ties crypto treasury KPIs and board reporting). Holding volatile assets alone isn't a going-concern problem; a treasury concentrated in crypto with limited fiat runway is exactly the dependency the assessment must address. Fact-specific auditor judgement.

Adjusting vs non-adjusting events

A crypto price movement after year-end is typically non-adjusting (reflects after-period conditions) — disclosed if material, not a reason to restate the year-end carrying amount. Classification is fact-specific, 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. 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 — e.g. confirming a counterparty/holding was already impaired or unrecoverable at year-end, as opposed to a fresh market move afterwards. The distinction: does the event reveal a year-end condition or a new one? Fact-specific auditor judgement — not a blanket "crypto events are always non-adjusting" rule.

Not only crypto-treasury companies

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 reporting-date-to-authorization movement more likely to be material than for many traditional assets. Materiality and treatment are auditor judgements per 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 period-end and post-period holdings/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, are auditor judgements under the applicable framework.

How Wag3s helps

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 is evidenced — while the adjusting/non-adjusting classification and going-concern conclusion stay auditor-confirmed. 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

• Where liquidity/solvency depends materially on volatile crypto, the going-concern assessment must consider a significant adverse move (runway, obligations) — concentration + thin fiat runway is the dependency, not holding volatile assets per se
• Events after the reporting period: adjusting (evidence of a condition existing at reporting date — adjust) vs non-adjusting (condition arose after — disclose if material, don't adjust); a post-year-end crypto price move is typically non-adjusting
• A post-reporting-date price change generally does not change the year-end carrying amount but is disclosed if material and can interact with going concern in severe cases; it can be adjusting if it reveals an already-existing year-end condition
• Relevant to any material crypto holder (most acute for treasuries); crypto volatility/24-7 trading makes after-period movements more likely material — materiality, classification, and going-concern conclusions are fact-specific auditor judgements, not accounting/audit advice