Potential Match Tasks Created With Score of 0.8 and Above

The following are the scenarios where a task with a score above 0.8 would be created.

Incoming and Existing Identities Match the Same Reference Document

If the score of incoming identity + referential data compared to existing identity is greater than 0.8, Verato checks to see if there is a penalty when comparing the incoming identity and existing identity head-to-head. If a penalty is found, the identities are not linked. Instead, a task is created but uses the score for incoming identity + referential data compared to the existing identity, which will be greater than 0.8.

Incoming and Existing Identities Match Different Reference Documents

If the score of incoming identity + referential data compared to existing identity is greater than 0.8, but because the reference documents are conflicting, Verato only links them if the incoming identity and existing identity are compared without the reference document score greater than 0.8.

If the comparison of the incoming and existing identities without reference document scores is below 0.8, Verato won't link them. Instead, Verato creates a task with the score of incoming identity + referential data compared to the existing identity, which is greater than 0.8.

Existing Incoming Identity had an MCM Penalty when Matched to the Reference Document

The new incoming posted identity gets a reference document match.  If the score of incoming identity + referential data compared to existing identity is greater than 0.8, but because the existing identity had an MCM penalty when it was compared to the reference document, Verato errs on the side of caution and only links if the comparison of incoming identity and existing identity without reference document scores above 0.8.

If the comparison of incoming identity and existing identity without reference document scores below 0.8, Verato won't link them but instead will create a task, with the task score being the score of incoming identity + referential data when compared with the existing identity, which will be greater than 0.8.

Tasks Created Due to the "Do-Not-Link" Rule

If two source+nativeIds were unlinked using the UI or the unlinkIdentities API call, the product creates a "do-not-link" rule between the respective source+nativeIds. This rule prevents any incoming record from bridging the source+nativeIDs in one linkID. If any incoming record is matched to both the source+nativeIDs above the match threshold, Verato creates a Potential Match Same Source/Potential Match Cross Source task requesting the steward to take action and confirm if the respective identities should be linked.

Details

There are three cases where Verato creates a task with a score recorded greater than or equal to 0.80 within the UI. These cases are driven by additional rules designed to prevent and protect against potential false positive matches.

Incoming and Existing records align to the same Reference Database ID, but get a penalty

• The existing record A:1 in Verato matched to Verato Reference ID C1.
• The incoming record B:2 also matched to Verato Reference ID C1 as it has the name Juan also in it. And the combined data from B:2 and Verato Reference ID C1 scores above 0.8 against the existing record A:1.

To be cautious, Verato also compares B:2 and A:1 against each other, and this comparison returns a penalty (a twin penalty or a parent/child penalty, for example) that reduces the matching score. In this case, we do not link B:2 with A:1 as the score is pushed below in the task range (0.7-0.8) due to a penalty. B:2 goes into a new link ID and this creates a task but that task is recorded with the highest score it received in the matching process, which is greater than or equal to 0.80.

The existing link entity finds Multiple Conflicting Matches in the Reference data

• Existing record A:1 in Verato is not matched to any Verato Reference ID because when we tried to match it to the Reference database, it matched to more than 1 Reference ID. So, we might suspect record A:1 contains commingled data and represents more than 1 person.
• The incoming record B:2 matches Reference ID C1. The combined data from B:2 and its Reference ID C1 scores above 0.8 against the existing A:1 record.

To be cautious, Verato also compares B:2 and A:1 against each other, and this comparison scores below 0.8 as you only have Last Name and DOB in common, with a different First Name and Address. In this case, we do not link B:2 with A:1. Instead, it goes into a new LinkID, and we create a task. The recorded task score is greater than 0.8 received when the reference identity data was factored in during the matching process.

Incoming and Existing records augment to diff Reference Database IDs

• Existing record A:1 in Verato matched to Verato Reference ID C1.
• The incoming record B:2 matched to Verato Reference ID C2. And the combined data from B:2 and Verato Reference ID C2 scores above 0.8 against the existing record A:1.

To be cautious, Verato also compares B:2 and A:1 against each other, and this comparison scores below 0.8 as you only have First Name, Last Name and DOB in common, with a different Address. In this case, we do not link B:2 with A:1. A:1 and B:2 receive different LinkIDs and a task is created, recorded with the highest score it received in the matching process, which is greater than or equal to 0.80.