DAC8 Reporting and Crypto Financial Reporting Standards: A Guide for Accounting Firms
Crypto financial reporting has moved from a niche concern to a board-level compliance obligation. DAC8 reporting, the OECD's CARF crypto reporting framework, FASB's ASC 350-60 update, and the evolving body of IFRS guidance on crypto assets are now converging at exactly the moment when clients hold more digital assets than ever before. For accounting firms, auditors, and finance teams, the question is no longer whether to engage with these standards but how to apply them consistently, defend positions under audit scrutiny, and help clients avoid costly errors. Malta, as an EU member state with an established crypto-asset licensing regime, sits at a particularly instructive intersection of these frameworks. Understanding how global standards land in a specific jurisdiction sheds light on the practical choices firms face everywhere.
What DAC8 Reporting Requires and Why It Matters Now
DAC8 is the eighth iteration of the EU Directive on Administrative Cooperation. It extends automatic exchange of information obligations to crypto-asset service providers, requiring them to collect, verify, and report user transaction data to national tax authorities, who then share that data across EU member states. The scope is broad. It covers transfers, exchanges, and certain other operations involving crypto assets as defined under MiCA, the EU's Markets in Crypto-Assets Regulation. For Malta-based CASPs and for firms advising clients who operate through Maltese entities, DAC8 reporting creates direct compliance obligations that feed into both tax filings and financial statement disclosures.
The directive follows the architecture of CARF crypto reporting at the OECD level. CARF, the Crypto-Asset Reporting Framework, was designed to close the information gaps that existed when crypto holdings sat outside traditional financial account reporting regimes such as CRS and FATCA. DAC8 is, in effect, the EU's implementation layer on top of CARF, adapted to sit alongside existing DAC obligations. For accounting firms, this dual-layer structure means that clients with cross-border operations may face both DAC8 obligations within the EU and CARF obligations in jurisdictions that have adopted the OECD framework independently.
The practical implication is that transaction-level data must be captured and classified accurately at source. Errors in classification, gaps in wallet attribution, or inconsistencies between exchange records and internal ledgers will surface during regulatory exchanges. Firms that have not yet built a clean data pipeline from client crypto accounts into their compliance workflows are exposed.
| Framework | Jurisdiction Scope | Reporting Obligation Falls On | Data Exchanged With |
|---|---|---|---|
| DAC8 | EU member states including Malta | Crypto-asset service providers | EU national tax authorities via automatic exchange |
| CARF crypto reporting | OECD adopting jurisdictions | Reporting crypto-asset service providers | Competent authorities in partner jurisdictions |
| MiCA licensing | EU member states | CASPs seeking EU passporting | ESMA and national competent authorities |
IFRS Crypto Assets: The Accounting Framework Most Firms Are Working With
Malta applies International Financial Reporting Standards for the financial statements of listed entities and for many regulated financial services firms. Crypto assets do not yet have a dedicated IFRS standard. The IASB issued an agenda decision in 2019 clarifying that most cryptocurrencies should be accounted for either as intangible assets under IAS 38 or, where they are held for sale in the ordinary course of business, as inventory under IAS 2. Neither treatment was designed with crypto assets in mind, and both create distortions that preparers and auditors have had to work around.
Under IAS 38, crypto assets held as intangible assets are measured at cost unless the entity elects the revaluation model, and the revaluation model is only available when an active market exists. For widely traded cryptocurrencies, an active market argument is supportable. For illiquid tokens, it is harder to sustain. Either way, the standard does not permit upward revaluation gains through profit or loss, only through other comprehensive income, and impairment must be recognised immediately when carrying value exceeds recoverable amount. The result is an asymmetric treatment that can depress reported asset values without reflecting economic reality.
The IASB has been working on a dedicated crypto assets standard. Any firm advising Maltese or other EU clients on crypto ifrs accounting should be tracking the IASB's project timeline and ensuring that interim positions adopted today can be adjusted as the standard develops. Disclosure, particularly around estimation uncertainty and the basis for active market determinations, is an area where auditors are increasingly focused.
FASB ASC 350-60 and Crypto US GAAP Accounting for Cross-Border Firms
US GAAP accounting for crypto assets changed materially when the Financial Accounting Standards Board finalised ASC 350-60 in December 2023, with the update effective for fiscal years beginning after December 2024. The FASB ASC 350-60 update requires entities to measure crypto assets at fair value through earnings, with changes recognised in net income each period. This is a significant departure from the prior indefinite-lived intangible asset model, under which only impairments were recognised and recoveries were not.
The FASB crypto fair value model is closer in spirit to how many practitioners and investors already think about crypto holdings. It means that a US-listed entity or a Malta-domiciled subsidiary preparing US GAAP financial statements will now record unrealised gains and losses on crypto positions in its income statement each quarter. For firms with clients operating across both IFRS and US GAAP jurisdictions, this creates an important reconciling difference. A client holding Bitcoin in a Maltese operating company and a US parent will report different carrying values and different income statement impacts depending on which set of standards applies.
Crypto US GAAP accounting also introduces specific disclosure requirements under ASC 350-60, including a tabular reconciliation of crypto asset activity, disclosure of restrictions on sale, and information about significant concentrations. Finance teams and their advisers need to ensure their sub-ledger systems can generate these disclosures without manual reconstruction, which is both time-consuming and error-prone.
| Standard | Measurement Basis | Gains Recognised | Impairment Model | Primary Users |
|---|---|---|---|---|
| IFRS (IAS 38 / IAS 2) | Cost or revaluation (IAS 38); lower of cost and NRV (IAS 2) | OCI only under revaluation model | IAS 36 impairment testing required | EU, UK, global listed entities |
| FASB ASC 350-60 (US GAAP) | Fair value through earnings | Through profit or loss each period | No separate impairment; fair value changes capture losses | US-listed and US GAAP preparers |
How CARF Crypto Reporting Sits Alongside Tax Disclosures in Malta
Malta transposed DAC8 into domestic law as part of its obligations as an EU member state. Maltese CASPs are therefore required to comply with the reporting obligations that flow from the directive. CARF crypto reporting, at the OECD level, follows a similar logic: reportable crypto-asset transactions are identified, user due diligence is conducted to establish tax residency, and aggregated transaction data is reported to the relevant competent authority for onward exchange.
For accounting firms advising Maltese CASPs or their clients, the CARF and DAC8 reporting cycle intersects with the preparation of annual financial statements and tax returns in ways that require careful coordination. The transaction data flowing through the CARF reporting system should reconcile to the figures used in the financial statements and to the positions taken in tax computations. Where there are differences, whether due to timing, classification, or treatment of staking rewards and airdrops, those differences need to be identified, explained, and documented before the filing season arrives.
Malta's tax authority, the Commissioner for Revenue, has been increasing its engagement with crypto taxation as the asset class has grown. Firms that can demonstrate clean, auditable data trails, with clear mapping between on-chain activity and reported figures, are in a far stronger position when queries arise. This is precisely where crypto compliance reporting for firms that automates the link between transaction data and regulatory filings delivers measurable value.
Audit Readiness and the Data Infrastructure Question
Across all of these frameworks, a common thread emerges: the quality of underlying data determines the quality of compliance. DAC8 reporting requires accurate user and transaction data at the CASP level. CARF crypto reporting requires the same, aggregated and formatted for exchange. IFRS crypto assets accounting requires defensible fair value inputs and contemporaneous documentation of active market assessments. FASB ASC 350-60 requires a complete and accurate inventory of crypto holdings with period-end fair values tied to observable market prices.
The firms and finance teams that will navigate this environment well are those that have built their data infrastructure with audit readiness in mind from the start. That means automated ingestion from exchanges and wallets, a sub-ledger that can hold cost basis, fair value, and impairment data simultaneously, and reporting outputs that can be exported in the formats required by different regulatory regimes without manual rekeying. For many firms, this is still a gap. Reconciling crypto activity retrospectively, at year end, across multiple exchanges and wallets, is slow, expensive, and prone to error. Prospective systems that capture and classify transactions in real time are materially easier to defend.
Illustrative Scenario
To illustrate how this applies in practice, consider the following scenario:
Markus is the CFO of a Malta-licensed fintech group that operates a crypto exchange for retail and institutional clients. The group prepares financial statements under IFRS and has a US holding company that files under US GAAP. During the year, the group held a significant Bitcoin treasury position and earned staking rewards on a proof-of-stake asset. At year end, Markus's team faced three simultaneous challenges: applying IAS 38 to the Bitcoin holdings while assessing whether an active market existed to support the revaluation model; implementing the FASB ASC 350-60 fair value model at the US parent level, creating a reconciling item between the two sets of financial statements; and preparing the group's DAC8 reporting data for submission to the Maltese Commissioner for Revenue, with transaction records needing to reconcile to the figures already in the draft financial statements.
By implementing CryptaCount across the group's exchange infrastructure, Markus's team was able to pull a single source of transaction truth that fed simultaneously into the IFRS sub-ledger, the US GAAP fair value schedules, and the DAC8 reporting output. The staking rewards were classified consistently across all three outputs, and the reconciliation between IFRS and US GAAP carrying values was documented automatically. The audit committee received a clean set of reconciliations with no last-minute manual adjustments.
Frequently Asked Questions
What is DAC8 reporting and who does it apply to?
DAC8 is an EU directive that requires crypto-asset service providers to collect user transaction data and report it to national tax authorities, who then share it automatically with other EU member states. It applies to CASPs operating within the EU, including those licensed in Malta. The scope covers exchanges, transfers, and certain other operations as defined under MiCA.
How does CARF crypto reporting differ from DAC8?
CARF is the OECD-level Crypto-Asset Reporting Framework, designed for adoption by jurisdictions globally. DAC8 is the EU's implementation of CARF principles within the existing EU administrative cooperation structure. For firms with clients operating both inside and outside the EU, both frameworks may apply simultaneously, requiring careful coordination of reporting obligations.
How should crypto assets be accounted for under IFRS?
Under current IFRS, most crypto assets are accounted for as intangible assets under IAS 38 or as inventory under IAS 2 for entities that hold them for sale in the ordinary course of business. The IAS 38 revaluation model is available where an active market exists, but gains flow through other comprehensive income rather than profit or loss. The IASB is working on a dedicated crypto assets standard.
What changed under FASB ASC 350-60 for US GAAP preparers?
The FASB ASC 350-60 update replaced the indefinite-lived intangible asset model with a fair value through earnings approach. Entities now recognise changes in crypto asset fair values, both gains and losses, in net income each period. The update also introduced specific tabular disclosure requirements, including a reconciliation of crypto asset activity and disclosure of any restrictions on sale.
What is the difference between IFRS and US GAAP treatment of crypto assets?
Under IFRS, unrealised gains on crypto assets held as intangible assets flow through other comprehensive income under the revaluation model, and impairment is recognised immediately. Under ASC 350-60 in US GAAP, all fair value changes go through profit or loss each period, creating a fundamental difference in income statement presentation. Groups preparing both sets of accounts need to reconcile this difference clearly.
Does Malta follow IFRS or local GAAP for crypto asset reporting?
Malta applies IFRS for the financial statements of listed entities and many regulated financial services firms, including licensed crypto-asset service providers. Smaller entities may use Maltese GAPSE, but firms operating in the crypto-asset space under MiCA licensing will generally be subject to IFRS requirements, making IFRS crypto assets guidance directly relevant.
How does FASB crypto fair value accounting affect cross-border firms?
A firm with both an IFRS-reporting Maltese entity and a US GAAP parent will carry the same crypto assets at different values in each set of financial statements. The IFRS entity may show cost or a revalued amount with gains in OCI, while the US parent shows fair value with changes in earnings. This creates a reconciling difference that must be documented, explained to auditors, and managed consistently across reporting periods.
What records should firms keep to support DAC8 and CARF compliance?
Firms should maintain complete, timestamped transaction records for all crypto-asset activity, including user due diligence documentation supporting tax residency determinations. These records need to reconcile to the figures used in financial statements and tax returns. Automated sub-ledger systems that capture this data at source reduce the risk of gaps or inconsistencies emerging during regulatory exchanges or audits.
Are staking rewards covered by DAC8 reporting obligations?
The DAC8 directive covers a range of reportable transactions and the treatment of staking rewards depends on how they are classified under the implementing rules in each member state. In Malta, as in other EU jurisdictions, firms should seek specific guidance on how staking income is characterised and ensure their reporting systems can capture and classify it consistently across both tax reporting and financial statement preparation.
How can accounting firms prepare clients for crypto financial reporting obligations?
The most effective preparation combines three elements: clean transaction data captured at source from all exchanges and wallets, a sub-ledger capable of supporting multiple accounting frameworks simultaneously, and a documented compliance workflow that links transaction-level data to both regulatory filings and financial statement disclosures. Firms that establish these systems prospectively rather than reconstructing data at year end are significantly better placed under both DAC8 reporting and audit scrutiny.
Source: CryptaCount
FAQ
DAC8 is an EU directive that requires crypto-asset service providers to collect user transaction data and report it to national tax authorities, who then share it automatically with other EU member states. It applies to CASPs operating within the EU, including those licensed in Malta. The scope covers exchanges, transfers, and certain other operations as defined under MiCA.
CARF is the OECD-level Crypto-Asset Reporting Framework, designed for adoption by jurisdictions globally. DAC8 is the EU's implementation of CARF principles within the existing EU administrative cooperation structure. For firms with clients operating both inside and outside the EU, both frameworks may apply simultaneously, requiring careful coordination of reporting obligations.
Under current IFRS, most crypto assets are accounted for as intangible assets under IAS 38 or as inventory under IAS 2 for entities that hold them for sale in the ordinary course of business. The IAS 38 revaluation model is available where an active market exists, but gains flow through other comprehensive income rather than profit or loss. The IASB is working on a dedicated crypto assets standard.
The FASB ASC 350-60 update replaced the indefinite-lived intangible asset model with a fair value through earnings approach. Entities now recognise changes in crypto asset fair values, both gains and losses, in net income each period. The update also introduced specific tabular disclosure requirements, including a reconciliation of crypto asset activity and disclosure of any restrictions on sale.
Under IFRS, unrealised gains on crypto assets held as intangible assets flow through other comprehensive income under the revaluation model, and impairment is recognised immediately. Under ASC 350-60 in US GAAP, all fair value changes go through profit or loss each period, creating a fundamental difference in income statement presentation. Groups preparing both sets of accounts need to reconcile this difference clearly.
Malta applies IFRS for the financial statements of listed entities and many regulated financial services firms, including licensed crypto-asset service providers. Smaller entities may use Maltese GAPSE, but firms operating in the crypto-asset space under MiCA licensing will generally be subject to IFRS requirements, making IFRS crypto assets guidance directly relevant.
A firm with both an IFRS-reporting Maltese entity and a US GAAP parent will carry the same crypto assets at different values in each set of financial statements. The IFRS entity may show cost or a revalued amount with gains in OCI, while the US parent shows fair value with changes in earnings. This creates a reconciling difference that must be documented, explained to auditors, and managed consistently across reporting periods.
Firms should maintain complete, timestamped transaction records for all crypto-asset activity, including user due diligence documentation supporting tax residency determinations. These records need to reconcile to the figures used in financial statements and tax returns. Automated sub-ledger systems that capture this data at source reduce the risk of gaps or inconsistencies emerging during regulatory exchanges or audits.
The DAC8 directive covers a range of reportable transactions and the treatment of staking rewards depends on how they are classified under the implementing rules in each member state. In Malta, as in other EU jurisdictions, firms should seek specific guidance on how staking income is characterised and ensure their reporting systems can capture and classify it consistently across both tax reporting and financial statement preparation.
The most effective preparation combines three elements: clean transaction data captured at source from all exchanges and wallets, a sub-ledger capable of supporting multiple accounting frameworks simultaneously, and a documented compliance workflow that links transaction-level data to both regulatory filings and financial statement disclosures. Firms that establish these systems prospectively rather than reconstructing data at year end are significantly better placed under both DAC8 reporting and audit scrutiny.