DAC8 2026: How to Configure Your ERP for Digital Asset Tax Reporting

Since 1 January 2026, the DAC8 directive has been in force across the European Union. Crypto-Asset Service Providers (CASPs) are required to identify, collect, and report to their national tax authority the full set of crypto transactions carried out by their EU-resident clients throughout the 2026 financial year, with a first filing deadline of 31 January 2027.

But DAC8 is not limited to crypto exchanges. Any mid-market company that holds digital assets on its balance sheet, has issued loyalty tokens for its B2B distributors, or pays executives and employees in cryptocurrency falls within scope. And this is where the topic becomes a concrete ERP challenge: your national tax authority will receive from your institutional exchange (Binance Institutional, Coinbase Prime, Kraken Pro) the full details of your 2026 transactions. If your internal accounts do not reflect the same reality, you face correction orders during the automated consistency check expected in 2027–2028.

This guide is aimed at CFOs and tax managers of mid-market companies (annual revenue €50–500 M). It answers three questions: are you genuinely in scope? What ERP configurations are essential before 31 December 2026? And which tools allow you to produce the DAC8 declaration without bespoke development?

What Is DAC8 and Who Among Mid-Market Companies Is Really Affected?

The Directive, the Implementing Measures, the Timeline

Council Directive (EU) 2023/2226 of 17 October 2023 (“DAC8”) extends the automatic exchange of tax information to crypto-assets, aligning with the OECD’s Crypto-Asset Reporting Framework (CARF).

Each EU member state has transposed DAC8 through national legislation, with implementing regulations published in late 2025. Obligations cover transactions carried out from 1 January 2026, with the first declaration due 31 January 2027 for 2026 data. Automatic exchange between EU tax administrations follows before 30 September 2027.

Milestone	Date
Mandatory transaction tracking begins	1 January 2026
First CASP → national tax authority filing	31 January 2027
EU cross-border automatic exchange	Before 30 September 2027
Automated cross-check with corporate tax returns	2027–2028

Scope: Not Just Exchanges

The directive primarily targets CASPs (Crypto-Asset Service Providers): exchanges, custodians, crypto-to-fiat conversion platforms. CASPs established in another EU member state or in a CARF-partner jurisdiction with equivalent exchange agreements are exempt.

Three situations directly affect non-CASP mid-market companies:

1. Crypto holdings on the balance sheet: a company that buys Bitcoin or Ether as a cash reserve or speculative investment. Your institutional exchange will report those transactions to the tax authority; the company must have consistent internal accounting.
2. Remuneration or loyalty tokens: a company that has issued tokens to reward B2B partners or supplement employee pay. Those tokens fall within MiCA/DAC8 scope if they can be used as a means of payment or investment.
3. NFTs held as stock or intangible asset: a company that has acquired NFTs as brand assets (digital rights, partner service access) must account for them under the new standards.

What DAC8 Concretely Requires of Mid-Market Companies

For non-CASP companies, DAC8 creates an indirect obligation: consistency between the data your exchanges report to the tax authority and the data declared in your corporate tax return. It also imposes, for companies that issue tokens or NFTs, internal registry obligations (attribution register, valuation at grant date, taxpayer identification numbers for beneficiaries).

The 4 Accounting Changes DAC8 Requires in Your ERP

1. New Accounts to Create in the Chart of Accounts

French accounting standard ANC 2020-05 (applicable for financial years ending before 31 December 2026) introduced asymmetric treatment of digital assets: unrealised losses are provisioned, but unrealised gains are not recognised. ANC 2026-01 (published January 2026) corrects this asymmetry and becomes mandatory from 1 January 2027, with the option of early adoption in 2026. Companies in other EU member states should verify the equivalent national standard or, for IFRS reporters, apply IAS 38 / fair-value guidance as appropriate.

For companies following French GAAP, the new accounts to create in your ERP chart of accounts are:

• Account 522: crypto-assets held (previously treated under account 50x under ANC 2020-05)
• Account 513: stablecoins (treated as electronic money, separate regulation)
• Account 524: borrowed digital assets (staking, institutional lending)

If your ERP uses a locked chart of accounts with non-configurable account codes, this is a blocking point to resolve before the 2026 year-end close.

2. Year-End Valuation: Shift to Fair Value

Under ANC 2020-05, historical cost prevailed, with depreciation provisions for unrealised losses. Under ANC 2026-01, fair value at each closing date becomes the rule, aligning French GAAP with IFRS treatment of intangible assets. For IFRS reporters, this alignment is already standard. Practical consequences for ERP configuration:

• The ERP must automatically import the closing price of each crypto-asset at every accounting cut-off (monthly, quarterly, annual).
• Unrealised gains are now recognised on the balance sheet, not just unrealised losses. This changes the income statement presentation and the corporate tax base.
• Crypto volatility creates significant profit-and-loss swings between cut-offs: auditors will require solid methodological documentation.

3. FIFO Gain/Loss Calculation: Lot-by-Lot Configuration

Each disposal of a digital asset — whether for fiat currency or in a crypto-to-crypto exchange — generates a separate taxable event. The calculation method must be documented and applied consistently across the entire portfolio.

The two accepted methods are:

• FIFO (First-In, First-Out): assets purchased first are treated as sold first. This is the default method under ANC 2026-01 and broadly recommended under CARF.
• WAC (Weighted Average Cost): the cost basis is recalculated after each acquisition.

Configuring FIFO in a general-purpose ERP (SAP, Oracle, Sage) requires creating a lot management model (batch management) specific to digital assets, separate from physical inventory management. Each lot corresponds to a dated acquisition with its unit entry cost and purchase date.

4. Interface with the Corporate Tax Return

Gains from digital asset disposals are taxable business income. The gain or loss calculated by the ERP module must feed directly into the corporate tax return without manual intermediate entry. Any discrepancy between ERP valuation and the declared amount is the first red flag for a tax inspector comparing your data with those transmitted by your exchange.

The 4 Priority ERP Configurations Before End of 2026

1. Integration of Feeds from Institutional Exchanges

Manual entry of crypto transactions into the ERP is not viable once monthly volume exceeds a few hundred transactions. Institutional exchanges offer REST APIs to export the full transaction history with, for each operation: UTC date and time, type (buy/sell/transfer/staking reward), quantity, EUR equivalent at transaction date, transaction fees.

Integration happens in three steps:

1. API connector: either via a specialist tool (Cryptio, Bitwave, Tres Finance) or an internal ETL pipeline (Python, dbt) that queries the exchange API and pushes data into the ERP.
2. Accounting mapping: each API operation type is mapped to a specific ERP account (purchase → debit account 522, incoming transfer → debit 522, disposal → credit 522 + debit bank account).
3. Reconciliation: operations imported from the exchange are matched against the corresponding bank payments (inbound/outbound SEPA transfers) to validate consistency.

2. Extended Multi-Currency Module: Crypto as a Third Currency

ERPs natively handle multiple fiat currencies. Crypto-assets require extending this module: each cryptocurrency held is treated as a “currency” with a variable exchange rate, updated at each transaction and at each closing date.

Configuration checklist:

• Create each cryptocurrency held (BTC, ETH, USDC…) as a third-party currency in the ERP reference data.
• Configure a price feed (CoinGecko API, Kaiko or Refinitiv for institutional rates) for automatic exchange-rate updates.
• Define the closing-date valuation rule (fair value = market price at 23:59 CET on the last day of the financial year).

3. FIFO Traceability for Digital Asset Disposals

FIFO management of disposals requires retaining, for each unit of digital asset acquired, a “lot” comprising: acquisition date, unit cost in EUR, remaining quantity. On each disposal, the ERP consumes the oldest lots first and automatically calculates the unit gain or loss.

This mechanism is conceptually identical to FIFO stock management for manufactured goods. The difference is that digital assets can be held in fractional units (fractions of a Bitcoin) and lots originate from an automated transaction feed rather than physical goods receipts.

4. Declarative Module: Preparing Data for DAC8 Reporting

For CASPs, the declarative module must produce a structured file compliant with the DAC8/CARF XSD schema, to be filed with the national tax authority before 31 January 2027. For non-CASP mid-market companies, the declarative module serves to prepare internal data for presentation in the event of a tax audit: token attribution register, disposal history, FIFO method documentation, audit trail of prices used.

Elements to archive and trace in the ERP:

• All transactions in the period (purchase, sale, crypto-to-crypto exchange, staking rewards, transfers)
• EUR equivalents used for each valuation, with their source
• The documented valuation method (FIFO, WAC) and its adoption date
• Declarations produced and data transmitted to the tax authority

See our guide on ERP audit trail: SOX, GDPR, GoBD and FEC retention obligations for the archiving requirements applicable to these documents.

Comparison: Which ERP Natively Supports Digital Assets?

SAP S/4HANA: FI Module + Cryptio or Bitwave Extension

SAP does not natively offer a “digital assets” module within its standard FI module. Configuration requires creating specific asset classes in the Asset Accounting module (FI-AA) or managing lots in Materials Management (MM), depending on volume and complexity. For CASPs or companies with high crypto volumes, partners such as Cryptio and Bitwave offer SAP-certified connectors that automate the exchange-to-FI transaction flow.

Oracle Fusion Cloud: Financial Management + Third-Party Connectors

Oracle Fusion includes an advanced multi-currency module and a configurable valuation engine that can absorb crypto-assets as third-party currencies with market prices. Kaiko and Refinitiv (LSEG) offer price-data connectors directly into Oracle Cloud. Chart of accounts adaptation (accounts 522, 513, 524 for French GAAP, or equivalent for other frameworks) is native in the Oracle reference-data structure.

Sage Intacct: Multi-Entity Module, Cryptio Partnership

Sage Intacct is particularly well suited to multi-entity mid-market groups that want to manage crypto-assets within a group structure. The partnership with Cryptio (announced in 2024) enables automatic synchronisation of exchange transactions into the Intacct GL module, with per-entity configurable account mapping.

Odoo 18: Limitations of the Native Module, Workarounds via Development

Odoo 18 has no native digital-asset management module compliant with ANC 2026-01 (French GAAP) or the equivalent IFRS approach. The accounting module handles multiple currencies well, but FIFO disposal management and automated exchange integration require community modules (OCA) or bespoke development. For a company using Odoo as its sole ERP, DAC8 compliance cost should be estimated at €15,000–40,000 in custom development, depending on transaction volume.

Dedicated Solutions: Cryptio, Tres Finance, Bitwave

These tools position themselves as “crypto accounting middleware” to integrate with your existing ERP rather than replace it. They handle exchange connectivity, FIFO calculation, accounting journal production, and ERP-format export (SAP IDOC, Oracle CSV, Sage import). For a company with fewer than 500 crypto transactions per year, one of these tools combined with your existing ERP is typically less costly than native development.

CFO Checklist: 10 Points Before the 2026 Year-End Close

Before 31 December 2026, review these 10 points:

1. Holdings inventory: list all company crypto wallets (institutional exchange, cold wallets, custodian).
2. DAC8 eligibility: determine whether your company is a CASP or falls within indirect scope (balance sheet holdings, tokens issued).
3. Chart of accounts: create the required digital-asset accounts in your ERP if not yet done (account codes per applicable GAAP).
4. Valuation method: choose FIFO or WAC, document it in writing, apply it retroactively from 1 January 2026.
5. Price source: choose an institutional price feed (Kaiko, Refinitiv or CoinGecko Pro), configure it in the ERP.
6. Exchange integration: activate or build the API connector to your institutional exchange.
7. Bank reconciliation: verify that each SEPA transfer linked to a crypto purchase or sale is automatically reconciled in the ERP.
8. Audit trail: configure archiving of valuation journals, prices used, and declarations produced (minimum retention: 10 years).
9. Corporate tax return: verify that your ERP’s tax module incorporates digital-asset gains in the corporate income tax calculation.
10. Consistency test: simulate the reconciliation between your internal accounting and a transaction export from your exchange — EUR amounts should match to within 0.5% variance.

For more on ERP financial reporting, read our guide on ERP and embedded business intelligence: dashboards and analytics in 2026 and our analysis of ERP data archiving and retention: legal obligations and technical strategy.

To validate your DAC8 readiness, start with a targeted audit of your current ERP configuration for digital assets. Typical budget: €8,000–20,000 depending on portfolio size and complexity. Output: a prioritised roadmap with the 3–5 critical workstreams to complete before the December close.