Crypto Asset Disclosure Notes: What the Financial Statements Must Say

Getting the recognition right is only half the work. The notes are where a reader actually learns what crypto an entity holds, how it is measured, and what could go wrong, and the requirements come from several directions at once: ASU 2023-08 added specific crypto disclosures, IFRS calls for policy and fair-value-hierarchy disclosure, and users increasingly expect custody and risk transparency. This article pulls those disclosure threads together. The fair-value measurement that feeds the hierarchy disclosure is covered separately in crypto and IFRS 13.

The disclosure picture in brief

• Crypto is volatile, often material, and measured under judgemental policies, so users need to know what is held, how it is measured, and the risks.
• FASB ASU 2023-08 added specific crypto disclosures alongside the move to fair value, with a separate balance-sheet line in the 2026 FASB taxonomy.
• IFRS requires the accounting policy and, where fair value is used, the IFRS 13 hierarchy level, valuation technique, and Level 2 and Level 3 inputs, plus the significant judgements.
• Custody and risk context is increasingly expected; some of it is required and some is good practice.
• IFRS and US GAAP disclosures differ, so a dual-reporting group has to satisfy both.
• The exact package is framework- and materiality-specific and auditor-confirmed. It is not a fixed template, and this is not accounting advice.

Why specific disclosures

Crypto is volatile, often material, and measured under judgemental policies, so users need to understand what is held, how it is measured, and the risks. ASU 2023-08 introduced specific crypto disclosures alongside the fair-value move; IFRS requires the accounting policy and, where fair value applies, the fair-value hierarchy. The exact package is framework-specific and an auditor judgement, not a generic template.

What ASU 2023-08 disclosure covers

Broadly, for in-scope crypto, ASU 2023-08 added disclosures around the holdings and their fair value, including information helping users understand the holdings and the period's changes, consistent with fair value through net income and the separate balance-sheet presentation (2026 FASB taxonomy). The precise line items/granularity are set by the standard and read from it with the auditor — not enumerated here as a fixed checklist (anti-fabrication discipline).

What IFRS disclosure covers

At minimum: the accounting policy (IAS 38 cost/revaluation, or IAS 2); where fair value is measured, the IFRS 13 hierarchy level, valuation technique, and L2/L3 significant inputs; and significant judgements in classification/measurement. The specific IFRS set depends on the standards applied, auditor-confirmed.

Custody and risk context

Users increasingly expect transparency on how crypto is held (self-custody vs third-party custodian) and related risks (volatility, concentration, key/operational). Depending on framework and materiality, some is required, some good practice. Disclosure is not only the balance-sheet number but the context a reader needs — a framework-/materiality-specific auditor judgement.

IFRS and US GAAP differ

Measurement bases differ (IAS 38 vs ASU 2023-08), so disclosures differ; a dual-reporting group satisfies each framework's requirements (see crypto CoA GAAP/IFRS mapping). The categories are similar in spirit; the specific required disclosures follow the entity's actual framework, auditor-confirmed.

Practical guidance

1. Treat disclosure as half the job — recognition is not enough.
2. Read ASU 2023-08 disclosures from the standard with the auditor — no fixed checklist assumed.
3. Disclose the IFRS policy + hierarchy level + judgements where applicable.
4. Add custody/risk context per framework and materiality.
5. Satisfy both frameworks if dual-reporting — disclosures aren't shared.
6. Confirm the required package with your auditor — framework-/materiality-specific; not accounting advice.

Choosing a tool that feeds the disclosure notes

The notes can only be finalised if the subledger can produce the source data behind each disclosure element. If you are evaluating a tool — Cryptio and Bitwave produce holdings, movement, and fair-value reports — confirm it can:

• produce a per-period holdings schedule that reconciles to the general ledger;
• build a roll-forward of additions, disposals, and remeasurements across the full fiscal period;
• carry the fair-value hierarchy data behind each asset's level;
• capture custody information (self-custody, named custodians, exchange venues).

The tool feeds the disclosures; what must be disclosed is an auditor judgement under the applicable standards.

Documentation required to support crypto disclosures

Regardless of framework, the entity must be able to produce source data for each disclosure element before the notes can be finalized. The following documents the minimum supporting evidence by category; the exact disclosure language and judgements remain the auditor's.

Holdings and balance sheet presentation

The entity must provide a holdings schedule as of the reporting date showing: each type of digital asset, units held, per-unit carrying value, and total carrying value. For ASU 2023-08 entities this schedule reflects fair value at period-end; for IFRS entities under IAS 38 cost model it reflects historical cost less any impairment. The schedule must reconcile to the general ledger balance. A schedule that cannot be tied to the GL is not sufficient to support the disclosure note.

Period movements (roll-forward)

Disclosures around the changes during the period require an opening balance, additions (purchases, staking rewards, airdrops), disposals (with proceeds and realized gain/loss), remeasurements (fair-value movements for ASU 2023-08 scope), and closing balance. This roll-forward is prepared from the subledger's transaction history and must cover the full fiscal period without gaps.

Fair-value hierarchy evidence

For entities measuring crypto at fair value, the disclosure note requires the hierarchy level for each asset:

• Level 1: quoted prices in active markets — the standard for major tokens (BTC, ETH) traded on regulated venues. The entity identifies the principal market used and documents why it qualifies as the most advantageous market.
• Level 2: observable inputs other than Level 1 — relevant for less-liquid tokens where pricing is derived from comparable markets or indices.
• Level 3: unobservable inputs — relevant for governance tokens, illiquid DeFi positions, or locked vesting contracts where no active market exists. Level 3 disclosures require the valuation technique and significant unobservable inputs.

The pricing source and methodology are documented and retained to support the hierarchy classification — the auditor tests not just the number but the basis for the classification.

Accounting policy note

The policy note discloses: the classification applied (e.g. intangible asset under IAS 38, or in-scope crypto under ASU 2023-08), the measurement model (cost, revaluation, or fair value through net income), and the recognition point for staking and other crypto income. Policy changes from prior periods require comparative disclosure under both IFRS (IAS 8) and US GAAP.

Custody and risk context

The custody section identifies: self-custody wallets (confirming key management and multisig arrangements), third-party custodians (named, with any SOC report reference), and exchange account holdings (named venues, with balances). Risk disclosures cover: price volatility, concentration risk, regulatory risk, and operational/key-management risk. Whether specific items are required under the applicable standard or are best-practice is confirmed with the auditor.

What happens when source data is incomplete

If the subledger cannot produce a complete roll-forward — for example due to unmapped wallets or missing pricing data for a period — the gap must be resolved before the disclosure is finalized, not papered over with an estimate. An incomplete disclosure note is a more serious audit finding than one that identifies a specific limitation with a quantified impact. The entity's obligation is completeness; the auditor's task is to verify it.

How Wag3s fits in

Wag3s Ledger produces per-period holdings, movements, fair-value, and custody data with an audit trail, feeding the crypto disclosure notes under IFRS or US GAAP. The required disclosure package is framework- and materiality-specific and stays auditor-confirmed; Ledger's role is to supply the complete, GL-reconciled source data your auditor verifies before the notes are finalised. See the Ledger product page.

Further reading

• Crypto & IFRS 13 Fair Value Measurement
• FASB ASU 2023-08 Crypto Fair Value
• Crypto CoA: GAAP and IFRS Mapping
• Crypto Asset Account Classification
• Crypto Going Concern & Subsequent Events
• Crypto Audit Readiness

Sources

• FASB — Accounting Standards Update 2023-08, Subtopic 350-60: the specific crypto-asset disclosures added alongside fair value, and the separate balance-sheet presentation reflected in the 2026 FASB taxonomy.
• IFRS — IFRS 13 Fair Value Measurement: the fair-value hierarchy level, valuation technique, and Level 2 and Level 3 input disclosures where crypto is fair-valued.
• IFRS — IAS 38 Intangible Assets and IAS 2 Inventories: the accounting-policy basis (cost or revaluation, or inventory) disclosed for crypto holdings.
• The exact disclosure line items are read from the standards with the auditor rather than from a fixed checklist; the package is framework- and materiality-specific, and a dual-reporting group satisfies both frameworks. This is not accounting advice.