Tatyana Orlov applies for a personal account. Her name looks like nine entries on the sanctions list. Eight of them are other women called Tatiana, with different surnames and different birth years. One is Tatiana Orlov, listed under the alias “Tatyana Orlov”, born on 3 March 1989, a national of Cyprus. So is the applicant. That one is not a false positive, and the whole point of screening is to make sure it never gets cleared along with the other eight.

In short

  • Most of a screening alert queue is people who merely share a name. The work is proving each one is someone else, quickly, with a reason a reviewer can check.
  • Score the name, the date of birth and the nationality separately, and show all three. A single blended score hides exactly the evidence an analyst needs.
  • Require the surname to agree. A shared first name on its own is not a match. In this case that rule alone keeps eight entries out of the queue.
  • No agent clears a strong sanctions match. The screening agent proposes escalation. A person records the disposition, with a reason, and the case cannot be decided until they do.

The situation

The case is KYC-2026-000001 on InsightKYC’s demo data, an onboarding for an individual, customer C000001, applying through the US business of the fictional Harbourline Bank. The screening lists are invented for the demo: a fictional sanctions list of 1,160 entries, 500 politically exposed persons and 130 adverse-media articles. The entry here, FSL-10765, sits on a fictional programme, “Narcotics trafficking (N-2)”.

List entryName on the listBornNationalitySame person?
FSL-10765Tatiana Orlov (alias Tatyana Orlov)3 Mar 1989CYName, date of birth and nationality all agree
FSL-10327Tatiana Kozlov (alias Tatyana Kozlov)1964CYDifferent surname, different birth year
FSL-10517Tatiana Fedorov19 Dec 1965CYDifferent surname, different birth year
FSL-10393Tatiana Sokolov2 Dec 1953CYDifferent surname, different birth year
FSL-10062Tatiana Kozlov14 Jan 1983RUDifferent surname, year and nationality
… four moreTatiana Morozov, Fedorov, Sidorov1957 to 2002RU, UADifferent surname, year and nationality

Every one of the nine shares a first name with the applicant, in one spelling or the other, and a surname of the same Russian pattern. A matcher that compares whole names loosely will raise all nine. That is how screening queues fill up.

Why screening queues fill up

Name matching has to be fuzzy. Names are transliterated (Tatiana, Tatyana), reordered, abbreviated and misspelt, and a list entry may carry several aliases. A matcher strict enough to miss nothing will match a lot of people who are not on the list. The usual response is to tune the threshold down until the queue is bearable, which trades false positives for misses, the one error a sanctions programme can’t afford.

Why a miss is the expensive error

US sanctions administered by OFAC are enforced on a strict liability basis: a bank can be penalised for dealing with a sanctioned person even if it didn’t know. That is why the answer to noise can’t simply be a higher threshold. It has to be better evidence on each alert.

The better answer is to look at more than the name, and to show the analyst every part of the comparison, so that clearing a false positive takes seconds and a true match stands out.

How InsightKYC scores a match

Each party on the case is screened against the sanctions, PEP and adverse-media lists, including every alias. The score has three parts, each kept and shown:

PartHow it is computedWhat it means here
NameToken-sort similarity on the normalised names, so word order doesn’t matter; a Jaro-Winkler comparison is used only when the token-sort score is already 0.85 or more; the surname must agreeTatyana Orlov vs alias Tatyana Orlov: 1.00. Tatyana Orlov vs Tatiana Kozlov: the surnames disagree, so it is not a candidate
Date of birthSame date, same year, different year, or unknown, each moving the scoreSame date of birth: 3 March 1989 on both
NationalitySame, different or unknownSame: Cyprus

The result is a strength: strong when name and secondary identifiers agree, possible, or weak when only the name is close. Names that are very close but whose dates of birth differ are still kept, as weak matches, rather than dropped, so a list entry with a wrong date on it can’t hide.

Kozlov, Fedorov, Sokolov,
Morozov, Sidorov: no

Orlov: yes

same date

same: CY

Applicant
Tatyana Orlov
born 3 Mar 1989, CY

Surname agrees?

Not a candidate
8 entries

Name score 1.00
alias Tatyana Orlov

Date of birth?

Nationality?

Strong match 1.00
FSL-10765

Nine look-alike entries. The surname rule removes eight before they become alerts; the ninth agrees on everything.

The screening tab for Tatyana Orlov: one open strong sanctions match at 1.00 against FSL-10765 Tatiana Orlov, matched on the alias Tatyana Orlov, same date of birth 3 March 1989 and same nationality CY, with the screening agent proposing escalation to the sanctions officer
One match, shown in full. The name score, the date of birth and the nationality side by side, the programme, and what the screening agent proposes: escalate.

What the agent may and may not do

The screening agent runs the screen and, for each match, proposes a disposition with its reason: false positive, true match, needs information, or escalate. For a weak match with a different birth year and nationality it proposes “false positive” and says why. For a strong sanctions match it proposes only escalation.

MatchThe agent proposesWho records the disposition
Weak: different surname or yearFalse positive, with the differences namedThe analyst, accepting or changing it
Possible: name close, identifiers missingNeeds informationThe analyst, usually after asking the customer
Strong sanctions matchEscalate to the sanctions officer. Never a clearanceA person, with a written reason; it blocks the decision until then

A design rule, not a setting

Clearing a strong sanctions match is not on any autonomy dial. However much autonomy the agents earn elsewhere, this action is not one they can be given. Two case controls enforce it: OPEN_STRONG_HITS blocks approval while a strong match is open, and SANCTIONS_TRUE_MATCH blocks it once one is confirmed.

Who does what

KYC leadCase controlsSanctions officerAnalystScreening agentKYC leadCase controlsSanctions officerAnalystScreening agentScreens the applicant and every alias on the lists1One strong match - proposes escalation2Escalates with the comparison3Checks identifiers against the customer documents4Confirmed - true match, with the reason5Records the disposition6The true match blocks approval7Declines, and the bank follows its sanctions procedure8

The case cannot be approved while the strong match is open, and cannot be approved at all once it is confirmed.

Handling a strong sanctions matchOwners in the tag
1
Screen every partyscreening agent

Applicant, owners, directors and aliases against sanctions, PEP and adverse media. Each match is stored with its three-part score.

2
Look at the comparisonanalyst

Name, date of birth and nationality side by side, with the customer’s passport fields one tab away, each quoted from its line.

3
Escalateanalyst → sanctions officer

A strong match goes to whoever your procedure names, with the comparison. Whoever disposes of it does so on the case, so the record shows who decided and when.

4
Dispose with a reasonsanctions officer or analyst

True match, or false positive with the specific difference that proves it. The reason is kept on the case and frozen into the decision record.

5
DecideKYC lead

A confirmed match blocks approval. The decline records the reason; any report or asset freeze follows the bank’s sanctions procedure outside the case.

Clearing a false positive well

Most matches on a real book are false positives, and the quality of each clearance matters as much as the speed. A reviewer or examiner sampling the file should be able to see why each one was cleared.

A WEAK CLEARANCE “Not a match”

Cleared with no reason, or a reason that just restates the outcome. A reviewer can’t tell whether anyone compared the identifiers.

A STRONG CLEARANCE “Different year of birth (1964 on the list, 1989 for the customer); passport confirms”

Names the identifier that differs, both values, and the evidence. Anyone can check it in a minute.

InsightKYC asks for the reason in the dialog that records the disposition, and the placeholder shows the kind of reason that holds up. A disposition with an empty reason can’t be saved.

What it means for each audience

For the CCO & MLRO

Every disposition carries who, when and why, and the decision record freezes them as they stood at the decision. If a cleared match is questioned later, the evidence is on the file.

The rule that no agent clears a strong sanctions match is visible in the product, not just in a policy document.

For the KYC operations lead

The queue holds matches worth looking at. Look-alike names with a different surname never arrive, and the ones that do arrive show the comparison, so clearing a weak match is a minute’s work.

The time saved goes to the matches that need judgement.

For the board

The bank screens every party, including owners found in the registry, and can show why each match was cleared or escalated.

Sanctions exposure is measured in confirmed and open strong matches, not in alert counts.

What to be careful about

  • The surname rule has limits. Some naming conventions don’t put the family name last, and some people change surnames. Aliases on the list help; so does screening on the name as it appears in the identity document. Test the rule against your own population before relying on it.
  • Missing identifiers weaken everything. Many real list entries have only a birth year, or none. A match with no date of birth to compare is “possible”, not cleared.
  • The demo lists are invented. A deployment screens against the bank’s own licensed or official lists, and the thresholds should be tuned and documented for them.

Screening isn’t about raising fewer alerts. It’s about never clearing the one that matters.

Show the name, date of birth and nationality on every match, ask for a reason on every clearance, and keep strong sanctions matches out of any agent’s reach.

Keep reading