Every name, resolved to the right person

The engine at the heart of DetectX® screening. It checks every name against every list at once, uses fuzzy matching to catch the spellings an exact search would miss, and looks past the name to the record to decide whether it’s really the same person. Every match comes with a score your analysts can read.

Request a demoAll capabilities

How names come in

From your core system, payments, batch runs or an analyst’s search.

Names arrive the moment a customer is opened or changed, inside payments, in scheduled runs and on demand. Every route ends in the same engine, so a name is matched and scored the same way however it arrives.

  1. Real time
    Core banking system

    New and changed customers arrive over message queues. The result goes back the same way.

  2. Real time
    REST API

    Other systems send customers or payments, and get a JSON or XML answer back.

  3. Real time
    Payments

    Counterparties are read from structured fields, and names picked out of free text.

  4. On demand
    Single name check

    An analyst checks a name in AlertViewer, or a system calls the web service.

  5. Scheduled
    Batch runs

    At an interval you set, every customer is screened again against the current lists.

Name Screening IntelligenceSame lists · same matching · same score
Lists, kept currentFull download monthly, changes in between
ResultMatch 0.91 · alert openedor returned to the system that asked

How a name is resolved

Checking a list is easy. Deciding whether two names are the same person is the work.

That decision is where false positives come from. Every name is resolved the same way, from millions of list names to one score you can read.

Find candidates: 37 candidates found. A fuzzy index keeps only the list names and aliases that look similar. Danijel Oberholtzer is 1 of 37 candidates.

Your customer · 418.229

Daniel Oberholzer
First nameDaniel
Last nameOberholzer
Date of birth03.05.1981
NationalitySwitzerland
GenderMale
TypePerson

List entry · 1 of 37 candidates

Danijel Oberholtzer
First nameDanijel
Last nameOberholtzer
Date of birth03.05.1981
NationalityAustria
GenderMale
TypePerson

What moves the score

The name gets it close. The rest of the record decides.

Daniel Oberholzer against Danijel Oberholtzer, exactly as resolved above.
Change what the list entry says, and see the score and the decision move.

Your customerDaniel Oberholzerfrom your client records

List entryDanijel Oberholtzeron the sanctions list

Date of birth

Customer 03.05.1981 List entry 03.05.1981

Nationality and country

Customer Switzerland List entry Austria, lives in Switzerland

Gender

Customer Male List entry Male

Type of entry

Customer Person List entry Person

How common the name is

List entry Few matches on the lists

Illustrative weights. How much each detail moves the score is configured with your team.

Every step on the record

What the engine checked, what it found, and who decided.

Every screening leaves a trail an auditor can follow, from the moment a name arrives to the final decision and the people who made it.

Fuzzy matching
Partial and approximate matches captured, each with a similarity score.
Parallel lists
Sanctions, PEP data, blacklists and whitelists checked together.
Beyond names
Companies, vessels, securities and other entities.

One alert, as the record holds it · AL-ONLINE-00312760 · example data

  1. Recorded on AL-ONLINE-00312760 · state Done

  2. Recorded on AL-ONLINE-00312760 · state Done

  3. Step
    Match scored
    Data used
    NameDate of birthNationalityGender
    Result
    0.91
    Why
    The date of birth matches; the nationality differs.
    By
    Name Screening Intelligence

    Recorded on AL-ONLINE-00312760 · state Done

  4. Recorded on AL-ONLINE-00312760 · state Open

  5. Recorded on AL-ONLINE-00312760 · state In process

  6. Recorded on AL-ONLINE-00312760 · state Closed

One engine, every screening solution

The same matching runs wherever a name is checked.

Customers, counterparties and payments are scored the same way, so a decision made in one place holds everywhere.

Real timeBatchName ScreeningCustomers and related parties, at onboarding, on every change and in batch runs.See Name ScreeningReal timeTransaction FilteringPayment parties and the names in free text, before a payment is released.See Transaction FilteringReal timeInstant Payment ScreeningInstant payments, checked in the seconds they allow.See Instant Payment ScreeningReal timeBatchAsset ScreeningCompanies, vessels and securities, checked against the same lists.See Asset Screening
Name Screening IntelligenceSame lists · same matching · same scoreLists kept current

Explore the DetectX® Platform

Rules work with every capability.

The Name Screening Intelligence decides what happens. The other capabilities give it more to decide on. Pick one to see what it does.

All capabilities

Name Screening Intelligence FAQs

What compliance teams usually ask before they change how names are screened.

Something we have not covered?Talk to our team

No. Fuzzy matching finds the spellings an exact check would miss, and entity resolution then weighs date of birth, nationality, gender and the rest of the record to decide whether it’s the same person. The name gets a match close. The record decides.

SolutionName Screening

Sanctions lists, PEP data, and your own black and white lists, all checked at once. Info4C, World-Check and Factiva lists load with a full download each month and the changes in between. Which commercial providers you use is your own subscription.

Both. Names are screened the moment a customer is opened or changed, inside payments, and on demand. Scheduled batch runs check every customer again against the current lists, so a name added to a list since the last run is still found.

You do. Every match carries a score, and only matches above your threshold open an alert. Where it should sit depends on your lists and your risk appetite, and is best set in a working session on your own data.

A missing detail doesn’t clear a match. With less to compare, the name carries more of the score, and an analyst decides with every reason shown.

Go Deeper

All resources
SolutionName Screening

Customers and counterparties screened on this engine, from onboarding to overnight rescreening.

See Name ScreeningWebinarThe False Positive Trap

Why matching on the name alone floods the queue, and how the rest of the record clears it.

Watch the recordingPlatformThe DetectX® platform

Every capability on one platform, sharing one queue, one set of lists and one audit trail.

Explore the platform

See Name Screening Intelligence in a demo

Book a working session on your own list set. Bring your questions about matching, thresholds, white lists and batch scheduling.

Request a demoTalk to us