On August 24, 2026, Ireland's Office of the Revenue Commissioners published eBrief No. 121/26, issuing the first official Irish guidance on how Reporting Crypto-Asset Service Providers (RCASPs) must meet their obligations under DAC8 and the OECD Crypto-Asset Reporting Framework (CARF). The accompanying Tax and Duty Manual Part 38-03-38 sets out, in operational terms, how the new reporting regime works in Ireland. The collection duty is already live since January 1, 2026, and the first annual return is due May 31, 2027.
DAC8, formally Council Directive (EU) 2023/2226, amended the long-standing administrative cooperation directive, Council Directive 2011/16/EU, to embed the OECD's CARF standard into EU law. It obliges crypto-asset service providers to collect user and transaction data and exchange it automatically between participating tax administrations. Revenue's manual is the Irish operational layer on top of that EU obligation, telling providers how to identify reportable users, what to capture, and how the filing and exchange mechanics work in Revenue's systems.
What must Reporting Crypto-Asset Service Providers now do under Part 38-03-38?
The manual requires an RCASP to collect identifying and transaction information on its reportable users and their crypto-asset transactions, then transmit that information to Revenue for automatic exchange with other participating jurisdictions. From January 1, 2026, the collection obligation is active: every reportable user onboarded or transacting in 2026 falls in scope. The first reporting cycle covers the full calendar year 2026 (January 1 to December 31, 2026), and the return must reach Revenue by May 31, 2027.
Part 38-03-38 is guidance rather than new binding legislation: the underlying obligation already took effect on January 1, 2026 under the transposed DAC8 rules. What the manual adds is the practical Irish detail on how to identify reportable users, what transaction fields to capture, and how the filing and exchange mechanics operate. For in-house tax and compliance leads, the document is the reference to build 2026 data collection and 2027 filing workflows against, not a future event to monitor passively.
Which crypto businesses are caught as RCASPs in Ireland?
The category of Reporting Crypto-Asset Service Provider is deliberately broad. It captures entities that provide services on behalf of another person in respect of crypto-assets, including crypto-asset exchanges, custodial wallet providers, brokers, and ATM operators, where those services are provided to Irish-resident users or otherwise fall within Ireland's reporting scope. A provider does not need to be Irish-domiciled to be in scope: an RCASP selling into the Irish market is within the net.
Ireland is a significant host jurisdiction for EU crypto activity. Coinbase Europe Ltd, one of the largest EU-licensed crypto exchanges, operates from Ireland under Central Bank of Ireland authorization, and other exchanges, custodians, and brokers serving Irish users fall within the RCASP definition. Big-4 and specialist crypto tax advisory practices should treat any client with an Irish user base or Irish operations as potentially in scope and confirm registration and reporting readiness now, before the 2026 data set hardens into a fixed filing obligation.
What is the reporting timeline and first filing deadline?
The critical dates are fixed and non-negotiable. Collection is already underway for 2026 transactions, and the first automatic exchange follows the 2026 calendar-year return.
| Obligation | Period covered | Deadline |
|---|---|---|
| Collect reportable user and transaction data | From January 1, 2026 | Ongoing |
| First annual RCASP return to Revenue | January 1 to December 31, 2026 | May 31, 2027 |
| Automatic exchange with partner jurisdictions | 2026 data | After the May 31, 2027 return |
Because collection runs from the start of 2026, any RCASP that has not yet stood up its data capture for the year is already accumulating a reporting gap. Identifying reportable users retroactively for a full year of transactions is materially harder than capturing the right fields at the point of transaction, so the manual should be read and operationalized now rather than close to the 2027 filing date.
How does the Irish guidance fit the EU DAC8 directive and OECD CARF?
CARF, developed by the OECD, is the international standard for the collection and automatic exchange of crypto-asset transaction information between tax administrations. The EU adopted it through DAC8, which sits inside the existing DAC architecture (Council Directive 2011/16/EU) that already governs the automatic exchange of information between EU member state tax authorities. Ireland transposes EU directives of this kind by Statutory Instrument made by the Minister for Finance under the European Communities Act 1972, with Revenue as the sole tax administration responsible for operational guidance and enforcement.
Revenue's Part 38-03-38 is therefore the national operational manual on a framework whose legal root is EU and whose data standard is OECD. Compliance teams tracking this across jurisdictions should treat the Irish manual as the local layer and expect parallel national guidance from other member states as the May 2027 deadline approaches. Continuous, per-jurisdiction real-time monitoring surfaces this kind of guidance the moment Revenue publishes it.
Take advantage of this real-time watch
Next steps for affected teams:
- Confirm whether your entity qualifies as an RCASP for Irish reporting purposes.
- Audit the transaction and user data captured since January 1, 2026 against the Part 38-03-38 requirements.
- Brief tax operations and engineering teams on the May 31, 2027 filing deadline and the fields Revenue expects.
Part 38-03-38 is the authoritative Irish reference for building the 2026 data set and the 2027 return.
