Skip to content
Contact us
  • There are no suggestions because the search field is empty.

Understanding Sanctions List Fields

Sanctions lists published by authorities such as OFAC, the EU, the UN, and the UK contain multiple data fields to help users accurately identify sanctioned individuals, entities, and assets.

This article explains the most common fields you may encounter and how to interpret them during sanctions screening and review.

Data Availability Disclaimer

sanctions.io application retrieves and displays all information made available by the original sanctions data sources (e.g., OFAC, EU, UN, UK, and other authorities).

The level of detail provided in sanctions records may vary significantly depending on the issuing authority and the specific listing. Some sanctions lists contain limited or incomplete information. If certain fields (such as identifiers, addresses, positions, or remarks) are not visible for a given record, this indicates that the information is not provided by the underlying data source, rather than being omitted by the application.

sanctions.io does not infer, supplement, or extrapolate missing data beyond what is published by the sanctions authority.

Topics Covered

Sanctions List Fields

→ Name

→ Alternative Names

→ Identifiers

→ Address

→ Place of Birth

→ Positions

→ Program

→ Remarks

→ Additional Information

→ Compliance Review and Escalation

 

Name

The primary name under which the individual, entity, or asset is listed by the sanctions authority.

How to use it:

  • Serves as the initial screening trigger

  • Should never be used alone to confirm a match

  • Must always be assessed together with other identifying fields

 

Alternative Names (Aliases)

Alternative Names (also called aliases, AKAs, or "also known as") are additional names associated with the sanctioned subject.

What they may include:

  • Name variations or different spellings

  • Transliterations from other alphabets

  • Former names

  • Nicknames or operational names

  • Names in different languages

How to use them:

  • Essential for detecting matches where the primary name is not used

  • A common source of false positives is if not cross-checked with identifiers

  • Should be considered equivalent to the primary name during screening

 

Identifiers

Identifiers are structured data elements used to uniquely distinguish a sanctioned individual or entity from others with similar names.

Common identifier types

  • For individuals:

    • Date of birth

    • Place of birth

    • Nationality

    • Passport or national ID number

  • For entities and assets:

    • Company or registration number

    • Tax ID

    • LEI (Legal Entity Identifier)

    • IMO number (vessels)

    • Aircraft tail number

Why they matter:

  • Provide high-confidence confirmation or exclusion

  • Strongly reduce false positives

  • Often carry greater weight than names in screening decisions

 

Address

The Address field lists known or last reported addresses associated with the sanctioned subject.

What it may include:

  • Residential addresses (individuals)

  • Registered or operating addresses (entities)

  • Multiple historical or current locations

  • Partial or outdated address information

How to use it:

  • Helpful for geographic and jurisdictional assessment

  • Useful for distinguishing between similar entities

  • Should not be assumed to be current unless confirmed

 

Place of Birth

The Place of Birth field specifies where a sanctioned individual was born.

How it is used:

  • Strong supporting identifier for individuals

  • Particularly valuable when combined with the date of birth

  • Often appears alongside nationality information

 

Positions

The Positions field describes official roles, titles, or functions held by the sanctioned individual.

Examples: Government minister, Military officer, Board member, Executive director, Political party official

Why it matters:

  • Helps confirm identity in cases of common names

  • Provides context on influence and authority

  • Often linked to the reason for the designation

 

Program

The Program field indicates the sanctions regime or legal framework under which the subject is designated.

What it represents:

  • The legal basis for the designation

  • Geographic or thematic scope of sanctions

  • Applicable restrictions (e.g. asset freeze, travel ban)

Examples:

    • OFAC: SDGT, IRAN, CYBER2, UKRAINE

    • EU: RUSSIA, BELARUS

    • UN: ISIL (Da’esh) & Al-Qaida, DPRK

Why it matters:

  • Determines regulatory obligations

  • Helps assess jurisdictional relevance

  • Supports policy rules, reporting, and regulatory explanations

 

Remarks

The Remarks field contains free-text notes provided by the issuing authority to give additional context about a sanctions designation.

What it may include:

  • Legal or regulatory references (e.g. “Listed pursuant to UNSCR 2374 (2017)”, UN resolutions, executive orders)

  • Clarifications about identity or aliases

  • Ownership or control information

  • Data quality notes (e.g. approximate dates)

  • Historical or administrative updates

How to use it:

  • Remarks are not primary matching fields

  • They are essential for manual review, investigation, and audit justification

  • They often explain why a subject is listed or how to interpret ambiguous data

 

Additional Information

This field contains supplementary data that does not fit neatly into other structured fields.

What it may include:

  • Relationships to other designated parties

  • Operational details

  • Industry or sector involvement

  • Clarifying notes not suitable for the Remark field

How to use it:

  • Provides supporting context during investigations

  • Helps assess indirect exposure or extended risk

  • Should be reviewed during enhanced due diligence

 

Compliance Review and Escalation

Sanctions screening decisions should never rely on a single field. Names trigger alerts, Identifiers support confirmation, Programs define legal impact, and contextual fields such as Remarks, Positions, and Additional Information enable accurate and defensible compliance assessments.

Screening results do not constitute a compliance decision. All alerts must be reviewed and assessed by qualified compliance or legal professionals, who are responsible for interpretation, decision-making, and regulatory outcomes.

 

We're here to help!

If you have any questions or need more help, please contact our support team anytime!

  • Chat: Available directly through the Portal and Help Center

  • Email: help@sanctions.io