If you search for PSC verification requirements 2026, most pages stop at the rule summary. The operating problem starts one layer later: which PSC path applies, which window is open, when does the same person still have a separate director obligation, and how does the team keep that visible across a live client portfolio?
This guide is for that narrower PSC question. If you need the broader deadline framing as well, use Companies House Identity Verification Deadline for Directors and PSCs and then come back here for the PSC-specific detail.
Why PSC verification work gets messy faster than firms expect
PSC work usually sits inside the same team queue as director follow-up, confirmation statement timing, and client chasing. That is why PSC requirements tend to break spreadsheets first: the rule paths differ, but the team is still trying to manage them inside one operational list.
The three PSC paths a real tracker needs to separate
PSC after confirmation statement If the PSC is also a director, the useful working window starts the day after the confirmation statement date and lasts 14 calendar days. Filing early does not move that window.
PSC birth-month window If the PSC is not also a director, the practical window is the first 14 days of the PSC's birth month. That needs its own explicit rule path in the tracker.
New PSC role window For PSC roles added on or after 18 November 2025, track the first 14 days from the role start date where the source record supports that timing.
The same person can still have two obligations
One of the easiest mistakes is treating a person as the unit of work instead of treating the obligation as the unit of work. If someone is both a director and a PSC at the same company, the PSC requirement should not disappear just because the name is already present in the director workflow.
If you need the wider explanation of how those deadlines sit together, use Companies House Identity Verification Deadline for Directors and PSCs.
What a PSC tracker needs to store to be useful
PSC role type or rule path The tracker should show whether the row is post-confirmation-statement, birth-month, or new-role timing instead of using one generic PSC deadline field.
Confirmation statement dates These are still needed for PSCs who are also directors, because the related PSC window depends on them.
Role start date for new PSCs Without a visible role start date, the team cannot work the new-role window confidently.
Owner, blocker, and explicit completion state PSC work becomes guesswork when nobody owns it, blockers live elsewhere, or completion is implied rather than recorded.
Exception flag for unsupported records Messy real-world cases should be surfaced as review work rather than disappearing from the firm’s portfolio view.
Exception handling matters as much as the rule itself
Corporate PSCs A live tracker should not pretend these behave like straightforward individual PSC cases. They need explicit review handling.
Protected-information records When public data is limited, the system should surface the gap instead of silently omitting the PSC from operational review.
Weak or incomplete source timing If the source record does not support clean automation, the tracker should push the case into an exception queue rather than inventing certainty.
People who are both directors and PSCs One person can still have two obligations at the same company. The PSC requirement should remain visible even when the same individual is already in the director workflow.
If you need the portfolio-wide operating checklist beyond PSC specifics, open Companies House Verification Tracker Checklist for 2026.
Common questions
What are the PSC verification requirements in 2026?
Operationally, firms usually need to track at least three PSC paths: PSC after confirmation statement, PSC birth-month window, and new PSC role timing where relevant. The important point is that these should not be collapsed into the same rule as director work.
Can the same person have both a PSC and director obligation?
Yes. If someone is both a director and a PSC at the same company, the tracker should still show separate obligations when the rule paths differ.
Do all PSCs use the same deadline?
No. Some PSC timing depends on confirmation statement dates, some depends on the PSC's birth month, and some depends on a new PSC role start date. A useful tracker needs to separate those cases clearly.
Can Entity Watch perform PSC identity verification or act as an ACSP?
No. Entity Watch is not an identity verification service, an ACSP registration tool, or a filing agent. It is a workflow layer that helps firms track due windows, owners, blockers, and proof across a portfolio.