Open Company Data in Ireland: Official Sources, APIs and Reuse Rights

Ireland has a serious official company-data ecosystem, but it should not be reduced to a simple list of companies. The right way to evaluate Ireland is to start with the official register, then add open-data, statistics, procurement, intellectual-property and regulator layers.

The strongest route is CRO Open Data Portal, CRO Company Records and Financial Statements datasets, CRO CKAN/API package endpoints, data.gov.ie CRO datasets, eTenders, CSO enterprise statistics and business demography, DETE RBO office context, Central Bank registers, Irish legal publications, IPOI and GLEIF LEI records. That makes Ireland a deep EU official-source refresh with CRO open-data/API evidence, data.gov.ie HVD discovery, procurement, statistics, regulator, IP, beneficial-owner/privacy cautions, source logos, Resource Pack and contact-data boundary, but it does not remove the usual reuse checks: dataset terms, attribution, no-endorsement language, privacy, marketing-law boundaries and source freshness.

This guide maps the main official sources for company data in Ireland, explains what each source can and cannot do, and shows where a normalized CompaniesData-style dataset adds value.

The deeper question is not whether a source exists. The useful question is which source can be trusted for identity, which one proves events or filings, which one is usable at scale, which one is only a manual service, and which fields become legally sensitive once the data is reused commercially.

Quick Answer

Ireland is a strong refresh candidate because the CRO Open Data Portal, CRO Company Records dataset, CRO Financial Statements dataset, data.gov.ie CRO pages, eTenders, CSO business-demography pages, DETE beneficial-ownership office context, Central Bank registers, Irish legal-publication sources, IPOI and GLEIF all passed live QA. The safe claim is not that every Irish company, beneficial-owner, filing, procurement, regulator, IP, tax and contact field lives in one unrestricted official file. The safe claim is that Ireland has a commercially valuable official open-data spine through CRO/data.gov.ie, with separate caveats for CORE/browser access, RBO access, natural-person data, attribution, no-endorsement language and marketing-contact use.

For practical work, the most useful source stack is: CRO Open Data Portal, CRO Company Records dataset, CRO Financial Statements dataset, CRO Company Records CKAN package, CRO Financial Statements CKAN package, data.gov.ie Company Records dataset.

The safe editorial answer is this: Ireland has strong public and official business-data sources, but public data is not automatically bulk-downloadable, marketing-ready or free of personal-data constraints.

A serious Ireland dataset normally needs at least four layers: the legal register for entity identity, official publications or filings for change events, public procurement/regulator/IP/statistical sources for enrichment, and a separate compliance layer for privacy, contact-data use, suppression and lawful outreach.

Key Takeaways

• Best starting point: CRO Open Data Portal, CRO Company Records and Financial Statements datasets, CRO CKAN/API package endpoints, data.gov.ie CRO datasets, eTenders, CSO enterprise statistics and business demography, DETE RBO office context, Central Bank registers, Irish legal publications, IPOI and GLEIF LEI records.
• Core source stack: CRO Open Data Portal, CRO Company Records dataset, CRO Financial Statements dataset, CRO Company Records CKAN package, CRO Financial Statements CKAN package, data.gov.ie Company Records dataset.
• Reuse rule: public visibility is not the same as bulk reuse, resale permission or marketing-contact permission.
• Buyer value: the useful dataset is the normalized, deduplicated and source-auditable version, not a raw list of portal links.
• Commercial separation: official company records, enriched company profiles and business contact data should remain separate layers with separate compliance notes.

Editorial Methodology

This article uses an official-source-first method. Sources are included when they help verify legal existence, public filings, procurement activity, taxpayer or identifier context, IP ownership, regulated status, statistics or lawful compliance context. Commercial providers and contact-data products are not used as authority for official reuse rights.

• Prefer the national registry, company house, gazette or official business-registration authority before any secondary source.
• Classify access as search, API, bulk download, paid extract, subscription, document workflow, data catalogue or unclear/manual access.
• Separate legal-entity data from establishment statistics, procurement suppliers, listed-company disclosures, tax identifiers and private contact data.
• Treat beneficial owners, officers, addresses, signatures, insolvency notices and sole-trader records as privacy-sensitive unless the source and law clearly support reuse.
• Hold or omit unstable source links when live QA shows 403, 429, 5xx, DNS, TLS or timeout behaviour that would create broken-link noise.

What Counts as Company Data in Ireland?

In Ireland, these layers should not be collapsed into one undifferentiated database. A registry result may prove legal existence, a procurement notice may prove public-sector activity, an IP record may prove brand or invention ownership, and a regulator list may prove supervision. Those are different facts with different update cycles, identifiers and reuse boundaries.

Reuse Rights and Compliance

Across jurisdictions, public-sector-information and open-data policies can support reuse of public-sector data, and high-value dataset rules increasingly treat company and company-ownership data as important public information. In practice, Ireland's actual reuse position still depends on each source, endpoint, licence and access method.

• Cite official sources and preserve update dates where the source provides them.
• Do not imply that a derived dataset is endorsed by the registry or public authority.
• Do not mix public register data with marketing-contact permission.
• Check whether API, bulk download, paid extract and web-search access have different terms.
• Treat officers, beneficial owners and natural-person data as GDPR-sensitive where applicable.

refreshable as an Ireland deep article using CRO open data, CRO CKAN/API package endpoints, data.gov.ie CRO datasets, eTenders, CSO, DETE/RBO context, Central Bank, Irish legal-publication sources, IPOI and GLEIF with EU/GDPR, beneficial-owner, attribution, no-endorsement, no-single-master-file and contact-data caveats

Coverage, Access and Update Risk

The most common mistake in Ireland company-data work is to confuse visibility with completeness. A public search screen can be authoritative for one entity lookup without being suitable for bulk ingestion. A downloadable dataset can be reusable for a defined snapshot while still excluding filings, documents, directors, inactive entities or historical changes.

• Coverage: identify whether the source covers companies, business names, branches, non-profits, sole traders, listed issuers, regulated entities or only a sector subset.
• Freshness: preserve the source update date and avoid mixing live portal results with old downloaded files without version labels.
• Identifiers: map registration numbers, tax identifiers, procurement supplier IDs, LEI records and exchange tickers as separate keys until verified.
• Language and formats: normalize local-language names, legal forms, transliteration, accents, abbreviations and address formats carefully.
• Operational access: document whether the workflow is public search, API, bulk file, paid extract, login-only service, PDF, CKAN/OData/SPARQL or manual request.

Reuse Checklist for Ireland

Controlled Registry Workflow and Source-Risk Clearance

Ireland passes the refresh bar as a strong official open-data and API-metadata guide, not as a claim of one unrestricted master company file. The public article links only to official or high-quality public sources that passed live QA from this node. CRO/CORE browser routes and the direct RBO portal remain documented as held source-risk findings, while the article relies on stable CRO open-data, data.gov.ie, procurement, statistics, regulator, legal-publication, IP and LEI sources.

Claims allowed in this article

• CRO open data and data.gov.ie provide strong official evidence for Irish company-record and financial-statement dataset discovery.
• CRO CKAN package endpoints support machine-readable metadata workflows, but each resource, field, licence and update cadence still needs its own review.
• eTenders, CSO, Central Bank, Irish legal-publication sources, IPOI and GLEIF can enrich known entities when source provenance is preserved.
• Beneficial ownership must be described as a controlled compliance layer, not as unrestricted public marketing data.

Claims not allowed

• Do not claim one unrestricted official Irish bulk file with every company, beneficial-owner, filing, tax, procurement, regulator, IP and contact field.
• Do not claim that CORE or direct RBO browser access passed automated live QA from this node.
• Do not use CRO, RBO, eTenders, CSO, Central Bank, IPOI or legal-publication visibility as consent for email, phone or sales-prospecting outreach.

Held source-risk findings

• CRO home: cro.ie – held because live QA returned 403 from this node; the CRO Open Data Portal and data.gov.ie CRO publisher pages are used as clean official evidence.
• CORE browser search: core.cro.ie – held because live QA returned 403 from this node; the refresh avoids direct browser-search dependence.
• CRO access-to-data page: cro.ie – held because live QA returned 403 from this node; CRO open-data and CKAN package endpoints are linked instead.
• CRO Open Data Portal launch article: cro.ie – held because live QA returned 403 from this node; current opendata.cro.ie source pages are linked instead.
• RBO direct portal: rbo.gov.ie – held because live QA returned 403 from this node and beneficial-ownership access is privacy-sensitive; DETE/RBO context is linked instead.

Operational boundaries

• CRO open-data boundary: CRO open data is the official anchor, but every package, resource, field and update date needs provenance and licence tracking.
• CORE boundary: CORE is important for manual registry work, but the public article avoids linking the browser route because live QA returned controlled-access behaviour from this node.
• RBO boundary: beneficial-owner information is a compliance-sensitive natural-person layer and must not be treated as lead data.
• Open-data/API boundary: CKAN package metadata improves machine access, yet supported resources and reuse conditions remain dataset-specific.

Resource Pack

Use this resource pack as a working map for verification, ingestion planning and source-risk review. The small source logos are decorative credibility cues only; the authority still comes from the official URL, owner, access model and reuse note.

Main Official Sources: Deep Dive

1. CRO Open Data Portal

Owner: official Companies Registration Office. Access: https://opendata.cro.ie/.

• What it gives: Primary official open-data discovery point for Irish company-register datasets.
• Reuse value: dataset-specific open-data licence and attribution terms
• Main limitation: Portal metadata is not a blanket licence for every document image, field or downstream use.

CRO Open Data Portal is a official Companies Registration Office source for Ireland. Its main practical value is Primary official open-data discovery point for Irish company-register datasets. Access is through https://opendata.cro.ie/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: dataset-specific open-data licence and attribution terms. The main limitation is Portal metadata is not a blanket licence for every document image, field or downstream use. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

2. CRO Company Records dataset

Owner: official Companies Registration Office. Access: https://opendata.cro.ie/dataset/companies.

• What it gives: Core company identity, status and register fields for Ireland.
• Reuse value: dataset-specific CRO open-data terms
• Main limitation: Field coverage and update cadence must be read from the dataset metadata.

CRO Company Records dataset is a official Companies Registration Office source for Ireland. Its main practical value is Core company identity, status and register fields for Ireland. Access is through https://opendata.cro.ie/dataset/companies, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: dataset-specific CRO open-data terms. The main limitation is Field coverage and update cadence must be read from the dataset metadata. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

3. CRO Financial Statements dataset

Owner: official Companies Registration Office. Access: https://opendata.cro.ie/dataset/financial-statements.

• What it gives: Financial-statement metadata and filing context linked to Irish companies.
• Reuse value: dataset-specific CRO open-data terms
• Main limitation: Filing metadata and document availability may follow separate rules.

CRO Financial Statements dataset is a official Companies Registration Office source for Ireland. Its main practical value is Financial-statement metadata and filing context linked to Irish companies. Access is through https://opendata.cro.ie/dataset/financial-statements, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: dataset-specific CRO open-data terms. The main limitation is Filing metadata and document availability may follow separate rules. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

4. CRO Company Records CKAN package

Owner: official Companies Registration Office. Access: https://opendata.cro.ie/api/3/action/package_show?id=companies.

• What it gives: Machine-readable package metadata for company-record ingestion planning.
• Reuse value: dataset-specific CRO open-data terms
• Main limitation: Package metadata does not replace field-level and resource-level checks.

CRO Company Records CKAN package is a official Companies Registration Office source for Ireland. Its main practical value is Machine-readable package metadata for company-record ingestion planning. Access is through https://opendata.cro.ie/api/3/action/package_show?id=companies, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: dataset-specific CRO open-data terms. The main limitation is Package metadata does not replace field-level and resource-level checks. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

5. CRO Financial Statements CKAN package

Owner: official Companies Registration Office. Access: https://opendata.cro.ie/api/3/action/package_show?id=financial-statements.

• What it gives: Machine-readable package metadata for filings and financial-statement context.
• Reuse value: dataset-specific CRO open-data terms
• Main limitation: Underlying resource availability and document reuse still need review.

CRO Financial Statements CKAN package is a official Companies Registration Office source for Ireland. Its main practical value is Machine-readable package metadata for filings and financial-statement context. Access is through https://opendata.cro.ie/api/3/action/package_show?id=financial-statements, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: dataset-specific CRO open-data terms. The main limitation is Underlying resource availability and document reuse still need review. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

6. data.gov.ie Company Records dataset

Owner: official Irish open-data portal / CRO publisher. Access: https://data.gov.ie/dataset/companies.

• What it gives: National open-data catalogue evidence for the CRO company-record dataset.
• Reuse value: dataset-specific open-data licence and attribution terms
• Main limitation: Catalogue metadata should be paired with the CRO source record before reuse.

data.gov.ie Company Records dataset is a official Irish open-data portal / CRO publisher source for Ireland. Its main practical value is National open-data catalogue evidence for the CRO company-record dataset. Access is through https://data.gov.ie/dataset/companies, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: dataset-specific open-data licence and attribution terms. The main limitation is Catalogue metadata should be paired with the CRO source record before reuse. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

7. data.gov.ie Financial Statements dataset

Owner: official Irish open-data portal / CRO publisher. Access: https://data.gov.ie/dataset/financial-statements.

• What it gives: National open-data catalogue evidence for CRO financial-statement data.
• Reuse value: dataset-specific open-data licence and attribution terms
• Main limitation: Financial-statement documents and metadata may have separate practical access rules.

data.gov.ie Financial Statements dataset is a official Irish open-data portal / CRO publisher source for Ireland. Its main practical value is National open-data catalogue evidence for CRO financial-statement data. Access is through https://data.gov.ie/dataset/financial-statements, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: dataset-specific open-data licence and attribution terms. The main limitation is Financial-statement documents and metadata may have separate practical access rules. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

8. data.gov.ie CRO publisher page

Owner: official Irish open-data portal / CRO publisher. Access: https://data.gov.ie/organization/companies-registration-office.

• What it gives: Publisher-level discovery for CRO datasets and provenance.
• Reuse value: dataset-specific open-data terms
• Main limitation: Publisher page is discovery metadata, not the legal source for each field.

data.gov.ie CRO publisher page is a official Irish open-data portal / CRO publisher source for Ireland. Its main practical value is Publisher-level discovery for CRO datasets and provenance. Access is through https://data.gov.ie/organization/companies-registration-office, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: dataset-specific open-data terms. The main limitation is Publisher page is discovery metadata, not the legal source for each field. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

9. eTenders Ireland

Owner: official Irish public procurement. Access: https://www.etenders.gov.ie/.

• What it gives: Public contract, buyer and supplier context for company enrichment.
• Reuse value: portal and procurement-document terms
• Main limitation: Supplier coverage is procurement-specific and not a complete business register.

eTenders Ireland is a official Irish public procurement source for Ireland. Its main practical value is Public contract, buyer and supplier context for company enrichment. Access is through https://www.etenders.gov.ie/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: portal and procurement-document terms. The main limitation is Supplier coverage is procurement-specific and not a complete business register. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

10. CSO enterprise statistics

Owner: official Central Statistics Office. Access: https://www.cso.ie/en/statistics/enterprisestatistics/.

• What it gives: Enterprise-population and sector benchmark context.
• Reuse value: CSO statistical reuse terms
• Main limitation: Aggregate statistics, not company-level legal identity records.

CSO enterprise statistics is a official Central Statistics Office source for Ireland. Its main practical value is Enterprise-population and sector benchmark context. Access is through https://www.cso.ie/en/statistics/enterprisestatistics/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: CSO statistical reuse terms. The main limitation is Aggregate statistics, not company-level legal identity records. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

How to Build an Ireland Company Dataset

A defensible Ireland company dataset should start with CRO open-data company records, then keep filings, procurement, statistics, regulator, legal-publication, IP and LEI layers separately sourced. Ireland has strong official open-data infrastructure, but dataset design still has to preserve access model, retrieval date, endpoint, reuse note and lawful-use flags for every field.

1. CRO identity seed: use the CRO Company Records dataset for legal entity identity, registration status and open-data provenance where the dataset provides it.
2. API metadata layer: use CRO CKAN package endpoints to validate package availability, resource metadata and update cadence before automated ingestion.
3. Filing layer: add the CRO Financial Statements dataset as a separate filing/financial-statement context layer, not as a substitute for full document review.
4. Procurement layer: add eTenders only as supplier and public-contract context.
5. Statistics layer: add CSO enterprise statistics and business demography for market sizing and quality checks, not company-level identity.
6. Compliance layer: keep DETE/RBO and Central Bank beneficial-ownership context behind lawful-use and GDPR controls.
7. Regulator/IP/LEI layer: add Central Bank registers, IPOI and GLEIF only as separately labelled enrichment layers.

Practical Options

Official open-data or API route

Start with the CRO Open Data Portal and the Company Records dataset for Irish company identity and open-data/API package discovery. Add the CRO Financial Statements dataset, data.gov.ie publisher records, eTenders procurement, CSO enterprise statistics and business demography, DETE/RBO context where lawful, Central Bank registers for supervised entities, Irish Statute Book and Iris Oifigiuil for legal publication context, IPOI for IP and GLEIF for LEI cross-checks.

For production use, treat this route as an ingestion plan rather than a single download. Start with the official registry or data catalogue, keep raw source snapshots, record access terms, then add enrichment sources one by one with field-level provenance.

Manual verification and document route

Some countries expose important company facts through certificates, PDF filings, gazette notices, paid extracts or login-based services. Those sources can be valuable, but they should be documented as controlled workflows. Do not describe them as open APIs or bulk datasets unless the authority clearly publishes that access model.

Contact-data and marketing-list route

For sales outreach, company identity data is only the first layer. Business emails, phone numbers, contact roles, suppression logic and segmentation require a separate compliant contact-data process. That layer should be documented separately from official registry reuse.

Private reports and risk products

Private company-report providers can be useful for manual due diligence in Ireland, but the editorial focus here is not a directory of competitors. The strategic value is understanding which official sources exist and where normalization is required.

If a user needs CRM-ready company records, the practical path is to combine official-source provenance with enrichment, deduplication, quality checks and lawful delivery controls. That is different from buying a generic lead list: the official-source layer explains what can be verified, while the commercial dataset layer explains how the records can be used operationally.

What Is Missing from Official Open Data?

• Do not claim one unrestricted Irish official bulk file containing every useful company, beneficial-owner, filing, tax, procurement, regulator, IP and contact field.
• Do not treat CRO, CORE, RBO, eTenders, Central Bank, IPOI, CSO or legal-publication visibility as marketing-contact permission.
• Do not reuse beneficial-owner, director, officer, address or other natural-person data without GDPR, lawful-use and purpose-limitation review.
• Do not rely on private Irish business-information portals as authority for official reuse rights.
• Do not treat CKAN package metadata as proof that every underlying resource, field or document image is open for unrestricted bulk reuse.
• Do not blur official company identity data with enriched commercial contact-data products.

This is why company-data products often add value even when the underlying public sources are strong: official data is frequently split across authorities, formats, languages, identifiers and access models.

Missing data should be treated explicitly in the dataset design. If an official source lacks bulk downloads, CompaniesData should not pretend that the bulk file exists; it should record the source limitation, add alternate official enrichment where lawful, and expose confidence fields so users know which attributes came from which layer.

Recommended Data Model

A practical CompaniesData-style model for Ireland should keep source evidence and commercial-use fields separate. The core table should hold legal entity identity, status, registration identifiers, legal form, jurisdiction, registered address and source dates. Separate enrichment tables can then store procurement awards, IP assets, regulator status, listed-company signals, LEI matches, sanctions/compliance hits and statistics-sector context.

• Entity identity: legal name, normalized name, registration number, jurisdiction, legal form and lifecycle status.
• Source provenance: source URL, authority, retrieval date, access method, licence/reuse note and confidence flag.
• Event history: incorporation, amendments, filings, gazette notices, insolvency or dissolution where legally public.
• Enrichment: procurement, IP, regulator, exchange, LEI and official statistics layers with their own source dates.
• Commercial delivery: CRM-ready exports, segmentation and contact-data fields only when a separate lawful basis and suppression workflow exist.

How CompaniesData Adds Value

For Ireland, CompaniesData's role is to turn fragmented source material into a usable business dataset: normalized company names, deduplicated entities, consistent country and activity fields, source provenance, update tracking and enrichment hooks.

• Normalize register identifiers and legal names.
• Match official company records with procurement, IP, LEI and regulator signals.
• Flag source provenance so every derived profile can be audited.
• Separate company identity from contact-data and marketing-permission layers.
• Package data for analysis, CRM enrichment and market research instead of forcing users to parse portals manually.

For Ireland, the editorial value of CompaniesData is not claiming that every record is open or that every field can be reused without conditions. The value is the opposite: making source boundaries visible, normalizing messy records, adding explainable enrichment and delivering a dataset that users can audit instead of a black-box scrape.

Request a CompaniesData sample for Ireland if you need a practical dataset rather than a list of source portals.

Commercial Dataset and Contact-Data Boundary

This Ireland guide supports CompaniesData’s company-database work, but official registry, filing, beneficial-owner, procurement, statistics, regulator, IP or open-data visibility is not outreach permission. These sources can verify company facts and compliance context. They do not automatically authorize email lists, phone outreach, WhatsApp enrichment or sales-prospecting resale.

• Company identity layer: legal name, company number, status, registered-office context, CRO source URL, retrieval date and confidence.
• Official enrichment layer: CRO filings/open data, data.gov.ie, eTenders, CSO, Central Bank, Irish legal-publication sources, IPOI and LEI context with separate source dates.
• Compliance layer: GDPR, beneficial-owner sensitivity, no-endorsement language, CKAN/API validation, dataset-specific licence review and held-source status.
• Contact-data layer: business emails, phones, roles, segmentation and suppression require a separate lawful workflow through CompaniesData.cloud.
• Spanish-speaking buyers: Hispanic contact-data demand should be routed to CentraldeComunicacion.es instead of third-party contact-data competitors.

Source Matrix

Source	Owner	What it gives	Reuse value	Limitations
CRO Open Data Portal	official Companies Registration Office	Primary official open-data discovery point for Irish company-register datasets.	dataset-specific open-data licence and attribution terms	Portal metadata is not a blanket licence for every document image, field or downstream use.
CRO Company Records dataset	official Companies Registration Office	Core company identity, status and register fields for Ireland.	dataset-specific CRO open-data terms	Field coverage and update cadence must be read from the dataset metadata.
CRO Financial Statements dataset	official Companies Registration Office	Financial-statement metadata and filing context linked to Irish companies.	dataset-specific CRO open-data terms	Filing metadata and document availability may follow separate rules.
CRO Company Records CKAN package	official Companies Registration Office	Machine-readable package metadata for company-record ingestion planning.	dataset-specific CRO open-data terms	Package metadata does not replace field-level and resource-level checks.
CRO Financial Statements CKAN package	official Companies Registration Office	Machine-readable package metadata for filings and financial-statement context.	dataset-specific CRO open-data terms	Underlying resource availability and document reuse still need review.
data.gov.ie Company Records dataset	official Irish open-data portal / CRO publisher	National open-data catalogue evidence for the CRO company-record dataset.	dataset-specific open-data licence and attribution terms	Catalogue metadata should be paired with the CRO source record before reuse.
data.gov.ie Financial Statements dataset	official Irish open-data portal / CRO publisher	National open-data catalogue evidence for CRO financial-statement data.	dataset-specific open-data licence and attribution terms	Financial-statement documents and metadata may have separate practical access rules.
data.gov.ie CRO publisher page	official Irish open-data portal / CRO publisher	Publisher-level discovery for CRO datasets and provenance.	dataset-specific open-data terms	Publisher page is discovery metadata, not the legal source for each field.
eTenders Ireland	official Irish public procurement	Public contract, buyer and supplier context for company enrichment.	portal and procurement-document terms	Supplier coverage is procurement-specific and not a complete business register.
CSO enterprise statistics	official Central Statistics Office	Enterprise-population and sector benchmark context.	CSO statistical reuse terms	Aggregate statistics, not company-level legal identity records.
CSO business demography	official Central Statistics Office	Business birth/death and enterprise demography context.	CSO statistical reuse terms	Aggregate demography, not a register extract.
data.gov.ie CSO business demography dataset	official Irish open-data portal / CSO publisher	Open-data discovery for business-demography series.	dataset-specific open-data terms	Aggregate dataset, not a company-level source.
DETE RBO office context	official Department of Enterprise, Trade and Employment	Beneficial-ownership governance and source-risk context.	DETE/RBO terms; GDPR and BO caution	Beneficial-owner data is sensitive; public access and reuse are constrained.
Central Bank of Ireland registers	official Central Bank of Ireland	Financial-sector supervised-entity enrichment and compliance checks.	Central Bank terms	Sector-specific, not general company-register coverage.
Central Bank beneficial ownership register	official Central Bank of Ireland	Beneficial-ownership context for certain financial vehicles.	Central Bank terms; GDPR and BO caution	Controlled compliance source, not marketing data.
Irish Statute Book	official Attorney General / Irish Statute Book	Legal framework context for company, procurement and data reuse interpretation.	official legal-publication terms	Legal source, not a company dataset.
Iris Oifigiuil	official Irish State gazette	Legal notice and official-publication context for company events.	official publication terms	Notice layer, not a normalized company register.
Intellectual Property Office of Ireland	official Intellectual Property Office of Ireland	Trademark, patent and design enrichment for Irish companies.	IPOI terms	IP rights do not prove active company status.
GLEIF LEI records for Ireland	GLEIF	LEI cross-checks for Irish legal entities with global identifiers.	GLEIF open data terms	Only entities with LEIs; not comprehensive company-register coverage.

Ireland's company-data workflow should start with CRO Open Data Portal company records and CKAN/API package metadata, then add financial-statement data, data.gov.ie discovery, eTenders procurement, CSO statistics, Central Bank registers, legal-publication context, IPOI and GLEIF enrichment layers. The refresh should highlight strong CRO/data.gov.ie open-data evidence while clearly separating official company records from RBO, natural-person and contact-data reuse.

FAQ

Is there a single free official bulk company database for Ireland?

Not always. Ireland has official company-data sources, but bulk access, API access, paid extracts and web search can be separate products. Do not assume a complete free bulk file unless the specific source proves it.

What is the best first source for Ireland company data?

The best first source is CRO Open Data Portal, CRO Company Records and Financial Statements datasets, CRO CKAN/API package endpoints, data.gov.ie CRO datasets, eTenders, CSO enterprise statistics and business demography, DETE RBO office context, Central Bank registers, Irish legal publications, IPOI and GLEIF LEI records. It should then be combined with statistics, procurement, IP and regulator sources.

Can public company data be reused commercially?

Often yes, but only under the conditions of the specific source. Attribution, update-date preservation, no-endorsement wording and GDPR controls may apply.

Can I use registry data for cold email marketing?

No automatic conclusion follows from public registry access. Marketing requires a separate lawful basis, suppression handling and contact-data compliance review.

Why use CompaniesData instead of manually collecting Ireland sources?

Manual collection is slow because identifiers, formats, languages and coverage differ by source. CompaniesData adds normalization, matching, deduplication, provenance and practical delivery formats.

How often should Ireland company data be refreshed?

Refresh cadence depends on the source. Registry searches and APIs can support frequent checks, while gazettes, procurement portals, statistical releases and paid extracts may update on different schedules. A reliable dataset should store retrieval dates and source-specific update notes.

What should be audited before publishing or selling an enriched dataset?

Audit source authority, licence terms, personal-data exposure, contact-data lawful basis, field provenance, suppression rules, update dates and whether any official source prohibits automated reuse or resale.

Sources

• CRO Open Data Portal – official Companies Registration Office
• CRO Company Records dataset – official Companies Registration Office
• CRO Financial Statements dataset – official Companies Registration Office
• CRO Company Records CKAN package – official Companies Registration Office
• CRO Financial Statements CKAN package – official Companies Registration Office
• data.gov.ie Company Records dataset – official Irish open-data portal / CRO publisher
• data.gov.ie Financial Statements dataset – official Irish open-data portal / CRO publisher
• data.gov.ie CRO publisher page – official Irish open-data portal / CRO publisher
• eTenders Ireland – official Irish public procurement
• CSO enterprise statistics – official Central Statistics Office
• CSO business demography – official Central Statistics Office
• data.gov.ie CSO business demography dataset – official Irish open-data portal / CSO publisher
• DETE RBO office context – official Department of Enterprise, Trade and Employment
• Central Bank of Ireland registers – official Central Bank of Ireland
• Central Bank beneficial ownership register – official Central Bank of Ireland
• Irish Statute Book – official Attorney General / Irish Statute Book
• Iris Oifigiuil – official Irish State gazette
• Intellectual Property Office of Ireland – official Intellectual Property Office of Ireland
• GLEIF LEI records for Ireland – GLEIF