Last updated: 18 Oct 2025
Ireland — Reporting Mechanisms (FATCA & CRS)
How Irish financial institutions report FATCA and CRS/DAC2 data: competent authorities, technical channels via Revenue and ROS, reportable data, annual timelines, error corrections, data quality, governance – and how this connects to the QI regime.
At a glance
- Authority: Revenue (Irish Tax and Customs) as the national hub for FATCA and CRS/DAC2.
- FATCA model: Model 1 IGA (reporting to Revenue, onwards to the IRS).
- Channels: Electronic submission via ROS/AEOI channels using XML schemas and secure transport.
- Scope: Account holder and account data, tax IDs (US TIN, other TINs), balances, income/ proceeds.
- Rhythm: Annual reporting (deadlines set by Revenue’s AEOI/FATCA guidance).
Who is affected?
- Irish banks, custodians, investment firms, management companies and other Reporting FIs.
- Insurance undertakings (relevant cash value / annuity contracts).
- Other entities classified as Reporting FIs under FATCA/CRS/DAC2 definitions.
1) Roles & responsibilities
- Revenue: receipt, validation and onward transmission of FATCA and CRS/DAC2 data; publication of filing guidelines, schema notes and deadlines.
- Institution: collection and validation of customer data (KYC/Tax), indicia checks, TIN capture and ongoing reporting and corrections.
- Central Bank of Ireland (CBI): prudential and conduct supervision of governance and AML/CFT – indirectly relevant for data quality and controls.
- IRS: recipient of FATCA data relayed by Revenue and primary supervisor of QI (separate regime, but relying on consistent data).
2) Reporting channels & technology
| Path | Description | Notes |
|---|---|---|
| ROS / AEOI upload | Electronic submission of structured XML files (FATCA and CRS) via Revenue Online Service (ROS) or AEOI upload services, using appropriate ROS credentials. | Files are validated against schema and Revenue business rules; acknowledgements and error messages must be retrieved and handled. |
| Registration | FATCA registration with the IRS (GIIN) plus registration of AEOI reporting obligations with Revenue via ROS. | GIIN has to be included where required; institutions without valid GIIN risk being treated as non-compliant for US withholding purposes. |
| Formats | FATCA XML aligned with IGA/IRS schema and Revenue FATCA Filing Guidelines; CRS XML aligned with OECD CRS schema and Irish implementation; specific transport/encryption settings per Revenue documentation. | Keep schema versions and Revenue updates under review; perform test submissions before first filings or major changes. |
3) Reportable data (content)
- Identifiers: account holder (individual/entity), addresses, jurisdictions of tax residence, US TIN (for FATCA-reportable US accounts), other TINs where required, GIINs of intermediaries where applicable.
- Account information: account numbers/identifiers, account type, year-end balance or value.
- Income/proceeds: interest, dividends, gross proceeds/redemptions and other relevant income as defined in the applicable schema and guidance.
- Due diligence status: documentation status (W-8/W-9/CRS self-certification), indicia outcomes, and, where relevant, recalcitrant or undocumented statuses.
4) Timing & reporting cycle
Reporting is generally annual. Concrete filing deadlines are specified in Revenue’s FATCA and CRS/AEOI guidance and may differ for FATCA and CRS/DAC2. In practice, institutions often use a sequence such as: cut-off extraction → technical validation → management sign-off → ROS/AEOI submission → monitoring of acknowledgements and error files.
5) Data quality & error corrections
- Error messages (business/schema): after submission, Revenue provides responses and error messages (e.g. TIN issues, country codes, numeric fields) that must be reviewed.
- Corrections: corrections, cancellations and re-submissions must follow Revenue’s technical specifications; stable record keys are essential.
- TIN management: process to obtain, validate and update US TINs (and other TINs) including monitoring, client outreach, reasonable explanation documentation and remediation of missing/invalid TINs.
- GIIN checks: periodic reconciliation of counterparty GIINs against IRS FATCA lists, with internal documentation as part of control evidence.
6) Governance & controls
Key controls
- Named reporting owner (and deputy) with clear accountability.
- Four-eyes principle and explicit management sign-off before submissions.
- Formal change/release process for schema and system changes.
- Comprehensive audit trail (input sources, mapping rules, validations, submissions, corrections).
- Regular training for Front Office, KYC, Tax Operations and IT/Data teams.
Policies & interfaces
- FATCA/CRS policy (including TIN escalation, indicia workflows, documentation requirements).
- Data protection/information security standards (legal basis, retention, access controls).
- Interface to QI: consistent W-8/W-9 data, “reason-to-know” logic and alignment between Chapter 3/4 IRC documentation and IGA/CRS due diligence.
FAQ
Who is the reporting authority in Ireland?
For FATCA and CRS/DAC2, the Revenue Commissioners act as the central reporting authority. They receive data from Irish Reporting Financial Institutions and exchange it with partner jurisdictions (including the IRS for FATCA).
Do Irish institutions report directly to the IRS?
No. Under the Model 1 IGA, Irish institutions report to Revenue, which then forwards FATCA data to the IRS. However, IRS registration (GIIN) is still required for FATCA status and QI purposes.
What data is reported?
Identifiers (including US TIN where required), account numbers, year-end balances/values, and relevant income/proceeds as set out in the FATCA and CRS/DAC2 schemas and Revenue guidance.
How does a correction work in practice?
Following an error message from Revenue, the relevant record is identified, corrected both functionally and technically, and then re-submitted as a correction/void/replacement in line with Revenue’s filing guidelines and schema rules.