Finland's YTJ Registry — what the official API actually returns

Finland's Patentti- ja rekisterihallitus (PRH) operates a dual-layer registration architecture that directly affects corporate diligence and KYC integrations. The Finnish Business Information System (YTJ) serves as the main portal. The data retrieved programmatically depends on whether you hit the public trade register or the AML-gated beneficial ownership database. Understanding this boundary is critical for compliance teams designing automated client onboarding workflows.

PRH maintains a relatively accessible digital infrastructure. However, the legal boundaries of what can be queried without an authenticated, legitimate interest under the EU Anti-Money Laundering Directives (AMLD) remain strict.

Structure of the Finnish YTJ payload

When querying a Finnish entity via the OpenRegistry MCP server, you interface with the public YTJ database. This registry indexes limited liability companies (Osakeyhtiö, or Oy), partnerships, and sole traders.

A successful query to the Finnish registry returns a structured payload where the raw jurisdiction_data block preserves the upstream Finnish and Swedish field names. Key fields you will parse from a standard profile lookup include:

• businessId (Y-tunnus): The standard Finnish nine-character format (e.g., 1234567-8). This is the primary key for all entity matching.
• name: The current registered legal name of the entity.
• companyForm: The legal structure, typically returned as Code OY for standard limited companies.
• registrationDate: The date of incorporation.
• liquidations: An array containing insolvency, liquidation, or bankruptcy proceedings, which serves as a primary flag for credit and legal risk.
• addresses: Historical and current postal and street addresses registered with the PRH.

The raw payload exposes the registeredOffices and postalAddresses arrays. YTJ tracks the exact source of each address field—whether it originates from the Tax Administration (Verohallinto) or the PRH itself. This distinction is vital for service-of-process validation, as only the PRH-registered address carries statutory weight for constructive notice.

Statutory boundaries of Finnish beneficial ownership data

Finland transposed the Fifth Anti-Money Laundering Directive (5AMLD) by requiring Finnish companies to file beneficial ownership details (Edunsaajatiedot) directly with the PRH. Following the Court of Justice of the European Union (CJEU) ruling in joined cases C-37/20 and C-601/20, public access to these registers was constrained.

In Finland, beneficial ownership information is not public record. Under the Finnish Act on Preventing Money Laundering and Terrorist Financing (444/2017), access to the UBO register is restricted to financial institutions, legal professionals under AML obligations, and those who can prove a specific legal interest.

Consequently, standard programmatic tool calls targeting the PRH via an unauthenticated gateway will not return the get_persons_with_significant_control dataset. To build an ownership chain, compliance developers must use the public officer registry to map the board of directors (Hallitus) and then run secondary verifications. The board members are publicly listed and accessible, providing a starting point for identifying the natural persons exercising control over the legal entity.

Querying Finland via OpenRegistry MCP

To fetch a Finnish company profile using the OpenRegistry MCP server, your AI agent or compliance tool issues a direct query using the ISO country code FI. There is no need to pre-parse or clean the inputs.

Here is how to structure the search tool call inside an agentic workflow:

{
  "name": "search_companies",
  "arguments": {
    "jurisdiction": "FI",
    "query": "Nokia Oyj"
  }
}

Once you obtain the correct Y-tunnus (business ID) from the search results, you can retrieve the full profile, including historical addresses, active trade names, and registration status, using the profile tool:

{
  "name": "get_company_profile",
  "arguments": {
    "jurisdiction": "FI",
    "registration_number": "0111691-0"
  }
}

The returned payload contains the unified OpenRegistry schema fields along with the raw jurisdiction_data block. This allows your downstream parsers to inspect the exact Finnish taxonomic labels if your compliance logic requires matching local registration codes.

Designing resilient compliance flows

For engineers building automated KYB and M&A diligence platforms, relying on stale database dumps is a regulatory liability. The legacy paid databases often serve outdated information. The Finnish trade register changes daily as entities update their representation rights, register auxiliary trade names (Aputoiminimi), or file for restructuring.

By leveraging the OpenRegistry MCP server, your systems query the live PRH database at the moment of onboarding. This setup eliminates the discrepancy between cached aggregator data and the official register of record. Because the anonymous tier requires no API key or complex OAuth setup, you can deploy and test this live integration within minutes. For high-volume production compliance pipelines, the paid tiers increase the rate limits and support concurrent queries across multiple European jurisdictions.

To integrate live Finnish registry checks directly into your tooling, visit the server documentation at openregistry.sophymarine.com.