Personal codes and company incorporation

A Companies House personal code identifies an individual who has completed identity verification. It is not the company's registration number, company authentication code or HMRC Unique Taxpayer Reference. Keeping those items distinct prevents avoidable filing errors.

What the personal code does

The personal code is an 11-character identifier issued after successful verification. It belongs to the person, not to one company. The same code can be used to confirm the person's verified identity for the relevant appointments. ^[1]

This means that a founder involved in several companies should maintain one clear personal record rather than requesting a different identity code for every business.

Find it through the correct route

How you retrieve the code depends on whether verification was completed through GOV.UK One Login or an authorised provider. The current guidance explains account access and email delivery arrangements. If an agent used an incorrect email address, contact the agent and follow the official correction process. ^[1]

Avoid creating repeated accounts simply because a code is not immediately visible. First identify the email address and route used for the successful verification.

Use it for the relevant company role

For a new directorship, the code is supplied as part of incorporation or the appointment filing under the applicable rules. Existing directors use it through the relevant confirmation statement process. PSCs have a separate role-specific process and timing. ^[1][2]

A person holding both roles should check both requirements. Providing information about a director does not necessarily complete the PSC obligation for the same individual.

Store and share it proportionately

Keep the code in a secure record and share it only with a trusted person who genuinely needs to file on your behalf. Do not place it in public company documents, marketing material or a general website contact form. Treat an unexpected request for it with care.

A useful internal checklist records who is authorised to receive filing information, which company they act for and how confirmation of the completed filing will be provided.

If information does not match

Compare the personal details linked to the code with the relevant record. Follow Companies House guidance for a mismatch or a suspected compromised code. Do not alter genuine personal information merely to force a form to accept the submission.

Keep a code directory without exposing the codes

An internal handover note can identify the person responsible for a credential, the system it belongs to and the recovery route. It does not need to display the credential itself. This is useful when directors, administrators and accountants use the word code to mean different things during a filing discussion.

For example, a company number identifies the entity on the register. A personal code relates to a verified person. A company authentication code is associated with company filing access. Ask the person requesting information to name the relevant field and task so a founder does not send every identifier in a single email.

Recover access using the original verification route

Establish whether the verification was completed using GOV.UK One Login or an ACSP. For the One Login route, the official guidance directs users to the Companies House account associated with the verification email. For an ACSP route, check the email address supplied by the provider if delivery appears to have failed. ^[1]

The July 2026 guidance also explains saving an ACSP-issued code to a Companies House account. Follow the current official process from the source link, particularly if a provider has ceased acting for you. Account recovery is easier when the individual retains control of the email address used for identity verification.

Example: one person, several appointments

Imagine a director involved in three companies, with a separate accountant for each. The individual does not need a fresh identity code for each company simply because different people prepare the filings. They need to ensure the appropriate trusted filer has the information required for that appointment and that the submission is accepted. ^[1]

Keep a list of which adviser received the code and for which legitimate purpose. When an engagement ends, review access arrangements and follow official guidance if there is reason to think information has been compromised. Avoid treating a historic adviser relationship as indefinite permission to use personal filing information.

Distinguish a mismatch from a missing code

If a filing rejects information, keep the exact error and compare the record concerned with the individual's correct details. A wrongly entered code, incorrect date of birth on the register and incorrect information supplied during verification may need different remedies. Establish the actual cause before changing accounts or making another application.

When asking for assistance, describe the filing, company role and error. A screenshot can often be prepared with the code and other sensitive details removed. Supply further information only through the official or agreed professional channel when the specific need is clear.

The completion record should identify the accepted appointment or confirmation statement and any separate PSC action. Possession of the code is preparation for the filing; it is not itself proof that every required submission has been made.

When asking for help, explain the error and the filing being attempted without sending the code in the initial enquiry. That gives an adviser enough context to identify the appropriate next step while keeping access information controlled.

For coordination of a new incorporation, read limited company formation support; do not put the personal code in the enquiry.