If you search for Companies House identity verification deadline, you usually land on rule summaries. What firms actually need in practice is a cleaner answer to a harder question: which role has which date, where can the same person still have two obligations, and how does the team track that without rebuilding the same spreadsheet every week?
This guide is for that deadline-specific question. If you also need the broader operating checklist after this, use the Companies House Verification Tracker Checklist for 2026.
Why there is no single Companies House identity verification deadline
For a client portfolio, deadline is really shorthand for several rule paths. The practical mistake is to force every role into one date column and hope the exceptions sort themselves out later.
Directors usually track to the next confirmation statement due date That is the practical deadline most firms need in front of the team every day. Keep the next made-up date visible too, because related PSC timing can depend on it.
A PSC who is also a director needs a separate PSC deadline The working window starts the day after the confirmation statement date and lasts 14 calendar days. Filing the confirmation statement early does not move that PSC window.
A PSC who is not also a director follows a birth-month window The practical window is the first 14 days of the PSC's birth month. That should not be merged into the same rule path as a director obligation.
A new PSC role from 18 November 2025 onward needs its own countdown Where the source record supports it, track the first 14 days from the PSC role start date as a separate new-role window.
Director deadline: use the next confirmation statement due date as the operating date
For directors, the practical deadline most firms need to manage is the next confirmation statement due date. That is the date the team usually works back from when deciding who needs follow-up first.
The operating mistake is not usually misunderstanding the rule in theory. It is losing the date across a wider client book, then discovering the gap only when filing work is about to happen.
PSC deadline: the window depends on which PSC case you are looking at
PSC timing is where the portfolio usually stops fitting into a single spreadsheet column. The useful operational distinction is whether the PSC is also a director, whether the PSC is director-independent, or whether a new PSC role has just started.
That is why PSC verification deadline is not a single answer. It is a set of deadline shapes that need separate tracking.
If you want the PSC-only breakdown without the wider director framing, use PSC Verification Requirements 2026 for Small UK Firms.
How to track directors and PSCs together without mixing the deadlines up
The safest pattern is to keep the role-level deadline logic explicit. That means separate obligations, visible rule paths, and a live workflow field set around each open item.
Keep the company, role, and rule path on the same row A workable tracker shows whether the open item is a director obligation, a PSC birth-month window, a PSC-after-confirmation-statement window, or a new-role window.
Store the next confirmation statement due date and made-up date Without those dates, the team cannot manage director work or the linked PSC timing accurately.
Keep owner, blocker, and next step visible Deadline tracking breaks down when the date lives in one file and the actual follow-up lives in someone else's inbox.
Do not auto-complete a role from assumption If the team expects work to be complete, that is still not the same thing as an explicit completion state on the obligation itself.
Surface messy or unsupported records for review Protected-information cases, corporate PSCs, and incomplete source data should become an exception queue rather than disappearing from the portfolio view.
Where small firms usually slip on deadline tracking
One person, one row That shortcut hides the fact that the same person can carry both a director deadline and a PSC deadline at the same company.
Early filing assumptions Teams often assume a filed confirmation statement clears the PSC work too. The linked PSC window still needs its own tracking.
One generic deadline column PSC birth-month windows, PSC new-role windows, and director deadlines should not be collapsed into one vague date field.
No daily review layer A monthly spreadsheet pass is too late once new windows, blockers, and client follow-up are moving every day.
No proof of what was reviewed If a manager or client asks what was in scope, the answer should come from a reusable artifact, not a rebuilt email summary.
If the team also needs the broader portfolio checklist for owners, blockers, daily review, and proof, go straight to the Companies House Verification Tracker Checklist for 2026.
Common questions
Is there one Companies House identity verification deadline in 2026?
No. In practical workflow terms, firms usually need separate deadline logic for directors, PSCs who are also directors, PSCs who are not directors, and new PSC roles where relevant. The rule path depends on the role.
Do directors and PSCs share the same deadline?
Not always. A person can be both a director and a PSC at the same company, but the tracker should still show separate obligations when the rule paths differ.
Does filing the confirmation statement early move the PSC deadline?
Operationally, no. For a PSC who is also a director, the useful working assumption is still that the PSC window starts the day after the confirmation statement date and lasts 14 calendar days.
Can Entity Watch verify identities or submit codes to Companies House?
No. Entity Watch is not an identity verification service, an ACSP registration tool, or a filing agent. It is a workflow and alerts layer for tracked companies, role-level obligations, owners, blockers, and proof.