# 3. Case Manager Case Manager is where analysts and reviewers work the alerts raised by Name Screening and Transaction Monitoring, group them into cases, record dispositions and prepare Suspicious Transaction Reports (STRs). The menu has three items: **Cases**, **Alerts** and **Config**. This chapter covers Cases and Alerts; Config is described in [Case Manager Config](#case-manager-config).
For
Analysts, supervisors and team leads
In the menu
Fyscal ARCX → Case Manager
Reading time
About 50 min
The sections below follow the Case Manager menu (Cases, then Alerts). To follow an investigation from start to finish, read them in this order: ::: checks - **1. Triage alerts**: [Alerts list](#s-3-23), [Alert Details: Name Screening](#s-3-24), [Alert Details: Transaction Monitoring](#s-3-25) and [Work an alert](#s-3-26). - **2. Investigate a case**: [Cases list](#s-3-1), [Filter and search cases](#s-3-2), [Case statuses and dispositions](#s-3-3), [Case Details](#s-3-4), the evidence in [Customer, accounts and matches](#s-3-5) and [Transaction Monitoring evidence tabs](#s-3-6), [Timeline and notes](#s-3-7), [Case Copilot](#s-3-8) and [Add alerts to a case](#s-3-9). - **3. Decide and review**: [Dispose alerts and close a case](#s-3-10), [Review a case in Pending Review](#s-3-11) and [Reopen a case](#s-3-12). - **4. File an STR**: [File an STR](#s-3-13), [Open the STR wizard](#s-3-14), the six steps ([1](#s-3-15), [2](#s-3-16), [3](#s-3-17), [4](#s-3-18), [5](#s-3-19), [6](#s-3-20)), [After the STR is filed](#s-3-21) and [Common blocks](#s-3-22). :::
  1. Alert raisedName Screening or Transaction Monitoring, listed under Alerts
  2. Grouped into a caseAutomatically, or with Add Alerts or Group into Case
  3. InvestigateMatches or evidence tabs, Timeline & Notes, Case Copilot
  4. DecideDispose Alert for each alert, then the case Disposition
  5. File STRSix-step wizard; the STR is listed in Regulatory Reports
Diagram 3.1 — From alert to STR in Case Manager
An alert is raised by Name Screening or Transaction Monitoring and appears under **Alerts**. Alerts are merged into cases automatically, as set in Case Creation & Assignment ([Case Manager Config](#case-manager-config)), or by hand with [Add Alerts](#s-3-9) on a case or [Group into Case](#s-3-26) on an alert. On the case you review the evidence, record a disposition for each alert and for the case, and, where the activity is suspicious, file a Suspicious Transaction Report (STR) from the case. A filed STR is listed in [Regulatory Reports](#str-listing). ::: note AML context An alert is a single detection: one screening match or one rule breach. A case brings together the alerts about one customer so that the evidence, the decision and its rationale are recorded once and can be reviewed later. An STR is the report sent to the financial intelligence unit when the investigation concludes that the activity is suspicious. ::: ## Cases list {#s-3-1} ::path[Fyscal ARCX → Case Manager → Cases] The **Cases** screen lists cases in two tabs. **My Queue** shows the cases assigned to you. **All Cases** shows every case you can see, with summary chips above the list. Each tab shows its count (in the example, My Queue 4 and All Cases 73.1K). ::figure[The Cases screen on the All Cases tab, with the summary chips, search and the case list]{src="case-manager/01-cases-list.png" id="fig-case-manager-cases-list"} ::: legend 1. **My Queue** and **All Cases** tabs, each with a count. 2. Summary chips (All Cases only): **Unassigned**, **Escalated**, **Pending Approval** and **Active Agents**, each with a count. Clicking **Pending Approval** filters the list to cases in **Pending Review** (see [Filter and search cases](#s-3-2)). 3. Search box: *Search by Case Title / ID or Customer Name*. 4. **Refresh** reloads the list. **Show Filters** opens the filter bar (the button then reads **Hide Filters**). 5. The case list. On All Cases, each row and the header have a checkbox. 6. Pagination: *Showing 1-10 of 73127* on the left; *Page 1 of 7313* with first, previous, next and last page buttons on the right. ::: | Column | What it shows | | --- | --- | | Case Title / ID | The case title (the customer name or, for some cases, an alert ID) and the case ID, for example *CASE-2026-0034617*, with a copy icon. | | Status | The case status as a coloured tag (see [Case statuses and dispositions](#s-3-3)). | | Disposition | The case disposition, for example **True Match**, or **-** when none has been recorded. | | Assigned To | The user the case is assigned to, or **-**. | | Alerts | The number of alerts in the case. | | Case Age | Days since the case was created, for example *9 Days*. | | Case Origin | **Manual** or **Automated**. | | Created At | Creation date and time, for example *26 Sept, 06:14:00 PM*. The column header carries a sort indicator. | Click a row to open the case in [Case Details](#s-3-4). ## Filter and search cases {#s-3-2} ::path[Fyscal ARCX → Case Manager → Cases → Show Filters] The filter bar narrows the current tab. Filters combine with each other and with the search box. | Filter | Default | Options | | --- | --- | --- | | Status | All Statuses | All Statuses, Not Started, Under Investigation, Pending Review, Escalated, STR Draft, STR Created, Closed, Reopened | | Creation Period | Pick a date range | A two-month calendar for choosing a start and end date | | Age Period | Any Age | Any Age, Less than a day, 1 to 3 days, 3 to 7 days, 7 to 30 days, More than 30 days | | Case Origin | All Origins | All Origins, Manual, Automated | | Assignee | All Assignees | A list of users. The signed-in user is labelled *(You)*. | ::: step Open the filter bar Click **Show Filters**. The **Status**, **Creation Period**, **Age Period**, **Case Origin** and **Assignee** filters appear below the search box. ::: ::: step Filter by status Open **Status** and choose one status. The current choice is ticked. ::figure[The Status filter open, with its nine options; the current choice is ticked]{src="case-manager/02-cases-filter-status.png" id="fig-case-manager-cases-filter-status"} ::: ::: step Filter by creation date Click **Creation Period**. A calendar showing two months opens; use the arrows to move between months, then click the first and last day of the range. ::figure[The Creation Period calendar]{src="case-manager/03-cases-filter-creation-period.png" id="fig-case-manager-cases-filter-creation-period"} ::: ::: step Filter by age or origin Open **Age Period** to choose how long cases have been open, or **Case Origin** to show only **Manual** or **Automated** cases. ::figure[The Age Period filter]{src="case-manager/04-cases-filter-age-period.png" id="fig-case-manager-cases-filter-age-period"} ::figure[The Case Origin filter]{src="case-manager/05-cases-filter-case-origin.png" id="fig-case-manager-cases-filter-case-origin"} ::: ::: step Use a summary chip On All Cases, click the **Pending Approval** chip (1). The **Status** filter is set to **Pending Review** (2), an active-filter tag *Status: Pending Review* appears with an **×** to remove it (3), **RESET FILTERS** appears beside it (4), and the **All Cases** count changes to the filtered total, 13 in the example (5). ::figure[All Cases after clicking Pending Approval (1): the Status filter (2), the active-filter tag (3), RESET FILTERS (4) and the filtered count (5)]{src="case-manager/06-cases-pending-approval.png" id="fig-case-manager-cases-pending-approval"} ::: ::: step Clear the filters Click **×** on an active-filter tag to remove that filter, or click **RESET FILTERS** to remove them all. ::: ## Case statuses and dispositions {#s-3-3} These are the values offered by the **Status** filter and the case **Disposition** dropdown, with what the case screen shows for each. | Status | What the screen shows | | --- | --- | | Not Started | Offered by the Status filter. No case in this status was captured for this guide. | | Under Investigation | Offered by the Status filter, and one of the **Case Status** values of the case-creation group in [Case Creation & Assignment](#s-4-1). No case in this status was captured for this guide. | | Pending Review | A disposition is waiting for a reviewer. The case shows the **Pending Review** panel with **Review Decision**, **Reject** and **Approve** (see [Review a case in Pending Review](#s-3-11)). Counted by the **Pending Approval** chip. | | Escalated | Counted by the **Escalated** chip. The escalated example case shows **Add Alerts**, with **Disposition** (*Select Outcome*) and **Dispose Alert** greyed out ([](#fig-case-manager-case-escalated)). | | STR Draft | The case bar shows **Preview STR** and **ReOpen**. | | STR Created | The case bar shows **Download STR** and **ReOpen**. | | Closed | The case bar shows the decision (Rationale Code, Details, Decided On, Decided By). The example Closed case, with disposition True Match, shows **File STR** and **ReOpen**. | | Reopened | A closed case that has been reopened. Its timeline records a **Reopened** event with *previous\_status: closed*. The reopened example case ([](#fig-case-manager-case-detail)) shows **Add Alerts**, the alert strip and **Dispose Alert**, and **Disposition** reads *Select Outcome*. | #### What the case bar shows in each status The buttons in the case bar change with the status. The table records what each example case shows; a status with no captured example is left out. **Yes**: shown; **Partial**: shown greyed out; **No**: not shown.
Case bar controlReopenedEscalatedPending ReviewClosedSTR DraftSTR Created
Add AlertsYesYesNoNoNoNo
Dispose AlertYesPartialGreyed outNoNoNoNo
Disposition reads Select OutcomeYesYesGreyed outNoShows True MatchNoShows True MatchNoShows True MatchNoShows True Match
Reject / ApproveNoNoYesNoNoNo
File STRNoNoNoYesNoNo
Preview STRNoNoNoNoYesNo
Download STRNoNoNoNoNoYes
ReOpenNoNoNoYesYesYes
Example cases: Reopened CASE-2026-0034617 ([](#fig-case-manager-case-detail)), Escalated CASE-2026-0107633 ([](#fig-case-manager-case-escalated)), Pending Review CASE-2026-0034612 ([Review a case in Pending Review](#s-3-11)), Closed CASE-2026-0034613 ([Dispose alerts and close a case](#s-3-10)), STR Draft CASE-2026-0107624 and STR Created CASE-2026-0034611 ([Open the STR wizard](#s-3-14) and [After the STR is filed](#s-3-21)). The escalated example is assigned to another user; the screen does not say why its controls are greyed out. ::figure[An Escalated case (CASE-2026-0107633): the Escalated status (1), Disposition greyed out (2), Add Alerts (3) and Dispose Alert greyed out (4)]{src="case-manager/07-case-escalated.png" id="fig-case-manager-case-escalated"} #### Status changes recorded on screen
  1. Closed
  2. ReOpen
  3. Reopened
  4. Disposition Submitted
  5. Closed
Diagram 3.2 — Case status changes recorded in a case timeline
The timeline of CASE-2026-0034617 records both changes. **ReOpen** on a Closed case gives the status **Reopened**, and the **Reopened** event shows *previous\_status: closed*. On the reopened case, a **Disposition Submitted** event tagged **Case closed** closes it again; the next **Reopened** event again shows *previous\_status: closed*. The STR statuses are covered in [File an STR](#s-3-13).
DispositionWhere it appears
True MatchThe case Disposition dropdown, the alert Disposition dropdown and the Dispose Alert dialog. Before a disposition is chosen, the case dropdown reads Select Outcome and the alert dropdown Select outcome; list columns show -.
False Match
Potential Match
::: note AML context In general use, **True Match** means the customer is the listed party or the activity is confirmed as suspicious; **False Match** means it is a different party or the activity is explained; **Potential Match** means a match cannot be ruled out without more information. How a Potential Match affects the case in Fyscal ARCX has not been confirmed. ::: ## Case Details {#s-3-4} ::path[Fyscal ARCX → Case Manager → Cases → (click a case)] **Case Details** shows one case: its status and owner, the alerts it contains, the customer, and the evidence behind each alert. The example is CASE-2026-0034617 for the customer Pooja Sharma, with six Name Screening alerts. ::figure[Top of Case Details for CASE-2026-0034617]{src="case-manager/08-case-detail.png" id="fig-case-manager-case-detail"} ::: legend 1. Header: **Case Details**, the case ID (with a copy icon), the case age (*60 Days* in the example), the number of alerts (*6 Alerts*) and the creation date and time, with the breadcrumb *Fyscal ARCX › Cases › CASE-2026-0034617*. At the right are **Timeline & Notes** (see [Timeline and notes](#s-3-7)) and **Case Copilot** (see [Case Copilot](#s-3-8)). 2. Case bar: **Status**, **Assigned To** (a dropdown of users) and **Disposition** (a dropdown with **True Match**, **False Match** and **Potential Match**). 3. **Add Alerts** adds ungrouped alerts to this case (see [Add alerts to a case](#s-3-9)). 4. Alert strip: one tab per alert, showing the module (**NS** for Name Screening, **TM** for Transaction Monitoring), the alert ID, the customer name, the alert's disposition once recorded, and the score band with its percentage. The selected tab is underlined in blue and the rest of the page shows that alert. When there are more tabs than fit, the strip continues to the right. 5. **Dispose Alert** records a disposition for the selected alert (see [Dispose alerts and close a case](#s-3-10)). 6. Customer card (see [Customer, accounts and matches](#s-3-5)). 7. **Accounts**, with the number of accounts in brackets. ::: Below the customer card, a Name Screening alert shows **Matches**; a Transaction Monitoring alert shows the tabs **Analytics**, **Transactions**, **Other Cases / Alerts** and **Rule Analysis** (see [Transaction Monitoring evidence tabs](#s-3-6)). The buttons in the case bar change with the status: see the table in [Case statuses and dispositions](#s-3-3). ## Customer, accounts and matches {#s-3-5} The customer card identifies the customer behind the selected alert. For the full customer profile, see [Customer 360](#customers). | Area | What it shows | | --- | --- | | Card header | Customer name and customer ID (with a copy icon), then tags: **TYPE** (for example INDIVIDUAL, CORPORATE), **SEGMENT**, **RISK** (band and score, for example HIGH (93)), **KYC**, **STATUS**, **COUNTRY** and **PEP Flag**. | | Tiles | **DECLARED INCOME**, **EXPECTED MONTHLY SPEND**, **SOURCE OF FUNDS** and **ONBOARDING** (date, time and channel, for example *via BRANCH*). A tile is left out when the value is missing. | | More / Less | **More** expands three panels and changes to **Less**: **BUSINESS & EMPLOYMENT** (Designation, Employer, Segment, Source of Funds, Country of Operations), **FINANCIAL INFORMATION** (Declared Income, Expected Monthly Spend, Purpose, Onboarding Channel, Expected Txn Frequency) and **Additioanl Details** (City, Country, Sanctions). | | Accounts (n) | One row per account: account number, account type (for example CURRENT), bank and status (for example ACTIVE, FROZEN, CLOSED). The arrow at the right expands the row to show **Type**, **Bank**, **Holding**, **Currency**, **Bank Country** and **Opened**. | ::figure[The customer card expanded: Less (1), BUSINESS & EMPLOYMENT (2), FINANCIAL INFORMATION (3) and Additioanl Details (4)]{src="case-manager/09-case-customer-more.png" id="fig-case-manager-case-customer-more"} ::figure[An account row expanded: Type, Bank, Holding, Currency, Bank Country and Opened]{src="case-manager/10-case-account-expanded.png" id="fig-case-manager-case-account-expanded"} #### Matches (Name Screening alerts) **Matches** compares the customer with each watchlist candidate found for the selected alert. The red tag gives the number of candidates (*Matches: 1*). ::: checks - The grey left column (1) lists the customer's own values for **Name**, **Nationality**, **Date of Birth**, **Address** and **Entity Type**, under the row labels **Match Score** and **UID (watchlist)**. - Each candidate column (2) shows the score band and percentage (for example *LOW 87.94%*), the watchlist category (for example INDIVIDUAL), the watchlist **UID**, and for each field the watchlist value with its **Weightage** and **Score**. - The candidate with the blue border is the one shown in the panel below (3), headed **Selected:** with the candidate's name, band, **UID**, **Screening** number and **Category**. ::: ::figure[Matches for CASE-2026-0034617: the customer column (1), one watchlist candidate (2) and the Selected panel (3) on the Identity tab (4)]{src="case-manager/11-case-matches.png" id="fig-case-manager-case-matches"} The **Selected** panel has two tabs (4): | Tab | Sections and fields | | --- | --- | | Identity | **IDENTITY SUMMARY**: Entity Type, Date of Birth, Place of Birth, Nationality, Citizenship, Address, Deceased. **KNOWN ALIASES & SPELLINGS**: Primary Aliases. Missing values read *Not Provided*, *Unknown* or *—*. | | Additional Information | **LIST CLASSIFICATION**: Category, Sub-Category. **ASSOCIATES**: watchlist UIDs of associated entries. **FURTHER INFORMATION**: BIOGRAPHY, IDENTIFICATION, REPORTS. **LIST METADATA**: List Entry Date, Last Updated. **KEYWORDS & SOURCES**: External Sources, with the number of sources and a link for each. | ::figure[The Additional Information tab: LIST CLASSIFICATION (1), ASSOCIATES (2), FURTHER INFORMATION (3), LIST METADATA (4) and KEYWORDS & SOURCES (5)]{src="case-manager/12-case-match-additional-info.png" id="fig-case-manager-case-match-additional-info"} ::: note The Weightage and Score shown are those recorded for the alert. How weightages are configured is described in [Name Screening](#name-screening). ::: ## Transaction Monitoring evidence tabs {#s-3-6} When the selected alert is a Transaction Monitoring (**TM**) alert, four tabs appear below the customer card. The same tabs appear on a Transaction Monitoring alert in [Alert Details](#s-3-25). | Tab | What it shows | | --- | --- | | Analytics | For the customer, period buttons **1D**, **7D**, **30D**, **All** and an **Alert Window** checkbox. **INCOMING** and **OUTGOING** each give, per currency, **TOTAL** (with the number of transactions and senders or recipients), **AVG** and **MAX** (with the transaction ID). Below: **Top Counterparties by Amount** and **Transaction Types**, five of each, with buttons such as *14 more Counterparties* and *4 more Types*. | | Transactions (n) | **Transaction Pattern** with **Transaction Trends** and **Volume Heatmap** views, a date range, **Day**, **Week** and **Month**, and the charts **Transaction Volume** and **Transaction Count**. **Transaction Table** with the filters **All Types**, **All Channels**, **Price range**, **Pick a date range**, **Sender ID**, **Receiver ID** and the **Triggered Txns** checkbox, and the columns Txn ID, Sender, Receiver, Amount, Type, Channel, Date. Each row has an arrow at the right to expand it. **Export CSV** sits at the top right. | | Other Cases / Alerts | A **Cases** / **Alerts** switch, each with a count. Cases uses the case-list columns with **Status** and **Date Range** filters; Alerts uses the alert-list columns with **Status**, **Disposition** and **Date Range** filters. | | Rule Analysis | **RULE TRIGGERED**: the rule name with a tag (for example *internal*), the **Window** start and frequency (for example *every 1 Month*), the number of breaches, and each breached condition (for example *transactions.amount > 10000*) tagged **Breach**. | ::figure[Analytics tab for CASE-2026-0034611 (Rafael Serrano Dimaculangan): the evidence tabs (1), period buttons and Alert Window (2), INCOMING (3) and OUTGOING (4) totals per currency, Top Counterparties by Amount (5) and Transaction Types (6)]{src="case-manager/13-case-analytics.png" id="fig-case-manager-case-analytics"} ::figure[Transactions tab with the Month view: the evidence tabs (1), Export CSV (2), Transaction Trends and Volume Heatmap (3), Day, Week, Month and the date range (4), the table filters (5), Triggered Txns (6) and the table columns (7)]{src="case-manager/14-case-transactions.png" id="fig-case-manager-case-transactions"} ::figure[Other Cases / Alerts tab: the Cases and Alerts switch with counts (1) and the Status and Date Range filters (2)]{src="case-manager/15-case-other-cases.png" id="fig-case-manager-case-other-cases"} ::figure[Rule Analysis tab: rule H\_V\_T with its tag and window (1), the breach count (2) and the breached condition transactions.amount > 10000 (3)]{src="case-manager/16-case-rule-analysis.png" id="fig-case-manager-case-rule-analysis"} ## Timeline and notes {#s-3-7} ::path[Case Details → Timeline & Notes] **Timeline & Notes** opens the **Activity Timeline** panel on the right, headed with the case ID. It holds the case notes and a dated log of what happened to the case, newest first. ::figure[Activity Timeline for CASE-2026-0034617: the note box (1), Attach File (2), Add note, greyed out while the box is empty (3), the newest event (4) and the close button (5)]{src="case-manager/17-case-timeline.png" id="fig-case-manager-case-timeline"} ::: step Add a note Type in **ADD A NOTE** (*Add an investigation note...*) (1). To attach a document, click **Attach File** (2). Click **Add note** (3); it is greyed out while the note box is empty. ::: ::: step Read the events Each event (4) shows its type, the user (or *System*) and the date and time. The events seen on cases are listed below. Click **×** (5) to close the panel. ::: | Event | Details shown | | --- | --- | | Created | The first event. *Alert Added* with the alert and a **View alert timeline** link. | | Linked to Case | Each alert added to the case, with customer name, alert ID, band and score, and **View alert timeline**. | | Disposition Submitted | Tags such as **Case closed** and the number of alerts, the **Rationale code** and **Rationale**. **View per-alert dispositions(n)** expands to list each alert with its band and score, disposition, rationale code and rationale. | | Reopened | *previous\_status* (for example closed), the **Rationale**, and *n alert(s) Reopened* with a link to each alert. | ## Case Copilot {#s-3-8} ::path[Case Details → Case Copilot] **Case Copilot** (*AI Investigation Assistant*) is a chat panel that answers questions about the open case. On first use it greets you by first name and asks *How can I help you with this case?*. Its prompt and model are set in Agentic Workflows (see [Case Manager Config](#case-manager-config)). ::figure[Case Copilot after Summarize case (1): the answer in headed sections (2), the suggested prompts (3), and the new-chat and close icons (4)]{src="case-manager/18-case-copilot.png" id="fig-case-manager-case-copilot"} ::: step Ask a question Click **Case Copilot**, then click one of the prompts under *What else would you like to know?*: **Summarize case**, **Review customer profile**, **Check watchlist matches**, **Explain match scores**, **Compare alerts**, **Review timeline**, **Risk assessment** or **Draft rationale**. ::: ::: step Read the answer Each answer appears under the prompt you chose, in headed sections. **Summarize case** returns CASE OVERVIEW, ALERT SUMMARY, CUSTOMER SNAPSHOT, INVESTIGATION STATUS and RECOMMENDED NEXT STEPS. **Explain match scores** returns OVERALL SCORE, COMPONENT ANALYSIS, SCORE RELIABILITY and CONCLUSION. Earlier answers stay in the panel. ::: ::: step Start again or close The icon at the top right starts a new chat; **×** closes the panel. ::: ::: note Check Copilot answers against the case before relying on them. In [](#fig-case-manager-case-copilot) the summary gives the case age as 49 days, while the case header in [](#fig-case-manager-case-detail) shows 60 Days. ::: ## Add alerts to a case {#s-3-9} ::path[Case Details → Add Alerts] **Add Alerts to Case** lists alerts that are not yet in a case (*Select ungrouped alerts to merge into* the case ID). ::figure[The Add Alerts to Case dialog with nothing selected: search (1), an ungrouped alert (2), the counter and paging (3), Cancel and Add alerts (4)]{src="case-manager/19-case-add-alerts.png" id="fig-case-manager-case-add-alerts"} ::: step Find the alerts Click **Add Alerts**. Search with *Search by customer name or Alert ID*, or page through the list with **Prev** and **Next** (the page indicator reads, for example, *1 / 6738*). Each row shows the customer name, status, date and time, alert number (for example *#174489*), score band and module. ::: ::: step Select and add Tick the alerts to add. The counter at the bottom shows how many are selected out of the total (*0 selected · 68810 total* in the example). Click **Add alerts**, or **Cancel** to close without changes. ::: Which alerts are grouped into cases automatically is set in Case Creation & Assignment (see [Case Manager Config](#case-manager-config)). ## Dispose alerts and close a case {#s-3-10}
Where
Case Details → Dispose Alert, then the case bar Disposition
Required
Disposition, Rationale Code, Rationale Details (10 characters or more)
Optional
Supporting Documents
Recorded as
A Disposition Submitted event in the case timeline
Each alert in a case gets its own disposition through **Dispose Alert**. The case has its own **Disposition** in the case bar. ::: step Select the alert In the alert strip, click the alert's tab and review its customer, matches or transaction evidence. ::: ::: step Open Dispose Alert Click **Dispose Alert**. The **Dispose Alert** dialog opens for the selected alert, whose ID appears under the title. ::figure[The Dispose Alert dialog: DISPOSITION (1), Rationale Code (2), Rationale Details (3), Supporting Documents (4), Cancel and Submit Decision (5)]{src="case-manager/20-case-dispose-alert.png" id="fig-case-manager-case-dispose-alert"} ::: ::: step Fill in the decision Complete the fields in the table below, then click **Submit Decision**. **Cancel** closes the dialog without saving. Repeat for each alert in the case. ::: | Field | What it expects | Required | Options or format | | --- | --- | --- | --- | | DISPOSITION | The outcome for this alert | Yes | True Match, False Match, Potential Match | | Rationale Code | The coded reason for the outcome | Yes | A dropdown. It reads *Select disposition first* until a disposition is chosen. Example code: *Identification number of the user is the same as the watchlist*. | | Rationale Details | Your explanation (*Explain your rationale*) | Yes | Minimum 10 Characters | | Supporting Documents | Files that support the decision | No | **Attach File** | ::: step Set the case disposition In the case bar, open **Disposition** (*Select Outcome*) and choose **True Match**, **False Match** or **Potential Match**. ::figure[The case Disposition list open on a Reopened case: True Match, False Match and Potential Match]{src="case-manager/21-case-disposition.png" id="fig-case-manager-case-disposition"} ::: A closed case shows **Status** Closed, the chosen **Disposition**, and a decision block with **Rationale Code**, **Details**, **Decided On** and **Decided By**. Each alert tab shows its own disposition. The timeline records a **Disposition Submitted** event tagged **Case closed**. ::figure[A Closed case (CASE-2026-0034613): Status Closed (1), Disposition True Match (2), the decision block (3), and File STR and ReOpen (4)]{src="case-manager/22-case-closed.png" id="fig-case-manager-case-closed"} The case timelines show two ways a case has reached **Closed**: | Path | Timeline events, oldest first | Example | | --- | --- | --- | | Direct | **Disposition Submitted**, tagged **Case closed** and the number of alerts (for example *1 Alert*) | CASE-2026-0034611 | | With review | **Review Requested** (tagged **Case closed**, with the disposition True Match and the rationale), then **Disposition Approved** by a second user (tagged **Case closed**, *5 Alerts*) | CASE-2026-0034613 | In both paths the closing event names all of the case's alerts, so the case disposition closes the case together with its alerts. ::: note On a Reopened case with six undisposed alerts (CASE-2026-0034617), both **Dispose Alert** and the case **Disposition** are available. The steps in this guide dispose of each alert first. ::: ::: note AML context Reviewers, auditors and supervisors read the rationale long after the decision. Say what you compared (for example name, date of birth, ID number or transaction pattern), what you found and why the disposition follows from it. The product checks only the minimum length of 10 characters. ::: ## Review a case in Pending Review {#s-3-11} A case in **Pending Review** shows a **Pending Review** panel under the case bar. Use **Pending Approval** on All Cases to list these cases. ::figure[The Pending Review panel on CASE-2026-0034612: the request (1), the decision card (2), Review Decision (3), and Reject and Approve (4)]{src="case-manager/23-case-pending-review.png" id="fig-case-manager-case-pending-review"} | Part of the panel | What it shows | | --- | --- | | Request (1) | **Rationale Code**, **Rationale Details**, **Requested by** and **Requested On**. | | Decision card (2) | The customer, **Disposition** (for example True Match), **Rationale Code** and **Note**. | | Review Decision \* (3) | A required text box: *Explain your reasoning for approve or reject*. | | Reject / Approve (4) | The two decision buttons. | ::: step Record the review Read the request and the decision card. Type your reasoning in **Review Decision**, then click **Reject** or **Approve**. ::: ::: note AML context A second review of a disposition (the "four-eyes" principle) is a common control: a different person checks that the evidence supports the decision before it stands. Write the review reasoning so that someone reading the case later can see what was checked. ::: ## Reopen a case {#s-3-12} Cases in **Closed**, **STR Draft** and **STR Created** show **ReOpen** in the case bar. ::figure[The Reopen Case dialog: Alert To Reopen with all disposed alerts pre-selected (1), Reason for reopening (2), Supporting Documents (3), Cancel and Reopen (4)]{src="case-manager/24-case-reopen.png" id="fig-case-manager-case-reopen"} ::: step Choose the alerts Click **ReOpen**. The **Reopen Case** dialog lists the case's alerts under **Alert To Reopen**, each with its disposition. *All disposed alerts are pre-selected. Uncheck any that should remain closed.* ::: ::: step Give the reason Enter **Reason for reopening** (required; *Provide a rationale for opening this case*). Optionally add **Supporting Documents** with **Attach File**. Click **Reopen**, or **Cancel**. ::: A reopened case has the status **Reopened**, and its timeline shows a **Reopened** event with the previous status, the rationale and the reopened alerts. ## File an STR {#s-3-13} ::path[Fyscal ARCX → Case Manager → Cases → (open a case) → File STR or Preview STR]
Where
Case Details → File STR, or Preview STR for a draft
Format
GoTRACS-compliant STR for the AMLC
Steps
Six, from Select Alerts to Narratives
Afterwards
The filed STR is listed in Regulatory Reports
The STR wizard, titled **Suspicious Transaction Report (STR)** with the subtitle *GoTRACS-compliant STR filing for AMLC*, prepares a Suspicious Transaction Report for the AMLC from a case. It opens over Case Details and shows the case ID in its header. The case bar shows the STR button that matches the case status: | Case status | STR button | What it does | | --- | --- | --- | | Closed (in the examples, with disposition **True Match**) | **File STR** | Opens the wizard to file an STR for the case. | | STR Draft | **Preview STR** | Reopens the saved draft at the step where it was left. | | STR Created | **Download STR** | Shown once the STR has been filed (see [After the STR is filed](#s-3-21)). | #### Before you start ::: checks - Dispose the case's alerts and close the case first (see [Dispose alerts and close a case](#s-3-10)). **File STR** appears only once the case is closed: open cases (for example Reopened) show **Dispose Alert** and the **Disposition** list instead, and no STR button. In the examples, **File STR** is shown on a **Closed** case with the disposition **True Match**. - After the STR is created, the timeline records an **STR Created** event and the case bar shows **Download STR** in place of **File STR** (CASE-2026-0034611). - You need at least one suspicious transaction for step 4. **Select Suspicious Transactions** is required, and **Next Step** stays disabled while no transaction is selected (see [Common blocks](#s-3-22)). - Have the **Date of determination** ready. On step 2 it sets the **Filing deadline** message shown next to it. ::: ::: note AML context A Suspicious Transaction Report tells the financial intelligence unit what happened, who was involved and why it is suspicious. Reports are expected within a set time of the point at which suspicion is formed, which is why the wizard asks for the date of determination and shows a filing deadline. ::: #### The six steps The progress bar across the top of the wizard shows the six steps. The current step has a blue number; a step already completed shows a green tick; later steps show a grey number. ::figure[The STR wizard for CASE-2026-0107624: the title and case ID (1), steps 1 to 3 completed (2), step 4 Transaction current (3), the later steps (4) and the close button (5)]{src="case-manager/25-str-wizard-steps.png" id="fig-case-manager-str-wizard-steps"} ::: legend 1. The title, **Suspicious Transaction Report (STR)**, with *GoTRACS-compliant STR filing for AMLC* and the case ID. 2. Steps already completed show a green tick (here steps 1 to 3). 3. The current step has a blue number (here step 4, **Transaction**). 4. Later steps show a grey number. 5. The close button (×). ::: | Step | Name | What you do | | --- | --- | --- | | 1 | [**Select Alerts**](#s-3-15) | Choose which of the case's alerts the STR covers. | | 2 | [**Report Type**](#s-3-16) | Choose the STR type and fill in the report header, including the date of determination. | | 3 | [**Reason for suspicion**](#s-3-17) | Tick the SC, PC or MC reason codes. | | 4 | [**Transaction**](#s-3-18) | Select the suspicious transactions to report. | | 5 | [**Subject parties**](#s-3-19) | Check the parties derived from the selected transactions. | | 6 | [**Narratives**](#s-3-20) | Write the STR narrative. | | Control | Where it appears | What it does | | --- | --- | --- | | **Next Step** | Footer, right | Moves to the next step. Greyed out while a required entry on the step is missing (seen on step 4). | | **Previous Step** | Footer, left; not shown on step 1 | Moves back one step. | | **Save as draft** | Footer, next to Next Step, while the STR is a draft | Saves your entries as a draft. Not shown when a filed STR is opened read-only from Regulatory Reports. | | **×** | Top right of the wizard | Closes the wizard and returns to Case Details. | The codes after field names, such as *H-3* or *D-SD-2*, are the GoTRACS field codes shown on screen. A red **\*** marks a required field. ## Open the STR wizard {#s-3-14} Open the wizard from the case: with **File STR** to start an STR, or with **Preview STR** to continue a saved draft. ::: step Start an STR from a closed True Match case Open the case in Case Details. Check that **Status** reads **Closed** and **Disposition** reads **True Match**, then click **File STR** in the case bar. ::figure[File STR in the case bar of a Closed case with disposition True Match (CASE-2026-0034613)]{src="case-manager/26-str-open-file-str.png" id="fig-case-manager-str-open-file-str"} ::: ::: step Find a case with a saved draft To continue a draft, go to **Cases**, open the **All Cases** tab and type the case ID in *Search by Case Title / ID or Customer Name*. The case shows the status **STR Draft**. Click the row to open the case. To list every draft, set the **Status** filter to **STR Draft** (see [Filter and search cases](#s-3-2)). ::figure[All Cases (1) searched for CASE-2026-0107624 (2), with the active-filter tag (3): one case, Bharat Traders LLP, in STR Draft (4)]{src="case-manager/27-str-open-find-draft.png" id="fig-case-manager-str-open-find-draft"} ::: ::: step Reopen the draft Click **Preview STR** in the case bar. The wizard opens at the step where the draft was left. In the example it opens at step 4 **Transaction**, with steps 1 to 3 ticked ([](#fig-case-manager-str-wizard-steps)). Use **Previous Step** to go back to earlier steps. ::figure[An STR Draft case (CASE-2026-0107624, Bharat Traders LLP): the STR Draft status (1), Preview STR (2) and ReOpen (3)]{src="case-manager/28-case-str-draft.png" id="fig-case-manager-case-str-draft"} ::: ## Step 1: Select Alerts {#s-3-15} Choose which of the case's alerts the STR covers. The screen states: *Transactions and parties from selected alerts appear in subsequent steps.* ::figure[Step 1, Select Alerts, for CASE-2026-0107624: the instruction (1), Select all and Deselect all (2), one alert, ALT-159099, selected (3), and the counter (4)]{src="case-manager/29-str-step1-select-alerts.png" id="fig-case-manager-str-step1-select-alerts"} ::: legend 1. **Alerts to include in STR**, with the instruction above. 2. **Select all** and **Deselect all**. 3. An alert row: a checkbox, the alert number (*ALT-159099*), the alert ID (*ALT-NS-17092026-009614*) with a copy icon, the customer ID (*CUST0111518*) and **Rule:**. A Name Screening alert shows **Rule:** with no value; a Transaction Monitoring alert shows its rule and its number of transactions (see [Regulatory Reports, step 1](#s-6-4)). 4. The counter, *1 of 1 Selected*. ::: The footer of step 1, below the list, holds **Save as draft** and **Next Step**. Step 1 has no **Previous Step**. | Field | Code | Required | What to enter or the options | | --- | --- | --- | --- | | Alerts to include in STR | None shown | No marker | One checkbox per alert in the case. **Select all** ticks every alert; **Deselect all** clears them. The counter shows how many are selected out of the total. | ::: step Tick the alerts to report Tick each alert the STR should cover, or click **Select all**. Untick any alert to leave out. Check the counter (for example *1 of 1 Selected*). ::: ::: step Go to step 2 Click **Next Step**. Step 1 now shows a green tick and step 2 **Report Type** opens. ::: ## Step 2: Report Type {#s-3-16} Choose the type of STR and complete the report header. The values in the figures are those saved in the draft for CASE-2026-0107624. ::figure[Step 2, Report Type: STR Type (1), Institution code (2), Supervising agency (3), Submission type (4), STR trigger (5), Date of determination (6) and the Filing deadline message (7)]{src="case-manager/30-str-step2-report-type.png" id="fig-case-manager-str-step2-report-type"} | # | Field | Code | Required | What to enter or the options | | --- | --- | --- | --- | --- | | 1 | STR Type | None shown | Yes (\*) | One of five radio-button cards: **STRR - Regular STR**, **STRA - Per Account**, **STRHP - High Priority**, **STRHU - Highly unusual** and **STRBR - Bulk Report**. See [STR types compared](#s-3-16-types) below. | | 2 | Institution code | H-3 | No marker | Greyed out and tagged **auto-filled**; you do not type it. Help text: *18-digit code assigned by AMLC/BSP*. Example: *FYSCALTECH20260001*. | | 3 | Supervising agency | H-2 | Yes (\*) | Bangko Sentral ng Pilipinas; Securities and Exchange Commission; Insurance Commission; Designated Non-Financial Businesses and Professions; Philippine Amusement and Gaming Corporation; Cagayan Economic Zone Authority; Aurora Pacific Economic Zone and Freeport; People's Bank Supervised by BSP ([](#fig-case-manager-str-step2-supervising-agency)). | | 4 | Submission type | H-6 | Yes (\*) | New; Edit/Correction; Delete; Test ([](#fig-case-manager-str-step2-submission-type)). | | 5 | STR trigger | D-SD-3 | Yes (\*) | CP (proactive/alerts); PPP (Public Private Partnership); KYC Docs requested by AMLC/AMLC Referrals; Shared AMLC Studies; Watch list; Freeze Orders; Targeted Financial Sanctions (TFS) ([](#fig-case-manager-str-step2-str-trigger)). | | 6 | Date of determination | D-SD-2 | Yes (\*) | A date, dd/mm/yyyy, typed or picked from the calendar icon. Help text: *Date the covered person knew or should have known of the suspicious nature of the transaction. Starts the filing deadline clock.* | | 7 | Filing deadline | None shown | Not an entry | A message beside the date, worked out from it. It changes with the current date. For 30/09/2026 it read *Filing deadline: October 7, 2026 (Due today!)* on 7 October and *Filing deadline: October 7, 2026 (Overdue by 6 days)* on 13 October. | ### STR types compared {#s-3-16-types} Each **STR Type** card carries a short description. The table sets the five cards side by side, using only what the cards say.
On the cardSTRRSTRASTRHPSTRHUSTRBR
NameRegular STRPer AccountHigh PriorityHighly unusualBulk Report
DescriptionStandard suspicious transaction report. Default for most cases.AMLC-requested account-level review or referralKidnapping, drugs, terrorism, trafficking, OSAEC, strategic tradeTransaction with no apparent economic purpose or business patternBulk Report (BSIs only, 5 working days)
Described as the defaultYesNoNoNoNo
Linked to an AMLC request or referralNoYesNoNoNo
Names specific crimesNoNoYesNoNo
Limited to some institutionsNoNoNoNoYesBSIs only
States a time limitNoNoNoNoYes5 working days
::: note AML context Pick the type from what the investigation found, not from the alert that started it. A transaction that matches none of the listed crimes but has no economic sense fits the "highly unusual" description; a report about one of the serious crimes named on the High Priority card fits that card. If more than one could apply, follow your institution's procedure or ask your compliance officer. ::: ::: step Choose the STR type Under **STR Type**, click the card that fits the report. The chosen card has a filled radio button and a blue border. ::: ::: step Check the institution code **Institution code** is filled in for you. Check that it is your institution's code. ::: ::: step Choose the supervising agency Click **Supervising agency** and click your institution's supervising agency. The current choice is ticked. ::figure[The Supervising agency list, with Bangko Sentral ng Pilipinas ticked]{src="case-manager/31-str-step2-supervising-agency.png" id="fig-case-manager-str-step2-supervising-agency"} ::: ::: step Choose the submission type Click **Submission type** and choose **New**, **Edit/Correction**, **Delete** or **Test**. ::figure[The Submission type list, with Delete ticked in the example draft]{src="case-manager/32-str-step2-submission-type.png" id="fig-case-manager-str-step2-submission-type"} ::: ::: step Choose the STR trigger Click **STR trigger** and choose what led to the report. ::figure[The STR trigger list, with PPP (Public Private Partnership) ticked]{src="case-manager/33-str-step2-str-trigger.png" id="fig-case-manager-str-step2-str-trigger"} ::: ::: step Enter the date of determination In **Date of determination**, enter the date as dd/mm/yyyy or pick it from the calendar icon. Read the **Filing deadline** message that appears beside it (number 7 in [](#fig-case-manager-str-step2-report-type)). In the example, 30/09/2026 gives a deadline of October 7, 2026; viewed on 13 October the message reads *Filing deadline: October 7, 2026 (Overdue by 6 days)*, in red. ::: ::: step Go to step 3 Click **Next Step**. Step 2 now shows a green tick and step 3 **Reason for suspicion** opens. ::: ## Step 3: Reason for suspicion {#s-3-17} Tick the reason codes that explain why the transactions are suspicious. There are two lists: the required primary codes and optional additional codes. Each list scrolls inside the wizard. ::figure[Step 3, Reason for suspicion: SC 1 ticked as a primary code and shown dimmed under Additional reason codes]{src="case-manager/34-str-step3-reason-codes.png" id="fig-case-manager-str-step3-reason-codes"} ::: legend 1. **Reason for suspicion codes** D-SD-2 (required): *Select one or more SC, PC, or MC codes. Multiple selections allowed.* 2. The counter, *1 of 43 Selected*. The lists hold 43 codes: SC 1 to SC 6, PC 1 to PC 36 and MC 01. 3. A ticked code (**SC 1** in the example). 4. **Additional reason codes** D-SD-5 (optional): *Secondary suspicion codes beyond primary codes from Step 3. Codes already selected as primary are shown dimmed.* 5. The same code, dimmed in the additional list because it is already a primary code. ::: | Field | Code | Required | What to enter or the options | | --- | --- | --- | --- | | Reason for suspicion codes | D-SD-2 | Yes (\*) | One or more codes, in three groups: **Suspicious circumstances — SC1-SC6**, **Predicate crimes — PC1-PC36** and **Transnational organized crime — MC1**. See the code table below. | | Additional reason codes | D-SD-5 | No (labelled *(optional)*) | The same three groups. Codes already ticked as primary are dimmed. | ::: step Tick the primary codes Under **Reason for suspicion codes**, scroll the list and tick each code that applies. The counter shows how many are ticked. ::: ::: step Check KYC REQ on predicate crimes Scroll to **Predicate crimes — PC1-PC36**. Most predicate-crime codes carry a yellow **KYC REQ** tag at the right; PC 4, PC 5, PC 13 and PC 35 do not. ::figure[Predicate crimes PC 6 to PC 9, each with a KYC REQ tag]{src="case-manager/35-str-step3-predicate-crimes.png" id="fig-case-manager-str-step3-predicate-crimes"} ::: ::: step Add MC 01 where it applies At the end of the list, **Transnational organized crime — MC1** holds one code, **MC 01**: *Transnational Organized Crime (used with another predicate crime)*. ::figure[The end of the primary list: PC 34 to PC 36 and MC 01]{src="case-manager/36-str-step3-mc1.png" id="fig-case-manager-str-step3-mc1"} ::: ::: step Tick any additional codes Under **Additional reason codes**, tick any secondary codes. Codes already ticked above are dimmed here. ::: ::: step Go to step 4 Click **Next Step**. Step 3 now shows a green tick and step 4 **Transaction** opens. ::: | Code | Description on screen | KYC REQ tag | | --- | --- | --- | | SC 1 | No underlying legal or trade obligation, purpose or economic justification | No | | SC 2 | Client not properly identified | No | | SC 3 | Amount not commensurate with business or financial capacity | No | | SC 4 | Transaction structured to avoid being reported | No | | SC 5 | Deviation from client's profile/past transactions | No | | SC 6 | Transaction similar, analogous or identical to any of the foregoing | No | | PC 1 | Kidnapping for Ransom | Yes | | PC 2 | Drug Trafficking and Related Offenses | Yes | | PC 3 | Graft and Corrupt Practices | Yes | | PC 4 | Plunder | No | | PC 5 | Robbery and Extortion | No | | PC 6 | Jueteng and Masiao | Yes | | PC 7 | Piracy on the High Seas | Yes | | PC 8 | Qualified Theft | Yes | | PC 9 | Swindling (Estafa) | Yes | | PC 10 | Smuggling | Yes | | PC 11 | Violations under the Electronic Commerce Act of 2000 | Yes | | PC 12 | Hijacking; Destructive Arson; and Murder | Yes | | PC 13 | Terrorism and Conspiracy to Commit Terrorism | No | | PC 14 | Financing of Terrorism | Yes | | PC 15 | Bribery | Yes | | PC 16 | Frauds and Illegal Exactions and Transactions | Yes | | PC 17 | Malversation of Public Funds and Property | Yes | | PC 18 | Forgeries and Counterfeiting | Yes | | PC 19 | Violations of Anti-Trafficking in Persons Act of 2003 | Yes | | PC 20 | Violations of Revised Forestry Code of the Philippines | Yes | | PC 21 | Violations of Fisheries Code of 1998 | Yes | | PC 22 | Violations of Philippine Mining Act of 1995 | Yes | | PC 23 | Violations of Wildlife Resources Conservation and Protection Act | Yes | | PC 24 | Violation of National Caves and Cave Resources Management and Protection Act | Yes | | PC 25 | Violation of Anti-Carnapping Act of 2002 | Yes | | PC 26 | Violations of Illegal Possession of Firearms, Ammunition or Explosives | Yes | | PC 27 | Violation of Anti-Fencing Law | Yes | | PC 28 | Violation of Migrant Workers and Overseas Filipinos Act of 1995 | Yes | | PC 29 | Violation of Intellectual Property Code | Yes | | PC 30 | Violation of Anti-Photo and Video Voyeurism Act of 2009 | Yes | | PC 31 | Violation of Anti-OSAEC and Anti-CSAEM Act | Yes | | PC 32 | Violations of RA 7610, Special Protection of Children Against Abuse | Yes | | PC 33 | Fraudulent Practices under Securities Regulation Code of 2000 | Yes | | PC 34 | Violation of Strategic Trade Management Act | Yes | | PC 35 | Violations of National Internal Revenue Code of 1997 | No | | PC 36 | Felonies or offenses of a similar nature punishable under penal laws of other countries | Yes | | MC 01 | Transnational Organized Crime (used with another predicate crime) | No | ::: note On screen, **Reason for suspicion codes** and **Date of determination** (step 2) both carry the code D-SD-2. ::: ## Step 4: Transaction {#s-3-18} Select the suspicious transactions to include in the STR. The list holds the triggered transactions of the alerts selected in step 1. In the example below, the case's only alert is a Name Screening alert, the list is empty and **Next Step** is greyed out. ::figure[Step 4, Transaction, for CASE-2026-0107624: no suspicious transactions found, and Next Step greyed out (9); the numbers follow the list below]{src="case-manager/37-str-step4-transaction.png" id="fig-case-manager-str-step4-transaction"} ::: legend 1. **Type** filter. 2. **Period From** and **Period To** date filters. 3. **Selected**: the number of transactions selected. 4. **total amount (D-TD-6)**: the total of the selected transactions. When they are in different currencies it is labelled **Mixed** (see [Regulatory Reports, step 4](#s-6-7)). 5. **Select Suspicious Transactions** (required): *Triggered transactions for this case. All are selected by default - deselect any you want to exclude from the STR*. The counter at the right reads, for example, *0 of 0 Selected*. 6. **Select all** and **Deselect all**. 7. The transaction table, with the columns Transaction, Amount, Type, Sender, Receiver, MOT, Product and Date. With no transactions it reads *No suspicious transactions found for the selected alerts.* 8. **Party Role** legend for the letters shown next to each sender and receiver. 9. **Next Step**, greyed out while no transaction is selected. ::: | Field | Code | Required | What to enter or the options | | --- | --- | --- | --- | | Type | None shown | No marker | A list with one option, **All type** ([](#fig-case-manager-str-step4-type-dropdown)). | | Period From | None shown | No marker | A date, dd/mm/yyyy. | | Period To | None shown | No marker | A date, dd/mm/yyyy. | | Selected | None shown | Not an entry | The count of selected transactions. | | total amount | D-TD-6 | Not an entry | The total of the selected transactions. | | Select Suspicious Transactions | None shown | Yes (\*) | One checkbox per transaction. All are selected by default. | | Party Role letter | Meaning | | --- | --- | | S | Subject of Suspicion | | B | Beneficiary | | C | Counterparty | | T | Transactor | | O | Other participant | ::: step Narrow the list if needed Set **Period From** and **Period To** to limit the list to a date range. **Type** offers only **All type**. ::figure[The Type filter open, with its only option, All type]{src="case-manager/38-str-step4-type-dropdown.png" id="fig-case-manager-str-step4-type-dropdown"} ::: ::: step Choose the transactions All triggered transactions are selected by default. Untick any transaction to leave out of the STR, or use **Select all** and **Deselect all**. Check **Selected** and **total amount (D-TD-6)**. ::: ::: step Read the note and go to step 5 Scroll to the bottom of the step. The note reads: *MOT, Product Type, Purpose of Remittance, and Transaction Code are sourced from ingested data and included automatically in the Format X CSV per selected transaction. Total amount can be manually overridden below.* Click **Next Step**. It is greyed out while no transaction is selected. ::figure[The bottom of step 4: the Party Role legend (8), the note on ingested data, and Next Step greyed out (9)]{src="case-manager/39-str-step4-bottom.png" id="fig-case-manager-str-step4-bottom"} ::: ::: note The note says the total amount can be overridden below, but no field for overriding it is shown on this step. ::: ## Step 5: Subject parties {#s-3-19} Check the parties named in the STR. The screen states: *Auto-derived from selected transactions. Click a row to expand and edit.* Each party row shows an **AH** tag, the name as *Last, First* (or *Last, First, Middle*) and the customer ID. The figure comes from a filed STR (STR 694, CASE-2026-0000075) opened read-only from [Regulatory Reports](#str-listing), so its fields appear greyed. ::figure[Step 5, Subject parties, in a filed STR viewed read-only: the party Sinha, Harish expanded (1), Party role (2), Account holder (3), Entity (4), IDENTITY (5), ID DOCUMENTS (6) and ADDITIONAL DETAILS (7)]{src="case-manager/40-str-step5-subject-parties.png" id="fig-case-manager-str-step5-subject-parties"} ::: legend 1. The party row (**Sinha, Harish**). The customer ID (*TEM-CUST-10L847*) is at the right; the arrow collapses the row. 2. **Party role**. 3. **Account holder** checkbox, labelled *(emits A-block in CSV)*. 4. **Entity** D-A-3. 5. **IDENTITY** fields. 6. **ID DOCUMENTS** fields. 7. **ADDITIONAL DETAILS** fields, further down (scroll the wizard). :::
FieldCodeRequiredWhat to enter or the options
Party roleNone shownNo markerA list. Example value: S - Subject of Suspicion.
Account holderNone shownNo markerCheckbox, labelled (emits A-block in CSV).
EntityD-A-3No markerA list. Example value: N - Natural Person.
IDENTITY
Last nameD-A-4aYes (*)The party's last name.
First nameD-A-4bNo markerThe party's first name.
Middle nameD-A-4cNo markerPlaceholder e.g. Salamanca.
CRND-A-2No markerThe customer ID, for example TEM-CUST-10L847.
Account no.D-A-8No markerPlaceholder e.g. 1238444223.
ID DOCUMENTS
ID typeD-A-12No markerA list. Example value: Others.
ID numberD-A-13No markerPlaceholder e.g. 045223411.
Date of birthD-A-4cNo markerA date (hidden in the figure).
NationalityD-A-11No markerPlaceholder e.g. PH.
ADDITIONAL DETAILS
Complete addressD-A-5No markerThe party's address.
Country codeD-A-6No markerExample value: PH - Philippines.
ID City code — PSGCD-A-7Labelled Required for PHThe PSGC city code.
Place of birthD-A-10No markerThe party's place of birth.
Source of fundD-A-6No markerExample value: Employed.
Contact no.D-A-15No markerThe party's contact number.
Old account no.D-A-16No markerA previous account number.
::: step Expand a party Click a party row. It expands to show **Party role**, **Account holder**, **Entity** and the **IDENTITY**, **ID DOCUMENTS** and **ADDITIONAL DETAILS** fields. ::: ::: step Check and complete the fields Check **Party role** and **Entity**, and whether **Account holder** should be ticked. Make sure **Last name** is filled in, then complete the other fields you hold for the party. For a party in the Philippines, fill in **ID City code — PSGC**. ::: ::: step Repeat for each party and go to step 6 Collapse the row with the arrow at its right and repeat for each party in the list. Then click **Next Step**. ::: ## Step 6: Narratives {#s-3-20} Write the narrative of the STR. The figure comes from the same filed STR (STR 694) opened read-only from [Regulatory Reports](#str-listing), so the text box appears greyed; the narrative text is hidden. ::figure[Step 6, Narratives, in a filed STR viewed read-only: the STR Narrative, text hidden (1), its counter (2) and the alerts covered (3)]{src="case-manager/41-str-step6-narratives.png" id="fig-case-manager-str-step6-narratives"} ::: legend 1. **STR Narrative** (D-SD-6, required). 2. The character counter, for example *254 / 4000 — meets GoTRACS recommendation*, in green with a tick. 3. **ALERTS COVERED BY THIS STR**: the IDs of the alerts selected in step 1, each with a copy icon. ::: The footer of step 6 holds only **Previous Step**. This is the last step, so there is no **Next Step**. | Field | Code | Required | What to enter or the options | | --- | --- | --- | --- | | STR Narrative | D-SD-6 | Yes (\*) | Free text. The counter shows the length against a maximum of 4000 characters. | | ALERTS COVERED BY THIS STR | None shown | Not an entry | The alerts selected in step 1. | ::: step Write the narrative Type the narrative in **STR Narrative**. Watch the counter below the box: it shows the number of characters out of 4000 and reads *meets GoTRACS recommendation* when the text meets it. ::: ::: step Check the alerts covered Read **ALERTS COVERED BY THIS STR**. If an alert is missing or should not be there, click **Previous Step** back to step 1 and change the selection. ::: ::: note AML context The narrative is the part of an STR that an analyst at the financial intelligence unit reads first. A useful narrative says who is involved, what happened and when, which accounts and amounts were used, why the activity is suspicious (with reference to the customer's profile and the reason codes chosen), and what the institution has done about it. ::: ## After the STR is filed {#s-3-21} A case whose STR has been filed has the status **STR Created**. Its case bar shows **Download STR** and **ReOpen**. The filed STR is listed in [Regulatory Reports](#str-listing), where you can open it read-only and download its CSV. ::: not-covered The final action on the Narratives step that completes the filing is not shown in this guide; this edition documents the wizard up to Narratives and the case after filing. If you are unsure how to complete a filing, ask your compliance lead or contact support at [hello@fyscaltech.com](mailto:hello@fyscaltech.com). ::: ::figure[An STR Created case (CASE-2026-0034611, Rafael Serrano Dimaculangan): the STR Created status (1), Download STR (2) and ReOpen (3)]{src="case-manager/42-case-str-created.png" id="fig-case-manager-case-str-created"} If you close the wizard with **×** before the STR is filed, you return to Case Details. A case that already had a saved draft keeps the status **STR Draft** and its **Preview STR** button. ## Common blocks {#s-3-22} ::: checks - **Next Step is greyed out on step 4.** **Select Suspicious Transactions** is required. When the alerts selected in step 1 have no transactions, the table reads *No suspicious transactions found for the selected alerts.*, **Selected** shows 0 and **Next Step** stays greyed out. No other message is shown. Click **Previous Step** back to step 1 and check that the selected alerts include ones with transactions; a Transaction Monitoring alert row shows its number of transactions (Figures 3.37 and 3.39). - **The filing deadline is shown in red.** The **Filing deadline** message beside **Date of determination** is shown in red in both examples captured: *Filing deadline: October 7, 2026 (Overdue by 6 days)* in a draft viewed on 13 October and *Filing deadline: August 31, 2026 (Overdue by 44 days)* on a filed STR viewed on 14 October (see [Regulatory Reports, step 2](#s-6-5)). On a filed STR the message alone does not show whether the STR was filed late. Check that the date of determination is correct ([](#fig-case-manager-str-step2-report-type)). ::: ## Alerts list {#s-3-23} ::path[Fyscal ARCX → Case Manager → Alerts] The **Alerts** screen lists alerts raised by Name Screening and Transaction Monitoring. **My Queue** shows the alerts assigned to you; **All Alerts** shows all alerts, with summary chips and row checkboxes. ::figure[The Alerts screen on My Queue: the tabs (1), search (2), Refresh and Show Filters (3), the alert list (4) and pagination (5)]{src="case-manager/43-alerts-my-queue.png" id="fig-case-manager-alerts-my-queue"} ::: legend 1. **My Queue** and **All Alerts** tabs, each with a count (43 and 175.3K in the example). 2. Search box: *Search by Customer Name / ID or Alert ID*. 3. **Refresh** and **Show Filters**. 4. The alert list. 5. Pagination: *Showing 1-10 of 43* and *Page 1 of 5* with first, previous, next and last page buttons. ::: | Column | What it shows | | --- | --- | | Customer Name / Alert ID | The customer name and the alert ID (for example *ALT-NS-23092026-008485*), with a copy icon. Name Screening IDs start with *ALT-NS*, Transaction Monitoring IDs with *ALT-TMS*. | | Module | **Name Screening** or **Transaction Monitoring**. | | Score | The score band and percentage, for example *Low 75.76%* or *Medium 90.79%*. | | Status | Not Started, Under Investigation, Pending Review, Escalated, Closed or Reopened. | | Disposition | True Match, False Match, Potential Match, or **-**. | | SLA Deadline | **On Track** (green) or **Breached** (red). | | Assigned To | The assigned user, or **-** when unassigned. | | In Case | **Yes** when the alert belongs to a case, **No** when it does not. | | Created At | Creation date and time. | #### All Alerts chips and filters On **All Alerts**, chips above the list (1) show **Unassigned**, **Escalated**, **SLA Breached** and **Active Agents**, each with a count. Click **Show Filters** to open the filter bar (2); the button then reads **Hide Filters**. ::figure[All Alerts with the filters shown: the summary chips (1), the filter bar (2), In case (3) and Show Hibernated (4)]{src="case-manager/44-alerts-all-filters.png" id="fig-case-manager-alerts-all-filters"} | Filter | Default | Options | | --- | --- | --- | | Status | All Statuses | All Statuses, Not Started, Under Investigation, Pending Review, Escalated, Closed, Reopened | | Module | All Modules | All Modules, Name Screening, Transaction Monitoring | | SLA | All SLAs | All SLAs, Breached, On Track | | Score | All Scores | All Scores, Low, Medium, HIGH | | Assignee | All Assignees | A list of users. The signed-in user is labelled *(You)*. | | In case (3) | All | All, Yes, No | | Hibernated (4) | Unticked | **Show Hibernated** checkbox | ## Alert Details: Name Screening {#s-3-24} ::path[Fyscal ARCX → Case Manager → Alerts → (click an alert)] **Alert Details** shows one alert. The example is ALT-NS-05102026-000115 for Ramon Michael Castillo Tan: a Name Screening alert with two watchlist candidates that is assigned but not yet started. ::figure[Alert Details for a Name Screening alert that is Not Started: the header (1), the alert bar (2), the AI Summary card (3) and the customer card (4)]{src="case-manager/45-alert-ns-detail.png" id="fig-case-manager-alert-ns-detail"} ::: legend 1. Header: **Alert Details**, the alert ID, the score band and percentage (*LOW 84.29%*), *Config:* followed by the configuration version ID, and the creation date (shown as **-** on this alert). At the right: **Timeline & Notes** and, on this Not Started alert, **Start Investigation**, shown in grey. 2. Alert bar: **Status**, **Assigned To** (the assigned user, hidden in the figure), **Disposition** (*Select outcome*; greyed out on this alert) and **SLA Deadline** (date and time; red with *(Breached)* once missed). 3. **AI Summary** card (see below). 4. Customer card and **Accounts**, as in [Customer, accounts and matches](#s-3-5). ::: Below these, **Matches** shows each watchlist candidate side by side with the customer (1). Here MICHAEL TAN (2) is selected and RAMON TAN (3) is the second candidate. The highlighted candidate's record opens in the **Selected** panel (4) with the **Identity** and **Additional Information** tabs. All fields are described in [Customer, accounts and matches](#s-3-5). ::figure[Matches for ALT-NS-05102026-000115: the customer (1), MICHAEL TAN, LOW 84.29%, selected (2), RAMON TAN, LOW 82.6% (3) and the Selected panel (4)]{src="case-manager/46-alert-ns-matches.png" id="fig-case-manager-alert-ns-matches"} #### AI Summary Until a summary is generated, the card reads *No summary yet* and *Generating reads this alert and its matches, and costs one run against the daily limit.* Click **Generate summary** to create one. The **AI Summary** control at the top right of the card collapses and expands it. The prompts behind the summary are managed in Agentic Workflows (see [Case Manager Config](#case-manager-config)). A generated summary, as on the Transaction Monitoring alert in [Figure 3.48](#s-3-25), has: ::: checks - a verdict tag with a one-line reason (for example **Insufficient Data**: *Insufficient data; transaction details unavailable*); - **RATIONALE**, with a copy icon; - sections with an item count, for example **KEY FINDINGS (4)**, **TRANSACTION PATTERN ANALYSIS (3)**, **RULE TRIGGER ANALYSIS (2)** and **RISKS & DATA GAPS (3)**; - **RECOMMENDED ACTION**; - a footer with the prompt version, the model and the generation time, for example *Prompt v3 · Model openai/gpt-oss-120b · 28 Sept, 05:28 PM*. ::: ::: note The AI Summary is generated text. Read it alongside the alert evidence; the disposition is recorded by the analyst. ::: #### Alert timeline **Timeline & Notes** opens the **Activity Timeline** for the alert, headed with the alert number. It has the same **ADD A NOTE**, **Attach File** and **Add note** controls as the case timeline (1). Events are listed newest first, each with its date and time: ::: checks - **Assigned** (2): who made the change, and the owner before and after it (here *Unassigned* » the new owner). - **Created** (3): an alert raised by screening starts with a Created event by *System*. ::: ::figure[Activity Timeline for alert 174489: the note controls (1), the Assigned event (2) and the Created event by System (3)]{src="case-manager/47-alert-timeline.png" id="fig-case-manager-alert-timeline"} ## Alert Details: Transaction Monitoring {#s-3-25} A Transaction Monitoring alert has the same layout, with the evidence tabs **Analytics**, **Transactions**, **Other Cases / Alerts** and **Rule Analysis** in place of Matches (see [Transaction Monitoring evidence tabs](#s-3-6)). The example is ALT-TMS-13092026-187809 for Margarita Ong Abalos: a Closed alert that belongs to a case. Its decision was recorded again on 13 Oct 2026, and the new decision leaves **Disposition**, **Rationale Code** and **Details** blank. ::figure[A closed Transaction Monitoring alert: the case button (1), the decision block (2), the AI Summary verdict (3), its sections (4) and the footer (5)]{src="case-manager/48-alert-tm-detail.png" id="fig-case-manager-alert-tm-detail"} ::: checks - An alert that belongs to a case shows a button with the case ID (1) (here **CASE-2026-0104894**) at the right of the alert bar. Click it to open the case. - A decided alert shows a decision block (2): **Rationale Code**, **Details**, **Decided On** and **Decided By**. A field with no value is left blank. - The AI Summary opens with its verdict (3). For monitoring alerts its sections (4) include **TRANSACTION PATTERN ANALYSIS** and **RULE TRIGGER ANALYSIS**, and the footer (5) gives the prompt version, model and time. ::: ## Work an alert {#s-3-26} These are the controls on Alert Details as an alert moves from Not Started to a decision. Which controls appear depends on the alert's status and on whether it is assigned and grouped; the table records what the example alerts show.
Alert Details controlNot StartedUnder Investigation, assigned, not in a caseClosed, in a case
Start InvestigationPartialShown in greyNoNo
Disposition reads Select outcomeYesGreyed outYesOpens the listNoShows the recorded outcome; blank on the example
Group into CaseNoYesNo
Button with the case IDNoNoYes
Decision block (Rationale Code, Details, Decided On, Decided By)NoNoYes
Examples: ALT-NS-05102026-000115 ([](#fig-case-manager-alert-ns-detail)), ALT-NS-20260813121854684951 ([](#fig-case-manager-alert-disposition)) and ALT-TMS-13092026-187809 ([](#fig-case-manager-alert-tm-detail)). ::: step Check the alert's status and owner Read **Status** and **Assigned To** in the alert bar. On the **Not Started** example, **Start Investigation** is shown in grey next to Timeline & Notes and **Disposition** is greyed out ([](#fig-case-manager-alert-ns-detail)). On an alert that is **Under Investigation** and assigned (1 in [](#fig-case-manager-alert-disposition)), **Start Investigation** is not shown and **Disposition** can be opened. ::: ::: step Choose a disposition Open **Disposition** (*Select outcome*) (2) and choose **True Match**, **False Match** or **Potential Match**. What happens after you choose is not covered in this edition. ::figure[An alert Under Investigation: Status and Assigned To (1), the open Disposition list (2) and Group into Case (3)]{src="case-manager/49-alert-disposition.png" id="fig-case-manager-alert-disposition"} ::: ::: step Group the alert into a case An alert that is Under Investigation and not in a case shows **Group into Case** (3) at the right of the alert bar. From a case, you can also bring ungrouped alerts in with [Add Alerts](#s-3-9). The result of Group into Case is not covered in this edition. ::: #### Alert status changes recorded on screen Reopening a case reopens the alerts you leave selected. The **Reopen Case** dialog pre-selects every disposed alert (*Uncheck any that should remain closed*), and the case timeline then records *n alert(s) Reopened* with a link to each alert (see [Reopen a case](#s-3-12)). The alert statuses offered by the **Status** filter are Not Started, Under Investigation, Pending Review, Escalated, Closed and Reopened.
Related in Core Workflow
Case Manager ConfigurationCustomer 360Regulatory Reports