Screening Reviewer
When prompted, the screening reviewer's responsibility is to review and resolve screening matches within a request. In this article we explore expected behavior for the screening reviewer if no matches are returned from the screening provider.
- For step-by-step instructions for resolving matches, please see Requests with Screening through RDC or Requests with Screening through LSEG (fka Refinitiv)
If a screening reviewer is triggered to review and resolve possible screening matches the following rules apply:
| Possible matches are returned from the screening provider → | and the screening reviewer is unable to find a match → | then the screening reviewer is removed from the approval flow because there is no need to approve this step. |
| Possible matches are returned from the screening provider → | and the screening reviewer is able to find a match and resolve screening → | then the screening reviewer remains in the approval flow and must approve the step. |
If a submitter initiates an update on a request that retriggers screening and the possible matches change the following rules apply:
| New possible matches are returned from the screening provider → | and the screening reviewer is unable to find a match → | then the screening reviewer is removed from the approval flow because there is no need to approve this step. |
| New possible matches are returned from the screening provider → | and the screening reviewer is able to find a match and resolve screening → | then the screening reviewer remains in the approval flow and must approve the step. |
If a screening reviewer marks a party as “no match” and the party is used in another request, the following rule applies:
| The screening reviewer marks a party as “no match” in request #1 → | and the same party is used in request #2 → | then the screening reviewer is removed from the approval flow in both request #1 and request #2. There is no need to approve this step since “no match” was selected. |