Crypto CoA: Mapping One Chart of Accounts to GAAP and IFRS

A group that reports under US GAAP and IFRS cannot maintain two disconnected crypto charts of accounts — it needs one, structured so the same data maps to both. The friction is real: ASU 2023-08 fair-value-through-net-income vs IAS 38 cost/revaluation. This guide is the mapping points, hedged, because the determination under each framework is an auditor judgement.

TL;DR

• A dual-reporting group needs one CoA capturing cost, fair value, realized, unrealized as distinct data, then mapped per framework.
• US GAAP (FASB ASU 2023-08): in-scope crypto at fair value, changes in net income.
• IFRS (IAS 38): cost (cost less impairment) or revaluation (increase → OCI, decrease below cost → P&L); IAS 2 inventory for broker-traders.
• Same price move can hit net income (GAAP) vs OCI / not-recognized-upward (IFRS) — the mapping must handle it.
• 2026 FASB XBRL: crypto fair value as a separate balance-sheet line (below intangibles, above ROU).
• Mapping is a presentation/measurement bridge, not a reclassification — divergence is disclosed. Auditor-confirmed; not accounting advice.

One CoA, two frameworks

For a group reporting under both, the CoA must let the same underlying data be presented under each framework's rules — not force one framework's treatment onto the other. Capture cost, fair value, realized results, unrealized changes as separate data points, then map to net income or OCI per framework. Two disconnected charts of accounts invite reconciliation failure; the dual mapping is an auditor-confirmed design (built on chart of accounts design).

The core divergence

The same price movement can hit net income under US GAAP and OCI (or nothing upward) under IFRS — see FASB ASU 2023-08 and crypto asset account classification. The mapping must handle it; the determination is an auditor judgement.

Presentation differs too

The 2026 FASB XBRL taxonomy places crypto fair value as a separate balance-sheet line (below intangibles, above right-of-use assets) for US GAAP; IFRS presentation follows IAS 1 and the chosen IAS 38/IAS 2 classification. The CoA should carry crypto so a separate, clearly identifiable presentation is possible under each framework — not buried in a generic intangibles line.

The data the CoA must capture

At minimum, as distinct, queryable data: acquisition cost and date (cost-basis layers), period-end fair value, realized results on disposal, unrealized remeasurement — plus classification and model attributes per entity. With those clean, the same data maps to ASU 2023-08 net income or to IAS 38 cost/revaluation. Missing any forces manual rework each period — an auditor-confirmed design input.

Mapping is not reclassification

Mapping presents the same classified asset under two frameworks' measurement/presentation rules — it does not make the asset two different things. Classification stays an auditor judgement per framework, and genuine divergence is disclosed, not hidden by the mapping. A bridge, not a reclassification.

Practical guidance

1. Run one CoA, not two — capture cost/fair value/realized/unrealized as distinct data.
2. Map unrealized to net income (GAAP) or OCI/cost (IFRS) per framework.
3. Support a separate crypto presentation line under each framework.
4. Carry per-entity classification/model attributes for the mapping.
5. Disclose genuine divergence — don't paper over it with the mapping.
6. Confirm the dual mapping with your auditor — fact-specific; not accounting advice.

How vendor tools handle dual mapping

Cryptio and Bitwave can hold cost and fair value and route results per framework. Confirm the tool captures cost, fair value, realized, unrealized as distinct data and maps net income vs OCI per framework — the tool applies the mapping; the framework determinations are an auditor judgement.

How Wag3s helps

Wag3s Ledger captures cost, fair value, realized results, and unrealized remeasurement as distinct data with per-entity classification attributes, so one data set maps to both US GAAP (ASU 2023-08) and IFRS (IAS 38) presentation with an audit trail and ERP export — while the framework determinations stay auditor-confirmed. See the Ledger product page.

Further reading

• Crypto Chart of Accounts Design
• FASB ASU 2023-08 Crypto Fair Value
• Crypto Asset Account Classification
• IFRS vs GAAP for Crypto
• Crypto Realized vs Unrealized Gain Accounts
• Multi-Entity Crypto Chart of Accounts

Sources

• Dual-reporting groups need one CoA capturing cost, fair value, realized, and unrealized as distinct data, mapped to net income or OCI per framework (running two disconnected CoAs invites reconciliation failure)
• Core divergence — US GAAP FASB ASU 2023-08 fair value through net income vs IFRS IAS 38 cost (cost less impairment) or revaluation (increase → OCI, decrease below cost → P&L); IAS 2 inventory for broker-traders
• Presentation — 2026 FASB XBRL taxonomy places crypto fair value as a separate balance-sheet line (below intangibles, above ROU); IFRS follows IAS 1 and the IAS 38/IAS 2 classification
• Mapping is a presentation/measurement bridge, not a reclassification — classification stays an auditor judgement per framework, genuine divergence disclosed not hidden — not accounting advice