Configuring LexisNexis

LexisNexis Fenergo SaaS Settings

The following settings can be configured for LexisNexis:

• Accept List: Enable/disable the adding of resolved results to a pre-defined Accept List in LexisNexis.
• Accept List ID: Where Accept List is enabled, the LexisNexis List ID of the Accept List that results should be added to the Configured Set required. The Accept List ID must be provided by LexisNexis. Note that when setting up an Accept List for the first time, it must have at least one record added to it before it can be subsequently added to a Predefined Search.
• Predefined Search (PDS): The LexisNexis PDS that should be used for screening searches. This is used to call the appropriate configuration from LexisNexis.

For further information on any of the specific settings mentioned above, please consult your LexisNexis documentation or contact your LexisNexis administrator.

LexisNexis Vessel Screening

To enable vessel screening using LexisNexis in Fenergo SaaS, the following field configuration must be applied for Company entities.

Subtype

• The "Subtype" field is used to identify vessels as a distinct entity type.
• Ensure the Datakey is an exact match with "subtype".
• Set the value to "vessel".
• This field should be configured in the Basic Details section for Company (and/or Other) entity types.
• When Subtype is set to "vessel", the IMO Number field will be displayed automatically.

UniqueId (IMO Number)

• The "UniqueId" field is intended to capture the vessel’s IMO Number.
• Ensure the Datakey is exactly "uniqueId". (Refer to the Secondary Identifiers section for further context.)
• Place this field in the Basic Details section for Company (and/or Other) entity types.
• If the IMO Number is populated, it will be included in the Search Criteria during screening.
• In the Screening Results, the IMO Number appears as the "Unique ID".
• Hits from LexisNexis vessel screening are displayed in the same format as other Company entity hits.

LexisNexis Configurable fields via API

The Screening API allows configuration of specific fields, similar to the PDS, within Screening Configuration. These configurable fields are as follows:

• Division
• RolesOrUsers
• True Match Alert Status
• False Positive Alert Status

If no custom values are configured, the system will default to the following values:

• Division: Default Division
• RolesOrUsers: Administrator
• True Match Alert Status: True Match
• False Positive Alert Status: False Positive

To incorporate these fields into the configuration sets, users should utilize the following API endpoint to update the settings schema:

PUT /screeningcommand/api/v2/configuration/provider/{providerId}/settings-schema HTTP/1.1

With the following request body:

{
  "data": {
    "additionalSettingsSchema": [
        {
            "fieldId": "AcceptListActive",
            "name": "Accept List",
            "type": "Toggle",
            "enabledBy": "",
            "mandatory": false
        },
        {
            "fieldId": "AcceptListId",
            "name": "Accept List Id",
            "type": "TextInput",
            "enabledBy": "AcceptListActive",
            "mandatory": true
        },
        {
            "fieldId": "PredefinedSearchName",
            "name": "Predefined Search Name",
            "type": "TextInput",
            "enabledBy": "",
            "mandatory": true
        },
        {
            "fieldId": "Division",
            "name": "Division",
            "type": "TextInput",
            "enabledBy": "",
            "mandatory": false
        },
        {
            "fieldId": "RolesOrUsers",
            "name": "RolesOrUsers",
            "type": "TextInput",
            "enabledBy": "",
            "mandatory": false
        },
        {
            "fieldId": "TrueMatchAlertStatus",
            "name": "True Match Alert Status",
            "type": "TextInput",
            "enabledBy": "",
            "mandatory": false
        },
        {
            "fieldId": "FalsePositiveAlertStatus",
            "name": "False Positive Alert Status",
            "type": "TextInput",
            "enabledBy": "",
            "mandatory": false
        }
    ]
  }
}

After applying the configuration, the new fields will be visible in the configuration set.

LexisNexis Configuration Pre-Requisites

In instances where specific fields have not been configured, as detailed in the preceding section, there are a number of settings that must be configured in a pre-defined manner in LexisNexis for the integration to work as expected. Most of these should already be in place with a baseline LexisNexis configuration.

Please ensure that the following configuration has been properly set up in LexisNexis before proceeding with the configuration in Fenergo SaaS.

1. A Role called Administrator must exist in the Roles configuration.

   

2. A Division called Default division must exist in the Division configuration.

   

3. The LexisNexis UserID that is being used must have the Administrator role and the Default division assigned to it.

   

4. The Predefined Search being used must have the Administrator role and the Default division assigned to it.

   

5. Alert Statuses called True Match and False Positive must exist in the Alert Status configuration.

   

6. If an Accept List is being used, this must be created in the List Management configuration and must be added to the Predefined Search being used. The Accept List ID will have to be provided by your LexisNexis Administrator.

   

LexisNexis Address Types

For screening purposes, all addresses must be captured in the Addresses Data Group.

• Residential and Business address types are supported for Individual entities in LexisNexis screening.
• Up to two addresses can be included in a single screening request.
• The two addresses may be any combination of Residential and/or Business (e.g., Residential + Business, Business + Business, or Residential + Residential).

If multiple addresses are captured:

• If both address types are sent (e.g. two Residential and two Business), the system will send one Residential and one Business address.
• If only one address type is captured (e.g., three Residential or three Business), the system will send the first two of that type.

Company Entities

• Only one address is supported.
• The address must be of type Registered.

Configuration Required — LexisNexis

• To ensure a second address is sent to LexisNexis as part of OGS, update the Individual LexisNexis Batch Format to include a second address type.
  Refer to the Batch Formats section below for instructions on this.
• The LexisNexis address types must be different, for example:
  • First address: Current Address
  • Second address: Mailing Address
• Ensure that the Automatic Batch is updated with the revised Batch Format (as described in the Automatic Batch section below).

Configuration Required — Fenergo

• Add Business to the Address Type Reference Data List to enable this address type.

LexisNexis Ongoing Screening Configuration

Ongoing Screening is supported in LexisNexis using the Automatic Batch process and the Accept List. The Automatic Batch process must first be configured in the LexisNexis Bridger portal. If the Batch Format is not configured as described below, OGS will not function. For further information on any of these subjects please consult your LexisNexis documentation or contact your LexisNexis administrator.

Batch Formats

In Bridger, configure a Batch Format by navigating to Batch | Batch Formats.

A separate Batch Format should be configured for Individual and Company entity types.

Within each Batch Format, set the Field Delimiter to "Pipe".

1. Individual

i. Upload the file BatchFormatIndFull or BatchFormatIndFirstLast depending on whether you want to use the Full Name or First Name and Last Name for screening.

ii. Choose a name for the Batch Format and select the values as per the following image:

iii. Set the field mappings* as follows:

For Full Name screening:

Fenergo SaaS Field	LexisNexis Field
Legal Entity ID	ID Numbers: AccountID: Number
Full Name	Name: Full Name
Date of Birth	Date of Birth
Gender	Gender
Address Line 1	Address: Current Address: Address Line 1
Address Line 2	Address: Current Address: Address Line 2
City	Address: Current Address: City
Postal Code	Address: Current Address: Postal Code
Country	Address: Current Address: Country
State Province	Address: Current Address: State
Address2 Line 1	Address: Mailing Address: Address Line 1
Address2 Line 2	Address: Mailing Address: Address Line 2
City	Address: Mailing Address: City
Postal Code	Address: Mailing Address: Postal Code
Country	Address: Mailing Address: Country
State Province	Address: Mailing Address: State
Nationality	Additional Information: Nationality
Place Of Birth	Additional information: Place of Birth
Citizenship	Citizenship
Other Information	Other Information
Passport Number	ID Numbers: Passport: Number
SSN	ID Numbers: SSN
Driver's License	ID Numbers: Driver's License

info

Note that two LexisNexis fields, ID Number and Phone Number do not have a corresponding Fenergo field, and can be set to (none) in Bridger.

These are the additional mappings for First Name and Last Name screening:

Fenergo SaaS Field	LexisNexis Field
First Name	Name: First Name
Middle Name	Name: Middle Name
Last Name	Name: Last Name

2. Company

i. Upload the file BatchFormatComp

ii. Choose a name for the Batch Format and select the values as per the following image:

iii. Set the field mappings* as follows:

Fenergo SaaS Field	LexisNexis Field
Legal Entity ID	ID Numbers: AccountID: Number
Legal Entity Name	Name: Full Name
Address Line 1	Address: Current Address: Address Line 1
Address Line 2	Address: Current Address: Address Line 2
City	Address: Current Address: City
Postal Code	Address: Current Address: Postal Code
Country	Address: Current Address: Country
State Province	Address: Current Address: State
Other Information	Other Information
EIN	ID Numbers: EIN

info

Note that two LexisNexis fields, ID Number and Phone Number do not have a corresponding Fenergo field, and can be set to (none) in Bridger.

Automatic Batch

In Bridger, configure an Automatic Batch batch using Batch | Automatic Batch.

This specifies:

• The name of the template e.g. “Clients (Individuals)”;

• The batch format created earlier;

• The Division, if appropriate, that will have access to this Automatic Batch;

• The Predefined Search that is to be used;

  • Ensure that the Predefined Search being used has an Accept List enabled.

• How any Alerts are to be distributed;

• How the screening process is to be activated;

  • Select ‘File Transfer’

• How selected users, or users of the selected role, will be alerted to Alert assignments;

• Whether the batch results are to be output to a file;

  • Select the values as per the following image:

• Upload the PGP Public Encryption Key as provided by your Fenergo SaaS administrator.

info

Batch runs will be created in Lexis Nexis with the following format: Fenergo_Ogs_<tenantName>_<Individual/Company>_<YYYYMMDD>_<unique_identifier>

Fenergo SaaS Ongoing Screening

In Fenergo SaaS, navigate to the LexisNexis configuration page in the Screening section of Fenergo SaaS and enter the following values:

1. Ongoing Screening: Set to Active.
2. SFTP Upload Domain, Username and Password: These values can be provided by your LexisNexis administrator. Please note that LexisNexis Password expires every 90 days.
3. SFTP Upload Folder: This can be obtained by connecting to the FTP server. Please note, it must contain the full file path, and there must be no spaces in the folder names.
4. SFTP Download Domain, Username and Password: These values can be provided by your LexisNexis administrator.
5. SFTP Download Folder: This can be obtained by connecting to the FTP server. Please note, it must contain the full file path, and there must be no spaces in the folder names.
6. Public Key, Decryption Key, Decryption Password: These values can be provided by your Fenergo SaaS administrator.

Understanding PGP Keys in the OGS Process

As part of the OGS process with LexisNexis, two different types of PGP keys are used to ensure secure file transfers between Fenergo and LexisNexis. These keys serve different purposes and are managed by different parties.

This guide will help clarify the difference between:

1. Upload Keys (used to send files to LexisNexis)
2. Download Keys (used to receive files from LexisNexis)

PGP Upload Keys – Managed by LexisNexis (Updated Annually)

Purpose: These keys are used when Fenergo sends client's entity lists to LexisNexis for screening.

How it works:

• Fenergo encrypts files using a Public Encryption Key provided by LexisNexis.
• LexisNexis decrypts it using their Private Key + Password.
• The public key is specific to each client's LexisNexis account, and is updated annually.
• LexisNexis notifies clients when they need to update the key each year and provides instructions on how to download it.

What clients need to do:

• Follow the instructions in the LexisNexis email to obtain the Upload Key.
• Format the key by copying it into a notepad, highlighting one of the line breaks and replacing all line breaks with \n, ensuring that the key is in a single line format.
• Update the key in the LexisNexis configuration page of the Screening Provider Configuration section of Fenergo SaaS.
• Refer to this video for guidance on formatting the PGP key:

2. PGP Download Keys – Managed by Fenergo (Updated Every 2 Years)

Purpose: These keys are used when LexisNexis sends screening results back to Fenergo.

How it works:

• LexisNexis encrypts results using the Public Key provided by Fenergo.
• Fenergo decrypts the results using a matching Private Key + Password.
• Clients will receive the following files from Fenergo every 2 years:
  • PGP Public Encryption Key
  • PGP Decryption Key
  • PGP Decryption Password

What clients need to do:

On the same day, complete the following steps in LexisNexis Bridger:

1. Log in and go to Batch > Automatic Batch.
2. Click into each active batch.
3. In the File Output section, upload the PGP Public Encryption Key file provided by Fenergo.
4. Click Save.

In Fenergo:

1. Go to Screening Provider Configuration > LexisNexis > Ongoing Screening.
2. Paste in the:
   • PGP Decryption Key
   • PGP Decryption Password
3. Click Save & Test.

When to do it:

• This update is required once every two years.
• The current update was completed by 30 April 2025.

Multiple Configuration Sets and Ongoing Screening Pre-Requisites

When using multiple configuration sets and ongoing screening, several aspects need to be considered to support ongoing screening:

• All predefined searches must utilize the same Accept List.
• Accept List must be enabled/disabled consistently across all configuration sets.
• For on-demand screening, multiple LexisNexis Predefined Screening (PDS) Lists can be configured, however for Ongoing Screening only one PDS list with the aggregation of all screening lists (Default configuration set) can be used.

Ongoing screening journeys use the Default configuration set. For this reason, we require all configuration sets to share the aforementioned settings.

Other Information Secondary Identifier:

When ongoing screening lists need to be segregated, the "Other Information" Secondary Identifier field can be sent to LexisNexis and used to create IMDS rules for ongoing screening across multiple lists, while allowing Fenergo SaaS to continue to use a single batch file combining all PDS lists.

In order to enable this, navigate to the Screening Provider Configuration and select the "Other Information" field under the Common section in the Secondary Identifiers for LexisNexis.

In addition, the Fenergo SaaS Datakey must exactly match the value specified in Column C of the Secondary Identifier Mapping Document ("otherInformation"). Further details on Secondary Identifier Configuration can be found in the Configuring Screening Functionality section of the User Guide.

Key Considerations:

• Default Configuration Remains Unchanged – The ongoing screening process will continue using a single batch file (one for Individual and one for Company) that combines all PDS lists, with the "Other Information" field integrated as part of the search criteria.
• Custom Providers – If needed, this field can also be used to send information to custom providers.