Sanctions Screening / Learning brief
Anatomy of a sanctions list entry
Your notes
In simple terms / 01
What this means in plain language
A single sanctions list record holds a primary name, aliases, dates and places of birth, nationalities, and identifiers, each tied to a programme tag. This article explains how every field drives a screening match and a defensible review.
A sanctions list is not a plain list of names; each entry is a structured record with many fields. At its centre sits a primary name, but around it are aliases (also known as names), one or more dates of birth, places of birth, nationalities, and identifiers such as passport or national identity numbers. Each entry also carries a programme tag showing which sanctions regime added it and why. A screening system compares customer and payment data against every field, not just the primary name. Understanding the record's shape explains why a match can fire on an alias or a date of birth rather than the headline name, and why a strong entry with several identifiers produces cleaner, more defensible results than a bare name. Reading an entry field by field is the first skill in screening analysis.
Complete lesson / 02
Understand the full idea, step by step
A letter arrives addressed to "J. Smith". Before you can act on it you have to decide which J. Smith — the neighbour two doors down, or a stranger who shares the name. You settle it with extra details: the flat number, a middle initial, a date you both remember. A sanctions list entry is the profile a screening team uses to make exactly that call about a party in a payment.
One list entry, field by field (SYNTHETIC — TRAINING ONLY)
- Primary name
- Orlin Freight Holding
- Aliases (AKAs)
- Orlin Freight; Orlin Logistics Group
- Entity type
- Company
- Country / address
- Registered office listed in one jurisdiction
- Registration number
- A national company registration identifier
- Programme tag
- Names the authority and the sanctions programme under which it was listed
The primary name is the heading, not the whole record
A sanctions list entry is a record with named fields, and each field is a separate signal. The primary name is where the eye goes first, but it is rarely where a match is decided. Aliases — also-known-as names — capture spellings, transliterations, and former names for the same party. For a person, a date of birth, place of birth, and nationality narrow a common name to one individual. Identifiers such as a passport number, a national identity number, or a company registration number are the strongest fields, because they are meant to be unique. Wrapping all of it is a programme tag recording which authority listed the party and under which regime.
Sanctions list entry — one structured record describing a listed party
A sanctions list entry is a single record on an official list that names a party a firm must not deal with, together with the supporting details that let a screening system recognise that party in real data. The engine compares an incoming customer or payment against every populated field and combines the results into a score — so reading the entry field by field, rather than skimming the name, is the first analytical skill in screening.
You may be wondering: if the name matched, is the work not already done?
No — a name match is where the review starts, not where it ends. Names are the weakest field: common names are shared by unrelated parties, and spelling shifts across languages and systems. The other fields are what turn a coincidence into a confident answer. If the entry carries a date of birth or a registration number and the payment carries the same one, agreement is strong evidence of a true match. If they clearly disagree, that is strong evidence the alert is a coincidence — which Kabir records through a documented review, never a silent dismissal.
How the fields drive the comparison
- VALIDATION
The engine compares names fuzzily, because spelling, word order, and transliteration vary. Near agreement counts as partial evidence, not proof.
- VALIDATION
It widens the same comparison across the aliases, so a former or alternative name still raises the alert.
- VALIDATION
Structured fields — date of birth, place of birth, nationality — either agree or they do not, so they confirm or separate two parties who share a name.
- VALIDATION
Identifiers carry the most weight: a matching passport or registration number turns a probable match into a near-certain one; a clear mismatch is strong evidence of a false positive.
- VALIDATION
The programme tag does not drive the comparison — it shapes the response, telling Kabir which regime applies and how the outcome must be handled.
| Name only | Name plus identifiers | |
|---|---|---|
| Fields to compare | Just the name | Name, dates, place, identifiers |
| Alerts produced | More, and weaker on each | Fewer, and stronger on each |
| Reviewer can | Only judge a name | Confirm or clear on a specific field |
| Decision note reads | Thin and uncertain | Short, factual, defensible |
COMMON CONFUSION
“A match on the primary name proves the payment involves the listed party.”
It proves only that a name resembled a listing. Whether it is the same party is decided by the supporting fields. Kabir treats each field as evidence and records which fields agreed and which stayed silent — that structured reading is what makes the decision explainable to a reviewer or auditor later.
STRICTLY SPEAKING
Strictly speaking, regimes and vendors populate entries to very different depths: some records carry several identifiers and full biographic detail, others are little more than a name and a programme tag. So real entries range from sparse to detailed, and an operation confirms what its own lists actually contain rather than assuming every field is present.
FOR NOW, REMEMBER
- A sanctions list entry is a structured record — primary name, aliases, dates and places, identifiers, and a programme tag — not just a name.
- Names are the weakest field; identifiers are the strongest, working as both confirmers and eliminators.
- The programme tag shapes the response rather than the comparison, naming the authority and regime.
- Reading an entry field by field is what makes a screening decision explainable after the fact.
TRY IT YOURSELF
An alert fires on a payment because the beneficiary name closely resembles a listed entry. The entry carries a company registration number; the payment carries a clearly different registration number for a company with the same name. What does Kabir have?
If identifiers are what turn a shared name into a confident answer, the next question follows naturally: why do those identifiers, and clean data on both sides, matter so much for matching?
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
A sanctions entry is a structured record, not a single name.
- 02
Aliases, dates of birth, places, nationalities, and identifiers each give the screening engine something specific to match on.
- 03
The programme tag records which regime listed the party and supports the review decision.
Practical use cases / 04
Where you would use this
A screening analyst reads every field of an entry to judge whether an alert is a true match or a false positive.
A data team maps customer and payment fields to the correct entry fields so the comparison is meaningful.
A compliance officer cites the programme tag and identifiers when documenting why a payment was held or released.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional list entry names 'Orin Vale' as the primary name, with two aliases ('O. Vale' and 'Orin V. Vale'), one date of birth (14 March 1971), a place of birth (the fictional town of Port Alder), one nationality, and a passport number (X0000000). A payment names 'Orrin Vale', born 14 March 1971. The engine scores a near-name agreement plus an exact date-of-birth match and raises an alert. An analyst compares the passport field, finds no number on the payment, and escalates for a documented review rather than releasing on the small name difference alone.
Evidence & review / 07
Evidence & review
Sanctions screening generally; field examples reflect the structure of major official lists (for example OFSI, OFAC, UN, EU). Not legal advice; a firm's obligations depend on the lists and jurisdictions it is subject to.
What this brief simplifies: Uses one synthetic entry and a simplified field-by-field match model. Real engines combine many weighted features and vendor-specific scoring, and entry completeness varies by regime.
Sources for this brief3
- Official requirement
The UK Sanctions List ↗ — UK Government (FCDO and HM Treasury / OFSI) · Consolidated list record structure
From 28 January 2026 the UK Sanctions List replaced OFSI's separate Consolidated List of Financial Sanctions Targets, which is no longer updated; OFSI provides a search tool over current designations.
- Market practice
Wolfsberg Group Sanctions Screening Guidance ↗ — The Wolfsberg Group · Use of primary and secondary identifiers in matching
Wolfsberg guidance is industry market practice, not law; institutions vary in how they apply it.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.