A "weak AKA" is a term for a relatively broad or generic alias that may generate a large volume of false hits when such names are run through a computer-based screening system. OFAC includes these AKAs because, based on information available to it, the sanctions targets refer to themselves, or are referred to, by these names. As a result, these AKAs may be useful for identification purposes, particularly in confirming a possible "hit" or "match" triggered by other identifier information. Realizing, however, the large number of false hits that these names may generate, OFAC qualitatively distinguishes them from other AKAs by designating them as weak. OFAC has instituted procedures that attempt to make this qualitative review of aliases as objective as possible. Before issuing this updated guidance, OFAC conducted a review of all aliases on the Specially Designated Nationals (SDN) list. Each SDN alias was run through a computer program that evaluated the potential of an alias to produce false positives in an automated screening environment. Names were evaluated using the following criteria:
Aliases that met one or more of the above criteria were flagged for human review. OFAC subject matter experts then reviewed each of the automated recommendations and made final decisions on the flagging of each alias.
OFAC intends to use these procedures to evaluate all new aliases added to its sanctions lists.
Weak AKAs appear differently depending on which file format of the sanctions list is being utilized.
ALLANE, Hacene (a.k.a. ABDELHAY, al-Sheikh; a.k.a. AHCENE, Cheib; a.k.a. "ABU AL-FOUTOUH"; a.k.a. "BOULAHIA"; a.k.a. "HASSAN THE OLD"); DOB 17 Jan 1941; POB El Menea, Algeria (individual) [SDGT]
In the DEL, FF, PIP, and CSV file formats, weak AKAs are listed in the Remarks field (found at the end of the record) of the primary name file. In these formats, weak AKAs are bracketed by quotation marks. Please see the data specification documents for more information on the SDN and Consolidated lists.
SDN List Data Specifications: https://home.treasury.gov/system/files/126/dat_spec.txt
Consolidated List Data Specifications: https://www.treasury.gov/ofac/downloads/consolidated/cons_dat_spec.txt
8219 @"ALLANE, Hacene"@"individual"@"SDGT"@-0- @-0- @-0- @-0- @-0- @-0-@-0- @"DOB 17 Jan 1941; POB El Menea, Algeria; a.k.a. 'ABU AL-FOUTOUH'; a.k.a. 'BOULAHIA'; a.k.a. 'HASSAN THE OLD'."
In the legacy XML version of OFAC's sanctions lists, there is a Type element for each AKA. The Type can either be 'weak' or 'strong' (see the XML SDN and Consolidated List Schemas (XSD files) at: https://home.treasury.gov/system/files/126/sdn.xsd and https://www.treasury.gov/ofac/downloads/consolidated/consolidated.xsd for more information).
In the advanced XML list standard, alias quality is represented as a Boolean attribute of the alias element. This attribute, "LowQuality" can be flagged as either "true" or "false." If the LowQuality attribute is false then the alias is strong. If the LowQuality attribute is true then the alias is weak.
For more information on the advanced XML standard, please visit OFAC’s SDN data formats page at https://home.treasury.gov/policy-issues/financial-sanctions/specially-designated-nationals-list-data-formats-data-schemas.
OFAC’s regulations do not explicitly require any specific screening regime. Financial institutions and others must make screening choices based on their circumstances and compliance approach. As a general matter, though, OFAC does not expect that persons will screen for weak AKAs, but expects that such AKAs may be used to help determine whether a “hit” arising from other information is accurate
A person who processes an unauthorized transaction involving a sanctions list entry has violated U.S. law and may be subject to an enforcement action. Generally speaking, however, if (i) the only sanctions reference in the transaction is a weak AKA, (ii) the person involved in the processing had no other reason to know that the transaction involved an entry on one of OFAC's sanctions lists or was otherwise in violation of U.S. law, and (iii) the person maintains a rigorous risk-based compliance program, OFAC will not issue a civil penalty against an individual or entity for processing such a transaction.