Data Source ID Mapping

September 09, 2026 17:07

source_id guarantees identity correlation within a specific supplier feed. Downstream case management and screening systems must evaluate the combination of dataset and source_id (for example, OFAC:12345) to establish a globally unique record reference.

The source_id, returned as sourceId in JSON payloads and source_id in gRPC contracts, is generally the primary key linking normalized screening hits back to specific rows in official watchlist publisher feeds. It enables compliance teams to trace an alert back to the exact published regulatory record. If a list does not contain a source_id, Equifax will generate one or the field will remain empty if the data source keeps the identifier explicitly null.

Key properties and technical derivation

Watchlist providers handle record identification differently. Depending on the feed structure, source_id is populated through one of the following:

Native Path Lookup: Extracted directly from standard supplier entity keys.
Synthesized/Precomputed Keys: Built deterministically or through sequence counters for feeds with composite rows or multi-subject files.
Explicit Null / Unbuilt: Emitted as NULL or omitted for sources that publish no native record identifiers.

Uniqueness is guaranteed for each data source. Downstream systems must correlate dataset and source_id to establish a unique record identifier.

Native supplier keys

These sources publish native, unique identifiers for every entry. The pipeline extracts these keys directly. They are completely stable across re-runs, updates, and replays.

Data source	`source_id` origin field	`source_id` example	Description
OFAC	`uid`	26714	Direct mapping to OFAC SDN entry unique identifier.
European Union (EU) Sanctions	`__attr__logicalId`	13209	Native EU Consolidated list logical entity key.
United Kingdom Sanctions List (UKSL)	`UniqueID`	UK00192	Native UK Sanctions List entity key.
Politically Exposed Persons (PEPs)/Greycon	`Ent_ID`	100293	Supplier entity identifier.
International Consortium of Investigative Journalists (ICIJ)	`node_id`	80123945	Graph node identifier across Offshore Leaks databases.
Hotlist	`EDDID`	HL-99201	Customer internal watchlist entry ID.
Marijuana-Related Business (MRB) (Business)	`AT ATNUM`	9982341	Equifax Universal Business ID.

sidebar. Native supplier key JSON example

{
  "screeningResult": {
    "matchStatus": "MATCH",
    "matchedPerson": {
      "source": {
        "dataset": "OFAC",
        "subDataset": "OFAC_SDN",
        "generationDate": ""
      },
      "sourceId": "26714",
      "entityType": {
        "type": "PERSON"
      },
      "name": {
        "firstName": "JOHN",
        "lastName": "DOE",
        "fullName": "JOHN DOE"
      },
      "sanctionsOrPrograms": [
        {
          "type": "program",
          "value": "SDGT"
        }
      ],
      "remarks": [
        {
          "type": "lastUpdated",
          "value": "2026-09-08T00:00:00AM"
        }
      ]
    }
  }
}

Synthesized or precomputed keys

These suppliers publish complex or multi-subject files without distinct individual keys. The pipeline constructs synthetic keys using business rules or in-memory counters.

For sources like Marijuana-Related Business (MRB), a single business file is fanned out into separate entities for executives. The pipeline deterministically constructs sourceId by appending the officer role code to the business ID (ATNUM).

Data source	Synthesis rule	`source_id` example	Description
MRB (Officers)	`ATNUM` plus `-CON`, -`CEO`, `-CIO`, `-CFO`	9982341-CE	Derived by joining the master business key with officer role codes. Stable across updates.

sidebar. Synthesized key JSON example

{
  "screeningResult": {
    "matchStatus": "MATCH",
    "matchedPerson": {
      "source": {
        "dataset": "MRB",
        "subDataset": "MRB",
        "generationDate": ""
      },
      "sourceId": "9982341-CEO",
      "entityType": {
        "type": "PERSON"
      },
      "name": {
        "firstName": "JANE",
        "lastName": "SMITH",
        "fullName": "JANE SMITH"
      },
      "remarks": [
        {
          "type": "TitleDesc",
          "value": "Chief Executive Officer"
        },
        {
          "type": "Associated Entity Equifax Name",
          "value": "GREEN DISPENSARY INC"
        },
        {
          "type": "lastUpdated",
          "value": "2026-09-08T18:30:00PM"
        }
      ]
    }
  }
}

Precomputed batch ordinals

These sources carry shared tracking numbers for entire files without individual entry keys. The pipeline appends an in-memory sequential counter.

Caution

Do not use these as permanent cross-file keys.

For FinCEN 314(a) request files where all subjects share a single tracking_number, sourceId is dynamically generated in memory by joining the tracking number with an incremental counter.

Data source	Precomputed rule	`source_id` example	Description
FinCEN 314(a)	`tracking_number` plus `-ordinal`	TRACK-883921-1	Batch-Scoped Only: Appends an in-memory counter (-1, -2) during ingestion. Sequence numbers may shift upon worker node reboots, re-sharding, or re-runs.

sidebar. Precomputed batch ordinal JSON example

{
  "screeningResult": {
    "matchStatus": "MATCH",
    "matchedPerson": {
      "source": {
        "dataset": "FINCEN314A",
        "subDataset": "CLIENT_ALPHA",
        "generationDate": ""
      },
      "sourceId": "TRACK-883921-1",
      "entityType": {
        "type": "PERSON"
      },
      "name": {
        "firstName": "ROBERT",
        "lastName": "JOHNSON",
        "fullName": "ROBERT JOHNSON"
      },
      "remarks": [
        {
          "type": "lastUpdated",
          "value": "2026-09-08T18:30:00PM"
        }
      ]
    }
  }
}

Unkeyed data sources

These official sources do not publish entity keys. The pipeline does not invent arbitrary database trackers for them.

For data sources such as Money Services Business (MSB) that do not publish a native entity key, sourceId is explicitly emitted as null in the JSON representation rather than omitted, preserving a stable payload shape.

Data source	Pipeline behavior	`source_id` output	Description/handling recommendation
MSB	Explicit null	Null	Emitted as explicit `null` in JSON to maintain stable payload structure.
Office of the Superintendent of Financial Institutions (OSFI)	Not built	Absent	Canadian OSFI feed. The `sourceId` field is omitted entirely from payload objects.

sidebar. Unkeyed data sources JSON example

{
  "screeningResult": {
    "matchStatus": "MATCH",
    "matchedBusiness": {
      "source": {
        "dataset": "MSB",
        "subDataset": "MSB",
        "generationDate": ""
      },
      "sourceId": null,
      "entityType": {
        "type": "BUSINESS"
      },
      "name": {
        "fullName": "GLOBAL TRADING CORP LTD"
      },
      "sanctionsOrPrograms": [
        {
          "type": "regime",
          "value": "UK Sanctions Regime - Russia"
        }
      ]
    }
  }
}

Was this article helpful?

0 out of 0 found this helpful