DAC8 Reporting and Crypto Financial Reporting Standards: A Guide for Finance Teams

Crypto financial reporting has entered a new phase. DAC8 reporting obligations are live across EU member states, the FASB has overhauled how US entities measure digital assets under ASC 350-60, and the IFRS Interpretations Committee has produced guidance that shapes how crypto assets sit on balance sheets worldwide. For accounting firms, CFOs, and finance teams, these are not abstract developments. They change client deliverables, audit file content, and the advisory conversations firms need to be having right now. Understanding how DAC8 reporting connects to broader accounting standards, including ifrs crypto assets treatment and crypto us gaap accounting requirements, is no longer optional. It is a baseline competency for any practice with crypto-active clients.

What DAC8 Reporting Requires and Why It Matters

DAC8 is the eighth iteration of the EU Directive on Administrative Cooperation, and it extends automatic exchange of information to crypto-asset service providers. Under DAC8, operators who are in scope must collect, verify, and report data on users and their transactions to the relevant national tax authority. That data is then exchanged between member states automatically. The scope covers most asset types traded on centralised platforms, and the obligations apply to both EU-based operators and non-EU operators who have clients in the EU.

For accounting firms advising crypto businesses, DAC8 reporting creates a direct compliance calendar item. Operators need systems capable of collecting the right data fields, mapping them accurately, and submitting in the required format. Firms that have not yet reviewed their clients' data architecture against DAC8 requirements are carrying advisory risk. The directive is also closely aligned with the OECD's CARF crypto reporting framework, which extends similar automatic exchange obligations to a wider group of jurisdictions beyond the EU. Practices with multinational clients need to understand how DAC8 and CARF interact rather than treating them as separate workstreams.

Framework	Jurisdiction Scope	Who Reports	Data Exchanged
DAC8	EU member states	Crypto-asset service providers (CASPs)	User identity, transaction volumes, asset types
CARF	OECD participating jurisdictions	Reporting crypto-asset service providers	User identity, gross proceeds, transaction counts

IFRS Crypto Assets: How the Standards Apply Today

IFRS does not yet have a dedicated standard for crypto assets. That absence forces preparers to apply existing standards by analogy, and the IFRS Interpretations Committee has confirmed the approach most commonly used in practice. For most holdings, entities apply IAS 38 (intangible assets) or IAS 2 (inventories) depending on the nature of the holding and the entity's business model. Under IAS 38, crypto assets are carried at cost less impairment unless the entity elects the revaluation model, which requires an active market to exist. Under IAS 2, broker-traders can measure at fair value less costs to sell, with movements going through profit or loss.

Crypto ifrs accounting therefore produces asymmetric outcomes depending on which standard applies. An entity holding Bitcoin as a treasury reserve under IAS 38 can only write assets down when impairment triggers are met, not write them back up unless the revaluation model is adopted. That creates a mismatch with economic reality during price recovery periods. Finance teams should document their classification decisions carefully and revisit them when business models change, for example when a treasury holding begins to be actively traded. Auditors increasingly scrutinise the rationale for IAS 38 versus IAS 2 classification, making that documentation audit-critical.

FASB ASC 350-60 and the Shift to Fair Value Under US GAAP

The FASB's update to ASC 350-60 represents the most significant change to crypto us gaap accounting in years. Before the update, US entities were required to measure crypto assets at historical cost with impairment-only write-downs, mirroring the practical outcome of IAS 38 without the revaluation option. The updated guidance requires entities to measure certain crypto assets at fair value at each reporting date, with changes recognised in net income. This is a mandatory change for entities in scope, not an option.

The fasb crypto fair value requirement applies to assets that meet the definition of an intangible asset, are fungible, and are traded on exchanges providing a quoted price. Most major cryptocurrencies held by US public companies fall within scope. The practical impact is that balance sheets will now reflect current market prices, and income statements will carry unrealised gains and losses each period. For finance teams, this means tighter integration between price data feeds and the general ledger, and clearer disclosures about the nature and concentration of crypto holdings. For audit purposes, fair value measurement introduces valuation risk and the need to assess whether the price source used meets the criteria under ASC 820.

Standard	Measurement Basis	Gains and Losses	Applicable To
IAS 38 (IFRS)	Cost less impairment, or revaluation model	Impairment only unless revaluation elected	Non-broker entities holding crypto as intangible
IAS 2 (IFRS)	Fair value less costs to sell	Through profit or loss each period	Broker-traders in crypto
ASC 350-60 (US GAAP)	Fair value	Unrealised gains and losses in net income	In-scope crypto assets held by US entities

How CARF Crypto Reporting Connects to DAC8

The OECD's CARF crypto reporting framework and DAC8 share a common design logic. Both require reporting entities to identify users, verify their tax residency, and report transaction data to tax authorities for automatic exchange. CARF was developed first as a global template, and DAC8 adapted that template for the EU legal context. In practice, a CASP that has built compliance infrastructure for DAC8 will find the CARF requirements familiar, though the specific data fields, submission formats, and exchange timelines differ by jurisdiction.

For accounting practices advising clients across multiple jurisdictions, the overlap is an efficiency opportunity. A single data collection and KYC process can often satisfy both frameworks if designed correctly from the outset. Firms should be helping clients audit their existing data flows now rather than waiting for the first reporting deadline. One area of particular complexity is the treatment of decentralised finance activity. Neither DAC8 nor CARF was designed primarily with DeFi in mind, and the regulatory perimeter for reporting obligations in that area remains subject to interpretation in several jurisdictions. Practices with DeFi-active clients should seek jurisdiction-specific guidance rather than assuming CARF or DAC8 rules apply straightforwardly.

Practical Implications for Accounting Firms

For accounting firms, the convergence of DAC8 reporting, IFRS crypto assets guidance, and the FASB fair value update creates both complexity and commercial opportunity. Clients who previously needed only basic bookkeeping for crypto holdings now require structured advice on classification, measurement, disclosure, and regulatory reporting. That broadens the scope of an engagement and increases the fee opportunity for practices that build the competency early.

Audit-readiness is a recurring pressure point. Finance teams that cannot produce a clean trail from transaction data through to balance sheet line items, supported by documented classification decisions and verifiable price data, will face extended audit procedures. Practices should be asking clients about their data infrastructure before year-end rather than discovering gaps during fieldwork. Where clients use multiple exchanges or wallets, a crypto compliance reporting workflow that aggregates and reconciles data across sources is essential. Manual processes at this stage introduce both error risk and resource cost that scales badly as transaction volumes grow.

Illustrative Scenario

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

Ciara is a Senior Manager at a mid-tier accounting firm in Dublin. Her client is a fintech startup that holds a treasury position in several cryptocurrencies and also operates a platform that qualifies as a CASP under the relevant EU rules. Approaching the year-end audit, Ciara realises the client has been carrying its crypto treasury under IAS 38 at historical cost without ever documenting the classification rationale or considering whether the revaluation model applies. Separately, the client's compliance team has not yet assessed its DAC8 reporting obligations and has no process to collect or verify user tax residency data.

Ciara uses CryptaCount to run a gap assessment across both workstreams. The platform helps her map the client's transaction records to the correct accounting treatment, produce the documentation needed to support the IAS 38 classification in the audit file, and identify which user data fields are missing for DAC8 submission. What began as a routine audit engagement becomes a structured advisory project covering accounting standards, regulatory compliance, and data infrastructure. The client gains audit-ready records and a clear DAC8 compliance roadmap before the reporting deadline.

Frequently Asked Questions

What is DAC8 reporting and who does it apply to?

DAC8 is an EU directive requiring crypto-asset service providers to collect and report information on users and their transactions to national tax authorities for automatic exchange between member states. It applies to both EU-based operators and non-EU operators serving EU clients. Any business that qualifies as a CASP under MiCA or equivalent national rules should assess whether it is in scope.

How does DAC8 relate to CARF crypto reporting?

CARF is the OECD's global framework for automatic exchange of crypto transaction data, and DAC8 is the EU's implementation of a similar approach within its own legal structure. The two frameworks share design principles but differ in data fields, deadlines, and exchange mechanisms. Businesses with clients in multiple jurisdictions may need to satisfy both, though a well-designed data collection process can serve both requirements efficiently.

How are crypto assets treated under IFRS?

IFRS does not have a dedicated crypto standard. Most entities apply IAS 38 (intangible assets) and carry holdings at cost less impairment, or at revaluation where an active market exists. Broker-traders may apply IAS 2 and measure at fair value less costs to sell. The classification decision depends on the entity's business model and must be documented and consistently applied.

What changed with FASB ASC 350-60 for crypto assets?

The FASB updated ASC 350-60 to require fair value measurement for certain crypto assets at each reporting date, with unrealised gains and losses recognised in net income. This replaced the previous cost-less-impairment model. The change applies to fungible crypto assets that are traded on exchanges providing a quoted price and meet the definition of an intangible asset under US GAAP.

What does fasb crypto fair value mean for financial statements?

Under the updated FASB guidance, balance sheets will reflect current market prices for in-scope crypto assets rather than historical cost. Income statements will include unrealised movements each period, which can increase earnings volatility. Finance teams need reliable price data feeds connected to their general ledger and clear disclosures about the nature of their crypto holdings.

Can a company apply IAS 38 revaluation to Bitcoin?

Yes, but only if an active market exists for the asset as defined under IAS 38. For major cryptocurrencies traded on multiple exchanges, the active market condition is generally met in practice. If the revaluation model is adopted, increases in carrying amount go to other comprehensive income and decreases are charged to profit or loss, subject to prior revaluation surplus. The choice must be applied consistently to the entire class of asset.

How should accounting firms prepare clients for DAC8 compliance?

Firms should start with a gap assessment of the client's data collection processes, focusing on whether they are capturing the user identity and transaction data fields DAC8 requires. Clients need a KYC process that records tax residency for each user. Firms should also check whether the client's reporting systems can generate output in the required submission format and whether internal controls over data quality are adequate.

Is crypto ifrs accounting the same across all jurisdictions?

The underlying IFRS standards are the same globally, but jurisdictions can add local interpretation or require additional disclosures. In Ireland, for example, entities follow EU-endorsed IFRS, which aligns closely with full IFRS but can lag slightly in adoption timing for new standards or amendments. Practices should always check the local endorsement status of any relevant guidance before advising clients on treatment.

Source: CryptaCount