# 5. Customer 360


Customer 360 is where you look a customer up. Analysts and reviewers use it during an investigation to find a customer in the list and open their Customer Profile, which brings together identity and KYC details, accounts, transaction analytics, transactions, prior cases and alerts, screening history and STR history. Administrators set up the customer risk profile (CRP) next to it, under **Customers**: which customer details are scored, how much each one weighs, and the score bands that turn a score into a risk level.

<dl class="chapter-facts"><div><dt>For</dt><dd>Analysts, supervisors and team leads; administrators for the CRP</dd></div><div><dt>In the menu</dt><dd>Fyscal ARCX → Customers → Customer 360, Risk Score Configuration, Score Configuration</dd></div><div><dt>Reading time</dt><dd>About 26 min</dd></div></dl>

::: checks
- [The customer list](#s-5-1): read the customer table and move between pages.
- [Search and filter the list](#s-5-2): find one customer, or narrow the list by KYC level, risk tier or country.
- [The Customer Profile](#s-5-3): check a customer's profile tags, financial details and accounts.
- [Customer Risk Score tab](#s-5-14): see the customer's risk score and how each attribute adds to it.
- [Analytics tab](#s-5-4): see the customer's incoming and outgoing totals, top counterparties and transaction types.
- [Transactions tab](#s-5-5): chart the customer's activity, filter their transactions and export them.
- [Other Cases / Alerts tab](#s-5-6): see the cases and alerts already raised for the customer.
- [Screening History tab](#s-5-7): see which name-screening runs included the customer and their result.
- [STR History tab](#s-5-8): see the STRs linked to the customer.
- [Review a customer during an investigation](#s-5-9): go through the profile tab by tab, with a worked example comparing the profile with the activity.
- [Customer risk profile (CRP)](#s-5-10): how a customer's risk score is worked out from scored attributes and weightages.
- [Set up the risk score attributes](#s-5-11): add attributes, score their values from 0 to 100 and weight them up to 100% in total.
- [Set the score bands](#s-5-12): set the score ranges for Low, Medium and High.
- [Configuration history](#s-5-13): see which version is active and who changed it.
:::

## The customer list {#s-5-1}

::path[Fyscal ARCX → Customers → Customer 360]

Start from the customer list to find the customer you need. The **Customer 360** page shows one row per customer, with a search box, a **Refresh** button and a **Show Filters** button above the table.

::figure[The Customer 360 list: search (1), Refresh (2), Show Filters (3), the column headings (4), a customer row (5) and the Score tag (6)]{src="customers/01-customer-list.png" id="fig-customers-customer-list"}

::: legend
1. **Search by Customer Name / ID**: finds customers by name or Customer ID.
2. **Refresh**: reloads the list.
3. **Show Filters**: opens the filter bar (KYC Level, Risk Tier, Country). The button then reads **Hide Filters**.
4. Column headings: **Customer Name / ID**, **KYC Level**, **Risk Level**, **Score**, **Country**, **Created At**.
5. A customer row: initials avatar, customer name, and the Customer ID with a copy icon.
6. **Score**: the score band and percentage, as a coloured tag (here **High 62.61%**).
:::

| Column | What it shows | Format or values seen |
| --- | --- | --- |
| **Customer Name / ID** | The customer's name (individual or business), with the Customer ID below it and a copy icon next to the ID. Long names are shortened with "…". | For example **Bienvenido Salazar Ocampo**, **C019-0000010** |
| **KYC Level** | The customer's KYC level as held in the customer data. | **Kyc 0**, **Kyc 1** (see the note under [Search and filter the list](#s-5-2)) |
| **Risk Level** | The customer's risk level, as a coloured tag. | **Low**, **Medium**, **High** |
| **Score** | The customer's score band and percentage, as a coloured tag (see [Customer risk profile (CRP)](#s-5-10)). | For example **High 62.61%** |
| **Country** | The customer's country. | For example **Philippines** |
| **Created At** | The date and time of the customer record. | For example **Dec 15, 2025, 07:40 AM** |

Below the table, the count line and the page controls show where you are in the list. The list shows 20 customers per page.

::figure[The count line, Showing 1-20 of 10000 (1), the page indicator, Page 1 of 500 (2), and the page buttons (3)]{src="customers/02-list-count.png" id="fig-customers-list-count"}

::: legend
1. **Showing 1-20 of 10000**: the rows on this page and the total number of customers that match the current search and filters.
2. **Page 1 of 500**: the page you are on.
3. Four buttons: first page, previous page, next page and last page.
:::

## Search and filter the list {#s-5-2}

::path[Fyscal ARCX → Customers → Customer 360 → Show Filters]

Use the search box to find one customer, and the filters to narrow the list by KYC level, risk tier or country.

| Filter | Default | Options shown |
| --- | --- | --- |
| **KYC Level** | **All** | **All**, **Advanced**, **Basic**, **Complete** |
| **Risk Tier** | **All** | A list with a search box: **Low**, **Medium**, **High** |
| **Country** | **All** | A list of country names with a search box, in alphabetical order from **Afghanistan** (243 options, including **Unknown**). |

::: step Search for a customer
Click the **Search by Customer Name / ID** box and type the customer's name or Customer ID, for example **CUST-FYSCAL-604554**.
:::

::: step Open the filters
Click **Show Filters**. Three filters appear below the search box: **KYC Level** (1), **Risk Tier** (2) and **Country** (3), each set to **All**. The button now reads **Hide Filters** (4); click it to close the filter bar.

::figure[The filter bar: KYC Level (1), Risk Tier (2) and Country (3), with Hide Filters (4)]{src="customers/03-filters-open.png" id="fig-customers-filters-open"}
:::

::: step Filter by KYC Level
Click the **KYC Level** box (1) and choose one option. A tick marks the current choice (**All** (2)). The other options are **Advanced**, **Basic** and **Complete**.

::figure[The KYC Level filter (1): All ticked (2), then Advanced, Basic and Complete]{src="customers/04-filter-kyc-level.png" id="fig-customers-filter-kyc-level"}

::: note
The KYC Level filter options (Advanced, Basic and Complete) do not match the values shown in the customer data. The **KYC Level** column shows values such as **Kyc 0** and **Kyc 1**, and the Customer Profile shows values such as **KYC L2**. The screens do not show how the filter options relate to these values.
:::
:::

::: step Filter by Risk Tier
Click the **Risk Tier** box. The list has a search box (1), followed by **Low**, **Medium** and **High**. Click the tier to show.

::figure[The Risk Tier filter: the search box (1), then Low, Medium and High]{src="customers/05-filter-risk-tier.png" id="fig-customers-filter-risk-tier"}

::: note
The **Risk Level** values seen in the list are **Low**, **Medium** and **High**, but in testing a search of the Risk Tier list for High, Medium or Low returned no options.
:::
:::

::: step Filter by Country
Click the **Country** box. Type part of a country name in the search box (1) at the top of the list, then click the country. The list (2) is alphabetical and long (243 options), so searching is quicker than scrolling.

::figure[The Country filter: the search box (1) and the alphabetical list of countries (2)]{src="customers/06-filter-country.png" id="fig-customers-filter-country"}
:::

::: step Reload the list
Click **Refresh** to reload the list.
:::

## The Customer Profile {#s-5-3}

::path[Fyscal ARCX → Customers → Customer 360 → *customer name*]

Open the Customer Profile to see everything held on one customer: profile tags, financial details, accounts and the tabs described below, starting with the Customer Risk Score. Click a customer in the list to open the **Customer Profile**. The breadcrumb reads **Fyscal ARCX › Customer 360 ›***customer name*; click **Customer 360** in it to return to the list. The examples in this chapter use the customer **Rafael Serrano Dimaculangan** (**CUST-FYSCAL-604554**).

::figure[The Customer Profile for Rafael Serrano Dimaculangan: name and ID (1), profile tags (2), More (3), summary cards (4), Accounts (5) and the tabs, starting with Customer Risk Score (6)]{src="customers/07-profile-header.png" id="fig-customers-profile-header"}

::: legend
1. The customer's name, initials avatar and Customer ID (with a copy icon).
2. Profile tags: **TYPE**, **SEGMENT**, **RISK**, **KYC**, **STATUS**, **COUNTRY** and **PEP Flag**.
3. **More**: expands the profile card with three detail panels ([](#fig-customers-profile-more)). It then reads **Less**.
4. Summary cards: **DECLARED INCOME**, **EXPECTED MONTHLY SPEND**, **SOURCE OF FUNDS**, **ONBOARDING**.
5. **Accounts (1)**: the customer's accounts, with the number of accounts in brackets.
6. Tabs: **Customer Risk Score** (selected: the profile opens on it), **Analytics**, **Transactions** (with a count, here 19), **Other Cases / Alerts**, **Screening History**, **STR History** and **Additional Data** (greyed out, not described in this edition).
:::

::: note
The profile opens on the **Customer Risk Score** tab, which is explained first below, before **Analytics**. The customer's risk score also appears as a coloured tag next to their name (see [Customer Risk Score tab](#s-5-14)).
:::

| Field | What it shows | Example |
| --- | --- | --- |
| **TYPE** | Customer type. | **INDIVIDUAL** |
| **SEGMENT** | Customer segment. | **Retail** |
| **RISK** | Risk tier, with a number in brackets. | **HIGH (77)** |
| **KYC** | KYC level. | **L2** |
| **STATUS** | Customer status. | **ACTIVE** |
| **COUNTRY** | Customer country. | **PHILIPPINES** |
| **PEP Flag** | Whether the customer is flagged as a politically exposed person. | **No** |
| **DECLARED INCOME** | Income declared by the customer. | **₱2,323,206.00** |
| **EXPECTED MONTHLY SPEND** | Expected monthly spend. | **₱1,710,199.43** |
| **SOURCE OF FUNDS** | Declared source of funds. | **Employed** |
| **ONBOARDING** | Onboarding channel. | **via API** |
| **Accounts** row | Account number, account type, institution and account status, with an expand arrow at the right. | account number (hidden in the figures), **SALARY**, **Land Bank of the Philippines**, **ACTIVE** |

::: step See the full customer details
Click **More** at the top right of the profile card. Three panels open between the summary cards and **Accounts**. The button now reads **Less** (1); click it to close them.

::figure[The profile card expanded: Less (1), BUSINESS & EMPLOYMENT (2), FINANCIAL INFORMATION (3) and Additioanl Details (4)]{src="customers/08-profile-more.png" id="fig-customers-profile-more"}
:::

| Panel | Fields | Example values |
| --- | --- | --- |
| 2 **BUSINESS & EMPLOYMENT** | **Designation**, **Employer**, **Segment**, **Source of Funds**, **Country of Operations** | Cook, BDO Unibank, Retail, Employed, PHILIPPINES |
| 3 **FINANCIAL INFORMATION** | **Declared Income**, **Expected Monthly Spend**, **Purpose**, **Onboarding Channel**, **Expected Txn Frequency** | ₱2,323,206.00, ₱1,710,199.43, Remittance receiving, API, QUARTERLY |
| 4 **Additioanl Details** (spelled this way on screen) | **City**, **Country**, **Sanctions** | city (hidden in the figure), PHILIPPINES, REVIEW\_REQUIRED |

::: note AML context
Customer due diligence records what the institution expects of a customer: who they are, their risk rating, whether they are a politically exposed person, their income and source of funds, and how much and how often they expect to transact. Monitoring and investigations compare actual activity with this expected behaviour.
:::

## Customer Risk Score tab {#s-5-14}

::path[Fyscal ARCX → Customers → Customer 360 → *customer name* → Customer Risk Score]

The **Customer Risk Score** tab shows the result of the [customer risk profile (CRP)](#s-5-10) for one customer: their risk score, its band, and how each attribute adds to it. It is the first tab of the Customer Profile. The same score appears as a coloured tag next to the customer's name, so you see the risk level as soon as you open the profile.

::figure[The Customer Risk Score tab for Emiliano Earl Gica Alvarez: the score tag next to the name (1), the Customer Risk Score tab (2), the total with the Config version (3), one attribute with its value, weightage and score (4), and the two reasons a value scores 0 (5, 6)]{src="customers/22-customer-risk-score-tab.png" id="fig-customers-risk-score-tab"}

::: legend
1. The risk score as a tag next to the customer's name, in the colour of its band: **LOW 9%**.
2. **Customer Risk Score**: the first tab of the profile.
3. **Customer Risk Score** with the **Config version** used to calculate it (**1793012340951**, the active version in [Configuration history](#s-5-13)), and the total, **LOW 9%**.
4. An attribute: its name (**KYC Level**), the customer's value (**KYC 0**), the attribute's **Weightage** (**14%**) and the value's **Score** (**10**).
5. *No value provided. Scored 0.*: the customer data has no value for this attribute (**PEP Status** shows **—**), so it scores 0.
6. *Unable to match value to any scoring row. Scored 0.*: the message shown when the customer has a value (**DRIVERS_LICENSE**) that no row of the attribute matches. This screen shows the attribute with **Score 0**; how such a value is scored is not confirmed for this edition (see [Customer risk profile (CRP)](#s-5-10)).
:::

Each row shows the attribute's **Weightage** and the **Score** of the customer's value. The total at the top is the sum of score × weightage for all attributes, as described in [How the risk score is worked out](#s-5-10). For this customer:

| Attribute | Customer's value | Weightage | Score | Score × weightage |
| --- | --- | --- | --- | --- |
| **KYC Level** | **KYC 0** | 14% | 10 | 1.4 |
| **PEP Status** | **—** (no value) | 20% | 0 | 0 |
| **Nationality** | **Philippines** | 7% | 5 | 0.35 |
| **Country of Residence / Operation** | **Philippines** | 17% | 5 | 0.85 |
| **Age** | **19-42** | 16% | 10 | 1.6 |
| **ID Type** | **DRIVERS_LICENSE** (no matching row) | 10% | 0 | 0 |
| **Occupation** | **Homemaker** | 16% | 30 | 4.8 |
| **Total** | | **100%** | | **9**, shown as **LOW 9%** |

::: tip
A score of 0 from *No value provided* or *Unable to match value to any scoring row* can make a customer look lower-risk than they are. If you see either message, check the customer's data, and ask the administrator of the [risk score configuration](#s-5-11) whether a scoring row is missing for that value (here, **DRIVERS_LICENSE** under **ID Type**).
:::

::: note
The **RISK** tag in the profile header (here **RISK LOW (6)**) is a separate value held in the customer data; it is not the CRP score. Use the **Customer Risk Score** tab, or the score tag next to the name, for the CRP result.
:::

## Analytics tab {#s-5-4}

::path[Customer Profile → Analytics]

Use Analytics for a summary of how money moves in and out of the customer's accounts. **Analytics** is the tab that is open when the profile loads. It summarises the customer's incoming and outgoing transactions, the top counterparties and the transaction types. The panel header shows the customer's name.

::figure[Analytics: the period buttons (1), Alert Window (2), and the INCOMING (3) and OUTGOING (4) totals per currency]{src="customers/09-analytics-flows.png" id="fig-customers-analytics-flows"}

::: legend
1. Period buttons: **1D**, **7D**, **30D**, **All**. In the figure, **All** is selected.
2. **Alert Window**: a check box, shown unticked and greyed in the figure.
3. **INCOMING**: one row per currency, each with **TOTAL** (amount, and the number of transactions and senders, for example "4 txns · 4 senders"), **AVG** and **MAX** (amount and the transaction ID of the largest transaction).
4. **OUTGOING**: the same layout for money sent, counting recipients instead of senders.
:::

In the example, incoming money is shown in PHP, USD, JPY and SGD, and outgoing money in PHP, USD, EUR and JPY. Totals are not converted to a single currency.

::figure[Analytics: Top Counterparties by Amount (1) with 14 more Counterparties (2), and Transaction Types (3) with 4 more Types (4)]{src="customers/10-analytics-counterparties.png" id="fig-customers-analytics-counterparties"}

::: legend
1. **Top Counterparties by Amount**: the five largest counterparties, ranked, each with name, ID (with a copy icon), amount, number of transactions and a bar at the right.
2. **14 more Counterparties** (in the example): lists the rest of the counterparties.
3. **Transaction Types**: the five largest transaction types (for example **TIME\_DEPOSIT**, **DEPOSIT**, **BILLS\_PAYMENT**), each with amount, number of transactions and a bar.
4. **4 more Types** (in the example): lists the rest of the transaction types.
:::

## Transactions tab {#s-5-5}

::path[Customer Profile → Transactions]

Use the Transactions tab when you need the individual transactions behind the analytics, or a CSV export of them. The **Transactions** tab shows charts of the customer's transaction activity and a table of the transactions. The count on the tab (19 in the example) is the number of transactions.

::figure[The Transactions tab: the Transaction Trends / Volume Heatmap switch (1), grouping and date range (2), the Transaction Volume (3) and Transaction Count (4) charts, Expand (5), the table filters (6), Export CSV (7), the Channel column (8) and a row's expand arrow (9)]{src="customers/11-transactions-tab.png" id="fig-customers-transactions-tab"}

::: legend
1. **Transaction Trends** / **Volume Heatmap**: switches the **Transaction Pattern** view. **Transaction Trends** is selected in the figure.
2. The grouping buttons **Day**, **Week**, **Month** (**Day** selected) and the date range (here **10 Oct - 14 Oct**, with a calendar icon).
3. **Transaction Volume** chart for the selected date range.
4. **Transaction Count** chart for the selected date range.
5. Each chart has an expand button at its top right (*Expand Transaction Volume*, *Expand Transaction Count*).
6. **Transaction Table** filters: **All Types**, **All Channels**, **Price range**, **Pick a date range**, **Sender ID**, **Receiver ID**.
7. **Export CSV**, at the right of the tab bar.
8. **Channel**: the channel of each transaction, for example **ONLINE\_BANKING**, **OTC**, **POS**.
9. The arrow at the end of each row.
:::

In the example, the charts cover 10 Oct to 14 Oct and show no activity, while the table lists 19 transactions dated 21 Jul. Change the date range above the charts to chart a different period.

| Column | What it shows | Example |
| --- | --- | --- |
| **Txn ID** | Transaction ID, with a copy icon. | **TXN-752684-ORQ** |
| **Sender** | Sender name and ID. | Rafael Serrano Dimaculangan, CUST-FYSCAL-604554 |
| **Receiver** | Receiver name and ID. | Manila Water, EXT-OVS-65825715 |
| **Amount** | Amount in the transaction currency. | ₱2,904.98; SGD 2,983.40; $3,810.03; €6,875.71 |
| **Type** | Transaction type. Long types are shortened with "…". | TRANSFER, LOAN\_PAYMENT, WITHDRAWAL, TIME\_DEPOSIT |
| **Channel** | Transaction channel. | ONLINE\_BANKING, OTC, POS, MOBILE\_BANKING |
| **Date** | Date and time. | 21 Jul, 06:59:35 PM |

## Other Cases / Alerts tab {#s-5-6}

::path[Customer Profile → Other Cases / Alerts]

Check this tab to see whether the customer has been investigated before. The **Other Cases / Alerts** tab lists the cases and alerts raised for this customer. Cases are managed in [Case Manager](#case-manager).

::figure[Other Cases / Alerts: the Cases and Alerts sub-tabs (1), the Status and Date Range filters (2), and one case, CASE-2026-0034611, in status STR Created (3)]{src="customers/12-other-cases.png" id="fig-customers-other-cases"}

::: legend
1. Sub-tabs **Cases** and **Alerts**, each with a count (1 case and 34 alerts in the example).
2. Filters: **Status** and **Date Range**.
3. A case row: the case title with the case ID below it; the columns are described in the table below.
:::

| Column (Cases) | What it shows | Example |
| --- | --- | --- |
| **Case Title / ID** | Case title, with the case ID and a copy icon below it. | ALT-TMS-21072026-041467, CASE-2026-0034611 |
| **Status** | Case status. | **STR Created** |
| **Disposition** | Case disposition. | **True Match** |
| **Assigned To** | The user the case is assigned to. | (hidden in the figure) |
| **Alerts** | Number of alerts in the case. | 1 |
| **Case Age** | Age of the case. | 75 Days |
| **Case Origin** | How the case was created. | - |
| **Created At** | Date and time the case was created. The heading has a sort icon. | 31 Jul, 06:52:00 AM |

## Screening History tab {#s-5-7}

::path[Customer Profile → Screening History]

Use this tab to see when the customer was screened against the watchlists and with what result. The **Screening History** tab lists the name-screening runs that included this customer, newest first.

::figure[Screening History: the Status and Screening Period filters (1) and the columns (2), with six Delta Screening runs, each with No Alerts]{src="customers/13-screening-history.png" id="fig-customers-screening-history"}

::: legend
1. Filters: **Status** (default **All Status**) and **Screening Period** (**Pick a date range**).
2. Columns: **Screening Date**, **Screening Type**, **Alert Score**.
:::

| Column | What it shows | Example |
| --- | --- | --- |
| **Screening Date** | Date and time of the run, with the **RUN ID** (and a copy icon) below it. | Sep 23, 2026, 11:03 AM; RUN ID 466 |
| **Screening Type** | The kind of screening run. | **Delta Screening** |
| **Alert Score** | The result of the run for this customer. | **No Alerts** |

The example shows six runs (RUN IDs 466, 465, 464, 463, 430 and 397), all **Delta Screening** with **No Alerts**. Screening runs are described in [Name Screening](#name-screening).

## STR History tab {#s-5-8}

::path[Customer Profile → STR History]

Use this tab to check whether STRs have already been filed that involve the customer. The **STR History** tab lists Suspicious Transaction Reports (STRs) linked to this customer, in the same columns as the [Regulatory Reports](#str-listing) register.

::figure[STR History: the Created By and Creation Period filters (1), the columns (2) and the Download CSV icon (3), with STR 661 for case CASE-2026-0034611, amount ₱707,955.42]{src="customers/14-str-history.png" id="fig-customers-str-history"}

::: legend
1. Filters: **Created By** (default **All Assignees**) and **Creation Period** (**Pick a date range**).
2. The columns, described in the table below.
3. **Download CSV**: a download icon in each row.
:::

| Column | Example |
| --- | --- |
| **Case Title / ID** | ALT-TMS-21072026-041467, CASE-2026-0034611 |
| **STR ID** | 661 |
| **Created At** | 14 Aug, 07:36:00 AM |
| **Created By** | (hidden in the figure) |
| **Subjects** | Pooja Sharma, David Lee, Estrella Abella Catalan |
| **Amount** | ₱707,955.42 |
| **Download CSV** | A download icon (3 in the figure) |

The case in this row, CASE-2026-0034611, is the case listed under [Other Cases / Alerts](#s-5-6). For what each column means and how to open a filed STR, see [Regulatory Reports](#str-listing).

::: note
The **Subjects** of STR 661 shown here are Pooja Sharma, David Lee and Estrella Abella Catalan; they do not include Rafael Serrano Dimaculangan. David Lee and Estrella Abella Catalan appear as his counterparties on the Transactions tab.
:::

## Review a customer during an investigation {#s-5-9}

::path[Fyscal ARCX → Customers → Customer 360 → *customer name*]

<dl class="key-facts"><div><dt>When</dt><dd>While you work an alert or case for the customer</dd></div><div><dt>Where</dt><dd>Customer 360 → the Customer Profile</dd></div><div><dt>Edits</dt><dd>None: the profile shows no edit controls</dd></div><div><dt>Output</dt><dd>Notes for the case timeline and the rationale</dd></div></dl>

Use the Customer Profile to compare what the customer said they would do with what they actually did, and to check their history. Work through it in the order below and note what you find in the case's [Timeline and notes](#s-3-7).

<figure class="diagram flow"><ol class="dg-steps"><li class="dg-step"><span class="dg-title">Profile</span><span class="dg-sub">Tags, More, Accounts</span></li><li class="dg-step"><span class="dg-title">Customer Risk Score</span><span class="dg-sub">Score, band, attributes scored 0</span></li><li class="dg-step is-key"><span class="dg-title">Analytics</span><span class="dg-sub">Totals per currency and period</span></li><li class="dg-step"><span class="dg-title">Transactions</span><span class="dg-sub">The individual records, Export CSV</span></li><li class="dg-step"><span class="dg-title">Other Cases / Alerts</span><span class="dg-sub">Earlier investigations</span></li><li class="dg-step"><span class="dg-title">Screening History</span><span class="dg-sub">Watchlist screening results</span></li><li class="dg-step"><span class="dg-title">STR History</span><span class="dg-sub">STRs already filed</span></li></ol><figcaption><span class="cap-num">Diagram 5.1</span> — Reviewing a customer, tab by tab</figcaption></figure>

The order goes from what the customer declared, to what they did, to what the institution already knows about them. Each step below matches one box of the diagram.

::: step Read the profile
Open the customer (see [The Customer Profile](#s-5-3)). Note **RISK**, **KYC**, **STATUS** and **PEP Flag**, then click **More** and note **Expected Monthly Spend**, **Purpose**, **Expected Txn Frequency** and **Sanctions**. Check the account status under **Accounts**.
:::

::: step Check the risk score
On [Customer Risk Score](#s-5-14), note the score and its band, which attributes add the most to it, and any attribute scored 0 because of *No value provided* or *Unable to match value to any scoring row*.
:::

::: step Compare with the Analytics totals
On [Analytics](#s-5-4), choose the period (**1D**, **7D**, **30D** or **All**) that you want to compare with the profile. Read **INCOMING** and **OUTGOING** one currency at a time: totals are not converted to a single currency. Note the largest transaction (**MAX**) and the top counterparties.
:::

::: step Check the individual transactions
On [Transactions](#s-5-5), find the transactions behind the totals: their dates, types and counterparties. Set the date range above the charts to the period of the transactions, and use **Export CSV** if you need the list outside the platform.
:::

::: step Look for earlier cases and alerts
On [Other Cases / Alerts](#s-5-6), check the **Cases** and **Alerts** counts and the status and disposition of earlier cases.
:::

::: step Check the screening results
On [Screening History](#s-5-7), check when the customer was last screened and the **Alert Score** of each run.
:::

::: step Check for earlier STRs
On [STR History](#s-5-8), check whether STRs have already been filed and open them in [Regulatory Reports](#str-listing) if you need the detail.
:::

#### Worked example: profile against activity

The values below are all on screen for Rafael Serrano Dimaculangan (CUST-FYSCAL-604554), with **All** selected on Analytics ([](#fig-customers-analytics-flows)) and the profile expanded with More ([](#fig-customers-profile-more)). The Transactions tab lists 19 transactions, all dated 21 Jul.

| Profile says | Activity shows | Point to note in the case |
| --- | --- | --- |
| **Expected Monthly Spend** ₱1,710,199.43 | **OUTGOING** PHP 915,874.18 (8 txns · 8 recipients), plus USD 198,759.28, EUR 6,875.71 and JPY 3,131.98 in one transaction each | Compare spend currency by currency; the foreign-currency amounts are not included in the PHP total. |
| **Expected Txn Frequency** QUARTERLY | 19 transactions, all on 21 Jul | Many transactions on one day against a quarterly expectation. |
| **Purpose** Remittance receiving | **INCOMING** PHP 845,674.79 (4 txns · 4 senders); **OUTGOING** PHP 915,874.18 | More PHP sent out than received, against a stated purpose of receiving remittances. |
| **Designation** Cook; **Declared Income** ₱2,323,206.00 | Largest outgoing transaction PHP 704,823.44 (TXN-455164-KJX) to Estrella Abella Catalan | The size of single transactions against the stated occupation and income. |
| **Sanctions** REVIEW\_REQUIRED | Screening History: six Delta Screening runs, each **No Alerts** | What the REVIEW\_REQUIRED value refers to, and whether it has been resolved. |

None of these points decides the case on its own. Record them, with the values, in your notes and in the rationale when you dispose the alerts (see [Dispose alerts and close a case](#s-3-10)).

## Customer risk profile (CRP) {#s-5-10}

::path[Fyscal ARCX → Customers → Risk Score Configuration]

The customer risk profile (CRP) gives every customer a risk score from 0 to 100, worked out from their customer data. Administrators decide which customer details count towards the score and how much each one counts; the platform applies the same settings to every customer. The CRP is set up on two pages under **Customers**, next to **Customer 360**:

- **Risk Score Configuration**: the attributes that are scored, the score of each attribute value, and the weightage of each attribute.
- **Score Configuration**: the score bands, such as **Low**, **Medium** and **High**, that turn a score into a risk level.

Each customer's score, and how each attribute adds to it, is shown on the [Customer Risk Score tab](#s-5-14) of their Customer Profile.

<dl class="key-facts"><div><dt>Who</dt><dd>Administrators and compliance heads who own the risk methodology</dd></div><div><dt>Where</dt><dd>Fyscal ARCX → Customers → Risk Score Configuration and Score Configuration</dd></div><div><dt>Changes</dt><dd>Made in a draft, then activated; every version is kept in the history</dd></div><div><dt>Limits</dt><dd>Each value score 0 to 100; weightages 100% in total at most</dd></div></dl>

::: note AML context
A risk-based approach means knowing which customers carry more money-laundering risk and giving them more attention: closer monitoring, more frequent reviews and enhanced due diligence. The CRP records that assessment in one place and applies it the same way to every customer, so the risk rating can be explained to supervisors and auditors.
:::

#### How the risk score is worked out

The configuration has three parts. Each **attribute** is a customer detail, such as **KYC Level**, **PEP Status** or **Nationality**. Each attribute has rows that give a **Score** from 0 to 100 to one or more of its values, for example **KYC 1** scores 20 and **KYC 0** scores 10. Each attribute also has a **Weightage**, the share of the total risk score it carries, in per cent.

<figure class="diagram flow"><ol class="dg-steps"><li class="dg-step"><span class="dg-title">Attributes</span><span class="dg-sub">Customer details to score, e.g. KYC Level, PEP Status</span></li><li class="dg-step"><span class="dg-title">Value scores</span><span class="dg-sub">0 to 100 for each value, e.g. PEP = 80</span></li><li class="dg-step is-key"><span class="dg-title">Weightage</span><span class="dg-sub">% per attribute, 100% in total at most</span></li><li class="dg-step"><span class="dg-title">Risk score</span><span class="dg-sub">0 to 100 for each customer</span></li><li class="dg-step"><span class="dg-title">Score band</span><span class="dg-sub">Low, Medium or High (Score Configuration)</span></li></ol><figcaption><span class="cap-num">Diagram 5.2</span> — From customer data to a risk level</figcaption></figure>

For each attribute, the platform takes the score of the customer's value and multiplies it by the attribute's weightage. The risk score is the sum of these weighted scores:

**Risk score = (score × weightage) for each attribute, added together**

The score used for each attribute is the score of the row that matches the customer's value. There is no normalisation, and the scores of the rows within one attribute do not have to add up to 100: each row's score stands on its own.

::: todo
Confirm with engineering that the live scoring engine uses this formula (sum of matched row score × attribute weightage %, no normalisation) before publishing. The formula is taken from the specification.
:::

Because every value score is between 0 and 100 and the weightages add up to 100% at most, the risk score is always between 0 and 100. The score bands in Score Configuration then give the risk level: with the bands of the draft shown in [Set the score bands](#s-5-12), a score below 71 is **Low**, 71 to below 80 is **Medium**, and 80 to 100 is **High**.

#### Worked example

These values are from the Customer Risk Score tab of the customer Emiliano Earl Gica Alvarez ([](#fig-customers-risk-score-tab)), scored with the active configuration in [](#fig-customers-risk-score-active).

| Attribute | Weightage | Customer's value | Value score | Weighted score |
| --- | --- | --- | --- | --- |
| **KYC Level** | 14% | **KYC 0** | 10 | 10 × 14% = 1.4 |
| **PEP Status** | 20% | none | 0 | 0 × 20% = 0 |
| **Nationality** | 7% | **Philippines** | 5 | 5 × 7% = 0.35 |
| **Country of Residence / Operation** | 17% | **Philippines** | 5 | 5 × 17% = 0.85 |
| **Age** | 16% | **19-42** | 10 | 10 × 16% = 1.6 |
| **ID Type** | 10% | **DRIVERS_LICENSE** | 0 (no matching row) | 0 × 10% = 0 |
| **Occupation** | 16% | **Homemaker** | 30 | 30 × 16% = 4.8 |
| **Total** | **100%** | | | **9**, band **Low** |

Occupation adds the most here: 4.8 of the 9 points. If the same customer were a PEP, **PEP Status** would add 80 × 20% = 16 points and the score would be 25. Raising an attribute's weightage makes its values move the risk score more; lowering it makes them count less.

When the customer data has no value for an attribute, the Customer Risk Score tab shows *No value provided. Scored 0.* for it.

::: not-covered
This edition does not confirm how a customer is scored when their value matches no row of an attribute (the screen above shows *Unable to match value to any scoring row. Scored 0.*), or when a newly activated configuration is applied to existing customers' scores.
:::

## Set up the risk score attributes {#s-5-11}

::path[Fyscal ARCX → Customers → Risk Score Configuration]

Open **Risk Score Configuration** to see the attributes, scores and weightages in use. The page has two tabs: **Active Configuration**, the configuration in force, and **Configuration History**, every version saved (see [Configuration history](#s-5-13)).

::: step Start when no attributes are configured
Before any attribute is added, the page shows **0 Attributes** and the message *No attributes configured yet*, and **Total Weightage** is **0%**. Click **Add Attributes**, tick the attributes to score, and click **Add**. **Edit** and **Activate** stay unavailable until there is something to activate.
:::

::figure[A configuration with no attributes: Cancel, Save Draft, Edit and Activate (1), Total Weightage 0% (2), the empty-state message (3), Add Attributes (4) and the list of attributes to choose from (5)]{src="customers/15-risk-score-empty.png" id="fig-customers-risk-score-empty"}

::: legend
1. **Cancel**, **Save Draft**, **Edit** and **Activate**. **Edit** and **Activate** are greyed out while there is nothing to edit or activate.
2. **Total Weightage: 0%** with the **Totals 0%** tag: no weightage has been given yet.
3. *No attributes configured yet*: risk scores are calculated from the attributes you add.
4. **Add Attributes**: opens the list of customer attributes.
5. The attributes to choose from, each with a checkbox; **Select All** ticks them all.
:::

::: note
[](#fig-customers-risk-score-empty) is from the product design. In the product, **Add Attribute** opens as a dialog with more attributes (see the step *Add attributes* below).
:::

::: step Read the active configuration
When a configuration is active, the page shows who created it and when, its **Config version** and the status **ACTIVE**. The **Total Weightage** panel shows each attribute's weightage as a bar, and each attribute below lists its values and their scores.
:::

::figure[The active configuration: the tabs (1), the version details (2), Edit (3), the Total Weightage panel (4), Expand All (5) and the KYC Level attribute with its values and scores (6)]{src="customers/16-risk-score-active.png" id="fig-customers-risk-score-active"}

::: legend
1. **Active Configuration** and **Configuration History** tabs.
2. **Created At**, **Created By**, **Config version** and **Status** (**ACTIVE**).
3. **Edit**: starts a draft of a new version.
4. **Total Weightage: 100%** with **Totals 100%**, and a bar for each attribute's weightage (here **KYC Level** 14%, **PEP Status** 20%, **Nationality** 7%, **Country of Residence / Operation** 17%, **Age** 16%, **ID Type** 10%, **Occupation** 16%).
5. **Expand All**: opens every attribute to show its values.
6. An attribute, **KYC Level**, with **Weightage 14%**: the value **KYC 1** has **Score 20** and **KYC 0** has **Score 10**.
:::

::: step Edit: work in a draft
Click **Edit**. The page opens a draft with the status **DRAFT** and its own **Config version**; the active configuration stays in force until you activate the draft. Each attribute now has a **Weightage** box, a delete icon and an arrow that opens its values.
:::

::figure[A draft: the version details with DRAFT (1), Cancel, Save Draft, Discard draft and Activate (2), the Total Weightage panel (3), the Weightage box (4), and the delete icon and arrow (5)]{src="customers/17-risk-score-draft.png" id="fig-customers-risk-score-draft"}

::: legend
1. **Created At**, **Created By**, **Config version** and **Status: DRAFT**.
2. **Cancel** leaves editing; **Save Draft** saves it without activating; **Discard draft** deletes the draft; **Activate** makes the draft the active configuration.
3. **Total Weightage** and the **Totals** tag, updated as you type.
4. **Weightage** of the attribute, in per cent.
5. The delete icon removes the attribute from the draft; the arrow opens its values.
:::

::: step Add attributes
Click **Add Attribute** below the last attribute. In the dialog, tick each customer attribute to score, or **Select All**, and click **Add**. The attributes are added to the draft, each with a weightage to fill in.
:::

::figure[The Add Attribute dialog: Select All (1), the customer attributes with three ticked (2), and Cancel and Add (3)]{src="customers/18-risk-score-add-attribute.png" id="fig-customers-risk-score-add-attribute"}

::: legend
1. **Select All**: ticks every attribute in the list.
2. The customer attributes, for example **Customer Type**, **Status**, **Customer Segment**, **Risk Level (ingested)**, **Risk Score (ingested)**, **Sanctions Status**, **Source of Funds**, **Relationship Tenure**, **Onboarding Channel**, **City**, **Province / Region** and **Address Country**; scroll for more.
3. **Cancel** closes the dialog; **Add** adds the ticked attributes.
:::

::: step Give each value a score
Open an attribute with its arrow. Each row links one or more values of the attribute to a score: choose the values in the row's list (they appear as tags, such as **KYC 1**), then type the **Score**, from 0 to 100. Click **Add Row** for another value, and the delete icon at the end of a row to remove it.
:::

::figure[Scoring the values of KYC Level: Weightage (1), a row with its value KYC 1 and Score 20 (2), the delete icon of the row (3) and Add Row (4)]{src="customers/19-risk-score-values.png" id="fig-customers-risk-score-values"}

::: legend
1. **Weightage** of the attribute (here 14%).
2. A row: the value or values it applies to (**KYC 1**), and its **Score** (20).
3. Deletes the row.
4. **Add Row**: adds a row for another value.
:::

::: step Set the weightages
Type a **Weightage** for each attribute. Watch **Total Weightage** at the top: the weightages of all attributes together must not exceed 100%. When they add up to exactly 100%, the tag reads **Totals 100%** and the risk score can use the full range from 0 to 100.
:::

::: step Save or activate
Click **Save Draft** to keep the draft and come back to it later, or **Activate** to put it in force. The activated version becomes **ACTIVE** in [Configuration history](#s-5-13), and the version that was active before becomes **INACTIVE**. To drop the draft, click **Discard draft**.
:::

#### Rules the configuration follows

| What | Allowed | Example |
| --- | --- | --- |
| **Score** of a value row | A number from 0 to 100. Higher means more risk. | **PEP** → 80 |
| **Weightage** of an attribute | A percentage from 0 to 100. | **PEP Status** → 20% |
| **Total Weightage** | The weightages of all attributes together: 100% at most. | 14 + 20 + 7 + 17 + 16 + 10 + 16 = 100% |
| Risk score of a customer | Always between 0 and 100, because of the two rules above. | 9 in the [worked example](#s-5-10) |

::: important
Keep **Total Weightage** at 100%. If the weightages add up to less, no customer can reach the top of the score range; for example, with a total of 70% the highest possible risk score is 70, which is below the **High** band of the draft in [Set the score bands](#s-5-12).
:::

::: note
The scores in these screenshots are from a test configuration. For example, **Not a PEP** scores 100 and **PEP** scores 80; in a live configuration, the value with more risk normally has the higher score.
:::

## Set the score bands {#s-5-12}

::path[Fyscal ARCX → Customers → Score Configuration]

Score Configuration sets the bands that turn a risk score into a risk level. Each band has a name, a colour and a score range; together the bands cover the whole range from 0 to 100. Like the risk score configuration, the bands are changed in a draft and then activated, and every version is kept under **Score Configuration History**.

::figure[A draft of the score bands: the tabs (1), the draft details (2), Cancel, Save Draft, Discard draft and Activate (3), the name and colour of the Low band (4), its Min score and Max score (5), the delete icon (6) and Add band (7)]{src="customers/20-score-bands.png" id="fig-customers-score-bands"}

::: legend
1. **Active Score Configuration** and **Score Configuration History** tabs.
2. **Draft Score Configuration**: **Created At**, **Created By**, **Config version** and **Status: DRAFT**.
3. **Cancel**, **Save Draft**, **Discard draft** and **Activate**, as for the risk score configuration.
4. **Name** (**Low**) and **Color** (**#15803D**, green) of the band.
5. **Min score** and **Max score**. The band includes its minimum and goes up to, but not including, its maximum (**< 71**). **Min score** cannot be edited: it follows the previous band's **Max score**.
6. Deletes the band.
7. **Add band**: adds a band.
:::

The bands of the draft in [](#fig-customers-score-bands), which is not the active configuration:

| Band | Color | Scores |
| --- | --- | --- |
| **Low** | **#15803D** (green) | 0 to below 71 |
| **Medium** | **#d9c708** (yellow) | 71 to below 80 |
| **High** | **#e90c0c** (red) | 80 to 100 |

::: step Change the bands
Open the draft and edit a band's **Name**, **Color** or **Max score**. You only type the maximum. **Min score** cannot be edited: each band's **Min score** follows the previous band's **Max score** automatically (here **Medium** starts at 71 because **Low** ends below 71). The first band starts at 0 and the last band ends at **≤ 100**.
:::

::: step Add or remove a band
Click **Add band** to add a band, or the delete icon to remove one. Check that the bands still run from 0 to 100 without a gap.
:::

::: step Activate
Click **Activate** to put the bands in force, or **Save Draft** to finish later.
:::

::: note
The **Risk Level** and **Score** columns of [the customer list](#s-5-1), and the **Risk Tier** filter, show risk levels such as **Low**, **Medium** and **High**. [](#fig-customers-score-bands) shows a draft, with bands at 71 and 80, not the active score configuration. That is why its bands do not match the scores in the customer list, for example **High 62.61%**.
:::

## Configuration history {#s-5-13}

::path[Fyscal ARCX → Customers → Risk Score Configuration → Configuration History]

Every version of the risk score configuration is kept. Open the **Configuration History** tab to see which version is in force, who created each version and when. Score Configuration has the same list under **Score Configuration History**.

::figure[Configuration History: the tabs (1), a Config Version ID with its copy icon (2), the status ACTIVE (3), Created by (4), the count line (5) and the page controls (6)]{src="customers/21-risk-score-history.png" id="fig-customers-risk-score-history"}

::: legend
1. **Active Configuration** and **Configuration History** tabs.
2. **Config Version ID**, with a copy icon.
3. **Status**: **ACTIVE** for the version in force, **INACTIVE** for earlier versions, and **DRAFT** for a draft not yet activated.
4. **Created by**: the user who created the version.
5. **Showing 1-20 of 22**: 20 versions per page.
6. **Page 1 of 2** and the first, previous, next and last page buttons.
:::

| Status | Meaning |
| --- | --- |
| **ACTIVE** | The version in force. Only one version is active at a time. |
| **DRAFT** | Saved with **Save Draft** and not yet activated. |
| **INACTIVE** | An earlier version, replaced when a newer one was activated. |

Use the history to answer an auditor's question about which risk methodology applied on a given date: find the version that was **ACTIVE** at that time, by its **Created** date and the date of the next activation.


<div class="related-modules"><div class="related-modules-title">Related in Core Workflow</div><div class="related-modules-grid"><a href="#case-manager" class="related-module-card"><span class="related-module-icon"><svg width="18" height="18" viewbox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><rect x="3" y="7" width="18" height="13" rx="2.5"/><path d="M8.5 7V5.5a2 2 0 0 1 2-2h3a2 2 0 0 1 2 2V7"/><path d="M3 12.5h18"/></svg></span><span class="related-module-name">Case Manager</span></a><a href="#case-manager-config" class="related-module-card"><span class="related-module-icon"><svg width="18" height="18" viewbox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M4 7h9M17 7h3M4 17h3M11 17h9"/><circle cx="15" cy="7" r="2"/><circle cx="9" cy="17" r="2"/></svg></span><span class="related-module-name">Case Manager Configuration</span></a><a href="#str-listing" class="related-module-card"><span class="related-module-icon"><svg width="18" height="18" viewbox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14 3H7a2 2 0 0 0-2 2v14a2 2 0 0 0 2 2h10a2 2 0 0 0 2-2V8z"/><path d="M14 3v5h5"/><path d="M9 13h6M9 17h6"/></svg></span><span class="related-module-name">Regulatory Reports</span></a></div></div>