Ongoing Screening
Once applied, ongoing screening allows screening results to be applied to a recipient or Third Party as soon as they are available from RDC or LSEG (fka Refinitiv).
Note: Ongoing screening must first be configured for your organization. There are two options for configuration. Click below to expand the instructions for your organization's configuration:
Option #1: In-Request Ongoing Screening
All Individuals and Organizations who are added to a request and initially screened are automatically entered into ongoing screening. Disabling ongoing screening is done by uploading a template through the bulk screening feature.
If your organization is configured to automatically put parties into on-going screening, ongoing screening will begin once a party is used in a request.
Anytime new screening results for this party are available, an email will be sent to the approver who originally resolved the match to alert them that new screening results are applied and the match will need to be resolved again.
The user can then view the results through the link in the email, or through the Screening link in the left navigation bar.

When searched, the screening results for the party who is subject to ongoing screening will be displayed with an Ongoing Screening icon in the far left column.

The Last Update column displays the last date that either screening results were returned, or screening results were resolved.

Returned Results from Ongoing Screening
| Screening Results | Description | Action |
|---|---|---|
| No Results | During the initial screen or ongoing screens, no results have been returned for the screened party. | No action is needed. |
| Potential Match | The party has been previously screened, but there are now new potential matches. | The party must be resolved again. |
| Match | The party has been previously screened and the match has previously been resolved. They are subject to ongoing screening, however, no new screening results exist. and no action is needed. | No action is needed. |

When the approver clicks Resolve to review new potential matches, any new results are displayed with the following statuses:
| Profile Status | Description |
|---|---|
| New | New profile returned for the screened party. |
| Updated | Updates to the existing profile returned for the screened party. |
| Reviewed | Previous results for the screened party that were already reviewed. |

From here, the approver can resolve the match again. Once the match is resolved, any New or Updated profile status will change back to Reviewed.
Further information regarding Ongoing Screening:
If in-request screening is enabled without ongoing screening (OS) then the following rules apply:
- The party will be screened in the initial request and rescreened each time they are added to a subsequent request. After initial screening or rescreening, OS will not be turned on for the party in requests.
If in-request screening is enabled with ongoing screening (OS) then the following rules apply:
- Any party who has not already been screened, will be screened in the first request, then entered into OS where the system will wait for updates for this party.
- Any party who has already been screened, will not be rescreened when they are added to a subsequent request. The system will wait for OS updates for this party.
Option #2 Ongoing Screening through Bulk Screening
Individuals and Organizations are uploaded through the bulk screening feature, where ongoing screening can be turned on and off.
Access Screening
To access Screening, click on the link from the left navigation menu.
Note: The Resolve Screening privilege is needed before a user can access Screening.

Once Screening is clicked, the user will be redirected to the Screening page. Click, Bulk Screening.

Once clicked, a Bulk Screening pop-up box will open.
Screening Template
In order to start Ongoing Screening for an Individual or Organization, the user must use the Screening Template to upload their list of parties into the Bulk Screening application.

The template file must be completed correctly in order for the system to initiate ongoing screening for the selected parties.
Required Fields:
- Lextegrity ID (required only for existing parties)
- Name field
- Is Organization?
- Screening Option
- Country
Select Ongoing from the dropdown in Column D for each party you wish to begin ongoing screening.

Master Data Export
To aid in obtaining a list of parties who need to be screened or to obtain the Lextegrity IDs, a user can also export a list from Master Data by clicking Master Data Export on the Screening page.

Users can select one or more options between Organizations, Individuals (non-employee), or Individuals (employees). Next, click Download. Results are returned in a .xlsx file.

Uploading your Template
Once your Screening Template file is ready to upload, click Upload Completed Template.

If the uploaded template file is not completed correctly, an error message will be displayed.
If you are having trouble uploading your file see: Why is my Bulk Screening template rejected?

Once the file is correct, the system will accept it. Next, click Screen to continue.

By clicking Screen in the Bulk Screening pop-up window, the system will:
- Send the data to the Screening Server who then sends the data to the Screening Provider.
- Add an Ongoing Screening event to Screening History.
Additionally, a pop-up box will open to confirm how many parties have been screened.

Screening Results
When searched again, the screening results for the screened party will be displayed with an Ongoing Screening icon in the far left column.

The Last Update column displays the last date that either screening results were returned or screening results were resolved.

Returned Results from Ongoing Screening
| Screening Results | Description | Action |
|---|---|---|
| No Results | During the initial screen or ongoing screens, no results have been returned for the screened party. | No action is needed. |
| Potential Match | The party has been previously screened, but there are now new potential matches. | The party must be resolved again. |
| Match | The party has been previously screened and the match has previously been resolved. They are subject to ongoing screening, however, no new screening results exist. and no action is needed. | No action is needed. |

When the approver clicks Resolve to review new potential matches, any new results are displayed with the following statuses:
| Profile Status | Description |
|---|---|
| New | New profile returned for the screened party. |
| Updated | Updates to the existing profile returned for the screened party. |
| Reviewed | Previous results for the screened party that were already reviewed. |

From here, the approver can resolve the match again. Once the match is resolved, any New or Updated profile status will change back to Reviewed.
FAQ
Email Notifications for Ongoing Screening
The system sends email notifications if the Ongoing Screening provides new results for a party or if certain profiles that are matched for a party are updated. Below is a summary of what emails are sent and to whom.
In-Request Ongoing Screening
All users (reviewers, approvers, and approver collaborators) with the resolve screening privilege who are assigned to a request will receive the following notifications when updates to ongoing screening are available:
- If the party has No Match confirmed from prior review, → The email notification should be sent to the screening reviewers only when a screening provider has new matched results.
-
If the party has A Match confirmed from a prior review, → The email notification should be sent to the screening reviewers only when there are:
- updates in the matched profile, or
- new matched results from a screening provider.
- If the party has No Results from the screening provider, → The email notification should be sent to the screening reviewers when any new matched results from a screening provider are found.
Ad-Hoc & Bulk Screening
Both the user who initiates the ongoing screening and the user (if different) who resolves the first match will receive the following notifications when updates to ongoing screening are available:
- If the party has No Match confirmed from prior review, → The email notification should be sent to the screening reviewers only when a screening provider has new matched results.
-
If the party has A Match confirmed from a prior review → The email notification should be sent to the screening reviewers only when there are:
- updates in the matched profile, or
- new matched results from a screening provider.
- If the party has No Results from the screening provider, → The email notification should be sent to the screening reviewers when any new matched results from a screening provider are found.
How often does the system check for updates for Ongoing Screening?
RDC - RDC informs our system when there are updates.
LSEG (fka Refinitiv) —Our system checks for updates daily. However, tenants can change the ongoing screening frequency via the LSEG UI (it's daily by default). If a tenant changes the frequency to weekly, then only one daily API call per week will return updates. The other six calls to the API per week will return nothing and, as a result, will be ignored by our system.
How do I disable ongoing screening for selected parties?
In order to disable Ongoing Screening for an Individual or Organization, the user must use the Screening Template to upload their list of parties into the Bulk Screening application.

The template file must be completed correctly in order for the system to disable ongoing screening for the selected parties.
Required Fields:
- Lextegrity ID
- Name field
- Is Organization?
- Screening Option
- Country
Select Disable Ongoing from the dropdown in Column D for each party you wish to disable.

Master Data Export
To aid in obtaining a list of parties or to obtain the Lextegrity IDs, a user can export a list from master data by clicking Master Data Export in the Screening page.

Users can select one or more options between Organizations, Individuals (non-employee), or Individuals (employees). Next, click Download. Results are returned in a .xlsx file.

Uploading your Template
Once your Screening Template file is ready to upload, click Upload Completed Template.

If the uploaded template file is not completed correctly, an error message will be displayed.
If you are having trouble uploading your file see: Why is my Bulk Screening template rejected?

Once the file is correct, it will be accepted by the system. Next, click Screen to continue.

By clicking Screen in the Bulk Screening pop-up window, the system will:
- Remove the selected parties from ongoing screening.
- Add an Ongoing Screening event to Screening History.
Additionally, a pop-up box will open to confirm how many parties have been removed from screening.

Screening an Individual by an Alternative Name
All screening results for Individuals are based off of the full name field Full Name located in Master Data. If there is a scenario where a user would like the screened party to be screened from the Alternative Name, the Alternative Name must be moved to the Full Name field by the Master Data Admin.

If a name is changed in Master Data and the Individual (or Organization) is already subject to ongoing screening, the party must be disabled and readded to Ongoing Screening.
Ongoing Screening Results from RDC without Risk ID
Once ongoing screening has been enabled through RDC, subsequent alerts may include matches “without Risk ID.”
A user (with the Resolve Screening privilege) is able to select the Alert (without the Risk ID) from the Ongoing Screening as a Match in the following cases:
- If the initial screening has been performed with the No Results screening status.
- If the initial screening matches have been resolved with the Not a Match screening status
- If the initial screening returned Possible Matches, but the matches have not yet been Resolved.
If a user (with the Resolve Screening privilege) selected an Alert (without the Risk ID) from the Ongoing Screening as a Match, the screening status will be changed to Matched.
If a screened party was previously resolved with Match as the screening status, Alerts (without the Risk ID) are disabled and cannot be used to resolve the match.

What counts as Screening “Hits?”
What counts as Screening
Both RDC and LSEG (fka Refinitiv) count screening “hits” in production environments as outlined below.
| Type | Screening Trigger | Counted as a New Screening Hit | Not Counted as a New Screening Hit |
|---|---|---|---|
| In-Request Screening | A party is screened for the first time within a request | X | |
| In-Request Screening | A party is re-screened within the same request or a subsequent request. | X | |
| In-Request Screening → Ongoing Screening | A party was already screened within a request and is then entered into Ongoing Screening. In this case, only the initial In-Request screen is counted. Subsequent “ongoing” screens are not counted. * | X | |
| Ad-Hoc | A party is screened using ad-hoc screening functionality. | X | |
| Ad-Hoc → Ongoing Screening | A party was already screened using ad-hoc screening functionality, and then entered into Ongoing Screening. In this case, only the initial ad-hoc screening is counted. Subsequent “ongoing” screens are not counted. * | X | |
| Bulk Screening | A party is screened using bulk screening functionality. | X | |
| Bulk Screening → Ongoing Screening | A party was already screened using bulk screening functionality, and then is entered into Ongoing Screening. In this case, only the initial bulk screening is counted. Subsequent “ongoing” screens are not counted. * | X |
*If Ongoing Screening is turned ON after a customer initially goes live, any previously screened party who is screened again as part of Ongoing Screening will be counted as a new hit. Subsequent “ongoing” screens are not counted.
Note: Screening hits in stage environments do not count. Test credentials are used in lower environments for both RDC and LSEG.
LSEG- Do bulk screening results from the LSEG app reflect in the Integrity Gateway?
If a party is screened and remediated within the LSEG UI, those remediations are not reflected in the Integrity Gateway and vice versa. Any party this is remediated in our system does not flow back the the LSEG app.