Coordinate identity verification when one person has PSC roles across several companies or LLPs or when several PSCs and overseas individuals require separate verification routes.

Determine the Appropriate Multi-Entity PSC Verification Route.

Whether one individual controls several companies or LLPs, one entity has several PSCs, or an individual is based overseas, our professional team helps you keep each person, entity, PSC role, verification route and applicable period separately identifiable while coordinating the relevant identity-verification and Personal Code steps.

Identify every affected person, company, LLP and PSC role before treating the matter as a coordinated verification requirement.

Keep each entity's PSC information, dates and filing responsibilities separate even where the same individual has control or PSC roles across several companies or LLPs.

Distinguish one person's identity verification from the separate code-use process for each applicable PSC or other role, so one completed check is not incorrectly treated as completing every entity's requirement.

Coordinate several PSCs individually, recognising that each person requires their own identity evidence, verification route, applicable period and Personal Code use.

Assess overseas individuals and their available identity and address evidence against the selected route rather than assuming that residence, nationality or document type automatically determines eligibility.

Record the applicable PSC period for each relevant person and entity rather than imposing one deadline across a group of companies, LLPs or individuals.

Coordinate suitable Companies House or Authorised Corporate Service Provider (ACSP) verification routes, with Coddan-supported individual verification available from £40 + VAT where the standard route is appropriate.

Recognise that the free Companies House verification route may remain available where the individual and evidence meet its requirements, so professional support is selected according to the circumstances rather than assumed to be mandatory.

Keep verification, Personal Code use and each company's or LLP's PSC notification separate so that completing one stage does not incorrectly represent another entity or role as completed.

Reduce avoidable administrative errors and back-and-forth by establishing the people, entities, roles, evidence, periods and appropriate verification route before the relevant PSC processes are progressed.

Determine the Appropriate PSC Route

Coddan CPM is a UK-based legal and corporate services firm and registered Authorised Corporate Service Provider (ACSP) providing professional support for multi-entity and overseas PSC identity-verification matters.
Call us on: 033 0808 0089 to discuss the appropriate people, entities, verification routes and separate PSC requirements for your circumstances.

Identity Verification for Multi-Company & Overseas PSCs: Centralised ACSP Services

Person-by-person PSC coordination

PSC Identity Verification for Several Companies, LLPs and Overseas Individuals

Where one person controls several entities, one entity has several PSCs or an individual is overseas, the work must be coordinated without combining separate responsibilities. Coddan can identify each person, entity, role, verification route, Personal Code use and applicable period before the relevant company or LLP completes its own PSC work.

One completed identity check does not satisfy another person’s requirement, and one PSC role connection does not connect the same individual with every company or LLP.

Map the affected people and entities

When coordinated PSC verification may help

The difficulty is often not the identity check alone. Different people may have different roles, evidence, verification routes and dates, while the same person may need to use one Personal Code through several separate processes.

One PSC, several entities

The individual controls several companies, LLPs or a mixture of both and must deal with each PSC role separately.

Several PSCs, one entity

Each individual needs their own identity-verification route, code and applicable PSC process.

Overseas individual

The person may need a route suited to their location, supported documents, address evidence and personal details.

Several affected roles

A PSC may also be a company director or LLP member, but each role has its own code-use process.

Keep every person, entity and role identifiable

Coddan’s coordination starts with a separate record for every affected combination. Information can be shared operationally where appropriate, but legal and Companies House steps must not be merged.

Individual

Full name, date of birth, residence, contact details and identity evidence.

Entity

The particular company or LLP and its own PSC information and dates.

PSC role

The underlying control condition and the separate PSC code connection.

Other role

Any directorship or LLP membership requiring its own process.

Verification route

Free Companies House verification or supported ACSP verification, where suitable.

Applicable period

The person-specific period for providing PSC verification details.

Entity action

The company’s or LLP’s separate notification, filing and record work.

Evidence status

What is supported, outstanding, inconsistent or route-dependent.

One individual with PSC roles in several entities

An individual normally completes identity verification once and retains one Companies House Personal Code. The same code can then be reused where required for relevant companies, LLPs and roles. Reuse of the code is not automatically another identity check or another paid verification service.

The reuse does not combine the roles. The individual must provide the code separately through every applicable PSC process, and separately again for an affected director or LLP-member role. Completing the requirement for one company does not connect the verified identity with another company or LLP.

One person → normally one Personal Code → separate use for every affected entity and role.

Several PSCs connected with one company or LLP

Each PSC is a separate individual. One person’s identity documents, completed check or Personal Code cannot be used for another person. The company or LLP may coordinate the overall work, but each PSC may use the verification route that is appropriate and available to them.

Separate identity checks

Evidence, liveness, personal details and the verification outcome belong to the individual concerned.

Different suitable routes

One PSC may use the free official route while another uses an ACSP. The identity standard is not reduced by the route selected.

Separate dates and actions

Each PSC’s applicable period and code submission must be tracked independently from the entity’s own notification work.

If an individual PSC is overseas

Residence or nationality outside the UK does not remove a current individual PSC’s identity-verification requirement. PSC status still depends on the applicable ownership or control conditions, not where the individual lives, works or holds documents.

Free official route

The free Companies House route may be available where the person and evidence meet its current requirements. GOV.UK currently lists a biometric passport from any country among the photo-ID options for online verification. Other routes and documents have their own conditions.

Supported ACSP route

An ACSP route may be appropriate where confirmed. Document support depends on current provider coverage, document type, issuing country, quality and consistency. Coddan checks this before presenting the route as suitable.

Names, addresses and scripts

Different spellings, transliteration, address formats or scripts may need comparison across the evidence, verification file and Companies House information. A difference should be examined rather than concealed.

Documentary caution: certification, translation, notarisation and an apostille are not universal identity-verification requirements. Where one of these steps is relevant, it serves a particular documentary purpose; it does not guarantee that Companies House, an ACSP or a provider will accept the underlying evidence.

Evidence must be checked for the selected route

Do not assume that a document is supported merely because it is official. Acceptance depends on the route, the document, its issuer, validity and the information it contains.

Identity document

Type, issuing country, expiry, readability and current route support.

Address evidence

Current residential address, acceptable evidence, issue date and consistency.

Personal information

Names, date of birth, address, email and telephone details must relate to the same individual.

Companies House record

The individual, entity and role must be matched without treating an inaccurate register entry as correct.

Why the PSC periods must be tracked separately

Every PSC has an applicable period for providing verification details, but the trigger depends on the person’s circumstances. A coordination schedule must therefore follow the individual and the relevant entity rather than impose one group deadline.

Situation	Current timing orientation	What remains separate
Became a PSC after 18 November 2025	The code may be provided when first added or within 14 days after being added.	The entity’s PSC notification and the individual’s code requirement.
Existing PSC who is also a director	The PSC period is linked to the company’s confirmation-statement date.	Director code use and PSC code use remain separate.
Existing PSC who is also an LLP member	The equivalent-role route is tied to the LLP’s applicable confirmation-statement timing.	LLP-member code use and PSC code use remain separate.
Existing PSC who holds neither office in that entity	The period falls in the first 14 days of the individual’s birth month.	Other entities may produce different dates for the same individual.

This is an orientation, not the complete timing service. The individual’s live Companies House position and dates should be checked. An early confirmation statement must not be assumed to move an existing PSC’s period.

Verification and the entity’s PSC work remain separate

PSC status arises from ownership or control. Identity verification confirms the individual’s identity within the Companies House framework; it does not determine whether the person is a PSC or which nature of control applies.

Each company or LLP must separately identify, confirm and notify its own PSC information and retain or maintain the appropriate supporting records. One entity cannot complete another entity’s obligation merely because the same individual controls both.

Coordinating proposed PSCs during company formation

A company-formation or registration application may involve several proposed PSCs, overseas controllers or one person connected with more than one new entity. Each proposed PSC must be identified correctly and their verification and Personal Code position coordinated with the application.

This page supplies person-centred verification support. The formation ecosystem retains responsibility for the complete incorporation application, company structure, constitutional information and registration outcome. Identity verification does not incorporate the company.

View Company Limited by Guarantee formation

How Coddan’s supported verification route works

Coddan CPM Limited is registered with Companies House as an Authorised Corporate Service Provider and is supervised by HMRC for anti-money-laundering purposes. Where the supported route is suitable, authorised and agreed, the following verification work applies to each individual.

1. Identify the case
Coddan identifies the individual, entity and affected PSC role.
2. Create the file
Coddan records the required name, date of birth, residential address, email address and telephone number.
3. Secure invitation
The individual receives a secure link by email or text message from Coddan’s identity-verification provider.
4. Complete evidence checks
The individual supplies supported identity and address evidence and completes the required selfie or liveness check.
5. Coddan review
Coddan reviews the result and any exceptional evidence rather than treating a technology result as the complete company event.
6. ACSP submission
Where satisfactory and authorised, Coddan manually submits the required verification information through its Companies House ACSP account.
7. Personal Code
Companies House sends the Personal Code to the individual using the supplied email address.
8. Separate role use
The code is then used through each applicable PSC or other role process; entity filings remain separate.

Coddan’s client onboarding and anti-money-laundering checks remain distinct from Companies House identity verification. Coddan and its provider do not issue the Personal Code or guarantee Companies House acceptance.

The free Companies House route remains available

An eligible individual may verify through the free official route. Professional ACSP support is optional, including for an overseas person where the official route and their evidence are suitable.

Several PSCs connected with the same entity can use different appropriate routes. A paid or priority Coddan service does not lower the identity standard, accelerate Companies House’s own decisions or guarantee acceptance.

Current, transitional and future position

Current-position wording checked against official guidance on 20 September 2026.

Current

Individual PSC requirements apply

Individual PSCs must verify and provide their code through the applicable PSC process. Overseas residence does not create an exemption, and every entity and role remains separate.

Transitional

Different PSCs have different dates

Mandatory identity verification began on 18 November 2025. Existing PSCs follow the period determined by their own role, registration history and relevant entity dates—not one universal deadline.

Future

Later categories remain reserved

Requirements for officers of corporate PSCs and general filers must not be treated as current until they are commenced and supported by operational guidance.

What Coddan can coordinate

Within the agreed scope, Coddan can create a person-and-entity schedule, identify appropriate verification routes, check apparent evidence and information differences, coordinate supported ACSP verification, identify separate Personal Code uses and direct the entity work to the appropriate company or LLP service.

People and entities

Separate every person, company, LLP, PSC role and additional office.

Routes and evidence

Identify the free or supported route and whether the proposed evidence appears suitable.

Dates and code use

Record each applicable PSC period and every separate role connection required.

Related entity work

Coordinate confirmed formation, notification or filing work only where authorised and separately agreed.

What information should you provide?

“Not known” is an acceptable answer. You do not need to determine the PSC status, timing route or documentary conclusion before Coddan reviews the position.

Every entity

Registered name, number, jurisdiction, entity type and relevant confirmation-statement date.

Every individual

Full name, date of birth, residential country, email, telephone number and affected roles.

PSC dates

When the person became registered or is proposed to be added, and any displayed PSC period.

Available evidence

Document type, issuing country, expiry, language or script and available address evidence.

Verification and code

Route used, result, whether a Personal Code was received and which roles have already been connected.

Differences or concerns

Name, birth date, address, email, register or control differences and any official message received.

This section does not transmit an enquiry. Use Coddan’s normal website contact details. Do not place an actual Personal Code, password, company authentication code or sensitive unredacted identity evidence in a general website enquiry.

What coordination does not do

Verification and coordination do not create or end PSC status, determine indirect control, complete another person’s requirement, connect every role automatically, complete an entity’s PSC notification, correct the register or guarantee acceptance of documents or filings.

Complex corporate, RLE, trust and firm arrangements require the specialist identification route. Detailed code timing and dual-role use, disputed status, historic inaccuracies and corrective work remain separate services.

Frequently asked questions

Do I verify again for every company or LLP?

Normally, no. Identity verification is personal and the same Personal Code is normally reused. You must still provide it separately for every applicable entity and role.

Does one PSC code submission cover all my entities?

No. One submission connects the verified identity with the relevant PSC role. Each other company or LLP must be dealt with through its own applicable process.

Can one PSC complete verification for another PSC?

No. Every individual completes their own identity-verification requirement. An authorised person may provide verification details on a PSC’s behalf, but the code and verified identity remain personal to that PSC.

Can different PSCs use different verification routes?

Yes. One person may use the free official route and another a suitable ACSP route. Each route must meet the applicable identity standard.

Must an overseas PSC verify?

Yes, where the person is an individual PSC subject to the current requirement. Overseas residence or nationality does not create an exemption.

Can an overseas PSC use the free Companies House route?

Potentially. Eligibility depends on the person and evidence. The official online route currently supports a biometric passport from any country, alongside other specified documents and routes.

Does Coddan accept every overseas passport or identity card?

No. Support depends on the current route and provider coverage, document type, issuing country, validity, quality and consistency.

Will certification, translation or an apostille guarantee acceptance?

No. These steps are not universally required and do not make an unsupported or inconsistent document acceptable automatically.

What if my name is written differently on overseas documents?

Provide the relevant versions and supporting explanation. The difference should be reviewed against the verification file and Companies House information before submission.

Do all PSCs in a group have the same deadline?

No. The applicable period depends on each person’s role, registration history and the relevant entity’s dates. One group deadline should not be assumed.

Does director code use complete the PSC requirement?

No. The same code is provided separately for the director and PSC roles through their applicable processes.

Does LLP-member code use complete the PSC requirement?

No. LLP membership and PSC status are different capacities. The code must be used separately through each applicable role process.

Can Coddan coordinate several people and entities?

Yes, within an agreed scope. Coddan can organise the people, entities, routes, evidence, periods and separate code uses, while each individual and entity retains its own responsibilities.

Map the people, entities and separate role requirements

Tell Coddan which individuals, companies, LLPs, countries and roles are involved. We can identify the appropriate verification and coordination route without treating the group as one person or one Companies House event.

Discuss coordinated PSC verification

Multi-Entity and Overseas PSC Identity Verification.

Coordinate identity verification when one person has PSC roles across several companies or LLPs or when several PSCs and overseas individuals require separate verification routes.

Follow the multi-entity PSC identity-verification journey from identifying each relevant role through checking Personal Code and role connections and completing the appropriate Companies House steps.