A single Irish company filing costs €2 to view on the CRO portal. Even the latest annual return sits behind that fee. That small charge quietly alters behaviour. Diligence teams treat Ireland differently from registers such as Companies House where documents open without payment.
The Companies Registration Office (CRO) acts as the statutory register for Irish companies. It holds incorporation records, director appointments, filing histories, and the financial statements submitted with each annual return (Form B1). Irish holding companies show up often in cross‑border structures. They sit between UK operating entities and EU subsidiaries. Some also hold intellectual property as part of tax planning.
I noticed the CRO difference during diligence on a SaaS acquisition last year. Our internal dataset showed a dormant Irish intermediate. The CRO page showed something else. A B1 filed three weeks earlier included new financial statements plus a fresh director appointment. The register had moved. The cached dataset had not.
What the CRO actually returns
A CRO record normally opens with a company profile followed by a filing history. When pulled through registry connectors, the response tends to fall into a few consistent groups.
Company profile data usually contains fields like:
- company_number
- company_name
- company_status
- incorporation_date
- company_type
- registered_office_address
Director information sits beside the company record. The CRO surfaces director names together with appointment dates through filings and profile views. Raw registry responses often place these inside a jurisdiction block with fields such as:
- director_name
- appointment_date
- director_address
Filings carry most of the substance. The annual return (B1) commonly includes the company’s financial statements as attached documents. Registry metadata around those filings usually contains fields like:
- filing_type
- received_date
- filing_number
- document_id
The filing list matters more than the summary profile. A company page may appear unchanged for years. The B1 documents tell the real story. Director movements appear there. So do financial statements. The occasional share restructuring also turns up inside those returns.
What the CRO does not expose freely
Irish registry access differs from several European systems because documents remain paid downloads. Filing metadata is visible. The PDF itself normally requires a small payment through the CRO storefront.
Automation hits that boundary quickly. A script can see that a B1 arrived on a certain date. Fetching the attached financial statements is another matter. Open endpoints rarely expose the document itself. Many diligence pipelines mark the filing first. Someone then retrieves the PDF manually through the portal.
Beneficial ownership also sits outside the CRO. Ireland keeps that information in the separate Register of Beneficial Ownership (RBO). Access tightened after European court rulings affecting AML registers. The public interface now exposes limited data, and automated queries run into restrictions.
That separation affects diligence work. The CRO confirms directors and filing activity. Ownership detail often appears in the latest annual return attachment or in shareholder registers shared during the deal process.
Querying the registry pattern via MCP
OpenRegistry connects AI assistants to national company registers through a single MCP endpoint. The Irish jurisdiction is not active on the server right now. The public coverage matrix lists IE as disabled. Requests against it return an unsupported jurisdiction response.
The query pattern still illustrates the workflow once the connector appears again.
Search for a company by name:
search_companies({
"jurisdiction": "IE",
"query": "Stripe Payments Europe"
})
Retrieve the company profile after obtaining the registry number:
get_company_profile({
"jurisdiction": "IE",
"company_number": "513174"
})
Pull the filing history for review:
list_filings({
"jurisdiction": "IE",
"company_number": "513174"
})
That order mirrors how diligence usually proceeds in a deal room. Confirm the legal entity first. Look at the directors next. Then inspect the most recent B1 filing and the financial statements attached to it.
Why Irish registry detail matters in deals
Irish entities appear frequently in acquisition structures because multinational groups route licensing income or EU operations through Ireland. The CRO record often exposes timing signals that aggregated snapshots miss.
Director appointments offer one example. A shared director between a target company and a related Irish holding vehicle may show up in CRO filings weeks before it appears in secondary datasets. That timing sometimes hints at internal restructuring ahead of a sale.
Annual return timing carries signals too. Irish companies must submit a B1 each year with financial statements attached unless exempt. When that filing arrives late, it can indicate internal disruption or corporate changes under way. Cached datasets rarely surface that delay clearly.
Capital changes also hide inside filings rather than the summary profile. A share allotment tied to a funding round may appear only inside the latest return. Skip the filing list and the change is easy to miss.
Across cross‑border diligence the pattern repeats. Aggregated datasets help with quick screening. The register of record shows what actually happened. When the Irish connector returns to the active list, CRO checks can run straight from an AI client through the OpenRegistry MCP server. Details on supported jurisdictions and the endpoint sit at https://openregistry.sophymarine.com.
Top comments (0)