Party deduplication - FYNDNA retail banking suite

Deduplication (dedupe) is the process of checking party data to ensure that no duplicate records are created for the same entity. When onboarding a new party or updating existing party data, the system must identify duplicate records that may already be present in the system.

Dedupe comprises the following processes:

Dedupe configuration - You can set up the criteria for dedupe. These parameters are used when dedupe call is executed.

Dedupe execution - You can execute this call to check whether a party already exists in the database or not.

Dedupe results - You can retrieve the result of a dedupe call where the caller gets to know whether the party is already available or not.

For example, if Driving license is set as a criterion, the system runs the dedupe call against the driving license number. In this case, the system looks for an exact match. For example, if the driving license number of the party being validated is DL1234, the system looks for parties with the same driving license number as DL1234. It narrows down on parties with the name as DL1234 in the eParty database. If there is an extra space or an extra letter or a missing letter in the string, the party is not identified as duplicate.

If the dedupe call is executed asynchronously, the dedupe results are stored against a unique identifier. You can retrieve the results later as and when you need them.