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

A group that reports under both US GAAP and IFRS cannot run two disconnected crypto charts of accounts; it needs one, structured so the same underlying data maps to both. The friction is real, because the two frameworks genuinely diverge: ASU 2023-08 puts fair-value changes through net income, while IAS 38 offers a cost or revaluation model that can send the same movement to OCI or recognise nothing upward. This spoke takes the dual-reporting case specifically — the mapping points, the data the ledger has to capture to bridge both, and why the mapping is a presentation bridge rather than a reclassification. The determination under each framework is an auditor judgement.

The mapping in brief

• A dual-reporting group needs one chart of accounts capturing cost, fair value, realized, and unrealized as distinct data, then mapped per framework.
• Under US GAAP (FASB ASU 2023-08), in-scope crypto is held at fair value with changes in net income.
• Under IFRS (IAS 38), the cost model (cost less impairment) or the revaluation model (increase to OCI, decrease below cost to P&L) applies; IAS 2 inventory applies for broker-traders.
• The same price move can hit net income under GAAP but OCI, or nothing upward, under IFRS — the mapping has to handle that.
• The 2026 FASB XBRL taxonomy presents crypto fair value on a separate balance-sheet line (below intangibles, above right-of-use assets).
• The mapping is a presentation and measurement bridge, not a reclassification; genuine divergence is disclosed. It is auditor-confirmed, and this is not accounting advice.

One CoA, two frameworks

For a group reporting under both, the chart of accounts has to let the same underlying data be presented under each framework's rules, rather than forcing one framework's treatment onto the other. Capture cost, fair value, realized results, and unrealized changes as separate data points, then map them 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 has to handle it, and the determination is an auditor judgement.

Presentation differs too

The 2026 FASB XBRL taxonomy places crypto fair value on 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 or IAS 2 classification. The chart of accounts should carry crypto so a separate, clearly identifiable presentation is possible under each framework, rather than burying it in a generic intangibles line.

The data the chart of accounts must capture

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

Mapping is not reclassification

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

Practical guidance

1. Run one chart of accounts, not two — capture cost, fair value, realized, and unrealized as distinct data.
2. Map the unrealized change 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 and model attributes for the mapping.
5. Disclose genuine divergence rather than papering over it with the mapping.
6. Confirm the dual mapping with your auditor. It is fact-specific, and not accounting advice.

Configuring a tool for dual mapping

Cryptio, Bitwave and similar sub-ledgers can hold cost and fair value and route results per framework. The capability that matters when choosing one for a dual-reporting group is whether it captures cost, fair value, realized, and unrealized as distinct data and can map the unrealized change to net income or OCI depending on the framework, rather than committing to one framework's treatment in the data itself. The tool applies the mapping; the framework determinations are an auditor judgement.

Where Wag3s fits

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. The framework determinations stay with the entity's auditor; Ledger is built to give the group's accountant and auditor one reconcilable data set that both reports can be drawn from, not to make the calls for them. 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

• US GAAP — FASB ASU 2023-08: in-scope crypto at fair value with changes through net income, and the 2026 FASB XBRL taxonomy presenting crypto fair value on a separate balance-sheet line (below intangibles, above right-of-use assets).
• IFRS — IAS 38 Intangible Assets: the cost model (cost less impairment) or revaluation model (increase to OCI, decrease below cost to P&L), with IAS 2 Inventories for broker-traders; IFRS presentation follows IAS 1 and the chosen IAS 38 or IAS 2 classification.
• The single-chart-of-accounts approach (capturing cost, fair value, realized, and unrealized as distinct data mapped to net income or OCI per framework) is a design convention; the mapping is a presentation and measurement bridge, not a reclassification — the classification stays an auditor judgement per framework and genuine divergence is disclosed. This is not accounting advice.