Trulioo has recently introduced a new, insightful set of data for UK Companies House: identity verification details for directors, officers and beneficial owners.

Under the Economic Crime and Corporate Transparency Act, these individuals must now prove who they are to Companies House, and the register publishes the result. Trulioo surfaces it as a single IdentityVerification status on every person we return. It lets you strengthen onboarding where UBO identity was previously taken on trust, flag companies whose officers are past their statutory deadline, and move faster on the majority already verified.

The object is register-neutral by design, so as other jurisdictions follow, they populate the same fields with no code change on your side.

IdentityVerification reports whether a director, officer or beneficial owner has verified their identity with the corporate register, as published by that register. It returns both the register’s raw evidence and a single derived Status you can act on directly.

Where the Object Appears

IdentityVerification is a nested object that appears in two places:

The object is omitted entirely when the register publishes no verification data for that person. It is additive: existing fields on both parent objects are unchanged, and integrations that ignore it continue to work.

Field Reference

All fields other than Status are passed through from the source register without modification. Any field the register does not publish for a given person is omitted rather than returned null.

The three Statement* dates describe this appointment at this company. VerifiedOn, VerifyingAgentName and VerifyingAgentSupervisoryBodies describe the person and carry across every appointment they hold.

Status Values

Status is derived by Trulioo from the register’s statement dates. It reflects whether verification is currently in force for this appointment.

Four of these six values mean something other than “this person is verified”, and only two of those four carry an adverse signal. Collapsing them into a single verified/unverified flag will produce false negatives on Not Applicable, Verification Pending and Unknown.

Status is evaluated at the time of the response. A record returning Verification Pending today can return Verification Overdue later with no change at the register, because the deadline simply passes. Do not cache it as a static attribute of the person.

How to Interpret the Data

Use Status, not VerifiedOn, to decide whether someone is verified. VerifiedOn records that a check happened on a date. It does not expire and it is not withdrawn when a verification statement is revoked, so a person can hold a VerifiedOn date while their verification is no longer in force. Treating a non-empty VerifiedOn as “verified” will produce false positives on exactly the records that matter most. VerifiedOn is provided as audit evidence and for recency analysis.

An absent object does not mean unverified. It means the register publishes nothing for that person. Depending on the jurisdiction and the person’s role, that may be because verification does not apply to them, because their deadline has not arrived, or because the register holds no record. Render it as “not on record” rather than as a negative finding.

This is a register attestation, not a Trulioo verification. Verified means the corporate register publishes a verification statement for this appointment. The underlying identity check was performed by the register or by an agent it authorises, under that jurisdiction’s standards. Trulioo reports what the register publishes and does not independently re-perform the check.

VerifyingAgentName is populated only where an authorised agent performed the check. Where a person verified directly with the register, the agent fields are absent while the statement dates are present. An absent agent name is not a gap in the record.

Example Response

A verified director, checked by an authorised agent:

{
  "StandardizedDirectorsOfficers": [
    {
      "GivenName": "Jane",
      "Surname": "Doe",
      "FullName": "Jane Doe",
      "Type": "Individual",
      "Status": "Active",
      "UniversalDesignation": "Director",
      "IdentityVerification": {
        "Status": "Verified",
        "VerifiedOn": "2025-07-16",
        "StatementStartDate": "2025-08-01",
        "StatementDueDate": "2026-04-16",
        "VerifyingAgentName": "Example Corporate Services LLP",
        "VerifyingAgentSupervisoryBodies": [
          "Institute of Chartered Accountants in England and Wales"
        ]
      }
    }
  ]
}

A director past their deadline, with no statement in force. Fields the register does not publish are omitted:

{
  "IdentityVerification": {
    "Status": "Verification Overdue",
    "StatementDueDate": "2026-04-16"
  }
}

A corporate director, where verification requirements do not apply:

{
  "IdentityVerification": {
    "Status": "Not Applicable"
  }
}

Coverage

IdentityVerification is populated today for the United Kingdom, from Companies House, covering directors, officers and persons with significant control.

The object is defined independently of any one register. As other jurisdictions begin publishing identity verification attestations, they will populate the same fields and the same Status values, so integrations built against this object will pick up new jurisdictions without code changes.

Not every field is published by every register. Where a register publishes fewer fields, the unpublished ones are omitted and Status is derived from what is available.