# 2. AML Dashboard The AML Dashboard gives a single view of the alert and case workload. Analysts and reviewers use it to see how many alerts and cases are overdue, unassigned, escalated or pending, and how they are distributed by status, disposition, score, type, assignment and age. It also shows STRs filed over time and whether each day's screening, monitoring and ingestion jobs succeeded.
For
Analysts, supervisors and team leads
In the menu
Fyscal ARCX → AML Dashboard
Reading time
About 12 min
::: checks - [Dashboard layout](#s-2-1): find each area of the page and see which charts each view shows. - [Metric tiles](#s-2-2): check the headline counts of overdue, unassigned, escalated and pending work. - [Case Distribution controls](#s-2-3): switch between cases and alerts and set the period the charts cover. - [By Status](#s-2-4): see how records are spread across statuses. - [By Disposition (Closed)](#s-2-5): see how closed records were dispositioned. - [By Score and By Type (Alerts view)](#s-2-6): break alerts down by score band and alert type. - [By Assignment](#s-2-7): see how much work is unassigned and who holds the rest. - [STR Filed](#s-2-8): follow the number of STRs filed per month. - [By Age](#s-2-9): see how many records fall in each age bucket. - [Pending Review, Avg. Handling and Reopens](#s-2-10): read three summary figures for cases. - [Daily Jobs](#s-2-11): check whether each scheduled job ran and succeeded. - [Team Performance](#s-2-12): find the link to team performance figures. - [Daily triage from the dashboard](#s-2-13): a short routine that goes from each tile to the list where you work it. ::: ## Dashboard layout {#s-2-1} ::path[Fyscal ARCX → AML Dashboard]
Who
Analysts, supervisors and team leads
Where
Fyscal ARCX → AML Dashboard
Views
Cases or Alerts, over a period you choose
Work it in
Case Manager → Alerts or Cases
Use this overview to find each area of the dashboard before you read a chart. Open **Fyscal ARCX** in the sidebar and click **AML Dashboard**. The page is titled **AML Dashboard**, with the breadcrumb **Fyscal ARCX › AML Dashboard**. Scroll down to see every area. [](#fig-aml-dashboard-layout) shows the whole page in the **Cases** view with the range set to **6M** (**18 Apr - 14 Oct**). ::figure[The AML Dashboard in the Cases view, with its areas numbered 1 to 10]{src="aml-dashboard/01-layout.png" id="fig-aml-dashboard-layout"} 1. **Metric tiles**: six headline counts for alerts and cases. See [Metric tiles](#s-2-2). 2. **Case Distribution** header and controls: **View Details**, the **Cases** / **Alerts** switch, the date range picker and the range presets. See [Case Distribution controls](#s-2-3). 3. **By Status**. See [By Status](#s-2-4). 4. **By Disposition (Closed)**. See [By Disposition (Closed)](#s-2-5). 5. **By Assignment**, with the **Team** / **Individual** switch. See [By Assignment](#s-2-7). 6. **STR Filed** (Cases view only). See [STR Filed](#s-2-8). 7. **By Age**. See [By Age](#s-2-9). 8. **Pending Review**, **Avg. Handling** and **Reopens** tiles (Cases view only). See [Pending Review, Avg. Handling and Reopens](#s-2-10). 9. **Daily Jobs**: **Screening & Monitoring Runs** and **Data Ingestion**. See [Daily Jobs](#s-2-11). 10. **Team Performance**. See [Team Performance](#s-2-12). Areas 3 to 8 sit inside the distribution panel and change with the **Cases** / **Alerts** switch. In the **Alerts** view the panel is titled **Alert Distribution** and shows these charts, in order: | Chart or tile | Cases view | Alerts view | | --- | --- | --- | | **By Status** | Yes | Yes | | **By Disposition (Closed)** | Yes | Yes | | **By Score** | No | Yes | | **By Type** | No | Yes | | **By Assignment** | Yes | Yes | | **STR Filed** | Yes | No | | **By Age** | Yes (case age buckets) | Yes (alert age buckets) | | **Pending Review**, **Avg. Handling**, **Reopens** | Yes | No | The metric tiles, **Daily Jobs** and **Team Performance** appear in both views. ::: note The counts in this chapter are example values from the test environment where the screens were captured. Some of them do not add up across charts (for example, in the Cases view **By Status** shows 25 **Closed** cases, while **By Disposition (Closed)** adds up to 70), so read them as examples of the layout, not as figures to reconcile. ::: ## Metric tiles {#s-2-2} Use the metric tiles for a quick count of the alerts and cases that are overdue, unassigned, escalated or pending. Six tiles at the top of the page each show a label, a count and a sub-label. The **Overdue Alerts** count is shown in red. ::figure[The six metric tiles, numbered 1 to 6]{src="aml-dashboard/02-metric-tiles.png" id="fig-aml-dashboard-metric-tiles"} | Tile | Sub-label | Value in [](#fig-aml-dashboard-metric-tiles) | | --- | --- | --- | | **Overdue Alerts** (1) | Past SLA Threshold | 173,346 | | **Unassigned Alerts** (2) | Awaiting Assignment | 153,865 | | **Escalated Alerts** (3) | Pending Supervisor Review | 87 | | **Pending Alerts** (4) | Awaiting Review | 14 | | **Pending Cases** (5) | Awaiting Review | 13 | | **Escalated Cases** (6) | Pending Supervisor Review | 10 | The tiles are counts only. To work the alerts or cases behind a tile, open the list in [Case Manager](#case-manager). The table shows where each count can be found again. In the captures, the chip counts on the **All Alerts** and **All Cases** tabs matched the tiles. | Tile | Where to work it | Matching count in the captures | | --- | --- | --- | | **Overdue Alerts** | Case Manager → Alerts → **All Alerts**. Click **Show Filters** and set **SLA** to **Breached** ([Alerts list](#s-3-23)). | Chip **SLA Breached** 173346 = tile 173,346 | | **Unassigned Alerts** | Case Manager → Alerts → **All Alerts**. The **Unassigned** chip shows the count ([Alerts list](#s-3-23)). | Chip **Unassigned** 153888, tile 153,865 (the two counts differ) | | **Escalated Alerts** | Case Manager → Alerts → **All Alerts**. Set **Status** to **Escalated**. | Chip **Escalated** 87 = tile 87 | | **Pending Alerts** | Case Manager → Alerts → **All Alerts**. Set **Status** to **Pending Review**. | No matching chip | | **Pending Cases** | Case Manager → Cases → **All Cases**, chip **Pending Approval**, which sets **Status** to **Pending Review** ([Filter and search cases](#s-3-2)). Act on each case as in [Review a case in Pending Review](#s-3-11). | Chip **Pending Approval** 13 = tile 13 | | **Escalated Cases** | Case Manager → Cases → **All Cases**. Click **Show Filters** and set **Status** to **Escalated** ([Filter and search cases](#s-3-2)). | Chip **Escalated** 10 = tile 10 | ::: note AML context An alert that nobody is working is a risk that nobody is managing. Overdue and unassigned counts show where the backlog is, and escalations show where a senior judgement is waiting. Teams often review these counts at the start of each day. ::: ## Case Distribution controls {#s-2-3} Use these controls before reading the charts below: they set whether the charts count cases or alerts, and over which period. The distribution panel has its own header and controls. ::figure[Case Distribution controls: View Details (1), the Cases / Alerts switch (2), the date range (3) and the range presets (4)]{src="aml-dashboard/03-distribution-controls.png" id="fig-aml-dashboard-distribution-controls"} 1. **View Details**: in the Cases view, opens the Cases list in [Case Manager](#case-manager). 2. **Cases** / **Alerts**: switches the panel between cases (**Case Distribution**) and alerts (**Alert Distribution**). The selected option is shown in white. 3. Date range picker: shows the period the charts cover, for example **18 Apr - 14 Oct**, with a calendar icon at the right. When the page was opened for these captures, it showed **8 Oct - 14 Oct**. 4. Range presets: **Today**, **7D**, **30D**, **3M**, **6M** and **1Y**. The selected preset is shown in black; in [](#fig-aml-dashboard-distribution-controls) it is **6M**, which sets the range to **18 Apr - 14 Oct**. ::: step Choose cases or alerts Click **Cases** or **Alerts**. The panel title changes to **Case Distribution** or **Alert Distribution** and the charts redraw. ::: ::: step Set the period Click a preset such as **30D**. The date range picker updates to show the new period. ::: ::: step Open the underlying list In the Cases view, click **View Details** to open the Cases list. ::: ## By Status {#s-2-4} Use By Status to see how cases or alerts are spread across statuses. It is a donut chart with a legend that gives, for each status, the count and its share of the total in brackets. ::figure[By Status in the Cases view, range 6M]{src="aml-dashboard/04-by-status-cases.png" id="fig-aml-dashboard-by-status-cases"} ::figure[Alert Distribution: the switch on Alerts (1), the range set to 6M (2) and By Status]{src="aml-dashboard/05-alert-distribution.png" id="fig-aml-dashboard-alert-distribution"} | Status | Cases view ([](#fig-aml-dashboard-by-status-cases)) | Alerts view ([](#fig-aml-dashboard-alert-distribution)) | | --- | --- | --- | | **Not Started** | 0 (0.0%) | 18,767 (10.6%) | | **Under Investigation** | 73,000 (99.8%) | 157,926 (89.2%) | | **Pending Review** | 13 (0.0%) | 8 (0.0%) | | **Escalated** | 10 (0.0%) | 85 (0.0%) | | **STR Draft** | 11 (0.0%) | Not shown | | **STR Created** | 34 (0.0%) | Not shown | | **Closed** | 25 (0.0%) | 228 (0.1%) | | **Reopened** | 35 (0.0%) | 84 (0.0%) | Cases have eight statuses and alerts six: **STR Draft** and **STR Created** apply to cases only. The statuses are described in [Case Manager](#case-manager). ## By Disposition (Closed) {#s-2-5} Use this chart to see how closed cases or alerts were dispositioned. It is a donut chart of closed records by disposition: **True Match**, **False Match** and **Potential Match**, each with its count and share. ::figure[By Disposition (Closed) in the Cases view, range 6M]{src="aml-dashboard/06-by-disposition.png" id="fig-aml-dashboard-by-disposition"} | Disposition | Cases view | Alerts view | | --- | --- | --- | | **True Match** | 43 (61.4%) | 113 (49.6%) | | **False Match** | 21 (30.0%) | 97 (42.5%) | | **Potential Match** | 6 (8.6%) | 18 (7.9%) | ## By Score and By Type (Alerts view) {#s-2-6} Use these charts to break alerts down by score band and by alert type. They appear only in the **Alerts** view, between **By Disposition (Closed)** and **By Assignment**. ::figure[By Score (1) and By Type (2) in the Alerts view]{src="aml-dashboard/07-by-score-and-type.png" id="fig-aml-dashboard-by-score-and-type"} ::: checks - **By Score** (1): a donut chart of alerts by score band, **High**, **Medium** and **Low**, each with its count and share. In [](#fig-aml-dashboard-by-score-and-type): High 3,577 (2.2%), Medium 155,404 (97.8%), Low 0 (0.0%). - **By Type** (2): a horizontal bar for each alert type, with its count and share at the right. In [](#fig-aml-dashboard-by-score-and-type): **Transaction Monitoring** 18,117 (10.2%) and **Name Screening** 158,981 (89.8%). ::: ## By Assignment {#s-2-7} Use By Assignment to see how many records are unassigned and how the rest are spread across assignees. It is a horizontal bar chart of records by assignee. The first bar is **Unassigned** (1); the other bars are named users. Names are hidden in this guide. ::figure[By Assignment: the Unassigned bar (1) and the Team / Individual switch (2); user names hidden]{src="aml-dashboard/08-by-assignment.png" id="fig-aml-dashboard-by-assignment"} The **Team** / **Individual** switch (2) at the top right changes the grouping. **Team** is selected (shown in black) in [](#fig-aml-dashboard-by-assignment). The horizontal axis scale follows the counts; in [](#fig-aml-dashboard-by-assignment) it runs from 0 to 80K. ## STR Filed {#s-2-8} Use STR Filed to follow the number of STRs filed per month. It is shown in the **Cases** view only: a line chart of STRs filed per month, with its own range presets **Today**, **7D**, **30D**, **1M**, **6M** and **1Y** at the top right (2). The title carries a link icon (1). In [](#fig-aml-dashboard-str-filed) the **6M** preset is selected and the chart runs from **Apr '26** to **Sep**. ::figure[STR Filed: the link icon (1) and its own range presets, with 6M selected (2)]{src="aml-dashboard/09-str-filed.png" id="fig-aml-dashboard-str-filed"} For the filed reports themselves, see [Regulatory Reports](#str-listing). ## By Age {#s-2-9} Use By Age to see how many records fall in each age bucket. It is a horizontal bar chart of records by age bucket. The buckets differ between the two views: | View | Age buckets | | --- | --- | | **Cases** | 0-3d, 4-7d, 8-14d, 15-30d, 30+ days | | **Alerts** | 0-24h, 1-3d, 4-7d, 8-14d, 14+ days | ::figure[By Age (1), followed by the Pending Review (2), Avg. Handling (3) and Reopens (4) tiles (Cases view)]{src="aml-dashboard/10-by-age-and-tiles.png" id="fig-aml-dashboard-by-age-and-tiles"} ## Pending Review, Avg. Handling and Reopens {#s-2-10} Use these tiles for three summary figures on cases: how many are pending review, the average handling time and the number of reopens. In the **Cases** view, three tiles close the distribution panel ([](#fig-aml-dashboard-by-age-and-tiles)): | Tile | Value in [](#fig-aml-dashboard-by-age-and-tiles) | | --- | --- | | **Pending Review** (2) | 13 | | **Avg. Handling** (3) | 6.3d (days) | | **Reopens** (4) | 218 | ## Daily Jobs {#s-2-11} Check **Daily Jobs** to see, day by day, whether the screening, monitoring and ingestion jobs ran and succeeded. It shows the outcome of the platform's scheduled jobs. It has two blocks: **Screening & Monitoring Runs** and **Data Ingestion**. ::figure[Daily Jobs: Screening & Monitoring Runs (1) and Data Ingestion (2), from 14 Oct back to 8 Oct]{src="aml-dashboard/11-daily-jobs.png" id="fig-aml-dashboard-daily-jobs"} Both blocks are grids with one row per job and one column per day, newest first. The day columns in [](#fig-aml-dashboard-daily-jobs) run from **14 Oct** back to **8 Oct**. The first column, **Job**, shows the job name as a link (shown in blue) to the screen where the job is managed. | Block | Jobs (rows) | Related chapter | | --- | --- | --- | | **Screening & Monitoring Runs** (1) | **Batch Screening**, **Delta Screening**, **TM Runs** | [Name Screening](#name-screening) (Batch and Delta Screening), [Transaction Monitoring](#transaction-monitoring) (TM Runs) | | **Data Ingestion** (2) | **Customers**, **Accounts**, **Transactions**, **Watchlist** | [Data Ingestion](#data-ingestion) | Each day cell shows a coloured dot for the outcome of that job on that day. When the job ran, the dot is followed by a figure in brackets, in most cells with a multiplier before it (for example **x2 (0)**). | Dot | Outcome | Example in [](#fig-aml-dashboard-daily-jobs) | | --- | --- | --- | | Green | **Succeeded** | Batch Screening on 9 Oct: **x3 (3K)**; every Watchlist day | | Red | **Failed** | TM Runs on 11 Oct: **x2 (0)** | | Orange | **Mixed outcomes** | TM Runs on 13 Oct: **x6 (263.6K)** | | Orange, pulsing | **In progress** | Batch Screening on 14 Oct: **(96.6K)** | | Grey, with a dash (—) or a figure | **No status** | Delta Screening on every day shown | ::: tip A red or orange dot is the cue to open the job: click its name. For file imports, check [Batch Ingestion](#s-10-1) and [Watchlist Ingestion](#s-10-4). ::: ## Team Performance {#s-2-12} Look here for analyst productivity, supervisor reviews and assignment analysis. The last panel on the page is **Team Performance**, described as **Analyst productivity, supervisor reviews, assignment analysis**, with a **See Team Performance** button at the right. ::figure[The Team Performance panel and the See Team Performance button (1)]{src="aml-dashboard/12-team-performance.png" id="fig-aml-dashboard-team-performance"} ## Daily triage from the dashboard {#s-2-13} ::path[Fyscal ARCX → AML Dashboard → Case Manager] Use this routine to go from the dashboard counts to the lists where the work is done. It uses only the tiles, chips and filters described in this guide. Adapt the order to your team's procedures.
Who
Supervisors and team leads; analysts for their own queue
Where
AML Dashboard, then Case Manager → Alerts and Cases
Output
The day's backlog listed and the job runs checked
::: step Read the tiles Open **Fyscal ARCX** → **AML Dashboard**. Note the counts on **Overdue Alerts**, **Escalated Alerts**, **Pending Cases** and **Escalated Cases** ([Metric tiles](#s-2-2)). ::: ::: step List the overdue alerts Open **Case Manager** → **Alerts** and click **All Alerts**. Click **Show Filters** and set **SLA** to **Breached**. To work one module at a time, also set **Module** to **Name Screening** or **Transaction Monitoring** ([Alerts list](#s-3-23)). ::: ::: step List the escalated alerts On the same tab, set **SLA** back to **All SLAs** and **Status** to **Escalated**. ::: ::: step Review the cases waiting for you Open **Case Manager** → **Cases**, click **All Cases**, then click the **Pending Approval** chip. The list shows the cases in **Pending Review**. Open each case and act on it as in [Review a case in Pending Review](#s-3-11). For escalated cases, click **Show Filters** and set **Status** to **Escalated**. ::: ::: step Check that the daily jobs ran Back on the dashboard, scroll to **Daily Jobs**. For **Batch Screening**, **Delta Screening** and **TM Runs**, look at the latest day columns: green marks **Succeeded**, red **Failed**, orange **Mixed outcomes** or **In progress**, and grey **No status** ([Daily Jobs](#s-2-11)). In the **Data Ingestion** block, check the **Customers**, **Accounts**, **Transactions** and **Watchlist** rows the same way. :::
Related in Get Started
Getting Started