# 7. Name Screening Name Screening checks names against the watchlist. Analysts use it to look up watchlist records and to screen a single name by hand. Compliance administrators use it to follow the batch and delta screening runs and to set the alert bands and field weightages that screening uses.
For
Analysts and administrators
In the menu
Fyscal ARCX → Name Screening
Reading time
About 24 min
::: checks - [Watchlist Search](#s-7-1): look up watchlist records by name and narrow them with filters. - [Watchlist Entity Details](#s-7-2): read a watchlist record's identity, risk, network and source details. - [Manual Screening](#s-7-3): enter one person's or company's details and screen them on demand. - [Batch Screening](#s-7-4): check the batch screening runs, their status and the alerts they created. - [Delta Screening](#s-7-5): follow the delta screening runs and change their schedule. - [Alert Configuration](#s-7-6) (**Configuration** → **Alerts**): review or change the alert bands. - [Screening Configuration](#s-7-7) (**Configuration** → **Screening**): review or change the field weightages. - [Review a name-screening match](#s-7-8): what True Match, False Match and Potential Match mean for an analyst, and how to decide between them. ::: ::: note AML context Name screening compares customers with lists of people and organisations that carry risk, such as sanctioned parties and politically exposed persons (PEPs). A possible match is not a finding. It prompts an analyst to check the record, decide whether it is the same person or organisation, and record why. :::
  1. Watchlist loadedLSEG and Internal Watchlist files, in Data Ingestion
  2. Customers screenedBatch Screening and Delta Screening runs
  3. Matches scoredEach watchlist candidate gets a band and a percentage
  4. Alert raisedFor example LOW 84.29%
  5. Analyst decidesTrue Match, False Match or Potential Match, in Case Manager
Diagram 7.1 — From watchlist to a decided name-screening alert
Diagram 7.1 shows where each part of this chapter fits. Watchlist files are loaded in [Watchlist Ingestion](#s-10-4) and can be looked up in [Watchlist Search](#s-7-1). [Batch Screening](#s-7-4) and [Delta Screening](#s-7-5) list the runs and the alerts each one created. Each alert shows its band and percentage, and the bands are set in [Alert Configuration](#s-7-6). The analyst reviews the matches and records a disposition in [Case Manager](#case-manager); [Review a name-screening match](#s-7-8) explains how to decide. ## Watchlist Search {#s-7-1} ::path[Fyscal ARCX → Name Screening → Watchlist Search] Use Watchlist Search to look up records on the watchlist by name, narrow them with filters and open any record's details. The table stays empty until you search. ::figure[Watchlist Search before a search: Search by Name (1), Refresh and Hide Filters (2), the five filters (3), the results columns (4) and the empty state (5)]{src="name-screening/01-watchlist-search.png" id="fig-name-screening-watchlist-search"} ::: legend 1. **Search by Name**: type the name of the person or entity to look up. 2. **Refresh** reloads the results. **Hide Filters** hides the filter row, which is shown when the page opens. 3. The filters: **Country**, **PEP Status**, **Category**, **Entity** and **Source**. Each one is set to **All** by default. 4. The results table, with the columns **UID**, **Name**, **PEP Status**, **Country**, **Category** and **Date of Birth**. 5. The empty state, **Oops! No data available** with the line "Please adjust your search criteria or try again later", which shows until a search returns records. ::: #### Filters Each filter opens a list with a search box at the top, so you can type to find an option. | Filter | Options | | --- | --- | | **Country** | Default **All**. Choose a country. | | **PEP Status** | **Active**, **NON-PEP**, **Unknown** | | **Category** | **WEBSITE**, **MILITARY**, **AIRCRAFT**, **VESSEL**, **BANK**, **POLITICAL INDIVIDUAL**, **SHELL BANK OR COMPANY**, **RELIGION**, **CRIME - ORGANIZED**, **CRIME - TERROR**, **EMBARGO**, **POLITICAL PARTY**, **EMBARGO VESSEL**, **TRADE UNION**, **PORT**, **CRIME - FINANCIAL**, **ORGANISATION**, **CORPORATE**, **EMBARGO AIRCRAFT**, **INDIVIDUAL**, **COUNTRY**, **DIPLOMAT**, **CRIME - WAR**, **CRIME - OTHER**, **ADDRESS**, **CRIME - NARCOTICS**, **SPECIAL JURISDICTION**, **LEGAL** | | **Entity** | **Male**, **Female**, **Entity**, **Unknown** | | **Source** | **All**, **Internal Watchlist**, **LSEG** | #### Results columns | Column | What it shows | | --- | --- | | **UID** | The record's identifier on the watchlist, for example **3601955**. A record marked deleted shows a red **Deleted** label and a date (for example **15/04/2026**) under its UID. | | **Name** | The name as held on the watchlist, for example **John SMITH**. | | **PEP Status** | A green **PEP** chip, a red **NON-PEP** chip, or **-** when the record has no PEP status. | | **Country** | The record's country, for example **UNITED KINGDOM**. | | **Category** | The record's category, for example **INDIVIDUAL**, **LEGAL** or **CRIME - NARCOTICS**. | | **Date of Birth** | The date of birth in YYYY/MM/DD format, or **-** when the record has none. | | **Source** | The list the record comes from, for example **LSEG**. This column appears once results are shown. | ::: step Search by name Type the name in **Search by Name**, for example *John Smith*. The table fills with matching records and a **Name: John Smith** tag appears under the filters. A common name returns many records: this search returns 20, and the footer reads **Showing 20 results**. ::: ::: step Narrow the results with a filter Click a filter, for example **PEP Status** (1), and choose an option from the list (3). You can type in the list's search box (2) to find an option. ::figure[The PEP Status filter (1) open: the search box (2) and the options Active, NON-PEP and Unknown (3)]{src="name-screening/02-watchlist-pep-status-filter.png" id="fig-name-screening-watchlist-pep-status-filter" width="459"} ::: ::: step Read the results Compare UID, PEP Status, Country, Category and Date of Birth to tell records with the same name apart (dates of birth are hidden in the figure). Use the arrows at the bottom right to move between pages. ::figure[Results for John Smith: the Name tag and RESET FILTERS (1), the Source column (2), a record marked Deleted with its date (3) and the result count (4); dates of birth hidden]{src="name-screening/03-watchlist-search-results.png" id="fig-name-screening-watchlist-search-results"} ::: ::: step Clear the search Click the **×** on the **Name** tag to remove that one filter, or click **RESET FILTERS** to clear them all. ::: ## Watchlist Entity Details {#s-7-2} ::path[Fyscal ARCX → Name Screening → Watchlist Search → a result row] Open a record's details when you need more than the results table shows: its identity, risk background, network and sources. Click a row in the results to open the **Watchlist Entity Details** dialog for that record. The dialog's heading is the entity name. Below it, two summary cards show **Entity Name**, **UID**, **PEP Status** and **Category**. These cards stay in place while you move between the four tabs: **Profile & Identity**, **Risk & Background**, **Network & Locations** and **Source**. A field shows **--** when the record has no value for it. Click **×** at the top right to close the dialog. The figures below show record **3601955**, JOHN SMITH, with PEP Status **PEP** and Category **LEGAL**. Third-party details from the watchlist (date and place of birth, address, associates, biography, identification, reports and source links) are hidden in the figures. | Tab | Fields | | --- | --- | | **Profile & Identity** | **Gender/Type**, **Date of Birth**, **Place of Birth**, **Citizenship**, **Alternative Spelling**, **Age**, **Identification Number**, **Aliases**, **IDs / Passports**, **Deceased Date** | | **Risk & Background** | **Position**, **PEP History**, **Title**, **Category**, **Sub-Category**, **Special Interests**, **PEP Status**, and a **Further Information/Biography** panel. In this record the panel is split into **BIOGRAPHY**, **IDENTIFICATION** and **REPORTS**. | | **Network & Locations** | **Addresses**, **Associates** (shown as UIDs in blue), **Companies** | | **Source** | **Links**: the source websites for the record, each shown as a link chip. | ::figure[Profile & Identity tab: the entity name (1), the summary cards (2), the four tabs (3), the left column of identity fields (4) and the right column (5)]{src="name-screening/04-entity-profile-identity.png" id="fig-name-screening-entity-profile-identity"} ::figure[Risk & Background tab: the tabs (1), Position, PEP History, Title and Category (2), Sub-Category, Special Interests and PEP Status (3), and the Further Information/Biography panel (4)]{src="name-screening/05-entity-risk-background.png" id="fig-name-screening-entity-risk-background"} ::figure[Network & Locations tab: the tabs (1), Addresses (2), Associates (3) and Companies (4)]{src="name-screening/06-entity-network-locations.png" id="fig-name-screening-entity-network-locations"} ::figure[Source tab: the tabs (1), the Links (2) and the close button (3)]{src="name-screening/07-entity-source.png" id="fig-name-screening-entity-source"} ::: note The PEP Status filter offers **NON-PEP**, **Unknown** and **Active**, but the results table and this dialog show **PEP**, **NON-PEP** or **-**. ::: ## Manual Screening {#s-7-3} ::path[Fyscal ARCX → Name Screening → Manual Screening] Use Manual Screening to screen one person or company by entering their details yourself. Next to each field the form shows the weightage it carries, taken from the active [Screening Configuration](#s-7-7). ::figure[The Manual Screening form, empty: the configuration chips (1), the weightage bar (2), Personal Details (3), Date of birth & Citizenship (4), Address (5), and Reset and Proceed to screen (6)]{src="name-screening/08-manual-screening-form.png" id="fig-name-screening-manual-screening-form"} ::: legend 1. Two chips: **Config version ID : 1791441937** and **Rule version : v2.1.0**. The config version ID is the same number as the ACTIVE version on the [Screening Configuration](#s-7-7) page. 2. The weightage bar: **Total Weightage: 100%**, split as **Name: 65%**, **Address: 10%**, **Citizenship: 10%**, **Gender: 10%** and **DOB: 5%**. 3. **Personal Details**: Customer Name, Entity Type and Gender. 4. **Date of birth & Citizenship**: Date of Birth and Citizenship. 5. **Address**: Street, City, Province/Region and Address Country. The section carries a single weightage of 10%. 6. **Reset** and **Proceed to screen**. :::
FieldWeightage shownRequiredOptions or format
Customer Name65%Yes (*)Free text. Placeholder "Enter Name".
Entity TypeNoneNoPlaceholder "Select Entity Type". Options Individual and Company.
Gender10%NoPlaceholder "Select Gender". Options Male, Female and Other.
Date of Birth5%NoPlaceholder "Select Date". A calendar with month and year selectors. Years run from 1926 to 2026, and dates after today are greyed out.
Citizenship10%NoFree text. Placeholder "Enter Citizenship".
Street10% for the whole Address sectionNoFree text. Placeholder "Enter Street".
CityNoFree text. Placeholder "Enter City".
Province/RegionNoFree text. Placeholder "Enter Province/Region".
Address CountryNoFree text. Placeholder "Enter Address Country".
::: step Enter the name Type the customer's name in **Customer Name**. This is the only field marked as required (\*). ::: ::: step Choose the entity type Open **Entity Type** (1) and choose **Individual** or **Company** (2). ::figure[The Entity Type field (1) and its list (2): Individual and Company]{src="name-screening/09-manual-screening-entity-type.png" id="fig-name-screening-manual-screening-entity-type" width="1119"} ::: ::: step Choose the gender Open **Gender** and choose **Male**, **Female** or **Other**. ::: ::: step Pick the date of birth Click **Date of Birth**. In the calendar, choose the month and year from the two lists at the top (2), or move with the arrows (1, 3), then click the day. Today's date is highlighted (4) and dates after it are greyed out. ::figure[The Date of Birth calendar: previous month (1), the month and year lists (2), next month (3) and today's date (4); dates after today are greyed out]{src="name-screening/10-manual-screening-date-picker.png" id="fig-name-screening-manual-screening-date-picker" width="480"} ::: ::: step Add citizenship and address Type **Citizenship**, then fill in whichever address fields you have: **Street**, **City**, **Province/Region** and **Address Country**. ::: ::: step Screen, or start again Click **Proceed to screen** to run the screening. To clear the form instead, click **Reset**. ::: ::: note On the empty form, **Proceed to screen** is greyed out. ::: ## Batch Screening {#s-7-4} ::path[Fyscal ARCX → Name Screening → Batch Screening] Use Batch Screening to check whether batch runs succeeded and how many alerts they created. Batch Screening lists the batch screening runs. For each run it shows how many customers were scanned, how many alerts were created, and the run's status and duration. The page has no **Change Schedule** button, and clicking a row does not open a detail view. ::figure[Batch Screening: the schedule card (1), Run Date (2), Status (3), Refresh (4), the Customers Scanned figure (5), the run ID (6) and the record count (7)]{src="name-screening/11-batch-screening.png" id="fig-name-screening-batch-screening"} ::: legend 1. The schedule card. Here it reads **Inactive**, **Current Frequency: Daily at 09:00**, **Next Run: -** and **Last Run: -**. 2. **Run Date**: a date-range field ("Pick a date range"). 3. **Status**: the status filter, set to **All Status** by default. 4. **Refresh** reloads the table. 5. The **Customers Scanned** figure, shown underlined in blue. 6. The run ID, with a copy icon next to it. 7. The record count, for example **Showing 1-13 of 13**, with the page controls on the right. ::: | Column | What it shows | | --- | --- | | **Run Date / ID** | The run's date and time (for example **14 Oct, 03:41:36 PM**) and, below it, **RUN ID:** with the run number and a copy icon. | | **Customers Scanned** | The number of customers the run screened. | | **Alerts Created** | The number of alerts the run created. | | **Errors** | The number of errors in the run. | | **Watchlist Count** | The number of watchlist records at the time of the run, for example **6,855,187**. | | **Status** | The run's status. See the table below. | | **Duration** | How long the run took, for example **10s**, **5m** or **1h 11m**, or **-** when no duration is recorded. | | Status | Meaning | | --- | --- | | **Screening In Progress** | The run has not finished yet. | | **Screening Success** | The run completed successfully. | | **Screening Failed** | The run failed. | ::: step Filter runs by status Click **Status** (1) and choose **Screening In Progress**, **Screening Success** or **Screening Failed** (3). You can type in the list's search box (2) to find a status. ::figure[The Batch Screening Status filter (1) open: the search box (2) and the options Screening In Progress, Screening Success and Screening Failed (3)]{src="name-screening/12-batch-screening-status-filter.png" id="fig-name-screening-batch-screening-status-filter" width="390"} ::: ::: step Filter runs by date Click **Run Date** ("Pick a date range") and choose the first and last day of the period. ::: ::: step Refresh the list Click **Refresh** to reload the table. ::: ::: note In the example list, the three batch runs of 05 Oct each started a few seconds after a **Customers** job in [Batch Ingestion](#s-10-1) and scanned the number of customers that job ingested: run 637 (50 customers) after job 168, run 638 (600) after job 171, and run 640 (1,000) after job 177. ::: ## Delta Screening {#s-7-5} ::path[Fyscal ARCX → Name Screening → Delta Screening] Use Delta Screening to follow the delta runs and to change when they run. Delta Screening shows the delta screening schedule and lists its runs, including the next scheduled run. Unlike Batch Screening, this page has **Resume** and **Change Schedule** buttons. ::figure[Delta Screening: the schedule bar (1), Resume (2), Change Schedule (3), Status (4), Date Range (5), the Upcoming run (6) and Refresh (7)]{src="name-screening/13-delta-screening.png" id="fig-name-screening-delta-screening"} ::: legend 1. The schedule bar. Here it reads **Inactive**, **Current Frequency: Daily at 05:00**, **Next Run: 08 Oct 2026, 05:00** and **Last Run: 23 Sep 2026, 12:01**. On 14 October the Next Run date shown had already passed, and the Upcoming row still showed it. 2. **Resume**: a button on the schedule bar. 3. **Change Schedule** opens the **Change Screening Schedule** dialog. 4. **Status**: the status filter, set to **All Status** by default. 5. **Date Range**: a date-range field ("Range"). 6. The next scheduled run, labelled **Upcoming** with the status **Scheduled**. Its other columns show **—**. 7. **Refresh** reloads the table. ::: The two screening pages differ as follows:
On the pageBatch ScreeningDelta Screening
Schedule with Current Frequency, Next Run and Last RunYesYes
Resume buttonNoYes
Change Schedule buttonNoYes
Errors columnYesNo
Next run listed as UpcomingNoYes
The **Watchlist Count** also differs in size: 6,792,763 on the batch runs of 05 Oct, and 12,396 on the delta runs of 23 Sep. ::: note AML context In screening generally, a full screen checks customers against the whole list, while a delta screen checks them against the records added or changed since the last run, so that list updates are picked up between full screens. ::: | Column | What it shows | | --- | --- | | **Run Date / ID** | The run's date and time (for example **23 Sep 2026, 10:52**) and, below it, **Run ID** with the run number and a copy icon. The next scheduled run shows **Upcoming** in place of the ID. | | **Customers Scanned** | The number of customers the run screened. | | **Alerts Created** | The number of alerts the run created. | | **Watchlist Count** | The watchlist count recorded for the run, for example **12,396**. | | **Status** | The run's status. See the table below. | | **Duration** | How long the run took, for example **1h 8m 43s**. | The table shows 20 runs per page (**Showing 1-20 of 30**, **Page 1 of 2**). | Status | Meaning | | --- | --- | | **Scheduled** | The next run, not yet started (the **Upcoming** row). | | **In Progress** | The run has not finished yet. | | **Completed** | The run finished. | | **Failed** | The run failed. | | **Paused** | A status offered by the filter. | ::: step Filter runs by status Click **Status** (1) and choose **All Status**, **Scheduled**, **In Progress**, **Completed**, **Failed** or **Paused** (3). A tick marks the current choice (2). ::figure[The Delta Screening Status filter (1): All Status ticked (2), then Scheduled, In Progress, Completed, Failed and Paused (3)]{src="name-screening/14-delta-screening-status-filter.png" id="fig-name-screening-delta-screening-status-filter" width="420"} ::: ::: step Filter runs by date Click **Date Range**. A two-month calendar opens. Click the first and last day of the period, then click **Apply**. **Clear** removes the range. ::: ::: step Open Change Schedule Click **Change Schedule**. The **Change Screening Schedule** dialog opens, headed "Select the new frequency and run time, add a reason, then review before confirming." ::figure[The Change Screening Schedule dialog: the current schedule (1), New Frequency (2), Run Time - UTC (3), Reason (4), Next Run Preview (5), and Cancel and Review Changes (6)]{src="name-screening/15-change-screening-schedule.png" id="fig-name-screening-change-screening-schedule" width="1064"} | Area or field | What it shows or expects | | --- | --- | | 1. Current schedule | **Current Frequency: Daily at 05:00 UTC**, followed by "Any schedule change — whether frequency or time — takes effect after the next scheduled run on Thu, 08 Oct 2026 at 05:00 UTC." | | 2. **New Frequency** | A list. Here it shows **Daily**. | | 3. **Run Time** - UTC | A list of times in UTC. Here it shows **05:00 AM**. | | 4. **Reason** | Free text. Placeholder "Describe why the schedule is changing." | | 5. **Next Run Preview** | The next run and a summary of the schedule, for example **Thu, 08 Oct 2026 at 05:00 UTC** and "Runs every day at 05:00 UTC." | | 6. Buttons | **Cancel** and **Review Changes**. **×** at the top right also closes the dialog. | ::: ::: step Set the new schedule Choose the **New Frequency** and the **Run Time**. Type the **Reason** for the change. Check the **Next Run Preview**, then click **Review Changes**. To leave without changing anything, click **Cancel**. ::: ::: note In the dialog as it opens, with no reason entered, **Review Changes** is greyed out. Run times in the dialog are in UTC. ::: ## Alert Configuration {#s-7-6} ::path[Fyscal ARCX → Name Screening → Configuration → Alerts] Use Alert Configuration to review or change the alert bands that screening uses. Each band has a name, a colour, a Min % to Max % range, a **No Alert** setting, an **SLA Deadline** and an **Auto Hibernate** setting. The page has two tabs: **Active Alert Configuration** and **Alert Configuration History**. ::figure[Active Alert Configuration: the tabs (1), the version details (2), Edit (3) and the bands table (4)]{src="name-screening/16-alert-config-active.png" id="fig-name-screening-alert-config-active"} ::: legend 1. The tabs **Active Alert Configuration** and **Alert Configuration History**. 2. The active version: **Version** (for example 6acdb8b7955aaed16603eea5), **Created At** (13 Oct 2026, 10:21:03 (+05:30)) and **Created By** (hidden in the figure). 3. **Edit** switches the table into the edit form. 4. The bands table. ::: | Column | What it shows | | --- | --- | | **Name** | The band's name. | | **Color** | The band's colour, as a swatch and a hex code. | | **Min %** | The lower end of the band's range. | | **Max %** | The upper end of the band's range. | | **No Alert** | **Yes** or **No**. | | **SLA Deadline** | The SLA as days, hours and minutes (for example **3d 0h 0m**), or **—** where No Alert is Yes. | | **Auto Hibernate** | **Yes** or **No**, or **-** where No Alert is Yes. | The active configuration in [](#fig-name-screening-alert-config-active) (saved on 13 Oct 2026): | Name | Color | Min % | Max % | No Alert | SLA Deadline | Auto Hibernate | | --- | --- | --- | --- | --- | --- | --- | | very low | #C4C5C4 | 0% | 85% | Yes | — | - | | Low | #3CAF49 | 85% | 90% | No | 3d 0h 0m | No | | Medium | #F59F66 | 90% | 95% | No | 5d 0h 0m | No | | HIGH | #FB5050 | 95% | 100% | No | 3d 0h 0m | No | The SLA does not rise with the band in this configuration: Medium has 5 days, while Low and HIGH have 3 days each. The values are set per band, so check them when you change the bands. A Name Screening alert shows its band and percentage in its header, for example **LOW 84.29%** on ALT-NS-05102026-000115, and the same band on each match candidate (see [Alert Details: Name Screening](#s-3-24)). The header also shows **Config:** with an Alert Configuration version ID. On that alert it is 6ab3c6efe9d518f3fc6b21d9. That version is not among the 10 listed in Alert Configuration History on 14 October 2026. The alert still shows LOW 84.29%, although 84.29% falls in the current very low band (0% to 85%). ::: note AML context Bands let a team review the strongest matches first and give each band a review deadline. An SLA here is the institution's own service level for reviewing an alert, not a regulatory deadline. ::: #### Edit the alert configuration ::figure[Alert Configuration in edit mode: Cancel and Save (1), the No Alert switch (2), Min % and Max % (3), the SLA Deadline fields (4), the delete icons (5) and Add More Threshold (6)]{src="name-screening/17-alert-config-edit.png" id="fig-name-screening-alert-config-edit"} ::: legend 1. **Cancel** and **Save** take the place of **Edit**. 2. **No Alert** is a switch, shown on for the very low band. 3. **Min %** and **Max %** are number fields. The first band's Min % (0) and the last band's Max % (100) are greyed out. 4. **SLA Deadline** has three fields: **DD**, **HH** and **MM**. On the band with No Alert switched on, these fields and the **Auto Hibernate** switch are greyed out. 5. A red delete icon appears at the end of the Medium and HIGH rows. 6. **Add More Threshold** adds a band. ::: ::: step Open the edit form On the **Active Alert Configuration** tab, click **Edit**. ::: ::: step Change the bands For each band, set the **Name**, the **Color**, **Min %** and **Max %**, the **No Alert** switch, the **SLA Deadline** (DD : HH : MM) and the **Auto Hibernate** switch. Click **Add More Threshold** to add a band, or a band's delete icon to remove it. ::: ::: step Save or cancel Click **Save** to keep your changes, or **Cancel** to discard them. ::: #### Alert Configuration History Open the **Alert Configuration History** tab to see every saved version. The table has the columns **Config Version ID** (with a copy icon), **Status**, **Created** and **Created by**. One version is **ACTIVE** and the rest are **INACTIVE**. In [](#fig-name-screening-alert-config-history) there are 10 versions (**Showing 1-10 of 10**), newest first. ::figure[Alert Configuration History: the tab (1), the columns (2) and the ACTIVE version (3), followed by nine INACTIVE versions; names hidden]{src="name-screening/18-alert-config-history.png" id="fig-name-screening-alert-config-history"} ## Screening Configuration {#s-7-7} ::path[Fyscal ARCX → Name Screening → Configuration → Screening] Use Screening Configuration to review or change how much weight each field and sub-field carries in screening. Screening Configuration holds the weightages of the screening fields and of their sub-fields. The [Manual Screening](#s-7-3) form shows the active version's ID and weightages. The page has two tabs: **Active Configuration** and **Configuration History**. ::figure[Active Configuration: the tabs (1), the version details (2), Edit (3), the Total Weightage bar (4), a field card with sub-fields, Address (5), and a field with no sub-fields, Citizenship (6)]{src="name-screening/19-screening-config-active.png" id="fig-name-screening-screening-config-active"} ::: legend 1. The tabs **Active Configuration** and **Configuration History**. 2. The active version: **Created At** (08 Oct 2026, 12:15:37 (+05:30)), **Created By** (hidden in the figure), **Config version** (1791441937) and **Status** **ACTIVE**. 3. **Edit** switches the page into the edit form. 4. **Total Weightage: 100%**: a bar showing each field's share in its own colour. 5. A field card. **Address**, **Name** and **DOB** have a chevron and list their sub-fields below. 6. **Citizenship** and **Gender** have no sub-fields. ::: The active configuration in [](#fig-name-screening-screening-config-active): | Field | Weightage | Sub-fields | | --- | --- | --- | | **Name** | 65% | Fuzzy 80%, Phonetic 20% | | **Address** | 10% | Country 60%, City 15%, Street Address 15%, Region 10% | | **Citizenship** | 10% | None | | **Gender** | 10% | None | | **DOB** | 5% | Year 50%, Month 40%, Day 10% | In this configuration, the field weightages add up to 100%. Within each of Address, Name and DOB, the sub-field weightages also add up to 100%. ::: note AML context Fuzzy matching finds names that are spelled differently, and phonetic matching finds names that sound alike, for example after transliteration from another script. Both widen the net, so common names produce many candidates. Date of birth, nationality and address are what tell those candidates apart. ::: ::: note The weightages shown on an alert's match candidates can differ from the ones on this page (see [Review a name-screening match](#s-7-8)). ::: #### Edit the screening configuration ::figure[Screening Configuration in edit mode: Cancel and Save (1), a field's weightage field, Address (2), and a sub-field's weightage field, Country (3)]{src="name-screening/20-screening-config-edit.png" id="fig-name-screening-screening-config-edit"} ::: legend 1. **Cancel** and **Save** take the place of **Edit**. 2. Each field's weightage becomes a number field with a **%** sign. 3. Each sub-field's weightage becomes a number field too. ::: ::: step Open the edit form On the **Active Configuration** tab, click **Edit**. ::: ::: step Change the weightages Type the new percentages for **Address**, **Name**, **Citizenship**, **Gender** and **DOB**, and for the sub-fields of Address (Country, City, Street Address, Region), Name (Fuzzy, Phonetic) and DOB (Year, Month, Day). ::: ::: step Save or cancel Click **Save** to keep your changes, or **Cancel** to discard them. ::: #### Configuration History Open the **Configuration History** tab to see every saved version. The table has the columns **Config Version ID** (with a copy icon), **Status** (**ACTIVE** or **INACTIVE**), **Created** and **Created by**, newest first. The example environment holds 105 versions, 20 per page (**Showing 1-20 of 105**, **Page 1 of 6**). ::figure[Configuration History: the tab (1), the columns (2) and the ACTIVE version 1791441937 (3), followed by INACTIVE versions; names hidden]{src="name-screening/21-screening-config-history.png" id="fig-name-screening-screening-config-history"} ## Review a name-screening match {#s-7-8} ::path[Fyscal ARCX → Case Manager → Alerts → a Name Screening alert → Matches]
Who
The analyst working the alert or case
Where
Alert Details or Case Details → Matches
Decision
True Match, False Match or Potential Match
Recorded with
A Rationale Code and Rationale Details (at least 10 characters)
Screening finds watchlist records that may be your customer. The analyst decides whether each one is. The **Matches** panel puts the customer's values next to each watchlist candidate's values, field by field, with a **Weightage** and a **Score** for each field and a band and percentage for the candidate. The panel is described in [Customer, accounts and matches](#s-3-5), and the decision is recorded with **Dispose Alert** (see [Dispose alerts and close a case](#s-3-10)). #### What the dispositions mean for you The **Disposition** list offers three values. The screen does not define them; the table gives their usual meaning in screening review. Your institution's procedures set what each one requires. | Disposition | Usual meaning in screening review | | --- | --- | | **True Match** | The watchlist record is your customer: the name matches and the other identifiers agree. In the examples, a Closed case with this disposition shows **File STR** (see [File an STR](#s-3-13)). | | **False Match** | The watchlist record is someone else: the names are only alike, or an identifier such as date of birth or nationality clearly conflicts. | | **Potential Match** | The record may be your customer, but the evidence is not enough to confirm or rule it out, for example because the record has no date of birth. | #### Decide on a match

Is the watchlist name the customer's name, allowing for spelling variants, transliteration and word order?

Diagram 7.2 — Deciding a name-screening match
Diagram 7.2 is a general review aid, not product logic. Start with the name. If it is not the customer's name, the candidate is a False Match. If it is, compare the secondary identifiers. Agreement points to a True Match and a clear conflict to a False Match. When identifiers are missing on either side, look for more evidence in the **Identity** and **Additional Information** tabs, such as aliases and ID numbers, before you settle on Potential Match. #### Example: reading a candidate Alert ALT-NS-05102026-000115 for Ramon Michael Castillo Tan is banded **LOW 84.29%** and has two candidates (see [Alert Details: Name Screening](#s-3-24)). The first candidate, UID 4880431, shows: | Field | Customer | Candidate (UID 4880431) | Weightage | Score | | --- | --- | --- | --- | --- | | **Name** | Ramon Michael Castillo Tan | MICHAEL TAN | 73% | 90% | | **Nationality** | Philippines | PHILIPPINES | 11% | 100% | | **Date of Birth** | Provided | - | 0% | 0% | | **Address** | Provided | A different city | 12% | 27% | | **Entity Type** | INDIVIDUAL (MALE) | M (M) | 0% | 0% | Read with Diagram 7.2: the name is close and the nationality agrees, but the record has no date of birth to compare and the address is in a different city. The identifiers are partly missing and partly different, so this candidate cannot be confirmed from the Matches panel alone. The second candidate, RAMON TAN (UID 7134045, **LOW 82.6%**), needs the same review. The alert in the example is **Not Started** and has no disposition yet. ::: note The field weightages shown on this alert (Name 73%, Nationality 11%, Address 12%) differ from the active [Screening Configuration](#s-7-7) (Name 65%, Address 10%, Citizenship 10%, Gender 10%, DOB 5%), and the weightages and scores on screen do not by themselves give 84.29%. Use the per-field scores to see where the candidate agrees and differs, not to recalculate the percentage. :::
Related in Detection & Monitoring
Transaction MonitoringTypology LibraryData Ingestion