Finland Company Data Sources and YTJ Records
Finland is one of the stronger European jurisdictions for official company-data work because the YTJ/PRH stack is explicit about open data, API use, daily updates, basic company details and important exclusions. That makes Finland a good benchmark for what a serious open-company-data article should do: start with the official register and API evidence, then keep every enrichment layer separate.
Quick source answer: For Finland, start with the Business Information System/YTJ and official PRH/statistics/open-data routes, then check which fields are available, downloadable or reusable. This guide answers the registry-source question first, then explains source limits, reuse conditions and where normalization adds value.
The practical mistake is to say that Finland has “all company data” available in one reusable file. The safer and more useful answer is more precise. YTJ/PRH open data is the primary machine-readable route. YTJ company search and PRH online services support manual verification and document/product routing. Suomi.fi Avoindata helps discover wider public-sector datasets. HILMA, PRH intellectual-property services, FIN-FSA, FCCA and GLEIF add supplier, IP, regulated-entity, competition and LEI context.
This refresh replaces the older Finland page, which was useful as a source list but below the current CompaniesData depth bar. The new article adds editorial methodology, source-risk analysis, reuse controls, practical manual/API/bulk options, source-by-source notes, a recommended data model, held-source findings and indexing-ready formatting.
Key Takeaways
- Best official starting point: YTJ / PRH open data, because it is free, official, API-oriented, updated daily and clear about missing email and phone fields.
- Best manual verification route: YTJ company and organisation search, which supports free searches by Business ID and exposes core current company details.
- Best register context: PRH Trade Register and PRH online services/Virre explain filings, extracts, paid products and service boundaries.
- Best enrichment stack: Suomi.fi Avoindata, HILMA, PRH IP, FIN-FSA, FCCA and GLEIF add public-sector dataset discovery, procurement, IP, regulator, competition and LEI signals.
- Held this cycle: Statistics Finland, direct paid PRH products, beneficial ownership, some private-trader personal details and private contact-data reuse remain held or special-review.
- Contact-data caution: Finnish public company data is not consent for email, phone, lead-list or sales-prospecting contact enrichment.
Editorial Methodology
The CompaniesData method starts with official, primary sources. For Finland, the editorial order is YTJ/PRH open data first, YTJ company search second, PRH Trade Register and PRH online services third, then public-sector catalogue, procurement, IP, regulator, competition and LEI sources as enrichment layers. High-quality non-official context can help discovery, but it is not used as evidence for official reuse rights.
Each final linked source was checked from this environment on 2026-06-14 using browser-like, Googlebot-like and Bingbot-like profiles. A source had to return real content, pass expected semantic checks, avoid hard 404/410 errors and avoid obvious challenge-page or bot-protection behavior. Sources that are official but blocked, paid, sensitive or too personal were moved into held notes instead of being used as clean linked evidence.
Source logos in the matrix and Resource Pack are decorative favicon cues loaded through a stable proxy. They are not evidence by themselves. The evidence is the official URL, source owner, access model, reuse note and limitation recorded in the local source-live artifact.
Coverage, Access and Update-Risk Analysis
Registry and API coverage: the YTJ/PRH open-data route provides the strongest source evidence. It supports basic company details, register-membership details and digital financial-statement information. The official page also states that the data are digital and updated once a day. That supports a high-confidence API and update-cadence claim, not a claim that every Finnish corporate document or contact field is freely reusable.
Known exclusions: YTJ/PRH open data does not provide email addresses or phone numbers. It also excludes private traders and certain public-sector or tax partnership categories. A derived Finland dataset should therefore expose source coverage and exclusions clearly instead of hiding them behind a generic “complete database” label.
Manual search and documents: YTJ company search is free and useful for Business ID lookup, register membership, legal name, company form, registered office and main line of business. PRH online services and Virre add extract and document workflows. Some products are free, but financial statements, articles of association and other documents can involve fees or product-specific terms.
Enrichment layers: HILMA covers procurement notices and supplier events; PRH IP pages route patent and rights-owner context; FIN-FSA registers cover supervised financial entities; FCCA covers competition and consumer authority context; GLEIF covers LEI-bearing entities. None of these sources replaces the YTJ/PRH company core.
Update risk: YTJ/PRH open data, YTJ search, PRH document products, procurement notices, IP records, regulator records, competition cases and LEI records update on different schedules. A trustworthy dataset should carry source-specific timestamps rather than one generic Finland freshness date.
Reuse Checklist
- Authority check: record whether each field came from YTJ/PRH open data, YTJ search, PRH Trade Register, PRH online services, Avoindata, HILMA, PRH IP, FIN-FSA, FCCA or GLEIF.
- Access check: separate API/open-data use, free search, paid extracts, document products, catalogue metadata, procurement notices, regulator lists and LEI API records.
- Field-scope check: do not claim that email addresses, phone numbers, beneficial ownership, all financial statements, articles of association or every private-trader detail are available in the open-data route.
- Licence and fee check: preserve source-specific terms, product fees, access dates, update dates, attribution requirements and no-endorsement wording.
- Personal-data check: private traders, representatives, beneficial owners, addresses and document-level natural-person data require lawful-basis, minimisation, retention and suppression controls.
- Crawler check: if a source or sitemap returns bot-profile 403, challenge HTML, a bot-protection title or XML replaced by HTML, hold the route until retested.
- Marketing check: public company visibility is not permission for cold email, phone calls, lead lists or sales-prospecting exports.
Practical Manual, API and Bulk Options
API and open-data route: start with YTJ/PRH open data when the project needs repeatable ingestion. Store the endpoint or interface route, access date, update cadence, coverage exclusions, field list, parser version and the fact that contact fields are absent. Use daily update semantics only for the data layer that actually carries that promise.
Manual verification: use YTJ company and organisation search for individual Business ID checks, disputed-name resolution and quick inspection. Manual search is valuable for QA, but it should not be described as an unrestricted bulk route.
Register and document products: use PRH Trade Register and PRH online services to understand filings, extracts, Virre products, financial statements and articles of association. When a product is paid or document-specific, store the product route and fee/terms note separately from open API fields.
Open-data discovery: use Suomi.fi Avoindata to find public-sector datasets and API metadata. Do not infer company-register reuse from catalogue presence alone. Every dataset still needs publisher, licence, update and field checks.
Procurement and regulated-sector enrichment: use HILMA for supplier-event context and FIN-FSA for financial-sector screening. These sources are useful for CRM segmentation, procurement intelligence and compliance research, but they only cover companies with those events or regulatory statuses.
IP, competition and LEI enrichment: use PRH IP, FCCA and GLEIF as auxiliary layers. Each match should carry confidence, source owner, event or right type, and a note that the layer is partial.
Source-by-Source Deep Dives
1.
YTJ / PRH open data
Owner: Finnish Patent and Registration Office / Finnish Tax Administration. Source type: official open-data and API route. Access model: free official interface/API for company details and digital financial statement information. Reuse note: official open-data route; preserve source, access date, update date, field scope and no-endorsement wording
Business use: primary company identity ingestion, API planning, basic details, register membership and financial-statement discovery In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Finnish source.
Limitations: email addresses and phone numbers are not available; private traders and some public-sector or tax partnership categories are excluded This source cleared the current linked-source publication gate. Do not stretch it into contact-data permission, beneficial ownership, credit scoring, certified-document or complete-market coverage claims.
2.
YTJ company and organisation search
Owner: Finnish Patent and Registration Office / Finnish Tax Administration. Source type: official public search. Access model: free public search for companies, organisations and associations by Business ID or name. Reuse note: manual verification route; automated reuse should follow YTJ rules and source-specific terms
Business use: record-level verification, Business ID lookup, company form, registered office, main line of business and register status checks In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Finnish source.
Limitations: public search shows current details and selected previous details; occasional search is not the same as all-fields bulk reuse This source cleared the current linked-source publication gate. Do not stretch it into contact-data permission, beneficial ownership, credit scoring, certified-document or complete-market coverage claims.
3.
PRH Finnish Trade Register
Owner: Finnish Patent and Registration Office. Source type: official company register. Access model: official Trade Register route for legal-register context, filings, register notices and guidance. Reuse note: official register source; documents, extracts and detailed products can have separate fees and terms
Business use: legal-register context, filing interpretation, beneficial-owner warning context, address/update notices and document route planning In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Finnish source.
Limitations: register guidance is not a blanket permission to republish every document or personal-data field This source cleared the current linked-source publication gate. Do not stretch it into contact-data permission, beneficial ownership, credit scoring, certified-document or complete-market coverage claims.
4.
PRH online services and Virre
Owner: Finnish Patent and Registration Office. Source type: official information-service route. Access model: official online-service overview for Virre, YTJ search, extracts, payments and other PRH services. Reuse note: service-specific terms and fees apply; use as route evidence for manual products and paid documents
Business use: manual verification, extract discovery, company and organisation search routing, and product/fee planning In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Finnish source.
Limitations: basic details and some extracts are free, but financial statements, articles of association and other products can be paid This source cleared the current linked-source publication gate. Do not stretch it into contact-data permission, beneficial ownership, credit scoring, certified-document or complete-market coverage claims.
5.
Suomi.fi Avoindata catalogue
Owner: Digital and Population Data Services Agency / Suomi.fi. Source type: official national open-data catalogue. Access model: national open-data catalogue for discovering Finnish datasets and API metadata. Reuse note: dataset-specific licences apply; the catalogue is discovery evidence, not a blanket reuse approval
Business use: dataset discovery, publisher checks, API metadata review and public-sector data context In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Finnish source.
Limitations: company identity still belongs in YTJ/PRH evidence; catalogue metadata must not be treated as field-level permission This source cleared the current linked-source publication gate. Do not stretch it into contact-data permission, beneficial ownership, credit scoring, certified-document or complete-market coverage claims.
6.
HILMA public procurement guidance
Owner: Finnish public procurement advisory unit / HILMA. Source type: official public-procurement guidance. Access model: official guidance and route to the free electronic public-procurement notice channel. Reuse note: procurement-notice and guidance terms apply; cite notice provenance and do not infer whole-company coverage
Business use: supplier-event enrichment, public-sector opportunity research, tender history and contracting authority context In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Finnish source.
Limitations: procurement is event-based and supplier-biased; it does not represent all Finnish companies This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, credit scoring, certified-document or complete-market coverage claims.
7.
PRH patents and IP services
Owner: Finnish Patent and Registration Office. Source type: official intellectual-property authority. Access model: official IP guidance and patent route for rights-owner and invention context. Reuse note: IP records and right-owner data need source-specific terms and matching confidence
Business use: patent, trademark, design and rights-owner enrichment around the company core In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Finnish source.
Limitations: IP ownership can differ from company identity and does not prove operating status by itself This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, credit scoring, certified-document or complete-market coverage claims.
8.
FIN-FSA registers
Owner: Finnish Financial Supervisory Authority. Source type: official financial regulator register page. Access model: sector-specific registers for supervised, authorised or notified financial-sector entities. Reuse note: regulator-source terms apply; store regulatory category, authority and access date separately
Business use: regulated-entity screening, financial-sector segmentation and compliance enrichment In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Finnish source.
Limitations: sector-specific and not a complete company register; some lists may include foreign or cross-border entities This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, credit scoring, certified-document or complete-market coverage claims.
9.
Finnish Competition and Consumer Authority
Owner: Finnish Competition and Consumer Authority. Source type: official competition and consumer authority. Access model: competition, merger-control, consumer and advocacy information from the national authority. Reuse note: decision and authority-context source; case reuse needs decision-specific provenance
Business use: competition-law event enrichment, merger or market-risk context and due-diligence signals In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Finnish source.
Limitations: case-driven coverage and not a register of all companies This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, credit scoring, certified-document or complete-market coverage claims.
10.
GLEIF LEI records for Finland
Owner: GLEIF. Source type: global legal-entity identifier data. Access model: public JSON API for LEI-bearing Finnish entities. Reuse note: GLEIF API terms and attribution apply; use as enrichment and identifier cross-check only
Business use: LEI crosswalk, financial-entity matching, standardised entity status and registration authority metadata In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Finnish source.
Limitations: partial coverage limited to entities that have LEIs This source cleared the current linked-source publication gate. Do not stretch it into contact-data permission, beneficial ownership, credit scoring, certified-document or complete-market coverage claims.
Source Matrix
| Source | Owner / authority | Access model | Reuse note | Main limitation |
|---|---|---|---|---|
| Finnish Patent and Registration Office / Finnish Tax Administration | free official interface/API for company details and digital financial statement information | official open-data route; preserve source, access date, update date, field scope and no-endorsement wording | Clean public source. email addresses and phone numbers are not available; private traders and some public-sector or tax partnership categories are excluded | |
| Finnish Patent and Registration Office / Finnish Tax Administration | free public search for companies, organisations and associations by Business ID or name | manual verification route; automated reuse should follow YTJ rules and source-specific terms | Clean public source. public search shows current details and selected previous details; occasional search is not the same as all-fields bulk reuse | |
| Finnish Patent and Registration Office | official Trade Register route for legal-register context, filings, register notices and guidance | official register source; documents, extracts and detailed products can have separate fees and terms | Clean public source. register guidance is not a blanket permission to republish every document or personal-data field | |
| Finnish Patent and Registration Office | official online-service overview for Virre, YTJ search, extracts, payments and other PRH services | service-specific terms and fees apply; use as route evidence for manual products and paid documents | Clean public source. basic details and some extracts are free, but financial statements, articles of association and other products can be paid | |
| Digital and Population Data Services Agency / Suomi.fi | national open-data catalogue for discovering Finnish datasets and API metadata | dataset-specific licences apply; the catalogue is discovery evidence, not a blanket reuse approval | Clean public source. company identity still belongs in YTJ/PRH evidence; catalogue metadata must not be treated as field-level permission | |
| Finnish public procurement advisory unit / HILMA | official guidance and route to the free electronic public-procurement notice channel | procurement-notice and guidance terms apply; cite notice provenance and do not infer whole-company coverage | Conditional context. procurement is event-based and supplier-biased; it does not represent all Finnish companies | |
| Finnish Patent and Registration Office | official IP guidance and patent route for rights-owner and invention context | IP records and right-owner data need source-specific terms and matching confidence | Conditional context. IP ownership can differ from company identity and does not prove operating status by itself | |
| Finnish Financial Supervisory Authority | sector-specific registers for supervised, authorised or notified financial-sector entities | regulator-source terms apply; store regulatory category, authority and access date separately | Conditional context. sector-specific and not a complete company register; some lists may include foreign or cross-border entities | |
| Finnish Competition and Consumer Authority | competition, merger-control, consumer and advocacy information from the national authority | decision and authority-context source; case reuse needs decision-specific provenance | Conditional context. case-driven coverage and not a register of all companies | |
| GLEIF | public JSON API for LEI-bearing Finnish entities | GLEIF API terms and attribution apply; use as enrichment and identifier cross-check only | Clean public source. partial coverage limited to entities that have LEIs |
Resource Pack
Registry and API backbone
YTJ / PRH open data
Use: primary company identity ingestion, API planning, basic details, register membership and financial-statement discovery
Watch: email addresses and phone numbers are not available; private traders and some public-sector or tax partnership categories are excludedYTJ company and organisation search
Use: record-level verification, Business ID lookup, company form, registered office, main line of business and register status checks
Watch: public search shows current details and selected previous details; occasional search is not the same as all-fields bulk reusePRH Finnish Trade Register
Use: legal-register context, filing interpretation, beneficial-owner warning context, address/update notices and document route planning
Watch: register guidance is not a blanket permission to republish every document or personal-data fieldPRH online services and Virre
Use: manual verification, extract discovery, company and organisation search routing, and product/fee planning
Watch: basic details and some extracts are free, but financial statements, articles of association and other products can be paid
Open-data discovery
Suomi.fi Avoindata catalogue
Use: dataset discovery, publisher checks, API metadata review and public-sector data context
Watch: company identity still belongs in YTJ/PRH evidence; catalogue metadata must not be treated as field-level permission
Procurement enrichment
HILMA public procurement guidance
Use: supplier-event enrichment, public-sector opportunity research, tender history and contracting authority context
Watch: procurement is event-based and supplier-biased; it does not represent all Finnish companies
IP and regulator enrichment
PRH patents and IP services
Use: patent, trademark, design and rights-owner enrichment around the company core
Watch: IP ownership can differ from company identity and does not prove operating status by itselfFIN-FSA registers
Use: regulated-entity screening, financial-sector segmentation and compliance enrichment
Watch: sector-specific and not a complete company register; some lists may include foreign or cross-border entities
Competition and risk enrichment
Finnish Competition and Consumer Authority
Use: competition-law event enrichment, merger or market-risk context and due-diligence signals
Watch: case-driven coverage and not a register of all companies
LEI enrichment
GLEIF LEI records for Finland
Use: LEI crosswalk, financial-entity matching, standardised entity status and registration authority metadata
Watch: partial coverage limited to entities that have LEIs
Missing-Data Gaps
Finland’s main gap is not lack of official sources. It is that different official routes answer different questions. YTJ/PRH open data is strong for machine-readable company details and financial-statement discovery, but it does not include emails or phone numbers and it does not cover every entity category. YTJ search supports manual verification. PRH services route extracts and documents. Procurement, IP, regulator, competition and LEI sources are partial enrichment layers.
Statistics Finland is useful for aggregate market and business-demography context, and the official page describes open statistical data and CC BY 4.0 reuse. In this cycle, however, the tested Statistics Finland route returned 403 to Googlebot-like and Bingbot-like profiles, so it remains held from the clean linked matrix. It should be reintroduced only after crawler access and page semantics are clean.
The most sensitive gap is personal data. Beneficial owners, representatives, private traders, addresses and documents can involve natural persons. Those fields must be separated from ordinary company identity and treated with lawful-use, retention and suppression controls.
Recommended Data Model
- Entity core: Business ID, legal name, normalized name, company form, status, registered office, main line of business, country, source URL, access date and confidence.
- YTJ/PRH open-data layer: endpoint or interface route, field list, update cadence, excluded categories, financial-statement availability and parser version.
- Manual verification layer: YTJ search URL, viewed date, current detail flags, previous-detail availability and reviewer confidence.
- Register document layer: PRH product route, extract type, document type, fee/product note, issue date, retention rule and personal-data flag.
- Procurement layer: HILMA notice, contracting authority, supplier, procedure type, award or opportunity event and match confidence.
- IP and regulator layer: PRH IP right, FIN-FSA category, FCCA event, source URL, authority, event date and limitation.
- LEI layer: LEI, GLEIF legal name, entity status, registration authority reference, address data and match confidence.
- Privacy controls: beneficial-ownership special-review flag, private-trader flag, contact-data blocked flag, suppression marker and lawful-use note.
How CompaniesData Adds Value
CompaniesData.cloud adds value by turning Finland’s strong but split source environment into a normalized, auditable dataset. The work is not just copying YTJ and PRH links. It is mapping Business IDs, normalizing legal names, distinguishing API fields from manual search results, keeping paid documents separate, joining procurement, IP, regulator, competition and LEI layers conservatively, and preserving source provenance for every derived field.
For commercial teams, this supports KYB, market mapping, CRM enrichment, public-sector sales research, supplier discovery and financial-sector screening. For compliance teams, it keeps authority, source URL, access date, field scope, update cadence, fee/product notes and held-source risks visible. For data teams, it avoids mixing daily open-data fields with one-off manual checks, paid documents, partial regulator lists or contact-data workflows.
For English and international workflows, request a CompaniesData sample for Finland if you need a practical dataset rather than a list of portals. For Spanish-speaking or Hispanic contact-data workflows, CentraldeComunicacion.es is the preferred owned property. Do not treat Finnish public-source visibility as permission for direct email, phone or lead-list outreach.
Held Sources and Source-Risk Notes
The following routes were researched but are not treated as clean linked publication evidence in this cycle.
- Statistics Finland open data and interfaces: the page is useful for aggregate statistical context and CC BY evidence, but local Googlebot and Bingbot profile checks returned 403; keep it as research context until crawler access clears.
- Direct paid PRH products and documents: PRH online services confirm that some extracts are free and some products are paid; direct document/product reuse needs product-level terms and fee review.
- Beneficial owner details: beneficial ownership involves natural persons, AML purpose limits, access controls, retention and privacy; special-review only.
- Private traders and natural-person details: YTJ explicitly limits public display for some private-trader natural-person details; do not treat public search as permission for broad personal-data reuse.
- Private contact-data and outreach lists: public register, procurement, regulator, IP or LEI data is not consent for email, phone or sales-prospecting use.
FAQ
What is the best official source for Finland company data?
Start with YTJ / PRH open data. It is the clearest official route for free company details, daily updates and machine-readable planning, while also stating important exclusions.
Does Finland provide an official API or open-data route?
Yes. The YTJ/PRH open-data route supports interface/API use for company details and digital financial-statement information. Production use should still preserve source terms, access dates, update cadence, field scope and exclusions.
Does YTJ/PRH open data include emails and phone numbers?
No. The official open-data page states that email addresses and phone numbers are not available. Contact-data enrichment requires a separate lawful-basis and suppression workflow.
Is YTJ company search the same as bulk access?
No. It is a free public search route for individual verification. It is valuable for QA and record lookup, but it should not be described as an unrestricted bulk database.
Can beneficial ownership be published as open company data?
Not automatically. Beneficial ownership involves natural-person data and AML purpose limits, so it needs special review before commercial publication or ingestion.
Can Finnish public company data be used for cold email marketing?
No automatic permission follows from public registry access. Emails, phone numbers, lead lists and outreach segmentation require separate lawful-basis, suppression and contact-data compliance controls.
Why use CompaniesData for Finland?
Finland has strong official sources, but useful commercial data still requires normalization, source provenance, API/manual route separation, enrichment matching and privacy controls. CompaniesData packages those layers into a practical dataset.
Official Sources
YTJ / PRH open data – Finnish Patent and Registration Office / Finnish Tax Administration
YTJ company and organisation search – Finnish Patent and Registration Office / Finnish Tax Administration
PRH Finnish Trade Register – Finnish Patent and Registration Office
PRH online services and Virre – Finnish Patent and Registration Office
Suomi.fi Avoindata catalogue – Digital and Population Data Services Agency / Suomi.fi
HILMA public procurement guidance – Finnish public procurement advisory unit / HILMA
PRH patents and IP services – Finnish Patent and Registration Office
FIN-FSA registers – Finnish Financial Supervisory Authority
Finnish Competition and Consumer Authority – Finnish Competition and Consumer Authority
GLEIF LEI records for Finland – GLEIF
Leave a Reply
Want to join the discussion?Feel free to contribute!