1969 XG5 AcceptWhiteLists English
R E P A P E T I H W
Accept Lists and White List
for LexisNexis® Bridger Insight® XG (XG) 5
L A C I N H C E T
FIN210-EN_US — 7 March 2024
CONFIDENTIAL
CONFIDENTIAL
The recipient of this material (hereinafter "the Material") acknowledges that it contains confidential and proprietary data the disclosure to, or use of which by, third parties will be damaging to LexisNexis Risk Solutions and its affiliated companies (hereinafter "LexisNexis Risk Solutions"). Therefore, recipient agrees to hold the Material in strictest confidence, not to make use of it other than for the purpose for which it is being provided, to release it only to employees requiring such information, and not to release or disclose it to any other party. Upon request, recipient will return the Material together with all copies and modifications, if any, to LexisNexis Risk Solutions.
LexisNexis Risk Solutions shall not be liable for technical or editorial errors or omissions contained herein. The information in this publication is subject to change without notice and is provided "as-is" without a warranty of any kind. Nothing herein should be construed as constituting a warranty, as any applicable warranty is exclusively contained in your signed agreement with LexisNexis Risk Solutions.
All names, addresses, birth dates or other identifying information in the text, or on the sample reports and screens shown in this document, are of fictitious persons and entities and have been created for illustrative purposes only. Any similarity to the name of any real person, school, business, other entity, address, date of birth, or other identifying information is purely coincidental.
Due to the nature and origin of public record information, the public records and commercially available data sources used in reports may contain errors.
The LexisNexis Bridger Insight XG service is not provided by "consumer reporting agencies," as that term is defined in the Fair Credit Reporting Act (15 U.S.C. 1681, et seq.) (FCRA), and does not constitute "consumer reports," as that term is defined in the FCRA. Accordingly, the Bridger Insight XG service may not be used in whole or in part as a factor in determining eligibility for credit, insurance, employment or for any other eligibility purpose that would qualify it as a consumer report under the FCRA.
LexisNexis and the Knowledge Burst logo are registered trademarks of RELX Inc. Bridger Insight is a registered trademark of LexisNexis Risk Solutions Inc. Other products and services may be trademarks or registered trademarks of their respective companies.
© 2024 LexisNexis Risk Solutions
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 2
CONFIDENTIAL
Con t ent s
Recurring Matches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Accept Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Accept Lists in Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Required Input Entity Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Matches That Are Suppressed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Matches That Are Not Suppressed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Examples of Accept List Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
White List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
White List in Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Examples of White List Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
White List Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 3
CONFIDENTIAL
Recur ri ng Matches
Organizations periodically rescreen their customer base or screen the same customer as part of different business processes. Recurring matches can be troublesome due to the resources that are required for reprocessing. LexisNexis® Bridger Insight® XG (XG) offers features that can reduce the repeated reviews of recurring matches.
To understand the magnitude of the problem of recurring matches, consider what can happen when the return rate of the list screening service is one percent. If your organization searches one million records, then a total of 10,000 potential matches could be generated. Your staff must investigate these 10,000 matches to determine whether they are true matches or false positives and what actions to take based on your review process. When you search your one million records again, those same 10,000 potential matches may be reported unless your software has methods to prevent repeat reports of recurring matches.
However, sometimes you may want to review a recurring match when certain information changes that may have you reconsidering your processing decisions. For example, when additional information is available for a false positive or list entity information changes for a true match, you may want to review the match again.
Considering the quantity of recurring matches, features that reduce these alerts when match information has changed are important to your business. However, you may want these alerts to be reported again when the match information has changed. Your due diligence does not need to be as repetitive as your efforts were in the past. XG can help reduce the time and staff burden needed to process repeated matches.
This publication describes how you can use accept lists and the White List to help suppress recurring matches that contain the same information as the original match.
This publication also describes how you can use accept lists to notify you when certain information changes for recurring matches that you may want to reconsider. These features can help you create a due diligence process that is more efficient and less risky for your organization. The accept lists and the White List are advanced features. Access to these features is controlled by privileges. To fully understand how these features work within XG processing, you should already have general knowledge of predefined searches, alert decisions, and privileges. For more information, see the LexisNexis® Bridger Insight® XG Help.
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 4
CONFIDENTIAL
Accept L i st s
Accept lists help reduce the number of recurring matches that are reported when match information has not changed. Accept lists can also notify you when certain information changes in matches. The lists can help decrease the time that your organization spends on repetitive due diligence activities.
You can create multiple accept lists to serve different business units or processing needs. For example, text records or payment transaction records are structured differently from the records that are contained in a typical batch file. Therefore, you should consider using a separate list for text records or payment transaction records. As another example, you can create an accept list for a general license that is applicable to your business. If the general license is ever revoked, then you can simply remove the list for that general license from your predefined search.
Accept List Processing
At a high level, accept list processing involves the following stages:
1. A list screening search is performed. 2. The alert is reviewed and added to an accept list. 3. The predefined search is configured to use the accept list. 4.
In repeated searches, the accept list suppresses the match if the match information has not changed. If match updates are configured, then XG generates an alert if certain match information has changed.
Accept lists support only parsed data. Unparsed data without defined fields or structure (such as files that contain only text strings) cannot be added to an accept list. For example, you cannot add alerts that were processed using the XG - Unstructured batch format. For unparsed data, you should consider the White List to suppress recurring false positives.
Match Reduction
Accept lists prevent a recurring match to be reported when no match information has changed. After an alert is added to an accept list, you can use the list in a predefined search to suppress the same match in future searches. Users at your organization build accept lists over time by adding alerts to the lists as part of their review process. You cannot manually add alerts to the accept lists outside of your review process.
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 5
CONFIDENTIAL
Match Updates
Match updates notify you when changes occur to a match in an accept list record. For XG to generate match updates, the predefined search must be configured to generate match updates and include the accept list that contains the record.
XG can generate an alert that contains a match update for a false positive when new match information is found for specified data elements. You can also set the default settings for false match updates that are used for all predefined searches. You can select the following data elements to generate a false match update:
• Address • AKA (also known as) • DOB (date of birth) • Citizenship
• Gender • ID Numbers • Name • Phone
False match updates are designed to alert you to new match information that may need further investigation to determine whether the match should remain on the accept lists as a false positive. For example, if you previously added a match to an accept list that did not contain a matching DOB and a matching DOB was found in a later search, then XG would generate a false match update.
XG can generate an alert that contains a match update for a true match when list entity information changes in an accept list record. True match updates are designed for profile monitoring and alert you to changes in the true matches that may lead you to reassess your previous risk level designation. This functionality is not designed for processing sanctions list matches. Due to regulations or high risk, you most likely do not want to conduct business with the entities that are on a sanctions list.
Accept Lists in Process
To incorporate accept lists into your review process, a previously-processed alert must be added to an accept list to be used in future search configurations.
You add an alert that you have investigated to an accept list based on your review process. The accept list record contains the input information that your organization provided for the search and the screening list information for each match in the alert.
In addition to the entity name, screening list records can contain multiple AKA names. XG determines which name in the screening list record best matches the name in the input record. This "best matching name" and the entity name in the screening list record are added to each match in the accept list record. The best matching name and the entity name in the screening list record may be the same.
Accept list records do not store MR (machine readable) Line 1 and Line 2 information that is provided in the input information for passports or visas.
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 6
CONFIDENTIAL
Each match in the accept list record can also contain the information that is needed for false match updates. When the information is available in a new search, XG adds the following information to an accept list match:
• Entity unique ID • File date • Published date
• Match state • Match date • Best DOB
You add the accept list to your predefined search. XG compares the input entity to the accept list entities to determine if an alert should be generated.
Required Inp u t En t ity Informat ion
The alert must contain specific input entity information before you can add the record to an accept list.
The alert must contain the following information:
• The input entity information must contain a name.
An alert may not contain an entity name if the input record was included in a batch file in which one of the following cases is true: • The batch file was large enough during upload to prevent missing name errors in the preview
validation from not allowing the search.
• The batch file was processed using the XG - Unstructured format. • The batch file was processed using a payment transaction format, and the match was generated
from the context text string.
• The input record must contain a unique identifier.
The accept lists use unique identifiers to find the matching accept list records. Unique identifiers can be an ID number (with the exception of group ID or provider ID) or a complete address. If an ID number was not provided in the search, then you can add an account ID in the record details of the alert and add the alert to an accept list. The complete address can be made up of at least four words or numbers in the following field combinations: • Address Line 1, City, and State • Address Line 1 and Postal Code • Address Line 1, City, and Country
Non-Un iq u e ID s A f f e ct Performanc e
The generic text or the repeated text in an ID field can cause performance issues.
For example, if you populate multiple records with the word "unknown" in the National ID field, then multiple accept list records can result as potential matches. During the search, XG finds the ID match and then must check each matching record for a matching name to rule out the match as a false positive.
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 7
CONFIDENTIAL
If your business needs require you to retain non-unique IDs, then you should consider using the Other Information field.
Optim ize d R es u lt s
Accurate data entry helps reduce the number of recurring matches.
For optimal matching, you should consider the following actions:
• Provide quality, consistent data. • Do not create or reuse IDs. • Use IDs that XG recognizes as unique IDs. • When you add an alert to an accept list, change the alert status to indicate that the record was
added.
Setting an alert status to False Positive does not automatically add the alert to an accept list.
• Add alerts for text records or alerts for payment transaction records to a different accept list for audit
purposes or business structure purposes.
• If no data is available, then leave the field empty instead of providing false data.
Matc hes T h a t A r e S u pp ress ed
XG uses accept lists to suppress recurring matches in certain situations.
To determine whether to suppress the matches, XG completes the following sequential comparisons between the input entity and the accept list entities. XG uses proprietary scoring (0-100) for the matches. The score is not a percentage. The score indicates how likely the information for the input entity matches the information for the accept list entity.
1. XG performs an ID search.
The ID number must be an exact match that returns a score of 100.
2. XG performs a name search.
The name match must return a score of 85 or higher.
3. XG performs an address search.
The address match must return a score of 85 or higher.
4. XG compares the match information from the search to the match information in the accept list
record. The entity name and the best name must be exact matches that return a score of 100.
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 8
CONFIDENTIAL
XG suppresses the matches when one of the following situations occurs:
• The input name and the input ID number match the name and the ID in an accept list record. Also, an
input ID number does not conflict with an ID number in the accept list record.
• The input name and the input address match the name and the address in an accept list record. Also,
an input ID number does not conflict with an ID number in the accept list record.
In either situation, the list match file name, the entity name, the best matching name, and the entity unique ID number must be exact matches.
If any matches are not suppressed, then XG generates an alert that contains only the remaining matches.
Matches T h at A r e No t Suppressed
XG does not suppress recurring matches in certain situations.
XG does not suppress the matches when the following situations occur:
• The information for the input entity changes in one of the following ways:
• A unique identifier changes. • The name is significantly different.
• The information for the screening list entity changes in one of the following ways:
• The entity name changes. • A new AKA that was added to the screening list entity generates a higher score than the previous
best matching name.
• The input entity information matches a new record in the screening list that was not previously added
to the accept list record.
• The input entity information matches a new screening list. • The search does not include the accept list that contains the input entity information. • The accept list match information contains an entity unique identifier, and the new match has a
different entity unique identifier.
If match updates were configured in the predefined search, then XG may generate an alert when match information changes. A true match update notifies you when the list entity information changes for a true match in an accept list record.
A false match update notifies you when new match information is found for specified data elements in the false positive, the confidence score for an intelligent match decision changes, or a new reason code is returned for the match. For a match from a custom screening list to generate a false match update, the list must be required to contain unique record IDs.
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 9
CONFIDENTIAL
Prede fin ed S e a rc h Ch anges Affec t Suppre ssion
Changes to predefined searches can affect match suppression.
The following changes to predefined searches can cause unexpected matches in future searches:
• The accept list was removed.
The accept list cannot suppress matches when the list is not included in the search.
• The score threshold for the screening list was decreased.
XG may report the matches with lower match confidence scores that previously did not meet the score threshold.
• Screening lists were added.
XG may report new matches that are found in the screening lists.
• The search options were changed.
XG may report new matches that were not found in searches that used the previous search options.
Examples of Accept List Results
Changes to future searches can affect the matches that XG reports or suppresses.
Input Data Differences
XG reports a match for the following input data:
Name: Zachary K. Thul Address: 305 Waybreeze Blvd Columbus, OH 34209 SSN (Social Security number): 960451234
You determine that the match is a false positive and add the alert to an accept list.
The following table illustrates how changes to the input data would affect the accept list results.
Input Data Changes That Affect Matches
Input Data
Result
Comments
XG suppresses the match.
The address and the middle name are not provided. The SSN is the same.
Zachary Thul 960451234
XG does not suppress the match.
The numbers in the address are out of order. The SSN was not provided.
Zachary K. Thul 503 Waybreeze Blvd Columbus, OH 34209
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 10
CONFIDENTIAL
Input Data Changes That Affect Matches (Continued)
Input Data
Result
Comments
XG does not suppress the match.
The SSN is different.
Zachary K. Thul 305 Waybreeze Blvd Columbus, OH 34209 960451235
XG does not suppress the match.
The middle name is not the same.
Zachary Adam Thul 305 Waybreeze Blvd Columbus, OH 34209
XG suppresses the match.
The address contains an extra number, but the address is not different enough.
Zachary K. Thul 3305 Waybreeze Blvd Columbus, OH 34209
XG suppresses the match.
The street name is different, but the street name contains the same words. However, the address is not different enough.
Zachary K. Thul 305 Way Breeze Blvd Columbus, OH 34209
List Data Differences
You search the following input data:
Name: ABC Company Address: 123 Main Street, Anytown, NY 12345-1111 Account ID: 00000111112222233333
XG reports a match for the following record in the Bad Business custom screening list:
Name: ABC Alphabet Corporation Address: 123 Main Street, Anytown, NY 12345 Account ID: 00000111112222233333
You determine that the match is a false positive and add the alert to an accept list.
The following table illustrates how changes to the list data would affect the matches.
List Data Changes That Affect Matches
List Data
Result
Comments
A new AKA is added to the Bad Business custom screening list: AKA: ABC Company
XG does not suppress the match.
The AKA matches better than the original entity name in the screening list record.
A new custom screening list that contains the following record is added to the search: Name: ABC Co.
XG does not suppress the match.
The input data matches the record in the new custom screening list.
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 11
CONFIDENTIAL
True Match Updates
You search the following input data using a predefined search with match decisions configured:
Name: Zach Thul Address: 305 Waybreeze Blvd 34209
XG reports a match for the following list entity:
Name: Zachary K. Thul Address: 305 Waybreeze Blvd Columbus, OH 34209
You determine that the input entity is the list entity. You select a True Match decision for the match and add the alert to an accept list to monitor the match for changes.
XG finds the following information for the list entity in a later search:
Name: Zachary K. Thul Address: 305 Waybreeze Blvd Columbus, OH 34209 Address: 406 Waybreeze Blvd Columbus, OH 34209
XG generates a new alert that contains the true match update because a second address was found.
Without match updates configured for the predefined search, you would not have been alerted to the additional address. This address may cause you to reconsider your review decisions.
True Match Update
False Match Updates
You search the following input data using a predefined search with match decisions and false match updates for DOB configured:
Name: Z. K. Thul Address: 305 Waybreeze Blvd 34209
XG reports a match for the following list entity:
Name: Zachary K. Thul Address: 305 Waybreeze Blvd Columbus, OH 34209
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 12
CONFIDENTIAL
DOB: 01/13/1955
You determine that the input entity is not the list entity. You select a False Positive decision for the match and add the alert to an accept list.
You search the input data again with a DOB of 01/13/1955.
XG generates a new alert that contains the false match update because a DOB match was found.
Without match updates configured for the predefined search, you would not have been alerted to the DOB match. This match may help you determine that this entity is a true match.
False Match Update
Wh ite L i st
The White List is designed to help you streamline the processing of recurring false positives that were generated from unparsed data.
False positives cannot be added to accept lists when the input data is not provided in well-defined parsed fields. For example, XG cannot determine whether "Libya" in unparsed data refers to a name, street, or country for standard fuzzy logic processing. Instead, unparsed data can be added to the White List. The White List uses word-for-word matching between the input name or the input context and the entity name or the AKA name in a screening list record. Input context is the text string in unparsed data that generated the match.
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 13
CONFIDENTIAL
The use of the White List affects how the list screening service finds and processes matches. The White List is a highly technical feature. LexisNexis® Risk Solutions does not support the use of the White List. You should thoroughly test the White List and use this feature with caution.
White List Processing
At a high level, White List processing involves the following stages:
1. A list screening search is performed. 2. The alert is reviewed, and a match is added as a White List record. 3. The predefined search is configured to use the White List. 4.
In repeated searches, the Automatic False Positive rules are applied to the same match.
White List in Process
To incorporate the White List into your review process, a previously-processed false positive must be added to the White List to be used in future search configurations.
Consider creating a specific predefined search to limit the use of the White List to searches of unparsed data.
In the White List record, you add an entry for each match that contains the list entity name as "match text." Each match text must be unique, or the match entry must also contain a unique screening list or a unique record identifier. For each match entry, you can set the following requirements that a match must meet:
• The screening list that contains the match text. • The record number of the screening list record that contains the match text.
The record number is the profile ID (the Number field in classic alert view) in the alert match details.
• The match confidence score range (70-100) that a match must meet.
Instead of typing the match text into the White List entry, consider copying and pasting the match text from the alert to help ensure that the White List affects the correct match. If the match text is not the same as the text in the White List entry, then the White List does not affect the match in repeated searches.
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 14
CONFIDENTIAL
If the input name or the input context matches the same entity name on multiple screening lists, then you add only one match entry. For example, the input name of "Zachary Thul," matches the following records:
• Zachary Thule on List A • Zach Thul on List B • Zachary Thule on List C
In a White List record, you enter "Zachary Thul" as the record text and "Zachary Thule" and "Zach Thul" as two match entries. You do not repeat "Zachary Thule" as a third match entry.
You configure the White List in a predefined search. The list screening service applies the Automatic False Positive rules to the matches that are generated in future searches when the following situations occur:
• The record text entry of a White List record matches the input name or the input context. • The match text entries of the same White List record exactly match the entity names on the screening lists. The match text entries also must meet any specified requirements for the screening lists, the record number, or the match confidence score range.
The Automatic False Positive rules can cause the list screening service to perform the following actions:
• Do not create an alert. • Create an alert with a closed alert state and no alert status. • Create an alert with an open alert state and an Automatic False Positive alert status.
Examples of White List Results
Input data changes can affect White List results.
You search the following input data:
Name: Alphabet Company USA
XG reports a match for the following record in the Bad Business custom screening list:
Name: ABC USA, Alphabet Co
Your organization determined that the match is a false positive and creates the following White List record:
Record Text: Alphabet Company USA Match Text: ABC USA, Alphabet Co.
The following table illustrates how changes to the input data would affect the White List results.
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 15
CONFIDENTIAL
Input Data Changes That Affect White List Results
Input Data
Result
Comments
The White List affects the match.
The name is the same.
Name: Alphabet Company USA
The White List does not affect the match.
The name contains additional characters.
Name: XXXmlwZZZ Alphabet Company USA
White List Limitations
Before you add the White List to your review process, you should understand your input data, your results, and the limitations of the White List. Also, you should consider whether the accept lists can better meet your review process requirements.
You should consider the following limitations when you use the White List:
• The White List matches record text in name fields, address fields, AKA fields, and context fields. The
White List does not support matches against other data elements.
• If the alert contains a potential match that is reported even when the name does not match, then the
White List does not cause XG to apply Automatic False Positive rules to the match.
• The White List affects the matches even if other information in the input record or the screening list records have changed. For example, an input record that contains a match on the White List and a match against a new screening list does not prevent XG from applying Automatic False Positive rules to the match.
Use the White List only after you have determined that all name matches are false positives.
FIN210-EN_US — 7 March 2024
Bridger Insight XG 5 Accept Lists and White List Page 16