DAC8 Reporting and Crypto Accounting Standards: A Global Framework for Finance Teams
Crypto financial reporting has moved well beyond a niche concern. Accounting firms, CFOs, and finance teams across Spain and the wider EU now face overlapping obligations: DAC8 reporting requirements coming into effect at the EU level, the OECD's CARF crypto reporting framework being adopted by an expanding list of jurisdictions, and fundamental shifts in how crypto assets are classified under both IFRS and US GAAP. Getting these frameworks wrong is not a minor inconvenience. It can expose firms to regulatory penalties, audit failures, and reputational damage with institutional clients. This article sets out each framework clearly, explains how they interact, and gives finance professionals a practical basis for building or reviewing their crypto compliance infrastructure.
What DAC8 Reporting Requires and Why It Matters Now
DAC8 is the eighth amendment to the EU's Directive on Administrative Cooperation. It specifically extends automatic exchange of information to cover crypto assets, obliging crypto asset service providers operating within the EU to collect and report user transaction data to their national tax authorities. Those authorities then share that data across the EU network. The directive is transposed into national law across member states, including Spain, meaning Spanish-resident taxpayers holding or trading crypto assets through EU-registered platforms will have their activity reported automatically to the Agencia Tributaria.
For accounting firms advising Spanish clients, this changes the advisory landscape significantly. Clients who previously took a casual approach to declaring crypto gains now face systematic cross-border data sharing. Firms need to ensure client records are reconciled and complete before the first reporting cycles produce data that tax authorities can match against filed returns. The compliance window is narrowing, and proactive advisory is far more valuable than reactive damage control.
The table below summarises the core reporting obligations DAC8 places on crypto asset service providers operating within the EU:
| Obligation | Detail |
|---|---|
| Entities in scope | Crypto asset service providers operating under MiCA or providing services to EU-resident users |
| Data collected | User identity, jurisdiction of residence, transaction volumes, and proceeds from crypto disposals |
| Reporting destination | National competent authority of the member state in which the CASP is registered |
| Information exchange | Automatic exchange between EU member state tax authorities |
| Coverage | All crypto assets as defined under MiCA, including exchange tokens and certain stablecoins |
CARF Crypto Reporting: The OECD's Global Layer
The OECD's Crypto Asset Reporting Framework, known as CARF, operates in parallel with DAC8 and is designed to bring non-EU jurisdictions into a coordinated global reporting network. CARF follows the architecture of the Common Reporting Standard and requires reporting entities to collect and transmit information on crypto asset transactions carried out by their users, including exchanges between crypto and fiat currencies, transfers of crypto assets, and certain retail payment transactions.
Where DAC8 applies to EU member states, CARF creates obligations for the broader group of jurisdictions that adopt it, including many in the Asia-Pacific region, the Middle East, and the Americas. For Spanish and EU-based accounting firms with multinational clients, this matters because clients with accounts on platforms in non-EU jurisdictions will not necessarily fall under DAC8 alone. CARF will capture that activity in the platform's home jurisdiction and, through bilateral competent authority agreements, share it with Spanish authorities.
Practically, the distinction between DAC8 and CARF is one of geographic scope rather than substantive difference. Both frameworks aim to eliminate information asymmetry between taxpayers and revenue authorities by making crypto transaction data flow automatically rather than relying on voluntary self-reporting. Finance teams advising clients with exposure to non-EU platforms should map those platforms against the CARF adoption schedule to understand when reporting obligations will activate.
IFRS Crypto Assets: How Classification Drives Reporting
Under IFRS, crypto assets do not have a dedicated standard. Instead, preparers must apply judgement to determine which existing standard applies to each asset type. For most cryptocurrencies held as investments, the default treatment under IAS 38 classifies them as intangible assets with an indefinite useful life. This means they are carried at cost less any impairment, with no ability to revalue upward through profit or loss unless the entity elects to use the revaluation model, and even then, only if an active market exists.
Entities that hold crypto assets as inventory, such as commodity traders or brokers, may instead apply IAS 2, which permits measurement at net realisable value with changes recognised in profit or loss. This is a meaningfully different treatment that produces more current fair value information in the financial statements. The IASB has acknowledged the limitations of forcing crypto assets into frameworks built for other asset types and has been developing targeted guidance, though a full dedicated standard has not yet been adopted.
For crypto ifrs accounting in Spain and across the EU, the lack of a uniform standard creates comparability problems between entities and increases audit complexity. Accounting firms need a documented, defensible policy for each client that explains which standard has been applied, why, and how the measurement basis was determined. The table below maps common crypto asset types to their most likely IFRS treatment:
| Crypto Asset Type | Most Common IFRS Treatment | Standard Applied |
|---|---|---|
| Exchange tokens held as investment | Intangible asset at cost less impairment | IAS 38 |
| Crypto held for sale in ordinary course | Inventory at lower of cost or NRV | IAS 2 |
| Stablecoins with contractual redemption rights | Financial asset at amortised cost or FVTPL | IFRS 9 |
| Tokenised securities | Financial instrument treatment | IFRS 9 |
| NFTs held as digital art or collectibles | Intangible asset or inventory depending on business model | IAS 38 or IAS 2 |
ASC 350-60 and Crypto US GAAP Accounting
For firms serving clients that report under US GAAP, either because they are US-headquartered or because they are listed on US exchanges, the FASB's ASC 350-60 standard represents a significant departure from the old indefinite-lived intangible asset model. Under ASC 350-60, entities are required to measure certain crypto assets at fair value at each reporting period, with changes in fair value recognised directly in net income. The standard applies to crypto assets that meet specific criteria, primarily that they are fungible, do not give the holder a claim on underlying goods or services, and are created or traded on a distributed ledger.
The FASB crypto fair value approach resolves one of the most criticised aspects of the previous treatment, where entities had to recognise impairment losses on price declines but could not recognise gains until disposal. Under ASC 350-60, the income statement reflects current market movements in both directions. This produces more decision-useful information for investors but also creates income volatility that finance teams need to plan for in earnings guidance and covenant compliance calculations.
For accounting firms in Spain working with subsidiaries of US groups or with clients preparing dual-framework reports, understanding the differences between IFRS crypto assets treatment and crypto us gaap accounting under ASC 350-60 is essential. Reconciling the two can produce material differences in reported assets and net income, particularly for entities holding significant crypto balances. Documenting the reconciliation clearly and consistently reduces audit friction and supports management commentary disclosures.
How DAC8, CARF, IFRS, and FASB Interact in Practice
These frameworks do not operate in isolation. A Spanish subsidiary of a US group holding crypto assets on its balance sheet may simultaneously need to apply ASC 350-60 for group consolidation purposes, apply IAS 38 or IFRS 9 for local statutory accounts, comply with DAC8 reporting obligations if it operates a crypto service, and respond to CARF data shared by non-EU platforms with the Agencia Tributaria. Each layer creates data requirements and documentation obligations that compound on one another.
The common thread across all of these frameworks is transaction-level data quality. DAC8 reporting depends on accurate records of what was sold, when, and for how much. FASB crypto fair value measurement requires verifiable market prices at each reporting date. IFRS impairment testing under IAS 38 requires evidence of active market prices. CARF crypto reporting requires full counterparty and transaction detail. Firms that invest in robust data infrastructure, including integrations between exchange accounts, wallets, and their accounting systems, gain a compounding advantage: the same clean data serves all frameworks simultaneously.
For accounting firms, this is also an advisory opportunity. Clients who understand that their crypto activity will now be visible to tax authorities through automatic exchange are receptive to structured compliance reviews. Positioning crypto compliance as a recurring engagement, rather than a once-a-year tax return exercise, increases the depth of the client relationship and the value of the advisory mandate. Firms that use purpose-built tools for crypto compliance reporting can deliver this work efficiently and scalably across their client base.
Spain-Specific Considerations Under DAC8 and CARF
Spain has been one of the more proactive EU member states in crypto tax enforcement. The Agencia Tributaria introduced mandatory informative declarations through forms 172, 173, and 721 ahead of many peer jurisdictions, requiring Spanish residents to report crypto holdings and transactions with detail that goes beyond what most other EU countries required at the time. DAC8 builds on this foundation by automating the inbound data flow from service providers, creating a cross-reference capability that makes underreporting significantly riskier.
For accounting firms with Spanish clients, the combination of domestic declarations and DAC8 automatic exchange means the Agencia Tributaria will soon hold transaction-level data from platforms alongside client-submitted declarations. Any discrepancy between the two becomes an audit trigger. The practical implication is that firm-level crypto reconciliation processes need to produce records that are not just accurate but also formatted and documented in a way that can withstand a tax inspection inquiry. This is not a theoretical risk. Spanish authorities have already issued information requests to individuals identified through early crypto data-matching exercises.
Illustrative Scenario
To illustrate how this applies in practice, consider the following scenario:
Carlos is a senior manager at a mid-sized audit and advisory firm in Madrid. Several of his firm's corporate clients have started holding Bitcoin and Ether on their balance sheets as treasury assets, and one client operates a small crypto exchange for retail users under a MiCA notification. Carlos needs to address three problems at once: ensuring the treasury-holding clients apply a defensible and consistent accounting policy under IFRS, preparing the exchange operator client for its DAC8 reporting obligations, and reconciling historical transaction records that have been maintained only in spreadsheets.
Carlos begins by implementing CryptaCount across the affected client portfolios. The platform pulls transaction data from exchange APIs and wallet addresses, applies IFRS-aligned classification rules, and generates fair value schedules at each reporting date. For the exchange operator, it maps transaction data to the fields required under DAC8 reporting and flags any gaps in user identification records that need to be remediated before the first submission cycle. Within two months, Carlos has converted a reactive, spreadsheet-based process into a structured compliance workflow. His firm now offers crypto accounting and DAC8 readiness as a named service line, with a recurring fee structure that reflects the ongoing nature of the obligation.
Frequently Asked Questions
What is DAC8 reporting and who does it apply to?
DAC8 is an EU directive that requires crypto asset service providers operating within the EU to report user transaction data to national tax authorities, which then share it automatically across the EU. It applies to any entity providing crypto asset services to EU-resident users, including exchanges, brokers, and certain wallet providers registered under MiCA.
How does CARF crypto reporting differ from DAC8?
DAC8 applies specifically within the EU and uses the EU's administrative cooperation infrastructure. CARF is an OECD framework designed to achieve similar automatic exchange between a broader group of participating jurisdictions globally. Both frameworks target the same goal of eliminating information gaps between crypto users and tax authorities, but they operate through different legal mechanisms and have different geographic scope.
How should crypto assets be classified under IFRS?
IFRS does not have a dedicated crypto standard, so classification depends on the nature and purpose of the holding. Most cryptocurrencies held as investments are treated as intangible assets under IAS 38. Assets held for sale in the ordinary course of business may qualify as inventory under IAS 2. Stablecoins with contractual redemption rights may be financial instruments under IFRS 9. Each classification produces different measurement and disclosure requirements.
What does ASC 350-60 require for US GAAP reporters?
ASC 350-60 requires entities to measure qualifying crypto assets at fair value at each reporting period, with changes in fair value recognised in net income. This replaces the previous indefinite-lived intangible asset model, which only allowed downward impairment. The standard applies to fungible crypto assets that do not give the holder a claim on underlying goods or services.
What is FASB crypto fair value and why does it create income volatility?
Under the FASB crypto fair value approach required by ASC 350-60, entities must mark their qualifying crypto holdings to market at every reporting date and run gains and losses through the income statement. Because crypto asset prices can fluctuate significantly between periods, this creates reported earnings movements that are unrelated to the entity's operating performance, which finance teams need to explain clearly in management commentary.
Are Spanish companies subject to both IFRS crypto accounting rules and DAC8?
Yes, but the obligations apply to different aspects of a company's relationship with crypto. IFRS crypto assets rules govern how crypto holdings appear in the financial statements. DAC8 reporting obligations apply to entities that provide crypto asset services to third parties, not to companies that simply hold crypto on their own balance sheet. A Spanish company that only holds Bitcoin as a treasury asset is subject to IFRS classification rules but would not itself have DAC8 reporting duties.
What records do accounting firms need to support DAC8 and CARF compliance?
Firms need complete transaction-level records including dates, asset types, quantities, counterparty identifiers, and proceeds in fiat currency for each disposal or transfer. For DAC8 specifically, user identity and residence information collected under KYC procedures must be linked to transaction records. The data must be held in a format that can be mapped to the reporting schema required by the relevant national competent authority.
How do IFRS and US GAAP treatment of crypto assets differ in a group reporting context?
Under IFRS, most crypto holdings are carried at cost less impairment as intangible assets, with no upward revaluation through profit or loss unless the revaluation model is applied and an active market exists. Under US GAAP via ASC 350-60, qualifying assets are measured at fair value with all changes flowing through net income. For a Spanish subsidiary consolidating into a US group, the same crypto holdings will produce different carrying amounts and different income statement effects depending on which framework applies.
When will DAC8 reporting obligations become active for Spanish firms?
DAC8 was adopted at the EU level and member states are required to transpose it into national law. Accounting firms should check the current status of Spanish transposition legislation and engage with the Agencia Tributaria's guidance on implementation timelines. Given Spain's track record of early and detailed crypto reporting requirements through forms 172, 173, and 721, firms should assume implementation will proceed on schedule and prepare client readiness accordingly.
Source: CryptaCount
FAQ
DAC8 is an EU directive that requires crypto asset service providers operating within the EU to report user transaction data to national tax authorities, which then share it automatically across the EU. It applies to any entity providing crypto asset services to EU-resident users, including exchanges, brokers, and certain wallet providers registered under MiCA.
DAC8 applies specifically within the EU and uses the EU's administrative cooperation infrastructure. CARF is an OECD framework designed to achieve similar automatic exchange between a broader group of participating jurisdictions globally. Both frameworks target the same goal of eliminating information gaps between crypto users and tax authorities, but they operate through different legal mechanisms and have different geographic scope.
IFRS does not have a dedicated crypto standard, so classification depends on the nature and purpose of the holding. Most cryptocurrencies held as investments are treated as intangible assets under IAS 38. Assets held for sale in the ordinary course of business may qualify as inventory under IAS 2. Stablecoins with contractual redemption rights may be financial instruments under IFRS 9.
ASC 350-60 requires entities to measure qualifying crypto assets at fair value at each reporting period, with changes in fair value recognised in net income. This replaces the previous indefinite-lived intangible asset model, which only allowed downward impairment. The standard applies to fungible crypto assets that do not give the holder a claim on underlying goods or services.
Under the FASB crypto fair value approach required by ASC 350-60, entities must mark their qualifying crypto holdings to market at every reporting date and run gains and losses through the income statement. Because crypto asset prices can fluctuate significantly between periods, this creates reported earnings movements that are unrelated to the entity's operating performance, which finance teams need to explain clearly in management commentary.
Yes, but the obligations apply to different aspects of a company's relationship with crypto. IFRS crypto assets rules govern how crypto holdings appear in the financial statements. DAC8 reporting obligations apply to entities that provide crypto asset services to third parties, not to companies that simply hold crypto on their own balance sheet. A Spanish company that only holds Bitcoin as a treasury asset is subject to IFRS classification rules but would not itself have DAC8 reporting duties.
Firms need complete transaction-level records including dates, asset types, quantities, counterparty identifiers, and proceeds in fiat currency for each disposal or transfer. For DAC8 specifically, user identity and residence information collected under KYC procedures must be linked to transaction records. The data must be held in a format that can be mapped to the reporting schema required by the relevant national competent authority.
Under IFRS, most crypto holdings are carried at cost less impairment as intangible assets, with no upward revaluation through profit or loss unless the revaluation model is applied and an active market exists. Under US GAAP via ASC 350-60, qualifying assets are measured at fair value with all changes flowing through net income. For a Spanish subsidiary consolidating into a US group, the same crypto holdings will produce different carrying amounts and different income statement effects depending on which framework applies.
DAC8 was adopted at the EU level and member states are required to transpose it into national law. Accounting firms should check the current status of Spanish transposition legislation and engage with the Agencia Tributaria's guidance on implementation timelines. Given Spain's track record of early and detailed crypto reporting requirements through forms 172, 173, and 721, firms should assume implementation will proceed on schedule and prepare client readiness accordingly.