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

Crypto financial reporting has moved well beyond a niche concern. For accounting firms and finance teams advising clients who hold or transact in digital assets, the convergence of DAC8 reporting, IFRS crypto assets guidance, FASB fair value rules, and the OECD's CARF crypto reporting framework now creates a genuinely complex compliance landscape. Getting it wrong is not just a technical error. It can expose clients to penalties, undermine audit readiness, and create reputational risk for the firms advising them. This guide maps the key frameworks side by side, explains where they interact, and gives practitioners the context they need to build a defensible reporting position for any client with crypto exposure.

What DAC8 Reporting Means for Accounting Firms

DAC8 is the eighth iteration of the EU Directive on Administrative Cooperation. It extends automatic exchange of financial account information to cover crypto-asset service providers, bringing them into a reporting regime that mirrors what banks and brokers have long been subject to under CRS. The directive requires crypto-asset service providers operating in the EU to collect, verify, and report information about their users' transactions to the relevant national tax authority, which then shares that data with other member states.

For accounting firms, the immediate implication is that tax authorities across the EU will, in time, hold detailed transactional data on clients who use regulated crypto platforms. This changes the advisory conversation. Firms can no longer treat crypto holdings as a low-visibility area. Clients who have historically under-reported or misclassified crypto income face a rising risk of detection, and firms that have not built a robust crypto reporting workflow face their own professional exposure. DAC8 reporting also places obligations directly on service providers, which means clients operating exchanges, wallet services, or crypto brokerages may themselves be in scope as reporting entities.

The timeline for transposition varied across member states, but the direction of travel is clear. Firms should treat DAC8 as already shaping the data environment their clients operate in, even where full enforcement has not yet been activated domestically.

Framework	Scope	Who Reports	Data Shared With
DAC8	EU member states	Crypto-asset service providers	EU national tax authorities (mutual exchange)
CARF	OECD participating jurisdictions	Crypto-asset service providers	Tax authorities in partner jurisdictions
1099-DA (US)	United States	Digital asset brokers	IRS and taxpayer

CARF Crypto Reporting and Its Relationship With DAC8

CARF, the Crypto-Asset Reporting Framework developed by the OECD, is the international counterpart to DAC8. Where DAC8 operates within EU administrative law, CARF provides the global template that non-EU jurisdictions are expected to adopt. The two frameworks are deliberately aligned in scope and definitions, which means data collected under DAC8 is broadly compatible with CARF exchange mechanisms.

For firms with clients who transact across jurisdictions, including clients based in Poland with accounts on platforms registered outside the EU, CARF crypto reporting is the mechanism through which foreign-held data will eventually flow back to domestic authorities. The practical effect is a shrinking information gap between what a client declares and what their tax authority can independently verify.

Accounting firms should understand that CARF covers not just straightforward spot trades but also transfers between wallets where the service provider cannot identify a counterparty, certain retail payment transactions, and exchanges between crypto assets. This breadth means that a client who considers themselves to have made only a handful of taxable disposals may be the subject of a far more granular dataset held by their tax authority.

IFRS Crypto Assets: The Accounting Standards Position

Until the International Accounting Standards Board issues a dedicated standard for crypto assets, entities reporting under IFRS must apply existing standards by analogy. The consensus that has emerged, and which is reflected in guidance from national standard-setters including those in Poland, is that most crypto assets held by entities do not meet the definition of cash or a financial instrument under IAS 32. They are instead treated as intangible assets under IAS 38, unless they are held for sale in the ordinary course of business, in which case IAS 2 inventory accounting may apply.

The practical consequences of IAS 38 treatment are significant. Under the cost model, which is the default, crypto assets are carried at cost less any impairment. Impairment is recognised when the recoverable amount falls below carrying value, but gains from price recovery cannot be recognised until disposal. This creates an asymmetry that many clients find counterintuitive: a token that falls and then rises in value will show an impairment charge but no corresponding gain on recovery.

The revaluation model under IAS 38 is available, but only where an active market exists for the asset in question. Where it applies, revaluation gains go to other comprehensive income rather than through profit and loss. Firms advising clients on crypto ifrs accounting need to document the active market assessment carefully, as this is an area that attracts auditor scrutiny.

Standard	Default Treatment	Upside Recognition	Impairment
IAS 38 (cost model)	Intangible asset at cost	Only on disposal	Required when recoverable amount falls below carrying value
IAS 38 (revaluation model)	Intangible asset at fair value	Through OCI	Required; gains on recovery limited
IAS 2	Inventory at lower of cost or NRV	Only on sale	Write-down to NRV required
ASC 350-60 (US GAAP)	Intangible at fair value	Recognised each period	Mark-to-market, gains and losses through P&L

FASB Crypto Fair Value and ASC 350-60: The US GAAP Position

The Financial Accounting Standards Board moved decisively in 2023 to address the asymmetric treatment that had made IFRS so frustrating for crypto-holding entities. ASC 350-60, which applies to certain crypto assets under US GAAP, requires fair value measurement with changes recognised in net income each period. This is a fundamental departure from the indefinite-lived intangible approach that preceded it.

The FASB crypto fair value model applies to assets that meet a specific definition: fungible, secured by cryptography, created and stored on a distributed ledger, and not issued by the reporting entity or a related party. Many of the major cryptocurrencies meet this definition. The result is that US GAAP reporters now carry crypto on a mark-to-market basis, which aligns the income statement more closely with economic reality but introduces volatility that finance teams need to manage carefully in their disclosures.

For accounting firms serving multinational clients or US-listed entities, understanding the divergence between crypto us gaap accounting and IFRS treatment is essential. A client with operations in both jurisdictions may need to maintain parallel accounting records, reconciling the fair value movements required under ASC 350-60 against the impairment-only model that applies under IAS 38. This reconciliation is a real audit and reporting burden that firms should factor into engagement scoping.

Polish Accounting Context and Local Obligations

Poland follows IFRS for consolidated financial statements of publicly listed entities, while the Accounting Act governs the preparation of statutory accounts for most other companies. The Polish Accounting Act does not yet contain specific provisions for crypto assets, which means practitioners must apply the general principles of the act, typically treating crypto assets as financial assets or intangibles depending on the nature of the holding.

Polish tax law treats disposals of crypto assets as capital gains subject to a flat rate. Businesses trading crypto as part of their commercial activity are subject to standard corporate income tax rules. The obligation to report and pay tax on crypto disposals exists independently of whether a foreign exchange has filed under DAC8 or CARF. However, as automatic exchange data becomes available to the Polish tax authority, the risk of detection for undeclared gains increases materially.

Firms advising Polish clients should also be aware that the Ministry of Finance has periodically issued interpretive guidance on crypto taxation. While this guidance does not carry the force of statute, it shapes the administrative practice of local tax offices and affects how disputes are approached. Staying current with ministerial communications is a practical necessity for any firm with a meaningful crypto client base in Poland.

Building an Audit-Ready Crypto Reporting Workflow

Regardless of which accounting standard applies, the foundation of a defensible crypto reporting position is complete and verifiable transaction data. Every acquisition, disposal, transfer, income event, and cost must be traceable to a source record. For clients operating across multiple exchanges and wallets, this is not trivial. Data gaps, inconsistent cost basis methodologies, and unreconciled wallet balances are the most common triggers for audit queries.

Firms should establish a consistent cost basis methodology at client onboarding and document the rationale. In Poland and across most EU jurisdictions, FIFO is the default method for tax purposes unless the client can justify an alternative. For financial reporting, the chosen method must be applied consistently and disclosed. Mixing methodologies between tax and financial reporting is permissible but requires careful reconciliation and clear documentation.

Effective crypto compliance reporting also requires a process for identifying and classifying non-standard events: staking rewards, airdrops, hard forks, DeFi protocol interactions, and wrapped token conversions each carry different tax and accounting treatment. Firms that build a classification matrix at the start of an engagement save significant time at year-end and reduce the risk of material misstatement. Using a dedicated crypto sub-ledger that integrates with the client's ERP or accounting platform makes this process scalable as client portfolios grow.

Illustrative Scenario

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

Markus is the CFO of a Warsaw-based technology company that began accepting Bitcoin as payment from clients in 2022 and has since accumulated a portfolio of several cryptocurrencies across three exchanges. The company prepares statutory accounts under the Polish Accounting Act and consolidated IFRS accounts for its German parent.

At year-end, Markus realises the finance team has been treating all crypto holdings as a single line in the balance sheet without distinguishing between trading inventory and long-term holdings. The auditors flag this as a potential misclassification, since inventory held for sale should be measured under IAS 2 while strategic holdings may fall under IAS 38. Separately, the tax advisor notes that the company's Polish crypto tax obligations require a FIFO cost basis, but the team has been using average cost, creating a discrepancy between the tax return and the financial statements.

By implementing CryptaCount, Markus is able to pull transaction-level data from all three exchanges into a single sub-ledger, apply FIFO cost basis for Polish tax purposes while maintaining a parallel IAS 38 valuation for IFRS reporting, and produce a reconciliation that satisfies both the auditors and the tax authority. The company is also prepared for DAC8 data that may be shared with the Polish tax authority, since its declared gains now match the exchange records.

Frequently Asked Questions

What is DAC8 reporting and who does it apply to?

DAC8 is an EU directive requiring crypto-asset service providers to report user transaction data to national tax authorities, which then share it automatically with other EU member states. It applies to regulated platforms operating within the EU and is designed to bring crypto into the same information-sharing regime as traditional financial accounts. Accounting firms should understand it because client data will increasingly reach tax authorities through this channel.

How does CARF crypto reporting differ from DAC8?

CARF is the OECD's global framework for automatic exchange of crypto transaction data, designed for adoption by jurisdictions outside as well as inside the EU. DAC8 and CARF are deliberately aligned in scope and definitions, so data collected under one framework is broadly compatible with the other. For clients with accounts on non-EU platforms, CARF is the mechanism through which foreign data will flow back to domestic authorities.

How should crypto assets be treated under IFRS?

In the absence of a dedicated IFRS standard, most crypto assets are treated as intangible assets under IAS 38, either at cost with impairment testing or at fair value through other comprehensive income if an active market exists. Crypto held for sale in the ordinary course of business may qualify as inventory under IAS 2. The appropriate classification depends on the entity's business model and should be documented carefully for audit purposes.

What does ASC 350-60 require for crypto us gaap accounting?

ASC 350-60 requires entities reporting under US GAAP to measure qualifying crypto assets at fair value each reporting period, with gains and losses recognised in net income. This applies to fungible, cryptographically secured assets on distributed ledgers that are not issued by the reporting entity. It represents a significant departure from the prior indefinite-lived intangible model and eliminates the asymmetric impairment-only approach.

What is FASB crypto fair value measurement and how does it affect disclosures?

Under the FASB's fair value model for crypto assets, entities must disclose the fair value of each significant crypto asset holding, the cost basis, and the cumulative gains or losses recognised. Because fair value changes flow through the income statement each period, entities need to consider how this volatility is communicated to investors and whether any hedging or risk management disclosures are warranted.

How does Polish accounting law treat crypto assets?

The Polish Accounting Act does not contain specific crypto provisions, so practitioners apply general principles, typically treating crypto as a financial asset or intangible depending on the nature of the holding. For tax purposes, Polish law treats crypto disposals as capital gains subject to a flat rate, with FIFO as the standard cost basis method. Firms should monitor ministerial guidance, as administrative practice can affect how local tax offices approach crypto-related queries.

How should an accounting firm prepare clients for DAC8 data matching?

The key step is ensuring that the client's declared crypto income and capital gains match, or can be reconciled with, the transaction data that will be shared by exchanges under DAC8. This means establishing complete transaction records, applying a consistent cost basis methodology, and classifying all crypto income events correctly before the tax return is filed. Gaps or inconsistencies that would be hard to explain in an audit should be addressed proactively.

What crypto events require special classification beyond simple buy and sell trades?

Staking rewards, airdrops, hard fork proceeds, DeFi protocol interactions, and wrapped token conversions all carry treatment questions that a simple trades-only workflow will miss. Each event type may be taxable at receipt, at disposal, or both, depending on the jurisdiction and the nature of the asset received. Firms should build a classification matrix at engagement start so these events are captured and treated consistently throughout the year.

Why does cost basis methodology matter for crypto financial reporting?

The cost basis methodology determines the gain or loss on each disposal and directly affects both taxable income and the carrying value of remaining holdings on the balance sheet. Using different methodologies for tax and financial reporting is technically permissible in many jurisdictions but requires a clear reconciliation. An inconsistent or undocumented methodology is one of the most common sources of audit queries in crypto engagements.

How can accounting firms scale crypto reporting across multiple clients?

Scalability requires standardised data ingestion from exchanges and wallets, a consistent methodology framework applied at onboarding, and a sub-ledger layer that sits between raw transaction data and the general ledger. Without these foundations, each client engagement requires bespoke manual work that does not become more efficient over time. Purpose-built crypto accounting platforms allow firms to apply firm-wide methodology policies while accommodating the asset-specific rules each client requires.

Source: CryptaCount