Sanctions screening sits at the intersection of international security policy and everyday financial services. Banks must identify prohibited relationships and payments while processing legitimate business. Excessive alerts consume investigation capacity; missed matches can allow restricted funds to move. The UK Financial Conduct Authority\u2019s review of firms\u2019 response to Russia sanctions documented both problems: overly sensitive systems produced false positives and operational strain, while insensitive systems missed even minor name variations.<\/p>\n
The practical question is how to improve discrimination between genuine exposure and coincidental similarity. Global guidance addresses this through better data, controlled calibration, documented investigations and checks beyond names.<\/p>\n
FATF <\/strong>Recommendation 6 requires countries to implement targeted financial sanctions concerning terrorism and terrorist financing, including UN designations under Resolution 1267 and successor resolutions, and national designations pursuant to Resolution 1373. Recommendation 7 covers UN targeted financial sanctions concerning proliferation and its financing. Both require freezing without delay and preventing funds or assets from being made available, directly or indirectly, to designated persons or entities.<\/p>\n These are standards for legal outcomes. They do not prescribe a universal screening algorithm, matching percentage or acceptable false-positive rate. Screening supports their implementation through domestic legal requirements.<\/p>\n Exemptions also matter. FATF updated Recommendation 6 in June 2026 to incorporate humanitarian exemptions under UNSCRs 2664, 2761 and 2615. Compliance therefore requires understanding permitted activity alongside prohibitions.<\/p>\n UN Security Council<\/strong> resolutions establish sanctions regimes; relevant sanctions committees maintain designation lists. The UN Consolidated List brings together individuals and entities across regimes, but inclusion does not mean identical restrictions apply to every entry. The relevant resolution and committee materials establish the applicable measures.<\/p>\n UN records contain permanent reference numbers identifying the regime, names in Latin and original scripts, aliases, birth details, nationality, identity-document numbers, addresses and listing information, where available. Narrative summaries explain designation reasons. The UN distinguishes good-quality aliases from low-quality aliases that are insufficient, by themselves, to identify someone. These distinctions directly affect matching decisions.<\/p>\n Other authoritative sources include:<\/p>\n OFAC\u2019s data also includes designated vessels and aircraft. Its service offers separate downloads, programme-based datasets and archived changes. These distinctions allow teams to retain the source, programme and identity of a record instead of treating every vendor entry as an interchangeable name.<\/p>\n Commercial databases can standardise and enrich these sources, but their coverage, update speed and transformation rules require oversight. Supplementary information includes corporate ownership records, vessel tracking, trade documentation and internal intelligence. The FCA\u2019s recent findings describe firms combining these sources to address gaps that name screening cannot resolve.<\/p>\n Politically exposed person records, adverse media and export-control lists serve different purposes. OFAC expressly cautions that vendor-generated alerts may originate from non-OFAC sources, including the US Bureau of Industry and Security Entity List. The first investigation step is identifying which list actually triggered the alert.<\/p>\n Two different measures are easily confused. The proportion of reviewed alerts closed as false positives is false positives divided by all reviewed alerts. The statistical false-positive rate is false positives divided by all actual negatives, including those correctly producing no alert. The denominators differ; comparisons require consistent definitions.<\/p>\n A low alert count alone cannot establish effectiveness: omitted records and insensitive rules also reduce alerts. Wolfsberg recommends independent testing of expected alert generation, screening rules, suppression and data integrity, supported by management information. Its guidance treats an alert as a starting point for investigation, rather than proof of sanctions exposure.<\/p>\n Reporting by list, jurisdiction and business helps locate disproportionate noise. Investigation timeliness and quality also matter: the FCA <\/strong>has documented backlogs, weak escalation and resource pressure that delayed action on genuine risks.<\/p>\n The literature supports several concrete practices:<\/p>\n Wolfsberg recommends screening at relationship establishment, on relevant changes, and before transaction execution.<\/p>\n Technology also needs organisational support. OFAC<\/strong>\u2019s compliance framework identifies management commitment, risk assessment, internal controls, testing and auditing, and training as essential components. It calls for sufficient expertise and resources and a compliance function with authority to act. An efficient matching engine cannot compensate for an investigation team unable to escalate or stop a transaction.<\/p>\n An exact name match does not establish that two records identify the same person. Conversely, a near match may represent the designated person despite spelling differences.<\/p>\n OFAC\u2019s September 2026 guidance directs investigators to compare the complete listing with available customer or counterparty information: person versus organisation, original-script names, birth information, nationality, identification numbers and other identifiers. A shared address alone is insufficient. A different city does not necessarily disprove identity. Additional reliable information may be needed.<\/p>\n Where evidence excludes the listed person, record the reasoning. Where a close or exact match remains unresolved, escalate under the applicable procedure. Once identity is established, determine the relevant prohibition and any exemption or licence before deciding whether blocking, rejection or another action is required. A numerical score cannot make these legal determinations.<\/p>\n An unlisted company can still be restricted. Under OFAC<\/strong>\u2019s 50 Percent Rule, an entity owned, directly or indirectly, 50% or more in aggregate by one or more blocked persons is itself blocked. Ownership research therefore remains necessary even when its name generates no alert. This is a US rule; it must not be assumed to describe every jurisdiction\u2019s ownership-and-control test.<\/p>\n For banks exposed to trade-based money laundering (TBML<\/strong>), checking counterparties addresses only part of the problem. FATF and the Egmont Group identify trade indicators involving business structures, documents, commodities, accounts and payments: inconsistent invoices, commercially implausible arrangements and payment patterns can require investigation even without a sanctioned name. An indicator is not, by itself, proof of criminality.<\/p>\n Trade screening also encompasses intermediaries, banks, vessels and IMO numbers, ports and relevant locations. Sectoral restrictions can depend on the underlying activity, so a clean name-screening result cannot establish that the financed trade is permissible.<\/p>\n In October 2024, the FCA <\/strong>fined Starling Bank \u00a328,959,426 for financial crime control failings, including sanctions screening and breaches of restrictions on high-risk customer onboarding. Its automated system had screened against only a fraction of the full sanctions list from 2017 until the problem was identified in January 2023. The penalty covered more than sanctions screening alone.<\/p>\n In April 2022, Australian logistics group Toll Holdings agreed to pay OFAC $6,131,855 to settle potential civil liability for 2,958 apparent violations. Payments through the US financial system involved sanctioned jurisdictions or persons. The case demonstrates why a transaction\u2019s payment route matters to a company operating outside the United States. OFAC classified the apparent violations as non-egregious and voluntarily self-disclosed; those factors informed the settlement.<\/p>\n OFAC <\/strong>states that sanctions violations can attract civil and, in some cases, criminal penalties. Its framework also recognises an effective compliance programme and appropriate remediation as potential mitigating factors in enforcement. Maintaining evidence of control design and operation therefore has practical significance.<\/p>\n In India, reporting entities must distinguish anti-money-laundering monitoring from targeted financial sanctions. The principal statutory mechanisms include section 51A of the Unlawful Activities (Prevention) Act, 1967 (UAPA<\/strong>), and section 12A of the Weapons of Mass Destruction and their Delivery Systems (Prohibition of Unlawful Activities) Act, 2005. Neither framework is simply a list of suspicious customers.<\/p>\n Section 51A empowers the Central Government to freeze, seize or attach relevant assets and prohibit making resources or services available to designated persons or others engaged, or suspected to be engaged, in terrorism. The MHA<\/strong>\u2019s 2 February 2021 implementation order requires covered financial institutions to maintain updated electronic lists and conduct daily checks. Matches require immediate reporting; a match beyond doubt requires preventing financial transactions. The order separately provides for official verification and freezing orders without prior notice, and STRs covering relevant completed or attempted transactions.<\/p>\n The RBI Commercial Banks – Know Your Customer Directions, 2025, updated on 1 October 2026, require daily verification of specified UNSC and 2007 Order lists, reporting resembling accounts to FIU-IND and advising MHA. They also require daily checks of the UNSCR 1718 list and consideration of other UNSCRs and UAPA\u2019s First and Fourth Schedules.<\/p>\n Section 12A, inserted in 2022, prohibits financing prohibited WMD-related activities. It empowers freezing and restrictions extending to assets owned or controlled directly or indirectly, held on behalf of relevant persons, or derived from their assets.<\/p>\n Under RBI\u2019s directions implementing the 1 September 2023 WMD procedure, banks must check at onboarding and periodically, refrain from transactions when particulars match, immediately inform the Central Nodal Officer-Director, FIU-IND and copy the State Nodal Officer and RBI. They must prevent transactions where the statutory grounds exist beyond doubt and implement freezing orders without delay. These obligations contain no minimum transaction-value exemption.<\/p>\n Sectoral scope remains important. IFSCA<\/strong>\u2019s AML\/CFT\/KYC Guidelines independently require its regulated entities to comply with the UAPA procedure and the September 2023 WMD order. Its treatment of FATF jurisdiction statements expressly preserves legitimate trade; a country-risk listing is not itself a blanket asset-freeze instruction.<\/p>\n For Indian compliance teams, reducing false alerts must preserve these reporting and prevention duties. The operational distinction is decisive: resolve similarity with evidence, identify the applicable legal measure, and follow its escalation, reporting and freezing procedure.<\/p>\n <\/p>\n [1] FCA, Sanctions systems and controls: firms\u2019 response to increased sanctions due to Russia\u2019s invasion of Ukraine (2023; updated<\/a> 2024).<\/a><\/p>\n [2] FATF Recommendations (amended June 2026),<\/a> Recommendations 6 and 7 and their Interpretive Notes.<\/a><\/p>\n [3] FATF, <\/a>Update to Recommendation 6 on humanitarian assistance, 23 June 2026.<\/a><\/p>\nStart with authoritative data<\/h3>\n
\n
Measure noise accurately<\/h3>\n
Reduce noise without creating blind spots<\/h3>\n
\n
Resolve perfect and near matches on evidence<\/h3>\n
Ownership and trade change the analysis<\/h3>\n
Enforcement shows the consequences<\/h3>\n
India requires distinct statutory responses<\/h3>\n
Sources and References<\/h3>\n