DAC8 Reporting and Crypto Financial Standards: A Guide for Accounting Firms

Crypto financial reporting is no longer a speculative corner of accounting practice. DAC8 reporting obligations, the OECD's Crypto-Asset Reporting Framework, IFRS crypto asset guidance and the recent FASB fair value changes have collectively transformed what accounting firms, CFOs and finance teams are expected to deliver. The rules are now layered: international exchange-of-information regimes sit above national tax rules, which sit above accounting standards, which each jurisdiction then interprets differently. For firms advising clients who hold, trade or issue crypto assets, understanding how these frameworks interact is not optional. This article maps each major standard, explains where they align, and highlights the practical compliance obligations that matter most to professional practice today.

What DAC8 Reporting Requires and Who It Affects

DAC8 is the eighth iteration of the EU's Directive on Administrative Cooperation. It extends automatic exchange of financial information to crypto-asset service providers, bringing them into a reporting regime comparable to that which already governs banks and investment platforms under CRS. From the compliance perspective of an accounting firm, DAC8 reporting creates new client obligations that need to be understood even if your practice is based outside the EU.

Any entity that qualifies as a Reporting Crypto-Asset Service Provider under the DAC8 framework must collect and report user information, transaction volumes and asset types to the relevant EU member state tax authority. That authority then shares the data with other member states automatically. The practical implication is that a Canadian exchange with EU-resident users, or a DeFi platform accessible in the EU, may be caught. Accountants advising such clients need to understand the scope rules before assuming non-applicability.

DAC8 is closely modelled on the OECD's CARF crypto reporting standard, which was designed as the global template. The two frameworks share similar asset definitions, reporting categories and due-diligence procedures. Where they diverge, the EU version typically adds specificity around penalties and the timeline for member state implementation. Firms advising multinational clients must therefore track both instruments, not just one.

Framework	Issuing Body	Primary Scope	Data Exchanged
DAC8	European Union	Crypto-asset service providers with EU nexus	User identity, transaction values, asset categories
CARF	OECD	Reporting crypto-asset service providers globally	User identity, gross proceeds, transfer data
CRS	OECD	Financial institutions holding financial accounts	Account balances, income, proceeds

CARF Crypto Reporting and the Canadian Position

Canada is an OECD member and has signalled its intention to implement the CARF crypto reporting standard domestically. The Canada Revenue Agency has been progressively tightening its crypto disclosure expectations, requiring taxpayers to report gains, losses and income from crypto transactions on their annual returns. CARF will add a further layer: exchanges and brokers operating in Canada will face exchange-of-information obligations that mirror what CRS already demands from banks.

For accounting firms with Canadian clients, this matters in two distinct ways. First, clients who use international platforms may find their transaction data reported to the CRA automatically once CARF is implemented and bilateral exchange agreements are activated. Second, Canadian businesses that operate as crypto-asset service providers will need their own compliance infrastructure to collect, validate and report user data. Firms that already support CRS or FATCA compliance work are well placed to extend that capability into CARF, but the asset-specific definitions require careful review.

The CARF standard covers a broad range of crypto assets: those that can be transferred or traded without going through a traditional financial intermediary. Stablecoins are included. NFTs may be included depending on whether they are fungible in practice. CBDCs issued by central banks are currently excluded from CARF, though that position could evolve. Firms advising clients in the digital asset space need clear asset classification protocols before any reporting obligation is assessed.

IFRS Crypto Assets: The Accounting Treatment Gap

IFRS does not yet have a dedicated standard for crypto assets. The IASB has acknowledged the gap, but in the absence of specific guidance, preparers have historically defaulted to IAS 38 (intangible assets) or, where the asset is held for trading, IAS 2 (inventories). Neither treatment was designed with digital assets in mind, and both produce outcomes that many users of financial statements find unsatisfactory.

Under IAS 38, most crypto assets are carried at cost less any impairment. This means that when the value of a holding rises, the gain is not recognised in the financial statements until the asset is sold. Impairment losses, however, are recognised immediately. The result is an asymmetric presentation that understates assets during bull markets and overstates losses during corrections. For entities holding crypto as part of a treasury strategy, this creates real tension with management reporting.

The IASB's agenda decision confirmed that entities in certain circumstances can apply the fair value model under IAS 2 if they are broker-traders in commodities, but this is a narrow carve-out. For most corporate holders, the intangible asset model remains the default under IFRS crypto accounting. Firms advising IFRS-reporting clients should document the classification rationale clearly and revisit it when holdings change in nature or volume.

Accounting Standard	Framework	Default Crypto Treatment	Fair Value Option Available
IAS 38	IFRS	Cost less impairment (intangible asset)	No (revaluation only if active market exists)
IAS 2	IFRS	Lower of cost or net realisable value	Yes, for broker-traders in commodities
ASC 350-60	US GAAP	Fair value with changes through net income	Mandatory from applicable effective dates

ASC 350-60 Crypto and FASB Fair Value Under US GAAP

The FASB moved decisively on crypto accounting in 2023 with the finalisation of ASU 2023-08, which introduced ASC 350-60 as a dedicated subtopic for certain crypto assets under US GAAP. This is a significant departure from the old approach, under which crypto was treated as an indefinite-lived intangible asset subject to impairment-only measurement.

Under ASC 350-60, entities holding crypto assets that meet the standard's scope criteria must measure them at fair value at each reporting date, with changes recognised in net income. The scope covers fungible assets that are created or reside on a distributed ledger, can be transferred peer-to-peer without an intermediary, and are not issued by the reporting entity or a related party. Wrapped tokens, stablecoins backed by other assets, and most NFTs fall outside the scope.

FASB crypto fair value measurement requires entities to follow the ASC 820 fair value hierarchy. Principal market pricing is used where it exists. For assets traded on multiple exchanges, the entity must identify the principal market, which is generally the exchange with the highest volume for that asset. This is a non-trivial exercise for firms that hold assets across multiple venues. Crypto US GAAP accounting under the new rules also introduces enhanced disclosure requirements, including a rollforward of crypto asset activity and a breakdown of unrealised gains and losses. Firms supporting US-listed clients or SEC registrants should treat this as an active workstream, not a future consideration.

How Canadian Reporting Sits Between IFRS and US GAAP

Canadian public companies listed on domestic exchanges apply IFRS as adopted in Canada. Private enterprises have the option to use Accounting Standards for Private Enterprises, which is a separate framework maintained by the Accounting Standards Board. Not-for-profit organisations have their own set of standards as well. This means that a single Canadian accounting firm may simultaneously be advising clients on three distinct frameworks, and the crypto treatment under each can differ substantially.

Canadian public companies applying IFRS will face the same intangible asset default described above. There is no Canadian-specific override that permits fair value measurement for crypto holdings absent the broker-trader exception. For private companies using ASPE, the guidance is similarly silent on crypto, and practitioners typically apply IAS 38 by analogy.

Where Canadian entities have US operations or US-based investors, the FASB's ASC 350-60 rules may also be relevant for reconciliation or subsidiary reporting purposes. Firms that support cross-border groups need to manage these parallel treatments carefully, particularly when preparing consolidated financial statements where the parent and subsidiary operate under different GAAP frameworks. The gap between IFRS and US GAAP on crypto fair value is real and creates reconciling differences that auditors will scrutinise.

Audit Readiness and What Accounting Firms Should Be Building Now

Audit readiness for crypto holdings is no longer about whether the amounts are material enough to warrant attention. Regulators, auditors and standard-setters have all moved in the direction of requiring more robust evidence. For firms that act as preparers or advisors, the practical question is: what does an audit-ready crypto accounting file look like?

At a minimum, it should include a complete transaction history reconciled to exchange records and wallet addresses, a documented asset classification for each holding, a clear cost-basis methodology applied consistently, fair value evidence as at each reporting date sourced from a principal or most advantageous market, and a record of any impairment assessments performed during the period. For CARF and DAC8 purposes, client due diligence records and reporting submissions should be retained alongside the financial accounting file.

Firms that use crypto compliance reporting infrastructure, rather than manual spreadsheet processes, are substantially better positioned when clients face audit queries or regulatory reviews. Automated reconciliation, timestamped pricing data and standardised disclosure outputs reduce the risk of error and the time cost of responding to information requests. This is where crypto compliance reporting software becomes a genuine practice management tool, not just a filing convenience. For firms looking to build that capability, understanding how the standards interact is the necessary first step before selecting or configuring any technical solution.

Illustrative Scenario

To illustrate how this applies in practice, consider the following scenario:

Priya is a senior manager at a mid-sized Canadian accounting firm in Toronto. Several of her audit clients have started holding Bitcoin and Ether on their balance sheets as part of treasury diversification strategies. Two of those clients are publicly listed and report under IFRS. One is a private company using ASPE. A fourth client is a subsidiary of a US parent that files under US GAAP.

When preparing for the year-end audit cycle, Priya realises she needs four different documentation approaches for four clients holding similar assets. The IFRS clients require impairment testing and disclosure under IAS 38. The ASPE client needs a judgment call documented by analogy. The US subsidiary must comply with ASC 350-60 and produce a fair value rollforward with principal market evidence.

One of the IFRS clients also operates a small platform that may fall within the scope of CARF when Canada implements the standard. Priya flags this for the firm's tax team.

Using CryptaCount, Priya's team pulls complete transaction histories for each client, applies the relevant cost-basis methodology, and generates the fair value evidence trail required for the US GAAP entity. The platform's structured output means the audit file is ready for review without a manual rebuild. The time saving across four clients with different frameworks is significant, and the documentation quality reduces the risk of queries from the external auditors.

Frequently Asked Questions

What is DAC8 reporting and does it apply to non-EU firms?

DAC8 is an EU directive requiring crypto-asset service providers to collect and automatically exchange user and transaction data with EU tax authorities. It applies to any provider that has EU-resident users or a sufficient nexus with the EU, regardless of where the provider is incorporated. A Canadian or US-based exchange serving EU clients may be within scope and should take legal advice on its obligations.

How does CARF crypto reporting differ from DAC8?

CARF is the OECD's global template for crypto reporting, designed to achieve the same outcome as CRS does for bank accounts. DAC8 is the EU's domestic implementation of CARF, adapted for EU law. The two share a similar structure, but DAC8 includes EU-specific penalty and implementation provisions. Firms advising multinational clients need to track both, since CARF implementation timelines vary by country.

What accounting standard applies to crypto assets under IFRS?

There is no dedicated IFRS standard for crypto assets. In most cases, IFRS crypto assets are accounted for under IAS 38 as intangible assets, measured at cost less impairment. A narrow exception allows fair value measurement under IAS 2 for broker-traders in commodities. The IASB has acknowledged the gap but has not yet issued a new standard specifically addressing crypto.

What changed with ASC 350-60 crypto under US GAAP?

ASC 350-60 was introduced by FASB through ASU 2023-08 and requires entities to measure qualifying crypto assets at fair value at each reporting date, with changes recognised in net income. This replaced the old impairment-only model. The standard applies to fungible, transferable crypto assets and excludes wrapped tokens, most stablecoins and NFTs. Enhanced disclosures, including a rollforward of activity and unrealised gains and losses, are also required.

How does FASB crypto fair value measurement work in practice?

FASB crypto fair value measurement follows the ASC 820 hierarchy. Entities must identify the principal market for each asset, typically the exchange with the highest volume, and use pricing from that market at the measurement date. For entities holding assets across multiple exchanges, this requires a documented market identification process. The evidence trail supporting fair value conclusions should be retained for audit purposes.

What crypto accounting standard applies to Canadian private companies?

Canadian private enterprises that use Accounting Standards for Private Enterprises do not have specific crypto guidance in ASPE. In practice, practitioners typically apply IAS 38 by analogy, treating crypto as an intangible asset measured at cost less impairment. The choice of methodology should be documented and applied consistently. If the private company has US operations or investors, US GAAP requirements may also be relevant for subsidiary or reconciliation purposes.

Is crypto IFRS accounting expected to change in the near future?

The IASB has had crypto assets on its agenda and has issued agenda decisions acknowledging the deficiencies in current guidance, but a dedicated standard has not been issued as of the time of writing. The contrast with the FASB's decisive action on ASC 350-60 is notable. Preparers and auditors applying IFRS should monitor IASB publications and be prepared to update their accounting policies if new guidance is finalised.

How should accounting firms prepare clients for CARF and DAC8 obligations?

Firms should start by assessing whether any client qualifies as a reporting crypto-asset service provider under either framework. For clients that do, the priorities are: establishing user due diligence procedures, building transaction data collection systems, and understanding the reporting submission format required by the relevant authority. Firms that already support CRS compliance have a useful starting point, but crypto-specific asset definitions and scope rules require separate analysis. Investing in crypto compliance reporting tools now reduces the risk of a rushed implementation when domestic deadlines are confirmed.

Source: CryptaCount