The alias that was the real name

Normalization

• Creditor name (Cdtr/Nm): “Arkady Selenov” → “ARKADY SELENOV” (Uppercase; no punctuation or legal-form tokens to remove.)
• List entry name set: “SELENTSOV, Arkadiy Pavlovich + 3 aliases” → “4 comparable name forms” (The primary name and every alias are normalized into the index, so a payment name is compared against the entry's full name set, not just the headline name.)

Candidates

• le-selentsov-vela: matched on Exact match against recorded alias 'Arkady Selenov' — Alias index lookup: the normalized creditor name equals one of the entry's recorded AKAs character for character.

Scores

• le-selentsov-vela: total 0.93 vs threshold 0.83 (Alias exact match 50%×100%; Alias strength 20%×90%; Country corroboration 20%×100%; Identifier corroboration 10%×50%)

Disposition

Alert generated. An exact hit on a documented full-name alias, with the account jurisdiction matching the entry's recorded country, scores 0.93 against a 0.83 threshold. This is the strongest pattern short of an identifier match and must be investigated before anything moves.

Investigation

1. Is the matched alias a genuine identity for the listed person, or a coincidental spelling? Evidence: The fictional list record documents 'Arkady Selenov' as an alternate spelling used on identity papers, not a nickname; The remaining aliases are consistent transliteration variants of the same underlying name. Finding: The alias is a strong identity marker for the listed person, not an accident of spelling.
2. Does the beneficiary's date of birth align with the list entry? Evidence: Beneficiary bank confirms the account holder's date of birth as 1979-06-23; List entry date of birth: 1979-06-23. Finding: The dates of birth match exactly.
3. Do any hard identifiers align? Evidence: The account was opened with fictional passport P7719302; The list entry records the same fictional passport number. Finding: A hard identifier ties the account holder to the list entry; this is no longer a name-similarity question.
4. Is there any indication this is a different person who shares the identifiers? Evidence: No conflicting date of birth, nationality, or address information anywhere in the case file. Finding: Nothing discounts the match; every checked attribute corroborates it.

Final: True match — escalate. Keep the payment on hold and escalate to the sanctions officer with the alias documentation, date-of-birth confirmation, and passport match. The blocking-versus-rejection decision and any regulatory filing belong to that escalation level, and the exact obligations depend on the institution's jurisdiction.