Overview
In the FenX RDC Screening Match Resolution task, hits are sometimes not displayed under Current Hits. Instead, results only appear under the History tab, even for first-time screenings, secondary screenings, new connected parties, and changes to connected party details.
This article explains why this happens and how to verify whether the screening provider is returning results correctly.
How Fenergo Screening Works
Entities added for screening via the Screening task are placed in a Batch. The Batch ID is sent to GRID, which processes each entity based on the search criteria defined in the JSON request.
Once GRID completes processing, the results are returned to FenX and displayed in the Screening task exactly as received. Fenergo does not modify or filter the provider response.
Why Results May Not Appear Under Current Hits
GRID returns matches based on a combination of First Name, Last Name, and Country. If any of these values do not match an entry in the GRID dataset, no results are returned regardless of other fields such as Date of Birth.
The table below shows this behaviour using test data.
Scenario Testing
Add related parties (RPs) with the data below and observe the screening results.
Scenario | First Name | Last Name | Country | Date of Birth | Result |
1 | Donald LEM | Trump LEM | Tunisia | 01/01/1992 | No matches |
2 | Donald | Trump LEM | Tunisia | 01/01/1943 | No matches |
3 | Donald | Trump | Tunisia | 01/01/1943 | No matches |
4 | Donald | Trump | United States of America | 01/01/1992 | Matches returned |
5 | Donald | Trump | United States of America | 01/01/1943 | Matches returned |
Root Cause
Scenarios 1 to 3 return no matches because the name or country values do not exist in the GRID dataset as entered. GRID requires an exact match on First Name, Last Name, and Country to return results. Date of Birth does not affect whether results are returned.
Scenarios 4 and 5 return matches because all three values align with a known GRID entry.
Resolution Steps
Confirm that the First Name, Last Name, and Country values on the entity match the format expected by the screening provider.
Check the GRID JSON request payload to verify the search criteria being sent. See the Capturing Journey Instance API Responses article for guidance on how to retrieve this.
If no results are returned for a valid entity, raise a case with GRID support and include the Batch ID and the JSON request/response for the affected screening run.
If results appear only in the History tab and not under Current Hits, check whether a previous screening run for the same entity has already consumed the results. Each hit is displayed only once under Current Hits.