§ 5.4
Choosing sanctions screening software
- Published
A guide to sanctions screening software, built on what OFAC and the FFIEC say: OFAC regulations do not explicitly require any specific screening regime, and screening choices rest on each institution and its circumstances.
A firm shopping for sanctions screening software meets a strange fact first. OFAC's FAQ says OFAC's regulations do not explicitly require any specific screening regime. No specific screening regime is explicitly required by those regulations.
That does not make the choice casual. OFAC's FAQ says financial institutions and others must make screening choices based on their circumstances and compliance approach. The software is a risk-based decision the institution owns.
What the software does, and what OFAC requires of it
OFAC's FAQ describes two broad kinds of tools. Some software packages interdict sanctioned countries and names in wire transfers. The names are on the Specially Designated Nationals or other sanctions lists. Others check names of new customers or routinely filter the names of all account holders. OFAC's framework says many organizations screen customers. They screen supply chains, go-betweens, counterparties, papers and payments. The goal is to spot banned places, parties or dealings.
The FFIEC manual adds that banks with lower OFAC risk and low transaction volumes may decide to manually filter for OFAC compliance. Software is common, not compulsory.
How the software matches names
Listed names arrive in many spellings. The FFIEC manual says the SDN list attempts to provide name derivations but may not include all of them. It also says more sophisticated interdiction software may catch variations of an SDN's name. Those variations are not included on the list.
This is fuzzy matching. OFAC's own free OFAC search tool shows how it works. It uses approximate string matching to find possible matches. It can detect misspellings. It can return near matches based on the confidence rating the user sets. OFAC does not recommend any specific confidence rating. Its FAQ says each user must set match thresholds from their own risk assessment.
Broad matching has a cost. OFAC's FAQ says many potential matches identified through screening are false positives. It also says some listed aliases are classified as weak aliases. A weak AKA is a broad or generic alias that may generate many false hits. A screening tool may exclude them as a risk-based decision. OFAC says it does not expect that persons will screen for weak AKAs.
The failures OFAC's framework names
OFAC's framework lists screening failures it has seen. Some organizations failed to update their screening software. They did not incorporate updates to the SDN List or SSI List. Others left out key details. One example is SWIFT codes for banks that are designated, blocked or sanctioned. Others did not account for alternative spellings of prohibited countries or parties.
The framework also names a root cause of sanctions violations. It is misinterpreting OFAC's regulations. A tool that runs cleanly on a wrong reading of the rules still runs toward the wrong place.
Where software sits in a compliance program
OFAC strongly encourages organizations subject to U.S. jurisdiction to use a risk-based approach by developing and routinely updating a sanctions compliance program. Its framework says each program should have five parts. These are management commitment and risk assessment. They also include internal controls, testing and auditing, and training.
OFAC's framework says internal controls should outline clear expectations and define procedures for OFAC compliance. What the risk assessment finds shapes the program's rules, steps, controls and training. The audit function should be independent of the activities it audits. It should answer to senior management. Training should be tailored to the entity's risk profile and to high-risk employees.
OFAC's framework notes that OFAC regulations do not require a formal sanctions compliance program. Still, OFAC can lower a civil penalty under General Factor E. It weighs whether a program exists and how good it is.
List updates and staying current
Sanctions lists change often. OFAC's FAQ says all changes to its lists are announced on its recent actions pages, with records going back to 2001. Its framework says a program should adjust fast to what OFAC publishes. That includes SDN List updates, new or changed programs, and new general licenses.
Many institutions set up a scheduled download of the SDN list and other sanctions lists. OFAC's FAQ points automated systems to XML, CSV, PIP, DEL and FF files on the SDN and Consolidated Sanctions List pages. The FFIEC manual says a program should update its lists of sanctioned countries and blocked people on time. It also says banks should recheck current customers when the OFAC list changes.
Screening tools often screen against OFAC's lists. They also screen lists from other agencies, vendors, or the user's own internal lists. OFAC's FAQ says to first find out which list fired. If so, OFAC's FAQ says to contact the agency that maintains that list.
Alerts, human review and records
OFAC's FAQ says software may flag payments that have nothing to do with OFAC targets. People may need to step in and dig by hand. The FFIEC manual says a high volume of false hits may indicate a need to review the bank's interdiction program.
When a hit looks wrong, OFAC's FAQ says an institution may identify a false positive where a name is similar but other information does not match the SDN List. OFAC's FAQ says that if you can reasonably determine the match is not valid, then you may proceed with the transaction or activity.
OFAC's FAQ says organizations should keep complete, accurate records of the steps taken to investigate a potential match. OFAC may ask for these records under 31 C.F.R. § 501.602.
Choosing a tool
OFAC's FAQ offers plain starting points. One suggestion for finding the right software is to research what peer banks are using. A bank could also talk to a variety of software vendors who can be located by doing an Internet search. OFAC suggests a bank research what its peer banks use and determine if the software package works for them.
Fit beats features. OFAC's FAQ says no ready-made program fits every bank. What counts as adequate depends on who your customers are and what business you do. OFAC is not itself a bank regulator. OFAC's FAQ says financial institutions should check with their regulators about the suitability of specific programs.
Two cautions close the shopping list. The FFIEC manual says a bank using a third party for OFAC checks is ultimately responsible for that third party's compliance with OFAC requirements. And OFAC's page says using Sanctions List Search is not a substitute for appropriate due diligence. OFAC's page says using its own search tool does not limit criminal or civil liability. The software narrows the work. The institution still owns the result.
Sources
- FFIEC BSA/AML Office of Foreign Assets Control - Office of Foreign Assets Control (FFIEC) (OFAC) (FFIEC BSA/AML Examination Manual)
- Creator: Acrobat PDFMaker 17 for Word (OFAC) (A Framework for OFAC Compliance Commitments)
- | Office of Foreign Assets Control (OFAC's FAQ) (OFAC FAQ) (OFAC)
- | Office of Foreign Assets Control (OFAC's FAQ) (OFAC FAQ) (OFAC)
- | Office of Foreign Assets Control (OFAC's FAQ) (OFAC FAQ) (OFAC)
- | Office of Foreign Assets Control (OFAC's FAQ) (OFAC FAQ) (OFAC)
- | Office of Foreign Assets Control (OFAC's FAQ) (OFAC FAQ) (OFAC)
- | Office of Foreign Assets Control (OFAC's FAQ) (OFAC FAQ) (OFAC)
- | Office of Foreign Assets Control (OFAC's FAQ) (OFAC FAQ) (OFAC)
- | Office of Foreign Assets Control (OFAC's FAQ) (OFAC FAQ) (OFAC)
- | Office of Foreign Assets Control (OFAC's FAQ) (OFAC FAQ) (OFAC)
- | Office of Foreign Assets Control (OFAC's FAQ) (OFAC FAQ) (OFAC)
- Sanctions List Service | Office of Foreign Assets Control (OFAC) (SLS)
- Sanctions List Search (OFAC) (OFAC's Sanctions List Search)