Free Acams Certified Global Sanctions Specialist CGSS Exam Questions

A key sanctions-evasion red flag in trade documents is reluctance or refusal to disclose end-use or end-user information. This may indicate diversion to a sanctioned jurisdiction, entity, or prohibited program (e.g., proliferation).

Expiration dates (D) are irrelevant to sanctions. Payment timing and product suitability (A, B) are normal commercial behaviors and not sanctions red flags.

Trade-based sanctions-evasion indicators (concealed end-user/end-use).

Red flags involving incomplete or intentionally vague documentation.

Risk-based screening controls include:

* Ensuring sanctions lists are current -- list freshness is essential to avoid processing transactions with newly designated parties.

* Using fuzzy logic -- captures alternative spellings, transliterations, phonetic differences, and reduces missed true matches.

Stopping all transactions (B) is not risk-based. Adding every country's sanctions list (C) creates operational noise without regulatory justification. Screening only names (D) ignores other critical fields like addresses, intermediaries, and free-text descriptions.

Risk-based list management expectations.

Fuzzy logic requirement for capturing name variations in sanctions tools.

The UK Office of Financial Sanctions Implementation (OFSI) applies the ownership and control test to determine whether an entity is considered owned or controlled by a designated person. Under OFSI rules, a person is deemed to own an entity if they hold, directly or indirectly, more than 50% of the shares or voting rights. This threshold also applies when determining indirect ownership through corporate structures.

Powers such as signing authority or power of attorney do not constitute ownership. The right to appoint or remove the majority of a board may indicate control but not ownership. Any threshold below 50% does not satisfy the OFSI ownership criteria.

Reference from Sanctions and Compliance Domains:

OFSI ownership threshold requiring more than 50% of shares or voting rights.

Distinction between ownership and other types of influence or authority.

OFAC regulations permit the use of USD for Cuba-related transactions only when explicitly authorized under specific exceptions or general licenses. These include certain remittances, humanitarian transactions, and authorized travel-related transactions.

General USD use with Cuba is otherwise prohibited unless OFAC has expressly allowed it through a license or regulatory exemption.

OFAC Cuba Sanctions Regulations.

Licensed and authorized activities involving USD clearing.

A historical review or lookback is warranted when previously unidentified data elements, missing reference data, or newly discovered customer attributes are detected that may have impacted earlier screening results. Sanctions and Compliance Domains explain that such scenarios indicate that past alerts may not have been correctly generated or evaluated, necessitating a retrospective review.

Routine list updates or daily refreshes do not automatically trigger lookbacks. New sanctions programs may require enhanced forward-looking monitoring, but only missing or newly uncovered data affecting past screening results justify a historical lookback.

Requirements for lookbacks when gaps in screening data are discovered.

Identification of previously missing identifiers as a trigger for retrospective review.

Sanctions and Compliance Domains and regulatory authorities such as OFAC, EU, and OFSI require institutions to update sanctions lists as quickly as possible after a new designation or change is published.

Weekly, biweekly, or monthly cycles are insufficient and can result in missed designations. Financial institutions must adopt systems that update sanctions lists promptly to maintain compliance and avoid facilitating prohibited transactions.

Regulatory expectation for immediate or prompt sanctions list updates.

Screening list management best practices for timeliness and accuracy.

Sanctions and Compliance Domains state that screening calibration must be tied directly to a financial institution's sanctions risk assessment, which evaluates products, customer base, geography, delivery channels, and transaction volume. Sensitivity adjustments must be justified by an institution's assessed sanctions exposure.

Staff levels or training do not determine screening thresholds; these are operational considerations. Management commitment supports governance but does not form the technical basis for calibration decisions.

Screening calibration tied to sanctions risk assessments.

Threshold adjustments must reflect actual sanctions exposure and transaction characteristics.

Sanctions and Compliance Domains outline that institutions must maintain effective and reliable sanctions screening systems. This includes screening all incoming and outgoing payment messages, and institutions may not rely solely on correspondent banks for sanctions controls. Screening tools must also be capable of detecting alternative spellings, transliterations, and name variations of sanctioned parties.

Sanctions list updates must be incorporated immediately or as soon as practicable after publication. Monthly updates would be considered insufficient.

The use of controlled internal whitelists, combined with proper governance, periodic review, and controlled threshold calibration, is an accepted method used to reduce false positives while maintaining compliance integrity. Threshold adjustments must always follow documented validation, testing, and oversight procedures.

Reference from Sanctions and Compliance Domains:

Requirements for screening all payment messages, including incoming SWIFT transfers.

System expectations for matching name variations and alternative spellings.

Regulatory expectations for timely list updates.

Recognition of whitelist use and threshold calibration as acceptable screening optimization methods.

OFAC's 2015 Guidelines indicate that internal sanctions lists must be updated:

* when changes occur to sanctions target listing information, and

* when enhanced restrictions or new requirements are imposed, including new Executive Orders, program changes, or sector restrictions.

OFAC does not mandate monthly reviews, daily reviews following system upgrades, or reviews based on percentage changes in customer data. Updates must correspond to regulatory changes, not arbitrary timelines.

OFAC guidance on internal list maintenance and update triggers.

Requirements linked to regulatory modifications and sanctions program developments.

When a potential sanctions match is detected, the required first action is to determine whether the alert represents a true match or a false positive. This involves comparing identifiers, reviewing customer documentation, and gathering additional details.

CDD is important but is not the specific required action at the moment of match investigation. The priority is confirming whether the entity is indeed the sanctioned party.

Sanctions investigation protocols requiring confirmation of match status.

Distinction between CDD and sanctions-specific investigations.