Finland company monitoring
Finnish Company Register Monitoring: How to Track PRH Trade Register Changes After Onboarding
A practical guide to monitoring Finnish company register changes after onboarding, including YTJ lookup, PRH registered notices, alert-service limits, and source-backed review workflows.
Short answer
Finnish company register monitoring is the process of matching companies to their official Business IDs, watching PRH and YTJ records for changes, classifying those changes into useful alerts, and keeping source links so reviewers can verify the official record.
Finnish company register monitoring means tracking official PRH and YTJ company record changes after a Finnish business has already been approved, onboarded, or added to a portfolio. The practical goal is simple: keep a known company list current when a Business ID, company name, address, status, role, capital, or registered notice changes.
This is useful for Europe-first fintechs, KYB products, B2B platforms, merchant-risk teams, procurement teams, lenders, and supplier-risk teams that work with Finnish companies.
It is not a full KYB, AML, sanctions, credit-scoring, or beneficial ownership product. It is a narrower monitoring layer for official company registry changes.
Why this topic matters now
Finland has a large public company register, but the monitoring workflow is scattered across different services.
PRH reported that the Finnish Trade Register contained more than 720,000 businesses and organisations in January 2026, and that 41,031 new businesses were entered in the register during 2025. The same official statistics show 309,714 limited liability companies and 275,702 private traders in the register on 9 January 2026.
The data access picture is also mixed. The YTJ company search is free and can find basic details such as Business ID, register entries, company name, company form, registered office, business line, address, company situation, tax debt details, and EUID. PRH open data is also free and machine-readable, but PRH says it is updated once per day.
That creates a clear operational problem: official data is available, but teams still need a monitoring workflow that can resolve the right company, detect relevant changes, and turn raw PRH records into reviewable alerts.
What is Finnish company register monitoring?
Finnish company register monitoring is a workflow for watching official Finnish company records after the initial company check is complete.
A practical workflow looks like this:
- Start with a known company list from onboarding, underwriting, procurement, account management, or a merchant portfolio.
- Resolve each company to the right Finnish Business ID.
- Confirm uncertain matches before monitoring starts.
- Watch PRH and YTJ sources for registered changes.
- Classify raw changes into clear signal types.
- Attach the official source and dates.
- Route the alert into a review queue, API feed, or operational process.
For a broader cross-country version of this workflow, read the company monitoring API guide. For the risk-control framing after onboarding, read the post-onboarding KYB monitoring guide.
Which Finnish sources matter?
The main sources for Finnish company monitoring are YTJ, PRH open data, PRH registered notifications, Virre, and PRH alert services.
YTJ company and organisation search
YTJ is the Finnish Business Information System. Its public company and organisation search can be used to search companies, organisations, and associations by details such as Business ID. YTJ says the search is free and shows details that are in effect at the time of viewing.
For monitoring, YTJ is most useful for company resolution and current company profile context. It helps answer: "Which official Finnish company is this?"
Useful YTJ fields include:
- Business ID
- registered company name and other names
- company form
- registered office
- main line of business
- address details
- register entries
- company situation, such as bankruptcy, liquidation, or restructuring when present
- EUID for companies and branches that have one
PRH open data
PRH open data provides machine-readable data for applications and systems. PRH says the open data service is free, uses JSON, and is updated once per day.
For monitoring, the daily update cadence matters. It makes PRH open data a good fit for scheduled monitoring and backfill, but it should not be described as a real-time stream.
PRH registered notices API
The PRH registered notifications API is the most important official source for tracking Trade Register notices programmatically.
According to the official API description, the interface provides notification details registered at the Finnish Trade Register since 7 November 2014. It includes registration date, subject matter of register entries, and basic company details. The OpenAPI schema supports lookup by exact Business ID and search by criteria such as company name, Business ID, location, company form, registration date, record number, entry code, notice registration date, and notification type.
This is the source that turns monitoring from "check the company profile again" into "watch registered events tied to a Business ID."
Virre information service
Virre is useful for manual searches, notification lookup, and documents. PRH's price list says company search, notification search, financial statement search, online document search, and electronic Trade Register extracts are free of charge, while other document products may be paid.
For monitoring teams, Virre can support manual review and evidence checking. It is not a portfolio-monitoring workflow by itself.
PRH alert service
PRH also documents a Trade Register alert service. The service lets a customer monitor changes in specified businesses by giving PRH the Business IDs and selecting all changes or specific change types.
The alert-service document lists monitored change types such as company type, company name, auxiliary or parallel company name, capital value, line of business, organisation rules, financial statements submitted, financial period, company situation, roles, and notification pending. It also says the alert information is sent by email.
That can be useful, but email delivery is not the same as an API-first review workflow with normalized signals, deduplication, source links, and portfolio-level filtering.
What Finnish company changes should teams track?
The most useful Finnish company monitoring signals are official legal-entity changes that can affect an already approved company record.
Company status and situation changes
Status and situation changes help reviewers understand whether a Finnish company still matches the approved state.
Examples include:
- bankruptcy
- liquidation
- restructuring proceedings
- dissolution or termination
- Trade Register status changes
- Business ID status changes
These are often higher-priority signals because they can affect merchant risk, supplier risk, lending review, or account eligibility.
Registered notice activity
Registered notices show that something has been accepted into the Trade Register. The useful monitoring question is not only "was there a notice?" but "what kind of change does this notice represent?"
Examples include:
- a registered role change
- a company name change
- a capital-related change
- a financial statement registration
- a financial period change
- a merger or demerger-related registration
Role and governance changes
PRH has published guidance explaining that some changes to persons responsible for a company can be processed automatically from 3 January 2024. The covered roles include board members, managing directors, auditors, procuration holders, and people authorised to represent the company when the conditions are met.
For monitoring, this is a reminder that governance changes are operationally meaningful. A company can pass onboarding with one set of responsible people and later file a change that a reviewer may need to see.
Name, address, and identity changes
Name and address changes can break internal matching or make an approved record stale.
Useful changes include:
- company name
- auxiliary or parallel company name
- registered office
- street or postal address
- company form
- EUID or register-entry context when available
These changes are not automatically risky. They are useful because they tell the team that the official record no longer matches the earlier snapshot.
Capital and structure changes
Capital changes, company form changes, mergers, demergers, and related registered notices can matter for lenders, supplier-risk teams, and platforms that rely on legal-entity stability.
PRH's alert-service material explicitly lists change of capital value and organisation rules as possible monitored changes, and the registered notices API exposes entry codes that can be used to classify many legal changes.
Financial statement and financial period activity
Financial statements submitted and financial period changes are useful context, especially for supplier, lending, or customer-risk review. They are not the same as credit scoring, but they can tell a reviewer when the official file has changed.
PRH open data includes a separate digital financial statement information interface, but PRH notes that it only covers digital financial statements filed using IXBRL and that these represent about 5 percent of all financial statements. That limitation matters if you are trying to build a complete financial-statement monitoring product from open data alone.
Free search vs PRH alert service vs monitoring API
Finnish company monitoring can be approached in several ways. Each one solves a different part of the workflow.
| Option | What it does well | Where it falls short |
|---|---|---|
| YTJ and Virre manual search | Good for checking one company and reviewing official details | Manual, hard to scale, and not designed for portfolio alerts |
| PRH alert service | Can monitor specified Business IDs for all or selected changes | Email-first and not built as a normalized API feed |
| PRH open data and APIs | Machine-readable, official, and useful for application workflows | You still need matching, polling, classification, deduplication, and delivery |
| Company monitoring workflow | Turns official changes into reviewable alerts tied to known companies | Requires product work or a vendor to maintain the monitoring layer |
The practical question is not whether Finnish official data exists. It does. The question is whether your team wants to build and maintain the workflow around that data.
Why raw PRH data is not the whole job
Raw registry access gives you the ingredients, not the finished monitoring process.
If you are monitoring a Finnish company portfolio, you still need to solve:
- matching names to the correct Business IDs
- handling similar names and previous names
- deciding which changes are review-worthy
- translating entry codes into readable signal types
- detecting duplicates across repeated pulls
- storing detected dates, event dates, source URLs, and evidence
- replaying recent changes when a company is added
- routing alerts to the right team or system
This is why Finnish company register monitoring is different from Finnish company lookup. Lookup answers "what is the company record right now?" Monitoring answers "what changed after we started watching?"
A practical Finnish monitoring workflow
For most teams, the best workflow is simple and evidence-led.
- Collect company name, country, and any known Business ID from the customer, supplier, merchant, or borrower record.
- Resolve the company through YTJ or PRH open data.
- Show likely matches when the name is ambiguous.
- Confirm the Business ID before monitoring starts.
- Create a watch for the confirmed company.
- Pull registered notices by Business ID and date window.
- Pull current company profile details for context.
- Classify changes into signal groups such as risk, legal entity, governance, address, capital, or filing.
- Attach the PRH or YTJ source details to the alert.
- Send the alert to the reviewer, API consumer, or case-management flow.
The most important rule is to preserve the official source trail. A monitoring alert should tell the reviewer what changed and where to verify it.
What to look for in a Finnish company monitoring setup
Use these checks when comparing an internal build with a company monitoring API.
Business ID-first matching
Finnish monitoring should be anchored on the Business ID whenever possible. Name-only monitoring is weaker because companies can have similar names, auxiliary names, previous names, or spelling variants.
Clear source coverage
The system should explain which sources it uses: YTJ company data, PRH registered notices, Virre evidence, or another official path. It should also explain update timing, especially because PRH open data is updated once daily.
Readable alert types
A reviewer should not need to interpret raw entry codes before deciding what to do. The alert should say something like "company status update," "registered address change," "board change," "capital change," or "financial statement filed."
Evidence and dates
Every alert should include the Business ID, company name, country, source, event date or registration date, detected date, and source reference.
Backfill for new watches
If a Finnish company is added today, the workflow should be able to check whether relevant notices were registered recently. Without backfill, teams can miss changes that happened just before the watch was created.
Cross-country fit
If your portfolio includes the UK, Finland, and Norway, a Finland-only process may create another silo. A cross-country monitoring layer should normalize the country-specific source details into shared signal types while preserving the original evidence.
How Churnscan fits
Churnscan monitors official company changes after onboarding. For Finland, the product flow is built around a known company list or API request, company resolution, confirmed watches, source polling, normalized signals, and reviewable evidence.
Current workflow coverage includes the United Kingdom, Finland, and Norway. Churnscan focuses on official company registry changes after onboarding, not broad enrichment, prospecting, full KYB, AML screening, sanctions screening, UBO verification, or credit scoring.
For implementation details, read the company monitoring API guide. For UK-specific monitoring, read the Companies House monitoring guide. For payment teams, read the merchant risk monitoring guide.
FAQ
What is Finnish company register monitoring?
Finnish company register monitoring means tracking official PRH and YTJ company record changes after a company has already been approved or added to a portfolio.
What is the main company identifier in Finland?
The main identifier is the Finnish Business ID, also known as the Y-tunnus. Monitoring should use the Business ID whenever possible because names can be ambiguous or change over time.
Does PRH provide an API for company changes?
Yes. PRH open data includes a registered notifications API that can search notification details by Business ID and other criteria. It also includes YTJ company data for company search and profile context.
Is PRH open data real time?
No. PRH says its open data service is updated once per day. That makes it useful for scheduled monitoring, but it should not be described as a real-time stream.
Is the PRH alert service enough for portfolio monitoring?
It can help when you want email alerts for specified Business IDs. It is usually not enough for an API-first portfolio workflow because teams still need matching, normalized signal types, deduplication, source evidence, filtering, and integration with review systems.
Sources and further reading
- YTJ company and organisation search
- PRH open data service
- PRH open data information
- PRH registered notifications OpenAPI schema
- PRH YTJ OpenAPI schema
- PRH regular public notices
- PRH alert service agreement PDF
- PRH number of businesses in the Finnish Trade Register
- PRH 2025 Trade Register statistics announcement
- PRH automated decision-making for changes to persons responsible for a company
- PRH Trade Register processing times
- PRH Virre information service price list
Monitor Finnish company changes after onboarding
Use Churnscan to upload a company list or connect by API, confirm the right Business ID, create watches, and review source-backed PRH and YTJ changes.