Control change monitoring
PSC Change Monitoring: How to Track Persons with Significant Control After Onboarding
A practical guide to PSC change monitoring after onboarding, including Companies House PSC updates, control changes, identity-verification signals, source evidence, and review workflows.
Short answer
PSC change monitoring means watching official registry data for changes to the people or legal entities that own or control a company. The useful alert is not "ownership risk." It is a source-backed signal showing what changed, when the registry processed it, and which approved relationship should be reviewed.
A company can pass KYB, supplier onboarding, merchant underwriting, or vendor approval with one set of control details, then later file a change to the people or entities that control it. For teams that manage known company relationships, that change can matter even when the company name, status, and registered address stay the same.
This guide focuses on official registry monitoring after onboarding. It does not replace full beneficial ownership investigation, sanctions screening, adverse media, enhanced due diligence, or private ownership-chain analysis.
Why PSC change monitoring matters after onboarding
A PSC change can alter who controls the company your team approved. A new person may cross a control threshold. A corporate PSC may replace an individual PSC. A nature of control may change from one voting-right band to another. A company may file a statement saying it has no registrable PSC, or that its PSC information has not been confirmed.
The Companies House register changes at large scale. In its 2024 to 2025 annual report, Companies House reported 14.7 million filings accepted and 16.3 billion register accesses for the year to 31 March 2025. Control data is one part of that broader public-record activity.
The compliance context is also becoming more dynamic. Companies House confirmed that, from 18 November 2025, identity verification became compulsory for new directors and PSCs, with existing PSCs given role-specific verification windows during the transition.
What is a person with significant control?
In the UK, a person with significant control is someone who owns or controls a company under the Companies House PSC rules. The official guidance says PSC details include the date they became a PSC and all natures of control that apply.
Companies House says share and voting-right levels are reported in bands: over 25% up to 50%, more than 50% and less than 75%, and 75% or more. Its statutory guidance explains that the first three PSC conditions cover more than 25% of shares, more than 25% of voting rights, or the right to appoint or remove a majority of the board.
PSC monitoring vs beneficial ownership monitoring
PSC change monitoring and beneficial ownership monitoring are related, but they are not the same product promise. PSC monitoring watches the official PSC records and statements exposed by a registry. Beneficial ownership monitoring may need broader ownership-chain analysis, private documents, regulated access, and customer due diligence.
| Question | PSC change monitoring | Full UBO monitoring |
|---|---|---|
| Main source | Official PSC records, statements, streams, and filings | Registry data plus ownership documents, customer data, and due-diligence sources |
| Best for | Detecting source-backed control changes for known companies | Understanding ultimate ownership across complex structures |
| Typical output | Review trigger with source evidence | Ownership assessment or refreshed customer risk file |
| Main limit | Only sees what the registry exposes | May require data not available in a public register |
FATF's beneficial ownership guidance says accurate and up-to-date basic and beneficial ownership information should be available to competent authorities in a timely way. That policy goal supports monitoring, but it does not mean every country exposes the same public data or API surface.
Which PSC changes should teams monitor?
The strongest PSC alerts are specific. They tell a reviewer which control fact changed instead of collapsing everything into a generic ownership-risk label.
New PSC added
A new PSC can indicate that a person or legal entity has crossed a control threshold, gained appointment rights, or otherwise become registrable.
PSC ceased
A ceased PSC may show that a previous controller no longer meets the source's control conditions, or that control has moved to a different person or corporate entity.
Nature of control changed
Nature-of-control changes include share bands, voting-right bands, appointment rights, and significant influence or control. Monitoring should preserve the source wording and previous and current values when available.
PSC statement or exemption changed
Statements such as no registrable PSC, unconfirmed PSC details, and restriction-related notices are official control-record signals. Exemptions also matter because they explain why some companies do not follow the same PSC reporting pattern as private companies.
Identity-verification details changed
Companies House PSC resources now include optional identity-verification fields, such as verification statement dates and due dates. Treat these as source facts, not as a substitute for your own KYB or AML policy.
Where official PSC monitoring data comes from
In the UK, Companies House exposes PSC-related data through several official channels. The Public Data API includes an endpoint to list a company's persons with significant control, excluding statements.
The Companies House streaming API includes a PSC stream and a PSC statements stream. Its overview says stream events wrap the same resources as on-demand API requests with metadata such as changed fields, published time, timepoint, and event type.
Companies House also publishes a PSC data product, described as a JSON snapshot containing the full list of PSCs provided to Companies House. Snapshots can establish a baseline, while streams or polling keep watched records current.
Outside the UK, beneficial-control access varies by country. A Europe-first monitoring workflow should state coverage by country and avoid promising full UBO visibility where the official source does not expose it.
What a useful PSC alert should include
A useful PSC alert should let the reviewer verify the source event and decide whether an approved relationship needs a refresh. Useful fields include:
- internal customer, merchant, supplier, or vendor ID
- official company name, country, and company ID
- official source name and source URL
- event type, such as new PSC, ceased PSC, changed control nature, PSC statement, exemption change, or identity detail update
- PSC name or corporate entity name when public
- PSC kind, such as individual or corporate entity
- notified date, processed date, and detected date
- changed fields when the source provides them
- previous and current control values when available
- source resource URL, filing URL, or statement URL
- plain-English summary of what changed
If the source only proves that a statement was filed, say that. Do not infer ultimate ownership, sanctions risk, or customer risk unless separate evidence supports it.
How to operationalize PSC change monitoring
The simplest workflow starts with companies your team already knows, not with a broad search across every company in a registry.
- Upload a portfolio list or send company records through an API.
- Resolve each company to the correct official registry record.
- Confirm uncertain name-only matches before monitoring.
- Establish a current PSC baseline from the official source.
- Watch PSC, PSC statement, filing, and exemption data where the country source supports it.
- Normalize raw source changes into clear review triggers, deduplicate repeated events, and route material changes with source evidence attached.
Churnscan is built around this known-company workflow: resolve the company, confirm ambiguous matches, create a watch, poll official sources, and return matched signals with evidence. For the broader implementation pattern, see the company monitoring API guide.
Common mistakes
- Calling every PSC update a risk event: a registry change should trigger review, not an automatic customer decision.
- Confusing PSC monitoring with full UBO: public PSC data is useful evidence, but it may not show the full ownership chain.
- Losing the nature of control: keep the source's control category and share or voting-right band when it is available.
- Ignoring PSC statements: "no PSC" and "PSC not confirmed" statements can be important even when no named person is added.
- Dropping source evidence: every alert should preserve the official source, date, and resource URL needed for review.
Frequently asked questions
What is PSC change monitoring?
PSC change monitoring means tracking official registry updates about people or legal entities with significant control over a company, then routing additions, cessations, nature-of-control changes, statements, exemptions, and identity-verification updates for review.
Is PSC monitoring the same as full UBO monitoring?
No. PSC monitoring follows what an official registry exposes about significant control. Full UBO monitoring may require ownership-chain analysis, private documents, regulated data access, and customer due diligence beyond public registry alerts.
Which PSC changes should trigger review?
Useful review triggers include a new PSC, a ceased PSC, changed share or voting-right bands, changed right to appoint or remove directors, a new PSC statement, a PSC exemption change, and identity-verification dates or due dates where the source provides them.
Can Companies House data be used for PSC monitoring?
Yes. Companies House provides PSC data through the Public Data API, a PSC stream, a PSC statement stream, company exemption data, and a downloadable PSC data product. Teams still need to match companies, deduplicate events, and preserve source evidence.
Can PSC change monitoring start from a customer list?
Yes. A practical workflow can start from a merchant, borrower, supplier, vendor, or customer list, resolve each row to the official company record, confirm uncertain matches, and monitor PSC-related changes for those known companies.
Source trail
This article was written from current search results, official Companies House guidance and API documentation, FATF beneficial ownership guidance, and Churnscan product context. Useful source starting points:
- GOV.UK guidance on people with significant control
- GOV.UK statutory guidance on significant influence or control
- Companies House Public Data API PSC list reference
- Companies House streaming API overview
- Companies House PSC stream reference
- Companies House PSC statements stream reference
- Companies House PSC stream resource fields
- Companies House company exemptions stream fields
- Companies House data products guidance
- Companies House identity verification update
- GOV.UK identity verification rollout announcement
- Companies House annual report and accounts 2024 to 2025
- FATF guidance on transparency and beneficial ownership
Monitor official company control changes
Use Churnscan to upload a company list or connect by API, resolve each company to the official record, and monitor source-backed changes after onboarding.