# PSC Resource ID

**URL:** <http://forum.companieshouse.gov.uk/t/psc-resource-id/13022>\
**Category:** Data Issues\
**Created:** [September 23, 2026, 10:21am UTC](http://forum.companieshouse.gov.uk/t/psc-resource-id/13022 "2026-09-23T10:21:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![radhika.sharma](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/r/e95f7d/32.png) [@radhika.sharma](http://forum.companieshouse.gov.uk/u/radhika.sharma)\
**Post date:** [September 23, 2026, 10:21am UTC](http://forum.companieshouse.gov.uk/t/psc-resource-id/13022/1 "2026-09-23T10:21:52Z")

</div>

Is “resource\_id” the only field which can help us identify PSCs uniquely?

Does it correspond to the “links\_self” field in the bulk PSC Snapshot?

---

<div class="post-metadata">

**Author:** ![companieshousedata](http://forum.companieshouse.gov.uk/user_avatar/forum.companieshouse.gov.uk/companieshousedata/32/2190_2.png) [@companieshousedata](http://forum.companieshouse.gov.uk/u/companieshousedata)\
**Post date:** [September 23, 2026, 11:25am UTC](http://forum.companieshouse.gov.uk/t/psc-resource-id/13022/2 "2026-09-23T11:25:31Z")

</div>

If you mean whether a PSC `resource_id` identifies the same source relationship consistently, then yes, it is intended to identify that particular PSC record.

If you mean whether it identifies the person across all Companies House records, then no. The same person may appear under multiple `resource_id` values, and different people may also share the same name. We therefore use corroborating evidence such as normalised name, DOB, address and a unique Officer anchor.

These figures were taken from Augusts data files:

- **44,498,666 eligible source links before resolution**
  - 30,698,283 Officer identity records
  - 13,800,383 individual PSC identity records

- **38,845,171 Person records after resolution**
- **5,653,495 excess source-link occurrences** , approximately **12.7%**

RE: `links_self`

The official Companies House Streaming API schema shows them as separate top-level fields:

- `resource_id` — “The ID of the resource”
- `resource_uri` — “The URI of the resource”
- `data.links.self` — “The URL of the resource”

See the [official PSC Streaming API schema](https://developer-specs.company-information.service.gov.uk/streaming-api/resources/pscstream), especially the fields around `resource_id`, `resource_uri`, and `data.links.self`.

Companies House also explicitly distinguishes a PSC’s identity from a notification/relationship ID in its [PSC resource specification update](https://forum.companieshouse.gov.uk/t/persons-with-significant-control-resource-specifications-update/12760):

> “`psc_id` is a unique ‘id’ for a PSC, `notification_id` is a unique ‘id’ for an actual ‘notification’.”

So the token at the end of `links.self` should not automatically be described as the same field as `resource_id`.
