A screening name match was treated as established identity

If a customer screening system finds a similar name on a restrictions list, an employee may treat the alert as a confirmed match. Transliteration, namesakes and incomplete records require comparison of further identifiers. A typical review concerns a screening record whose decision rests solely on a high name similarity score.

What needs to be clarified

Reconstruct the alert's basis, compare available customer and list identifiers, review the recorded decision and identify matters requiring further checks by the organization's responsible department.

Materials to prepare

Alert record naming the list, database version and search settings
Customer identification documents and the original spelling of the name
Complete list entry and staff log of the match review

What to compare

Identify the list behind the alert and the fields actually searched. Compare the full name, spelling variants, date of birth and available documentary identifiers. Distinguish conflicting information from missing information; assess whether the employee explained the transition from automated similarity to a decision on this particular match.

Possible outcome of the analysis

A table may separate matching, differing and unchecked attributes, examine the decision's reasoning and list clarifications needed to complete the internal review on the supplied materials.

Limits of the conclusions

Name similarity does not establish identity. The review does not replace applicable AML or sanctions controls, promise release of a transaction or exempt anyone from mandatory checks.