Status change monitoring
Company Status Change Monitoring: How to Track Dissolved, Liquidation, and Bankruptcy Signals
A practical guide to company status change monitoring after onboarding, including active, dissolved, liquidation, insolvency, bankruptcy, and strike-off signals from official registry sources.
Short answer
Company status change monitoring means watching official company records for changes such as active to dissolved, liquidation, insolvency, bankruptcy, strike-off, or forced dissolution. It helps teams keep approved customers, merchants, suppliers, and vendors under review after the first onboarding check.
Company status change monitoring is the part of post-onboarding monitoring that asks a simple question: is the legal entity still in the state you approved?
For a fintech, KYB product, payment provider, lender, B2B marketplace, or procurement team, that question can matter long after onboarding. A company can be active when it is approved and later become dissolved, enter liquidation, appear in insolvency records, or receive another official registry status update.
Why status change monitoring matters after onboarding
Status changes are one of the cleanest official company signals because they come from public registries, filings, notices, or registry-maintained profile fields. They are not predictions. They are source-backed facts that can tell a review team what changed and where to verify it.
The need is current, not theoretical. Eurostat's quarterly business demography statistics track business registrations and bankruptcies across the EU and euro area. In the UK, the Insolvency Service publishes company insolvency statistics so teams can follow formal insolvency activity over time.
A status change does not answer every risk question by itself. It does give teams a practical trigger for reviewing a known business before the next scheduled KYB, supplier, or merchant review.
What is company status change monitoring?
Company status change monitoring means resolving a company to an official registry record, creating a watch for that record, and checking official sources for status-related changes over time.
The workflow is intentionally narrow. It does not replace sanctions screening, fraud monitoring, adverse media, transaction monitoring, credit scoring, or full third-party risk management. It keeps the official legal-entity status current between those other controls.
A useful monitoring flow should:
- Start from companies the team already knows, such as customers, merchants, suppliers, borrowers, or vendors.
- Resolve each company to the right official registry record.
- Ask for confirmation when a name-only match is weak.
- Create watches for the confirmed records.
- Poll source systems or source feeds for relevant changes.
- Return alerts with the source, date, company ID, and evidence attached.
For the API version of this flow, see the company monitoring API guide.
Which company status changes should teams track?
The highest-value status signals are the ones that can change how a team treats an already approved company. The exact names vary by country and registry, but the review logic is similar.
Active to dissolved
Dissolution means the company no longer exists as a live registered entity in the way it did at onboarding. For a customer, merchant, supplier, or borrower record, that should trigger a review of the relationship, open balances, contracts, and any downstream systems that still treat the company as active.
Liquidation
Liquidation is often a high-urgency signal because it can affect payment, service continuity, credit exposure, supplier replacement planning, or merchant settlement review. The alert should point to the filing, notice, or registry source rather than only saying "liquidation found."
Insolvency or bankruptcy
Insolvency and bankruptcy signals need careful handling because legal terms and processes differ by country. The practical monitoring rule is simple: when the official source shows an insolvency-related status, route it to the team that owns the relationship and attach the evidence.
Strike-off, forced dissolution, or removal
Some registries expose strike-off, forced dissolution, removed, deleted, or closure-style statuses. These are useful review triggers when a company record no longer matches the approved operating assumption.
Registry-specific status labels
Not every official source uses the same vocabulary. Companies House, PRH, Brreg, and other registries may expose status through profile fields, filings, notices, update feeds, or snapshot changes. Monitoring should normalize the source label into a readable alert while preserving the original evidence.
Where official status data comes from
The best status monitoring starts with official sources. The source does not need to look the same in every country, but it should be authoritative enough for a reviewer to trust.
Companies House in the UK
The Companies House company profile endpoint exposes profile fields such as company status. The filing history endpoint provides filing events that can include liquidation, insolvency, dissolution, officer, address, and capital categories depending on the company record.
Companies House also publishes a filing history stream for listening to filing activity. For API planning, the official rate-limit guide says requests are limited within a five-minute window, so polling design matters.
PRH and YTJ in Finland
Finland's official open-data path combines company lookup and registered notices. The PRH open data service describes public API access, and PRH's OpenAPI documentation includes the Finnish Business Information System company search and registered notices APIs.
For status monitoring, registered notices and company records can surface changes such as trade register status, liquidation, restructuring, bankruptcy, dissolution, or other entry-coded updates when present in the source data.
Brreg in Norway
Norway's Bronnoysund Register Centre publishes datasets and APIs for public registry data. The Enhetsregisteret API documentation covers entity data and update feeds that can support status and legal-entity monitoring.
In Norway, status monitoring may rely more on updated entity records and snapshot comparison than explicit filing events. That makes evidence and clear change summaries especially important.
Status monitoring vs periodic review
Periodic review is still useful, but it has an obvious blind spot: a company can change status the week after a review and stay stale until the next cycle. Status monitoring fills that gap.
| Question | Periodic review | Status monitoring |
|---|---|---|
| When does it happen? | On a fixed schedule | Between scheduled reviews |
| What does it catch? | Known checklist items | New official status changes |
| What source does it use? | Documents, questionnaires, and internal records | Official registry records, filings, notices, or feeds |
| What is the output? | A refreshed assessment | A source-backed review trigger |
| Best use | Broad reassessment | Keeping legal-entity status current |
The strongest operating model uses both. Periodic review handles broader reassessment. Status monitoring keeps the official company record from drifting between review dates.
How to operationalize company status monitoring
A good status monitoring workflow is practical before it is sophisticated. It should make it easy to start with a known company list and return alerts that a reviewer can trust.
Start with known companies
Start from a customer list, merchant portfolio, borrower book, supplier list, or vendor master export. The best input includes country and official company ID. If the team only has name and country, the workflow should resolve candidates and ask for confirmation when the match is uncertain.
Separate high-urgency and routine alerts
Not every status-related update deserves the same response. Liquidation, insolvency, bankruptcy, dissolution, and forced closure usually need faster review than routine registry maintenance.
A simple starting model:
- High urgency: liquidation, insolvency, bankruptcy, dissolution, strike-off, forced dissolution.
- Medium urgency: unexpected inactive status, suspended status, removed or deleted registry record.
- Lower urgency: routine profile refreshes or ambiguous status labels that need source inspection.
Keep evidence attached
Every alert should include enough source context for a reviewer to verify it without repeating the whole search.
Useful evidence includes:
- internal customer, merchant, supplier, or vendor ID
- official company name, country, and company ID
- previous status and new status when available
- source publication date and detected date
- source name, source URL, filing reference, or notice ID
- a short readable summary of what changed
Avoid automatic decisions without review
A status change should route work, not silently make every business decision. A dissolved supplier, insolvent borrower, or liquidating merchant may require different action depending on contracts, exposure, country, timing, and internal policy.
The monitoring system should make the source-backed fact visible and let the owning team decide what happens next.
Example workflow
Imagine a payment provider that monitors approved merchants in the UK, Finland, and Norway. The team wants to know when a merchant's official status changes after onboarding.
- Export the merchant portfolio with merchant ID, company name, country, and company number when available.
- Resolve each merchant to the official Companies House, PRH, YTJ, or Brreg record.
- Confirm rows where the name and country return multiple possible companies.
- Create watches for status and risk-change signals.
- Backfill recent changes so the team sees recent events before waiting for the next new filing or update.
- Route liquidation, insolvency, bankruptcy, and dissolution alerts to merchant-risk review with source evidence.
The same pattern works for supplier-risk, lending, KYB, and B2B platform teams. The list changes, but the core workflow is still resolve, confirm, watch, and review source-backed changes.
How Churnscan fits
Churnscan helps teams monitor official company registry changes after onboarding. For status monitoring, that means resolving known companies to official records, creating watches, polling supported sources, and returning source-backed changes for review.
The product is intentionally focused. It does not replace a full KYB, AML, sanctions, credit, fraud, or supplier-risk suite. It gives teams a clean feed of official company status and legal-entity changes that can support the workflows they already run.
To see the broader implementation shape, read the company monitoring API guide or start with the post-onboarding KYB monitoring guide.
FAQ
What is company status change monitoring?
Company status change monitoring means tracking official registry changes that show whether a company remains active, has entered liquidation, is insolvent or bankrupt, has been dissolved, or is otherwise no longer in the expected legal state.
Which company status changes should trigger review?
The most important review triggers are liquidation, insolvency, bankruptcy, dissolution, strike-off, forced dissolution, removed or deleted company records, and any registry status change that conflicts with the company's approved onboarding record.
Is status monitoring the same as KYB screening?
No. KYB screening usually checks a business at onboarding or review time. Status monitoring keeps watching the official company record between those reviews so teams can see source-backed changes when they happen.
Can company status monitoring start from a CSV list?
Yes. A practical workflow can start from an existing customer, merchant, supplier, or vendor CSV, resolve each row to the right official company record, confirm uncertain matches, and then create watches for status changes.
Does a status change automatically mean the company is risky?
No. A status change is a review trigger, not an automatic decision. The alert should include the source, date, official company ID, and evidence so a reviewer can decide what action is appropriate.