Companies House: Directors ID verification – what should you do?

You may have seen recent emails from Companies House about new identity verification requirements for company directors and people with significant control (PSCs). If the content of the email has worried you — don’t panic. The ID verification is part of new legal changes coming in autumn 2025.
These emails are part of a planned and important update to how company directors and (PSCs) are registered — and the goal is to improve security, transparency, and trust in the UK’s business environment. Once the rules take effect, you won’t be able to file key documents — like your Confirmation Statement — if you haven’t completed identity verification.
While mandatory verification doesn’t come into force until the autumn (the exact date is still unknown), you can voluntarily verify your identity now in readiness. We would encourage clients to complete their verification at the earliest opportunity, where possible, to avoid any last-minute stress or inconvenience.
Your Personal Code
Once verified, you’ll get a personal code. Keep this safe (and let us have it), as you’ll use this code to link your identity to all company roles you hold.
There are three main ways to verify your identity:
-
-
Online via GOV.UK One Login
Quick and convenient — if you have the right ID (like a passport or driving licence). https://www.gov.uk/guidance/verify-your-identity-for-companies-house
-
-
-
In person at selected UK Post Offices
Only available if you live in the UK — check eligibility via the GOV.UK verification tool first.
-
-
-
Through an Authorised Corporate Service Provider (ACSP)
This could be your accountant or solicitor.
-
We’re Here To Help
Whitings LLP are registered as an ACSP and plan to be able to assist you with the Companies House ID verification process once it becomes mandatory. If you have any queries or concerns, please do not hesitate to get in touch with you usual Whitings LLP contact or your local Whitings LLP Office today.
Disclaimer - All information in this post was correct at time of writing.