DAC8 Reporting and Global Crypto Accounting Standards: A Guide for Accounting Firms
Crypto financial reporting has moved from a niche concern to a boardroom priority. DAC8 reporting obligations in the EU, the FASB's revised fair value model in the United States, evolving IFRS guidance on crypto assets, and the OECD's CARF crypto reporting framework are all live or approaching live status simultaneously. For accounting firms, auditors, and CFOs managing clients with digital asset exposure, the challenge is no longer whether to address crypto, it is which framework applies, when, and how the requirements interact. Getting that wrong carries real consequences: misclassified assets, misstated financial statements, and regulatory penalties that are increasingly difficult to negotiate away.
Why Multiple Frameworks Exist and How They Relate
The absence of a single global crypto accounting standard is deliberate, at least historically. Standard-setters in different jurisdictions have moved at different speeds, responding to their own regulatory cultures and the specific concerns of domestic markets. The result is a patchwork that firms with cross-border client portfolios must navigate carefully.
At the accounting standards level, the two dominant frameworks are US GAAP, now updated through the FASB's ASC 350-60 guidance, and IFRS, which handles crypto assets primarily through IAS 38 and, in some cases, IAS 2. At the tax and regulatory reporting level, DAC8 reporting covers EU-based crypto-asset service providers and certain users, while CARF crypto reporting represents the OECD's attempt to create a globally consistent automatic exchange of information regime for crypto. These are not competing frameworks. They operate at different layers: accounting standards govern how an asset appears on a balance sheet, while reporting regimes govern what information gets shared with tax authorities. A firm needs to comply with both layers, and the data requirements overlap significantly.
For firms advising Singapore-based entities or clients with Singapore operations, there is an additional layer. Singapore follows financial reporting standards that converge with IFRS, and the Monetary Authority of Singapore has developed its own regulatory perimeter for digital assets. Understanding how global standards map onto local requirements is a practical necessity, not a theoretical exercise.
DAC8 Reporting: What Firms Must Understand Now
DAC8 is the eighth iteration of the EU's Directive on Administrative Cooperation. It extends the automatic exchange of tax-relevant information to cover crypto-asset transactions, bringing crypto broadly in line with the information-sharing obligations that already apply to traditional financial products under DAC2.
The directive requires crypto-asset service providers, or CASPs, that are registered or operationally based within the EU to collect and report user transaction data to the relevant national tax authority. That authority then shares the information with other EU member states where the user is tax-resident. The scope is broad: it covers exchanges between crypto assets and fiat currencies, exchanges between different crypto assets, and transfers to or from external wallets above certain thresholds.
For accounting firms, DAC8 reporting creates two distinct workstreams. First, if any client is a CASP, they need a compliance programme that captures the right data at transaction level and routes it correctly through the reporting chain. Second, if a client is a high-volume individual or corporate trader using EU-registered platforms, their transaction data may already be flowing to tax authorities in ways that must be reconciled against filed returns. The table below summarises the core reporting obligations under DAC8.
| Obligation | Who it applies to | What must be reported | Direction of reporting |
|---|---|---|---|
| CASP transaction reporting | EU-registered crypto-asset service providers | User identity, transaction type, asset type, fiat value, wallet addresses | CASP to national tax authority |
| Automatic exchange | EU member state tax authorities | Aggregated user transaction data received from CASPs | Between EU member states |
| Non-EU CASP obligations | CASPs serving EU-resident users but registered outside the EU | Same data set as EU CASPs for EU-resident users | CASP to designated EU member state authority |
FASB ASC 350-60 and Crypto US GAAP Accounting
The FASB's update to ASC 350-60 represents a significant shift in how crypto assets are treated under US GAAP. Before the update, most crypto holdings were classified as indefinite-lived intangible assets and measured at historical cost, subject to impairment testing but never written up. That treatment created obvious distortions: a company holding bitcoin that had risen substantially in value could not reflect that gain until a disposal event.
The revised ASC 350-60 requires entities to measure qualifying crypto assets at fair value at each reporting date, with changes recognised in net income. This brings crypto US GAAP accounting closer to the treatment of certain financial instruments, though the FASB was careful to scope the guidance narrowly. It applies to assets that meet specific criteria: they must be fungible, secured through cryptographic means, operate on a distributed ledger, and not represent a financial interest in another entity. Assets that fall outside these criteria, including most NFTs and certain wrapped tokens, are not covered by ASC 350-60 and require separate analysis.
For accounting firms and CFOs, the practical implications are significant. Fair value measurement requires a defensible pricing source, which is straightforward for assets trading on major exchanges but considerably more complex for thinly traded tokens. Disclosures have also expanded: entities must now provide information about the nature and risks of their crypto holdings, the reconciliation of opening and closing balances, and the method used to determine fair value. The table below compares the old and new treatment.
| Aspect | Previous US GAAP treatment | ASC 350-60 treatment |
|---|---|---|
| Measurement basis | Historical cost less impairment | Fair value at each reporting date |
| Gains recognition | Only on disposal | Recognised in net income each period |
| Impairment testing | Required at least annually | Not applicable under fair value model |
| Disclosure requirements | Limited | Expanded: nature, risks, pricing methodology, balance reconciliation |
IFRS Crypto Assets: The Current Framework and Its Limits
IFRS does not yet have a dedicated standard for crypto assets, which is one of the most significant gaps in global financial reporting. The IASB has acknowledged this and has work in progress, but for now preparers must apply existing standards by analogy, guided by the IFRS Interpretations Committee's agenda decision from 2019.
Under that guidance, crypto assets are generally classified as intangible assets under IAS 38, unless they are held for sale in the ordinary course of business, in which case IAS 2 inventory treatment may apply. The IAS 38 route permits either the cost model or the revaluation model. The revaluation model can produce fair value measurement, but only when an active market exists for the asset, a condition that is met for major assets but uncertain for smaller tokens. Unlike FASB ASC 350-60, IFRS does not mandate fair value: it permits it under specific conditions.
This divergence between IFRS crypto assets treatment and crypto US GAAP accounting creates a real challenge for firms with clients reporting under both frameworks, or for multinational groups that must consolidate entities using different standards. Reconciliation tables become essential, and auditors need documented rationale for classification decisions at each reporting date. The IASB's ongoing work may eventually produce a dedicated standard, but firms cannot wait for that. They need defensible positions now.
CARF Crypto Reporting and the Global Exchange Regime
The OECD's Crypto-Asset Reporting Framework, known as CARF, is designed to close the information gap that existed because crypto transactions fell outside the Common Reporting Standard. CARF requires reporting crypto-asset service providers to collect and report user information to their domestic tax authority, which then exchanges that information automatically with the user's country of tax residence.
CARF crypto reporting covers a wide range of transaction types: exchanges between crypto and fiat, exchanges between crypto assets, and certain transfers. It is built on a definition of reportable crypto assets that deliberately excludes assets already covered by existing financial account reporting regimes, avoiding duplication with CRS where overlap exists.
The relationship between CARF and DAC8 is important to understand. DAC8 is the EU's domestic implementation of CARF principles, adapted to EU legal architecture and applied through the directive mechanism. Jurisdictions outside the EU that adopt CARF will have their own domestic implementing legislation. The result is an emerging global web of automatic information exchange that mirrors what already exists for bank accounts, extended to cover crypto. Firms advising clients with presence in multiple jurisdictions need to map which CARF-implementing regimes are in force and which are still being transposed. You can find a detailed breakdown of these obligations through our crypto compliance reporting for accounting firms resource.
Singapore's Position Within the Global Framework
Singapore occupies an interesting position in the global crypto reporting landscape. The country has a mature regulatory framework for digital assets, centred on the Payment Services Act administered by the Monetary Authority of Singapore. Entities licensed under that act face AML and KYC obligations that already require significant transaction data capture, creating a foundation that overlaps with CARF-style reporting requirements.
On the accounting side, Singapore's financial reporting standards, known as SFRS(I), are converged with IFRS. This means that Singapore-incorporated entities applying SFRS(I) follow the same IAS 38 and IAS 2 logic described above when accounting for crypto assets. There is no locally developed Singapore-specific crypto accounting standard. For groups with a Singapore parent or subsidiary, the practical work is ensuring that the group's crypto accounting policy is consistently applied and documented, and that local regulatory reporting obligations under the Payment Services Act are mapped alongside group financial reporting requirements.
Singapore has also signalled engagement with the CARF framework, reflecting its broader commitment to international tax transparency. Firms with Singapore-based clients should monitor the MAS and IRAS positions as CARF transposition progresses, since the timeline and scope of domestic implementing rules will directly affect data collection and reporting obligations for both CASPs and their users.
Illustrative Scenario
To illustrate how this applies in practice, consider the following scenario: Priya is the CFO of a mid-sized Singapore-incorporated fintech group that operates a crypto exchange business within the EU through a licensed subsidiary in Germany. The group prepares consolidated financial statements under SFRS(I), converged with IFRS, while the German subsidiary also files local statutory accounts under German GAAP adapted to EU requirements.
At the group level, Priya's team must classify the crypto assets held on the exchange's proprietary book under IAS 38, deciding whether the revaluation model is appropriate given that the assets trade on active markets. At the subsidiary level, the German entity is a CASP subject to DAC8 reporting, which means it must collect and submit detailed user transaction data to the German tax authority each year. CARF crypto reporting obligations are also on the horizon as Singapore implements the OECD framework.
Without a centralised sub-ledger that captures transaction data at the right level of granularity, Priya's team faces the prospect of manually reconciling exchange data for both the fair value disclosure and the DAC8 submission. Using CryptaCount, the group maps exchange API data directly into the accounting engine, generating the fair value movements needed for SFRS(I) disclosures and the transaction-level data needed for DAC8 simultaneously, from a single source of truth.
Frequently Asked Questions
What is DAC8 reporting and who does it apply to?
DAC8 is an EU directive that requires crypto-asset service providers registered or operating in the EU to collect and report user transaction data to national tax authorities. Those authorities then share the data automatically with other EU member states where users are tax-resident. Non-EU CASPs serving EU users also fall within scope for those users' transactions.
How does FASB ASC 350-60 change crypto US GAAP accounting?
Before the FASB updated ASC 350-60, qualifying crypto assets were treated as indefinite-lived intangibles measured at cost less impairment, meaning unrealised gains were never recognised. The revised standard requires fair value measurement at each reporting date, with changes flowing through net income. It applies to fungible, cryptographically secured assets on distributed ledgers that do not represent a financial interest in another entity.
What is FASB crypto fair value measurement in practice?
FASB crypto fair value measurement requires an entity to determine the fair value of its qualifying crypto holdings at each balance sheet date using a defensible pricing source, typically a principal market price from a major exchange. The resulting gains or losses are recognised in net income for the period. Assets that lack active market pricing require a more judgement-intensive valuation approach and additional disclosure.
How are crypto assets treated under IFRS?
Under current IFRS guidance, crypto assets are generally accounted for as intangible assets under IAS 38, or as inventory under IAS 2 when held for sale in the ordinary course of business. The IFRS Interpretations Committee clarified this in 2019. Unlike ASC 350-60, IFRS does not mandate fair value: the revaluation model under IAS 38 permits it when an active market exists, but is not required. The IASB has ongoing work towards a dedicated crypto standard.
What is CARF crypto reporting and how does it differ from DAC8?
CARF is the OECD's Crypto-Asset Reporting Framework, designed to extend automatic exchange of financial information to crypto transactions globally. DAC8 is the EU's domestic implementation of CARF principles within its directive architecture. Other jurisdictions that adopt CARF will implement it through their own national legislation. The data collected and exchanged is broadly similar, but the legal mechanism and timeline vary by country.
Does IFRS crypto accounting apply to Singapore entities?
Singapore applies SFRS(I), which converges with IFRS. Singapore-incorporated entities using SFRS(I) therefore follow the same logic as IFRS preparers: IAS 38 for crypto held as intangible assets or IAS 2 where inventory treatment is appropriate. There is no Singapore-specific crypto accounting standard that departs from the IFRS-converged position.
What data do accounting firms need to capture for DAC8 compliance?
For a CASP client subject to DAC8 reporting, firms need transaction-level data covering user identity details, the type of transaction, the crypto asset involved, the fiat equivalent value at the time of the transaction, and in some cases wallet addresses. This data must be captured at source and held in a format that allows annual submission to the relevant tax authority.
Can the same data set serve both financial reporting and regulatory reporting purposes?
Yes, with the right infrastructure. The transaction-level data required for DAC8 reporting and CARF crypto reporting overlaps substantially with the data needed to produce fair value disclosures under ASC 350-60 or IFRS crypto assets accounting. A centralised sub-ledger that ingests exchange and wallet data at transaction level can serve both the accounting engine and the regulatory reporting workflow, reducing manual reconciliation and the risk of inconsistency between filed returns and audited accounts.
Source: CryptaCount
FAQ
DAC8 is an EU directive that requires crypto-asset service providers registered or operating in the EU to collect and report user transaction data to national tax authorities. Those authorities then share the data automatically with other EU member states where users are tax-resident. Non-EU CASPs serving EU users also fall within scope for those users' transactions.
Before the FASB updated ASC 350-60, qualifying crypto assets were treated as indefinite-lived intangibles measured at cost less impairment, meaning unrealised gains were never recognised. The revised standard requires fair value measurement at each reporting date, with changes flowing through net income. It applies to fungible, cryptographically secured assets on distributed ledgers that do not represent a financial interest in another entity.
FASB crypto fair value measurement requires an entity to determine the fair value of its qualifying crypto holdings at each balance sheet date using a defensible pricing source, typically a principal market price from a major exchange. The resulting gains or losses are recognised in net income for the period. Assets that lack active market pricing require a more judgement-intensive valuation approach and additional disclosure.
Under current IFRS guidance, crypto assets are generally accounted for as intangible assets under IAS 38, or as inventory under IAS 2 when held for sale in the ordinary course of business. The IFRS Interpretations Committee clarified this in 2019. Unlike ASC 350-60, IFRS does not mandate fair value: the revaluation model under IAS 38 permits it when an active market exists, but is not required. The IASB has ongoing work towards a dedicated crypto standard.
CARF is the OECD's Crypto-Asset Reporting Framework, designed to extend automatic exchange of financial information to crypto transactions globally. DAC8 is the EU's domestic implementation of CARF principles within its directive architecture. Other jurisdictions that adopt CARF will implement it through their own national legislation. The data collected and exchanged is broadly similar, but the legal mechanism and timeline vary by country.
Singapore applies SFRS(I), which converges with IFRS. Singapore-incorporated entities using SFRS(I) therefore follow the same logic as IFRS preparers: IAS 38 for crypto held as intangible assets or IAS 2 where inventory treatment is appropriate. There is no Singapore-specific crypto accounting standard that departs from the IFRS-converged position.
For a CASP client subject to DAC8 reporting, firms need transaction-level data covering user identity details, the type of transaction, the crypto asset involved, the fiat equivalent value at the time of the transaction, and in some cases wallet addresses. This data must be captured at source and held in a format that allows annual submission to the relevant tax authority.
Yes, with the right infrastructure. The transaction-level data required for DAC8 reporting and CARF crypto reporting overlaps substantially with the data needed to produce fair value disclosures under ASC 350-60 or IFRS crypto assets accounting. A centralised sub-ledger that ingests exchange and wallet data at transaction level can serve both the accounting engine and the regulatory reporting workflow, reducing manual reconciliation and the risk of inconsistency between filed returns and audited accounts.