How to check and verify the exact user from caseScreeing results

mallinathan.saranyes
mallinathan.saranyes Explorer
in World-Check One

Hi,

We are getting multiple profiles in response for a case when caseScreening. what we understood is matchStrength = EXACT is according to the name only, if the name matches. It is not considering all the secondaryFields. Is that true? How to identify a particular user in response with all the secondaryFields (DOB and Nationality). Do we have to check "Matched" for all the secondaryFieldResults? In our request DOB was 1950-09-27 but response is showing matched with DB value 1950-09-17. Please explain.

We want to check a user according to his first name, last name, Date of birth and nationality. What should be our request?

Request :

<Request><caseId>Narendra2</caseId><entityType>INDIVIDUAL</entityType><groupId>0a3687d0-6542-1714-9956-ef630000020c</groupId><name>Narendra Modi</name><secondaryFields><typeId>SFCT_2</typeId><dateTimeValue>1950-09-27</dateTimeValue></secondaryFields><secondaryFields><typeId>SFCT_3</typeId><value>IND</value></secondaryFields><secondaryFields><typeId>SFCT_4</typeId><value>IND</value></secondaryFields><secondaryFields><typeId>SFCT_5</typeId><value>IND</value></secondaryFields><providerTypes>WATCHLIST</providerTypes></Request>

Response:

<?xml version="1.0"?>
<string>{"caseId":"Narendra2","results":[{"resultId":"0a3687d0-65b4-1d30-9999-b5a800323d36","referenceId":"e_tr_wci_54817","matchStrength":"EXACT","matchedTerm":"MODI,Narendra","submittedTerm":"Narendra Modi","matchedNameType":"AKA","secondaryFieldResults":[{"field":{"typeId":null,"value":null,"dateTimeValue":"1950-09-17"},"typeId":null,"submittedValue":null,"submittedDateTimeValue":"1950-09-27","matchedValue":null,"matchedDateTimeValue":"1950-09-17","fieldResult":"MATCHED"},{"field":{"typeId":null,"value":"IND","dateTimeValue":null},"typeId":null,"submittedValue":"IND","submittedDateTimeValue":null,"matchedValue":"IND","matchedDateTimeValue":null,"fieldResult":"MATCHED"},{"field":{"typeId":null,"value":null,"dateTimeValue":null},"typeId":null,"submittedValue":"IND","submittedDateTimeValue":null,"matchedValue":null,"matchedDateTimeValue":null,"fieldResult":"UNKNOWN"},{"field":{"typeId":null,"value":"IND","dateTimeValue":null},"typeId":null,"submittedValue":"IND","submittedDateTimeValue":null,"matchedValue":"IND","matchedDateTimeValue":null,"fieldResult":"MATCHED"},{"field":{"typeId":null,"value":"IND","dateTimeValue":null},"typeId":null,"submittedValue":"IND","submittedDateTimeValue":null,"matchedValue":"IND","matchedDateTimeValue":null,"fieldResult":"MATCHED"}],"sources":["b_trwc_PEP N"],"categories":["PEP"],"creationDate":"2018-10-12T05:53:53.951Z","modificationDate":"2018-10-12T05:53:53.951Z","primaryName":"Narendra Damodardas MODI","events":[{"day":17,"month":9,"year":1950,"address":null,"fullDate":"1950-09-17","allegedAddresses":[],"type":"BIRTH"}],"countryLinks":[{"countryText":"INDIA","country":{"code":"IND","name":"INDIA"},"type":"NATIONALITY"},{"countryText":"INDIA","country":{"code":"IND","name":"INDIA"},"type":"LOCATION"}],"identityDocuments":[{"entity":null,"number":"AAHPM8993N","issueDate":null,"expiryDate":null,"issuer":null,"type":null,"locationType":{"type":"IN-PAN","country":{"code":"IND","name":"INDIA"},"name":"PERMANENT ACCOUNT NUMBER (INCOME TAX INDIA)"}}],"category":"POLITICAL INDIVIDUAL","providerType":"WATCHLIST","gender":"MALE"}...........

Tagged:

Best Answer

  • Prabhjyot
    Prabhjyot LSEG
    Answer ✓

    @mallinathan.saranyes,

    That's correct. The date of birth is showing as 'MATCHED' due to the auto-resolution toolkit settings. If the secondry field value specified in the request is -/+ 2 years, it will show in the results and the "fieldResult":"MATCHED" would be displayed. If the value specific in the secondary field is more than -/+ 2 years, then fieldResult":"NOT_MATCHED" and the profile would be auto resolved as False, due to the fact that the value entered does not satisfy the criteria of the auto-resolution toolkit.

    You can check the auto-resolution toolkit settings from the UI.

    Hope this clarifies your concern.

Answers

  • Prabhjyot
    Prabhjyot LSEG

    @mallinathan.saranyes,

    Thank you for the query.

    When you pass the details of the entity to World-Check, our system fetches the matched profiles from the database, which can be further determined based on the details provided while initial screening.

    Like, if the name of the screened entity is exactly matching a World-Check profile, it can be identified with the value "matchStrength":"EXACT". Similarly, World-Check also looks for the secondary fields which have been provided in the initial screening and if the values of the secondary field matches to that of the database, they will return "fieldResult":"MATCHED" for the specific secondary field.

    Hope this clairifes your concern.

  • mallinathan.saranyes
    mallinathan.saranyes Explorer

    Hi @Prabhjyot,

    Thank you for your response. So that means to find any particular user in Database we will have to check "Matched" fields of secondaryFields as well because name can be same for various users?

    Also, as mentioned before in above example why Date of Birth is showing matched when entered date is different than that of db response date?

Categories