Sanctions Testing
Sanctions Testing automates compliance, so your systems identify sanctioned entities and PEPs, but allow legitimate transactions. It offers quality assurance, performance assessment, list accuracy, risk alignment, control automation, and peer comparison - all through secure web-based technology for easy integration.
Benefits
Learn more about Sanctions Testing
Features
-
Real-time testing and comparison
With Sanctions Testing, you can test your payments, customer and PEP filters automatically at scheduled intervals, or on demand without disrupting live operations. Test multiple systems or configurations, or repeatedly test the same system to monitor changes over time. Test results can be tracked, compared, visualised in graphs and charts and exported for audit and other reports.
-
Puts you in control
Sanctions Testing gives you a wide range of testing options. You can generate test objectives closely aligned to your institution’s compliance policy and risk criteria. You can also customise tests with your choice of sanctions list data and produce them for multiple message formats, including Swift MT, ISO 20022, Fedwire, CHIPS and customer record formats.
Sanctions Testing provides thorough testing for exact or “fuzzy” matches, such as misspellings and acronyms, based on a comprehensive library of derivations. You can also include relevant risk information, such as BICs, country, city or other keywords.
-
Unrivalled list coverage and support
Sanctions lists are subject to constant change and amendments, making list management a challenge. To ensure your lists are correct and up to date, use the Sanctions Testing user interface to navigate, search and review key regulatory sanctions lists and your own internal lists. List alerts provide early notification, and change reports are standardised to help you manage and prioritise change processes and updates.
-
Quantify your filter performance
We’ve worked closely with our customers to define Sanctions Testing features and functionality to meet the dynamic challenges of sanctions compliance.
For example, Peer Assessment is an optional add-on for Sanctions Testing users, developed in close collaboration with the Swift community. It provides baseline aggregated data from peer institutions, enabling banks to evaluate the performance of their filters against key data from other participating users.
We also offer packaged and bespoke services, including advice on design and implementation of your testing framework, maximising the effectiveness and efficiency of your sanctions compliance programme.
-
Model validation
Sanctions Testing checks that your screening models and filter settings are correctly aligned with your organisation’s compliance policies and risk appetite. You can define tests in line with your compliance and risk policy, test and understand your screening models and verify consistent implementation across your organisation. Our optional Peer Assessment service provides more information on how your filter models operate and compare to your peers, helping you make the best compliance decisions.
Frequently Asked Questions
What is Sanctions Testing?
Sanctions Testing is a secure, web-based product. It allows you to test, tune and optimise your transaction, customer and PEP filters, validate the lists you are using are correct, and align your filter configuration to your business needs and risk appetite. We also offer a range of assessment, training and filter tuning services to optimise your effectiveness and efficiency.
What’s the difference between Sanctions Screening and Sanctions Testing?
Sanctions Screening is a Swift-hosted service allowing you to screen transactions against sanctions lists. With Sanctions Testing, you can test, tune and optimise your own transaction, customer and PEP filters. But it doesn’t replace these filters.
Who benefits most from using the service?
Sanctions Testing is used by global institutions operating their own sanctions filters. They use it to optimise their sanctions and PEP filters to improve their sanctions compliance programmes.
What kind of data is used to test filters?
We take data from public sources. No customer data is used. Users can design and specify tests to include relevant risk data and meet their in-house risk objectives. We can also test your in-house lists if required.
Which lists are covered?
We maintain up-to-date more than 50 sanctions lists from all the major regulatory bodies, including OFAC, United Nations, Europe and HMT. You can also add your own private lists.
What types of filters can you test?
Sanctions Screening can be used to test filters that are used for transaction, customer and PEP screening. It can be configured for any filter, whether that is an in-house solution or one from a third-party supplier.
What file formats can be tested?
We can test virtually any format, including Swift MT and MX messages, as well as other structured transaction formats, such as CHIPs, Fedwire or your own internal formats. For customer and PEP screening, we can configure the format to meet your own specifications.
What is the difference between testing sanctions and PEP filter performance?
PEP screening is usually only performed in a customer screening environment. The majority of the testing processes are similar, but the test structure and outcomes will differ between sanctions and PEP filters.
How easy is it to get Sanctions Testing up and running?
We offer standard onboarding packages and these can be tailored to your own implementation needs. Swift experts will train you on how to use the tool and optimise the value of your investment.
Why should I use this Swift service rather than third-party consultancy?
Sanctions Testing provides the benefits of independent, third-party testing without the cost and delays of commissioning an external consultancy to perform the testing on your behalf. You are able to test whenever you like and make updates based on test findings immediately. You’ll have the assurance that the tests and measurement processes are aligned with best practice, as defined by the leading institutions across the Swift community that use Sanctions Testing.