Help
  • FAQ
    • Introduction
    • Name Matching
      • Does Screena provide rules-based and/or fuzzy matching capabilities?
      • Does Screena have any machine learning or AI capabilities?
      • What are name cultures and how does Screena handle them?
      • How does Screena handle different scripts, diacritics, and transliteration?
      • How does Screena handle common names?
      • How does Screena handle inaccurate data?
      • What methods does Screena use to reduce false positives?
      • What is the percentage of false positives reduced with the methods used by Screena?
      • How does whitelisting work?
      • What differentiates pairwise name-matching between Screena One and Screena Plus?
      • How does secondary attributes-matching work?
      • Can Screena match beyond names and allow firms to blacklist identifiers or locations?
      • What is the difference between 'matchingNames' in screening responses and 'names' in 'targetData'?
    • Watchlists
      • Which lists are available out of the box?
      • Is Screena watchlist agnostic?
      • How is watchlist data loaded into Screena?
      • How frequently is data updated within Screena?
      • Do you provide proprietary watchlist data?
      • What sort of data (e.g., names, known aliases, known associates, etc) is used for name matching?
      • Does Screena support adverse media screening?
      • Do you provide information about whether a list entry is active, inactive or deceased?
      • Do you provide a URL link to the reference article for adverse media screening?
      • How is the data of third-party list providers conveyed to your name-screening API response?
      • Can I screen against specific sanction programs within a watchlist and not all of them?
      • What is the difference between the USA and the OFAC lists?
      • Is there a template to upload private lists into Screena?
      • How many records can I upload to my private watchlist?
      • Can I upload more than one private list?
      • How can I update my private list?
      • Why can't I find Politically Exposed Persons (PEPs) at regional level when I use Instant Search?
      • How do you monitor that watchlists are up to date and correctly uploaded to your platform?
    • Performance
      • Does Screena provide real-time screening capabilities?
      • What is the speed of screening?
      • How do you ensure horizontal and vertical scalability?
      • Does Screena support batch processing?
      • Do you have performance benchmarks?
    • Integration
      • Can clients configure the solution themselves or would they need support from you?
      • Do you partner with any other solutions/vendors?
      • Do you provide technology or solutions to support alert remediation investigation?
      • Can Screena be integrated within third-party platforms and systems?
      • How do you handle changes to your API data model?
    • Personalization
      • What options do I have to optimize my screening results?
      • What screening parameters can I configure to meet my risk appetite?
      • To which extent are the screening thresholds adjustable?
      • What is the difference between the algorithm value "ignore" and the option "nullMatch" set to false?
    • Hosting & Deployment
      • How can Screena be deployed?
      • How do you set resources per customer?
      • How do you segregate the data and configuration between customers?
      • How often does Screena release new versions?
      • How often are models re-trained and what does roll out to clients look like?
      • How do you handle High Availability?
      • What AWS regions do you operate as of now?
      • What operating systems and/or execution platforms are supported?
      • How do you provide bug fixes and distribution across clients?
    • Pricing & Support
      • What is your pricing model?
      • Can you clarify the difference between Screena One, Plus and Firm?
      • What additional modules are not included in your core product pricing package?
      • Do you charge for professional services and/or after-sales services?
      • Do you offer bespoke solutions to clients?
      • Can I test your solution for free?
      • What happens at the end of my trial period?
      • What are my payment options - credit card and/or invoicing?
      • What are your standard support & maintenance agreements?
      • Are there integration costs to work with Commercial-Off-The-Shelve (COTS) lists?
    • Security & Audit
      • Does Screena have security certifications?
      • What security measures do you apply?
      • How do you adhere to GDPR?
      • Does Screena provide versioning capabilities?
    • Tech Stack
      • What is your tech stack?
      • What programming language(s) is Screena written in?
      • What source and version control systems are used to manage development?
      • What testing tools do you use?
  • How To
    • Install Screena Portal
      • Preparing your system
      • Installing Screena Portal backend
      • Launching Screena Portal backend
      • Installing the web server
      • Configuring Screena Portal
    • Start Screena Portal
      • Starting PostgreSQL database
      • Starting Apache HTTP server
      • Starting Screena application
        • Start command
        • Restart command
        • Stop command
  • Release Notes
    • 2.1.17
    • 2.1.16
    • 2.1.15
    • 2.1.14
    • 2.1.13
    • 2.1.12
  • Legal
    • Terms & Policies
      • Website Terms of Use
      • Screena API Terms of Service
      • Screena API Data Policy
    • Privacy & Security
Powered by GitBook
On this page
  • Libraries
  • Stopwords for Name Matching
  • Stopwords for Identifier Matching
  • Stopwords for Geo-Matching
  • Prefixes
  • Suffixes
  • Synonyms
  • Whitelisted Aliases
  • Private Lists
  • Rules-Based Algorithms
  • AI Models

Was this helpful?

  1. FAQ
  2. Personalization

What options do I have to optimize my screening results?

PreviousPersonalizationNextWhat screening parameters can I configure to meet my risk appetite?

Last updated 1 year ago

Was this helpful?

Screena’s core screening configuration applies to every client equally, but custom components consider a client’s specific screening strategy.

While libraries are a crucial first step in optimizing your screening results, Screena offers a range of advanced rules and options tied to distinct API keys, allowing you to fine-tune every aspect of the screening engine beyond the libraries.

Libraries

Screena allows users to build their own libraries of stopwords, synonyms, prefixes or suffixes. You can provide your own libraries (i.e., custom libraries) to either replace or supplement the default ones (i.e., core libraries).

Libraries are paramount to keep false negatives rates as low as possible, as they are used in the name normalization process and ensure consistency in how your data is matched. For example, synonyms will help to determine which names should be considered equal despite being syntactically dissimilar.

Libraries can be managed independently. There is no need to populate all of the libraries in one go (i.e., prefixes, suffixes, synonyms, and stopwords) through a single API call. For example, it is quite possible to populate prefixes all while leaving suffixes unchanged when calling the method to populate Libraries.

Stopwords for Name Matching

This library is designed to prevent the matching of specific terms contained within narrative fields that add no meaning to names (e.g., 'of', 'markets', 'final payment') against the sanctions lists, thus reducing false positives.

You can manage the list of stopwords for name matching by importing JSON or CSV files.

Changes to the library of stopwords for name matching are considered low-medium risk but full regression testing is recommended to ensure no false negatives are inadvertently produced.

Stopwords for Identifier Matching

This library is designed to prevent the matching of specific terms contained within narrative fields having the same structure as BIC8 or BIC11 codes (e.g., 'language', 'february') against the list of blacklisted countries, thus reducing false positives.

You can manage the list of stopwords for identifier matching by importing JSON or CSV files.

Changes to the library of stopwords for identifier matching are considered low risk as they don’t affect the name-matching logic on sanctions lists.

Stopwords for Geo-Matching

This library is designed to prevent the matching of specific terms contained within narrative fields against the library of high-risk locations (e.g., ‘CAF Bank’ against the country code ‘CAF’, ‘imran’ against the country name ‘Iran’), thus reducing false positives.

You can manage the list of stopwords for geo-matching by importing JSON or CSV files.

Changes to the library of stopwords for geo-matching are considered low-medium risk but full regression testing is recommended to ensure no false negatives are inadvertently produced.

Prefixes

This library is designed to discard specific terms placed "before" a name such as titles or honorifics (e.g., 'Dr'), academic qualifications (e.g., 'M.D.'), and organization designators (e.g., 'The Bank') when matching names against the sanctions lists, thus reducing false positives.

You can manage the list of prefixes by importing JSON or CSV files.

Changes to the library of prefixes are considered low-medium risk but full regression testing is recommended to ensure no false negatives are inadvertently produced.

Suffixes

This library is designed to discard specific terms placed "after" a name such as qualifiers (e.g., 'Jr') and legal forms of companies (e.g., 'LLC') when matching names against the sanctions lists, thus reducing false positives.

You can manage the list of suffixes by importing JSON or CSV files.

Changes to the library of suffixes are considered low-medium risk but full regression testing is recommended to ensure no false negatives are inadvertently produced.

Synonyms

This library is designed to enforce the matching of names like alternative spellings, nicknames, diminutives (e.g., '20th' and 'Twentieth', 'Bill' and 'William', 'Ronald' and 'Ron') against the sanctions lists, thus reducing the risk of false negatives.

You can manage the list of synonyms by importing JSON or CSV files.

Changes to the library of synonyms are considered low risk. While they influence the name-matching logic on sanctions lists, they are intended to minimize the occurrence of false negatives. Conversely, the likelihood of increasing false positives is also low.

Whitelisted Aliases

This library is designed to whitelist specific watchlist aliases that are deemed of low quality but are not specified as such on the watchlists (e.g., the alias 'Alexander' on the Consolidated Canadian Autonomous Sanctions List).

You can manage the list of whitelisted aliases by importing JSON or CSV files. The files should include the watchlist, the alias, and the alias’ unique identifier as specified on the watchlist.

Changes to the library of whitelisted aliases are considered low risk as they don’t affect the name-matching logic on sanctions lists. They just reduce the scope of watchlist aliases when screening names.

Private Lists

Private lists are lists of names or entities that are created and maintained by an organization for its own internal screening purposes. Private lists are not publically available or shared with others, and they typically contain names or entities that are specific to the organization's business operations, risk tolerance, or compliance requirements.

Data contained in private watchlists are treated as personal data encrypted with a password encryption key and remain inaccessible to Screena.

You can manage additions to or removals from the private list by importing a CSV file.

Changes to the private list are considered low risk as they don’t affect the name-matching logic on sanctions lists.

Rules-Based Algorithms

Rules-based algorithms are deterministic name-matching rules such as traditional edit-distance algorithms (e.g., Jaro) or other proprietary algorithms designed to detect specific name patterns including, but not limited to: name order variations; missing name components; misspellings and errors; name concatenations; acronyms and initials; detection of address and geolocation elements within narrative fields; noise detection, etc.

Changes to rules-based algorithms are considered high risk. Full regression testing is recommended as such changes can potentially increase the risk of false negatives and false positives.

AI Models

Training of AI models is designed to increase the accuracy of name-matching prediction scoring when simple deterministic rules are not enough to retain or reject candidate hits immediately.

You can check our API Reference Guide for more information about .

In addition to the , you can also upload your own private watchlist.

To learn how to upload your private list into Screena, check the answer to this question:

To activate or deactivate any rules-based algorithms for your Screena subscription, contact .

Screena AI training is based on supervised learning using labelled name datasets. The work of our R&D team is based on new data and clients' feedback. If you would like to share your insights and optimize your screening results, contact .

Libraries
public watchlists
Is there a template to upload private lists into Screena?
experts@screena.ai
experts@screena.ai
Screena Components-Based Screening Architecture