Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • User Guides
  • Approvals & Disclosures
  • Integration
  • Screening Integration

What counts as Screening "Hits"?

Written by Michelle Henley

Updated at May 10th, 2024

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Home
  • User Guides
    Approvals & Disclosures Third-Party Management Compliance Monitoring
  • Integrity Gateway Configuration Guide
    Approvals & Disclosures Request Types Configurable Components FAQ
  • Service Desk FAQ
  • Release Notes
    Release Notes - Approvals & Disclosures/ Third Party Management Release Notes - Compliance Monitoring
  • Roadmap
+ More
  • User Guides

    • Integrity Gateway Configuration Guide

      • Service Desk FAQ

        • Release Notes

          • Roadmap

            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.

            screening hits ongoing screening

            Was this article helpful?

            Yes
            No
            Give feedback about this article
            Print to PDF

            Related Articles

            • Requests with Screening through LSEG (fka Refinitiv)
            • Requests with Screening through RDC
            • Ongoing Screening
            • Limiting Screening Results by Name + Country

            Knowledge Base Software powered by Helpjuice

            Expand