Sanctions foundations checkpoint
Check your grasp of what sanctions are, who imposes them, what an asset freeze actually requires, and how sanctions screening differs from AML monitoring. Covers the screening foundations topics plus list delivery basics.
QUESTIONS AS TEXT
Q1. What are financial sanctions, at their core?
Answer: B: Restrictive measures imposed by governments and international bodies, for foreign policy and security reasons, that limit dealings with listed persons and entities and sometimes with whole sectors or regions.
Sanctions are tools of foreign and security policy expressed as legal restrictions. For a bank they translate into concrete obligations: do not deal with designated persons, freeze what you already hold for them, and in some programs restrict specific activities or sectors. That legal character is what separates sanctions compliance from a bank's own commercial risk decisions.
Q2. Match each sanctions authority to its role.
Answer: Adopts designations that member states around the world are then obliged to implement in their own legal systems → United Nations Security Council (United Nations designations bind member states, but the UN operates no payment systems — each state must implement the list in its own legal system.); Administers United States sanctions programs and publishes the SDN List → OFAC (US Treasury) (OFAC is the US Treasury office that administers United States sanctions programs; the SDN List is its best-known list.); Adopts restrictive measures that apply across all EU member states, reflected in a consolidated EU list → Council of the European Union (EU restrictive measures are adopted by the Council and apply across every member state, reflected in the consolidated EU list.); Implements and enforces UK financial sanctions and publishes the UK consolidated list → OFSI (UK HM Treasury) (OFSI is the UK's implementation and enforcement arm within HM Treasury, publishing the UK consolidated list.)
Several authorities issue sanctions, and their lists overlap without being identical. Which lists a bank screens against depends on where it operates, which currencies it clears, and its own documented risk decisions — most internationally active banks screen against several lists at once, which is why list aggregation and provenance matter.
Q3. Bank Alfa discovers that one of its account holders has just been designated under an asset-freeze program that applies to the bank. What does the freeze require?
Answer: B: Stop dealing with the funds: the balance stays where it is, nothing is paid out or otherwise made available to the designated person, and the bank reports the frozen assets to its competent authority.
An asset freeze prohibits dealing with a designated person's funds and economic resources and making funds available to them. The frozen balance remains on the bank's books, the freeze is reported to the competent authority, and specific payments can sometimes be permitted under a licence or exemption. The exact reporting duties and licensing grounds are regime-specific, so operational teams work from the guidance of the authority that applies to them.
Q4. A colleague asks why the bank runs both sanctions screening and AML transaction monitoring. What is the core difference?
Answer: B: Sanctions screening compares parties against published lists and aims to stop prohibited payments before they complete; AML monitoring examines patterns of behavior over time to detect and report suspicious activity.
Sanctions screening is list-based and largely preventive: is this party someone we may not deal with, right now, on this payment? AML monitoring is behavior-based and largely retrospective: does this activity look suspicious enough to investigate and report? The two controls intersect — a screening hit can trigger an AML review — but neither replaces the other.
Q5. A sanctions authority adds new names to its list this morning. Why do banks treat loading the update — and rescreening existing customers against it — as time-critical?
Answer: A: Because designations generally take effect when they are published: a payment or relationship that was unproblematic yesterday can be prohibited today, and screening against a stale list will not catch it.
Two clocks start when a designation is published. Transaction screening picks up the new name only once the engine's list data is refreshed, and customer screening finds existing relationships only once the book is rescreened against the change. The gap between publication and loading is real exposure, so institutions measure it and decide — as a documented, risk-based choice — how quickly each system must catch up.