Term	Definition
Activation Mode	The choice made when you click Activate on a typology: Shadow Mode, "Alert generated against live data will be shown in rule detail page.", or Published Mode, "Alert from this rule will flow into Alert Manager." The choice goes to a checker as an Activate Typology request, and the typology stays Draft while the request waits. See Request Shadow activation.
Activity	In Maker Checker Approval, a configuration that names an action somewhere in the platform and sets its approval rules: SLA, warning point, approval count, and maker and checker permissions. Activity codes begin ACT_. See Configs.
Activity Timeline	The panel opened by Timeline & Notes on a case or alert. It holds notes and a dated log of events, newest first. See Timeline and notes.
Agentic Workflows	The Case Manager Config page that holds the prompts (Prompt Config) and the model configuration (Model Config) used by Case Copilot and the AI Summary. See Agentic Workflows: Prompt Config.
Aggregation	The part of Create Variables where you set what a variable calculates: Field, Function and Group by, all required. See Create a variable.
AI Summary	A card on Alert Details that generates a summary of the alert: a verdict, rationale, findings and a recommended action, with the prompt version and model. Each generation costs one run against the daily limit. See Alert Details: Name Screening.
Alert	A single detection that needs review: one screening match or one rule breach. In Fyscal ARCX an alert is raised by Name Screening (ID starting ALT-NS) or Transaction Monitoring (ID starting ALT-TMS) and listed in Case Manager → Alerts. Alerts have six statuses. See Alerts list.
Alert band	A named score range in Name Screening Alert Configuration, with a colour, Min % and Max %, a No Alert setting, an SLA Deadline and an Auto Hibernate setting. The band and percentage appear as an alert's score, for example Low 75.76%. See Alert Configuration.
Alert Manager	A name shown in the Activation Mode dialog: in Published Mode, "Alert from this rule will flow into Alert Manager." No sidebar item is called Alert Manager. See Request Shadow activation.
AML	Anti-money laundering: the laws, controls and checks that stop criminal money being made to look legitimate. Fyscal ARCX is an AML platform for screening, monitoring, case work and reporting. See How Fyscal ARCX fits together.
AMLC	Anti-Money Laundering Council (Philippines). The STR wizard prepares a GoTRACS-compliant STR for the AMLC. See File an STR.
AND, OR (Match)	How conditions combine. Inside a group, Match AND means every row must be true ("AND — all must match"); OR means one true row is enough ("OR — any one matches"). Combine groups with does the same between groups. See Building blocks and How conditions are evaluated.
Approval Count	The number of approvals set on a Maker Checker activity. The default on the Create Activity form is 1. See Create an activity.
Auto Assignment of Cases	The part of Case Creation & Assignment that maps a group of alert types to people, with a method such as Sequential. See Case Creation & Assignment: Active Configuration.
Auto Hibernate	A Yes or No setting on each alert band in Alert Configuration. See Alert Configuration.
Average	A variable Function for numeric fields such as amount: the average value of the field over the window. See Create a variable.
Batch Ingestion	The Data Ingestion page that holds the ingestion schedule and lists the import jobs for Customers, Accounts and Transactions files. See Batch Ingestion.
Batch Screening	The Name Screening page that lists the batch screening runs, with customers scanned, alerts created, errors, watchlist count, status and duration for each run. See Batch Screening.
Beneficiary	The person or organisation that receives the funds or the benefit of a transaction. In an STR, party role B. See Step 4: Transaction.
Between, Not Between	Filter operators for number fields: the value falls inside, or outside, a range you give. Rule 1 uses two amount filters to set its band instead. See Building blocks.
BSP	Bangko Sentral ng Pilipinas. The STR Institution code is described on screen as an "18-digit code assigned by AMLC/BSP". See Step 2: Report Type.
Case	A record in Case Manager → Cases that holds one or more alerts for a customer, with its own status, assignee and disposition. Case IDs look like CASE-2026-0034617. See Case Details.
Case Copilot	An AI Investigation Assistant: a chat panel on Case Details that answers questions about the open case, from prompts such as Summarize case or Explain match scores. Check its answers against the case. See Case Copilot.
Case Origin	How a case was created: Manual or Automated. See Cases list.
Checker	The second person in a Maker Checker request: the user who approves or declines it. An activity sets the Checker 1 Permission and the Approval Count, and a ticket shows Checker Progress, for example "0 / 1 checkers acted". No approve or decline buttons appear in the maker's view of their own ticket, which offers only Withdraw. See View a ticket.
Condition	One row of a typology group: WHEN a variable, an operator, and a Static Value or another Variable to compare with. A variable only calculates a value; the condition decides whether that value is suspicious. See Create Typology form.
Config version	The unique ID of a saved configuration. Saved configurations are listed in a history tab, where one is ACTIVE and the rest INACTIVE. See Configuration History.
Count	A variable Function that counts the transactions in the window, for example Count of `id` per sender (Rule 1). See Create a variable.
Count Distinct	A variable Function that counts the different values of a field, for example the different receivers a sender paid (Count Distinct of `receiver_entity_id`, Rule 5). See Rule 5 · Fan-out.
Counterparty	The other party to a customer's transaction: the receiver when the customer sends, the sender when the customer receives. Customer 360 shows the top counterparties; in an STR, party role C. See Analytics tab.
Covered person	In Philippine AML rules, an institution such as a bank that must report suspicious transactions to the AMLC. The phrase appears in the help text of Date of determination. See Step 2: Report Type.
Covered Transaction Report (CTR)	A report to the AMLC of a covered transaction, in general one of more than ₱500,000. Fyscal ARCX creates CTRs automatically once a day from ingested transactions, with a CSV in the GoTRACS format. See The CTR register.
Cross-border	A transaction between parties in different countries. Rule 15 adds up what a sender sent to a country other than their own in the last 30 days. See Rule 15 · Cross-border volume.
Customer 360	The module that lists customers and opens a Customer Profile for each: identity and KYC details, accounts, analytics, transactions, prior cases and alerts, screening history and STR history. See The customer list.
Customer due diligence (CDD)	The checks an institution makes on a customer: who they are, their risk rating, whether they are a PEP, their income and source of funds, and how much and how often they expect to transact. Customer 360 shows these details. See The Customer Profile.
Daily Jobs	The AML Dashboard panel that shows the outcome of the platform's scheduled jobs: Screening & Monitoring Runs and Data Ingestion. See Daily Jobs.
Data Difference	The table on a Maker Checker ticket that shows each changed Field with its Current Value and Proposed Value. See View a ticket.
Date of determination	An STR field, described on screen as the "Date the covered person knew or should have known of the suspicious nature of the transaction. Starts the filing deadline clock." See Step 2: Report Type.
Delta Screening	The Name Screening page that shows the delta screening schedule and lists its runs, including the next scheduled run. Its schedule can be changed with Change Schedule. See Delta Screening.
Device, IP address	The device and network address a payment was made from, held in the transaction fields `sender_device_id` and `sender_ip`. Rules 10 and 11 count how many a sender uses; proposals P5 and P6 count how many customers share one. See Rule 10 · Many devices and Rule 11 · Many IP addresses.
Disposition	The outcome recorded for an alert or a case: True Match, False Match or Potential Match. Lists show - until one is recorded. See Case statuses and dispositions.
Dormant account	An account with no activity for a long period. A sudden payment after a quiet spell is a common red flag; Rule 4 looks for no transactions from 100 to 1 days ago, then a payment in the last day. See Rule 4 · Dormant account.
Draft	A typology status: the rule is saved but not activated. New typologies are saved as Draft, and a rule stays Draft while its activation request is Pending. Dry Run works on a saved draft. See Typology list.
Dry Run	A test of a saved draft typology against past records, started with Dry Run on the Review & schedule rule page. "No alerts are created during a dry run." The result gives Records Scanned and Alert Created for each time window, without listing the matches, and is erased when the rule is updated. See Test a typology with Dry Run.
Duplicate	Makes a copy of a typology (the Actions menu of a Draft rule, or Duplicate Typology on its page) or of a variable. A variable used in a live rule cannot be edited: duplicate it and change the copy. See View Variable.
Enhanced due diligence (EDD)	Extra checks applied to customers an institution rates as higher risk, such as PEPs: more information on the source of funds and closer review of their activity.
Entity	In Create Variables, the Transaction and Entity tabs choose whether a variable is calculated from transactions (the default) or from entity data. In the Rule index, Entity is the field a rule's variables are grouped by: sender or receiver. See Create a variable.
Escalated	A status of cases and alerts. In AML work, escalation passes an alert or case to a more senior reviewer. The dashboard tiles Escalated Alerts and Escalated Cases carry the sub-label Pending Supervisor Review, and All Alerts and All Cases each have an Escalated chip. See Case statuses and dispositions.
Execution Interval	How often a Transaction Monitoring schedule runs: a number and a unit, for example every 1 day. See Schedules: Schedule List.
Expired	A Maker Checker ticket status. The activation requests made for this guide expired with no checker action, and their rules stayed Draft: a request has to be approved before it expires, and an expired one needs a new request. See Ticket statuses.
False Match	A disposition value. For an alert it is chosen in the Dispose Alert dialog, together with a required Rationale Code and Rationale Details; a case has its own Disposition in the case bar. The other values are True Match and Potential Match. See Dispose alerts and close a case.
False negative	Suspicious activity that a rule or screening check does not alert on. Raising thresholds cuts false positives but can create false negatives, which is why changes are tested first.
False positive	An alert that turns out, on review, not to be suspicious or not to be the listed party. Many false positives usually mean a rule needs tuning. See Tuning and false positives.
Fan-in	Many different senders paying one receiver, a pattern typical of money-mule and pooling accounts. See Rule 6 · Fan-in.
Fan-out	One sender paying many different receivers, for example to spread funds quickly. See Rule 5 · Fan-out.
Field	In Create Variables, the transaction field a variable calculates on, for example `amount`, `id` or `receiver_entity_id`. The field decides which functions are offered. See Create a variable.
Filters	Optional rows in Create Variables (field · operator · value) that limit a variable to matching transactions. Rows combine as "AND — all must match". See Create a variable.
Financial intelligence unit (FIU)	The national agency that receives and analyses suspicious transaction reports. STRs in this guide are prepared for the AMLC. See File an STR.
Four-eyes principle	A control in which one person proposes or decides and a different person checks and approves. Maker Checker Approval and the review of a case in Pending Review apply it. See Configs.
FT AML	The breadcrumb shown at the top of the Transaction Monitoring screens (typologies, variables and schedules). It is a label on those screens, not a separate module: you reach them from Fyscal ARCX → Transaction Monitoring in the sidebar. See Typology list.
Function	In Create Variables, the calculation: Count, Count Distinct, Sum, Average, Minimum or Maximum. Numeric fields offer all six; text and ID fields offer only Count, Count Distinct, Minimum and Maximum. See Building blocks.
Fuzzy, Phonetic	The two sub-fields of Name in Screening Configuration, each with its own weightage (Fuzzy 80% and Phonetic 20% in the configuration shown). See Screening Configuration.
GoTRACS	The AMLC reporting format the STR wizard follows ("GoTRACS-compliant STR filing for AMLC"). Codes after STR field names, such as H-3 or D-SD-2, are the GoTRACS field references shown on screen. See File an STR.
Greater Than Equal (>=)	The condition operator most rules in this guide use: the variable is equal to or above the threshold, for example ≥ 10 receivers. See Create Typology form.
Group by	The field a variable is calculated per: `sender_entity_id` gives one result per sender, `receiver_entity_id` one per receiver. See Create a variable.
Hibernated	Alerts shown when the Show Hibernated checkbox on All Alerts is ticked. Alert bands carry an Auto Hibernate setting. See Alerts list.
Hierarchy	A template in Team Management that defines an organisational structure as levels of roles with members. The AML hierarchy has the levels AML Admin, AML Team Lead, AML Supervisor and AML Analyst. Status: Active, Inactive or Removed. See Team Management: the hierarchy list.
High value	A large total moved in a period. Rule 3 adds up what a sender sent in the last 30 days; High Value (HV01) is also a typology type. See Rule 3 · High value.
High-risk country	A country (jurisdiction) an institution's policy treats as higher risk for money laundering or terrorist financing. Proposal P1 looks for payments to such countries. See Proposed typologies.
In, Not In	Operators that compare a field with a list of values. Type each value and press Enter. See Building blocks.
Ingestion	Loading data files into the platform: customer, account and transaction files in Batch Ingestion, and watchlist files in Watchlist Ingestion. Each job shows its total, ingested and skipped rows. See Batch Ingestion.
Instrument	The card or account a payment is paid from, held in the field `sender_instrument_id`. Rule 12 counts the different instruments a sender used in 7 days. See Rule 12 · Many instruments.
Internal Watchlist	A watchlist source alongside LSEG. You add subjects to it, or remove them, by uploading a CSV file in Watchlist Ingestion. See Upload an Internal Watchlist file.
Is Null, Is Not Null	Operators in the operator lists that test whether a value is empty. In a typology condition they are not saved with the rule, so do not rely on them. To test for "no transactions", see Building blocks.
KYC	Know Your Customer: checking who a customer is and understanding the business they expect to do. Customer 360 shows a KYC Level in the customer list (for example Kyc 0, Kyc 1) and KYC on the Customer Profile (for example L2). See The Customer Profile.
Large single transaction	One very large payment. Rule 7 takes the sender's largest single amount in the last day; Large Transaction (LT-01) is also a typology type. See Rule 7 · Large single transaction.
Layering	The stage of money laundering that moves funds through many transactions or accounts to hide where they came from. Layering is also a typology type; proposal P2 (pass-through account) looks for it. See Proposed typologies.
Live Alerts, Shadow Alerts	Columns of the Transaction Monitoring Run History: the alerts raised in a run by Published rules (Live) and by Shadow rules. See Schedules: Run History.
Look-back	Another name for a variable's window: the period counted back from the trigger time T. See Building blocks.
LSEG	A watchlist source. LSEG files appear in Watchlist Ingestion in pairs named watchlist_delta__… and watchlist_deleted__…. See Watchlist Ingestion.
Maker	The user who raises a Maker Checker request, for example by submitting an Activate Typology request with a Reason. An activity sets the Maker Permission. The maker can Withdraw their own pending ticket, with a remark, but has no approve or decline buttons. See Tickets and View a ticket.
Maker Checker Approval	The sidebar item that holds the activities that need approval (Configs) and the approval requests raised against them (Tickets). See Maker Checker Approval.
Manual Screening	The Name Screening page where you enter one person's or company's details and screen them on demand. See Manual Screening.
Match Score	A row of the Matches panel on a Name Screening alert or case. Each watchlist candidate shows its score band and percentage (for example LOW 87.94%), and each field its own Weightage and Score. See Customer, accounts and matches.
Matches	The area of a Name Screening alert that compares the customer with each watchlist candidate, field by field, with the weightage and score of each field. See Customer, accounts and matches.
Merchant category code	A code for a merchant's type of business, held in the transaction field `merchant_category_code`. Proposal P7 looks for payments to categories your policy treats as high risk. See Proposed typologies.
Minimum, Maximum	Variable functions: the smallest or largest value of a field in the window. Rule 7 uses Maximum of amount to find the largest single payment. See Rule 7 · Large single transaction.
Money mule	A person whose account is used to receive and pass on criminal money, knowingly or not. Fan-in, many devices on one account, and one device used by many customers are typical signs. See Rule 6 · Fan-in.
Name Screening	Checking customer names against watchlists of sanctioned parties, PEPs and other names of concern. In Fyscal ARCX, the module that runs batch, delta and manual screening and sets alert bands and weightages. See Name Screening.
Operator	The comparison in a filter or condition. Number fields offer Equal, Not Equal, Greater Than, Greater Than Equal, Less Than, Less Than Equal, Between, Not Between, In and Not In; text fields also offer Contains, Starts With, Ends With, Is Null and Is Not Null. See Building blocks.
Party role	The letter shown against each sender and receiver in an STR: S Subject of Suspicion, B Beneficiary, C Counterparty, T Transactor, O Other participant. See Step 4: Transaction.
Pass-through account	An account where money received is sent on almost in full within a short time, a sign of layering. Proposal P2 describes a rule for it. See Proposed typologies.
Paused	A chip beside a typology's status on its page: the rule is not currently running, and the page offers Resume. See Typology list.
PEP	Politically exposed person. Customers carry a PEP Flag; watchlist records carry a PEP Status. See The Customer Profile and Watchlist Search.
Positive control	A check used in this guide when a dry run returns 0 alerts: lower the threshold so that any matching record would alert, confirm that alerts appear, then restore the real threshold. It shows whether 0 means "no such pattern" or "the rule cannot read the data". See Test a typology with Dry Run.
Potential Match	A disposition value, chosen in the same places as True Match and False Match. In general use it means the evidence is not enough to confirm or rule out the match. See Dispose alerts and close a case.
Predicate crime	A crime that produces the money being laundered, such as fraud, drug trafficking or corruption. STR step 3 lists Predicate crimes — PC1-PC36. See Step 3: Reason for suspicion.
Published, Published Mode	Used in three places. A typology status: the rule was activated in Published Mode, "Alert from this rule will flow into Alert Manager." In Agentic Workflows, publishing a prompt creates a new version, and saving a model configuration "publishes a new configuration and retires the current one". In Batch Ingestion, Published is one of the ten job statuses, which the screen does not describe. See Typology list, Edit and publish a prompt and Batch Ingestion.
Rationale code	The coded reason for a disposition, chosen from a dropdown in the Dispose Alert dialog, for example "Identification number of the user is the same as the watchlist". It is required, together with Rationale Details of at least 10 characters. See Dispose alerts and close a case.
Reason for suspicion codes	The codes chosen in step 3 of an STR: Suspicious circumstances SC1–SC6, Predicate crimes PC1–PC36 and Transnational organized crime MC1. See Step 3: Reason for suspicion.
Records Scanned	In a Dry Run result and in a rule's run history, the number of records the run read. 0 means there was no transaction data in the window: check data ingestion for that period before judging the rule. See Schedule Details.
Red flag	A sign that activity may be suspicious and worth a closer look. Each Typology Library rule opens with the red flag it looks for. See Rule index.
Risk Level, RISK	The customer's risk rating. The customer list shows Risk Level as a coloured tag; the Customer Profile and the case customer card show RISK as a tier with a number in brackets, for example HIGH (77). See The Customer Profile.
Risk-based approach	Setting controls in proportion to risk: more checks and lower thresholds for higher-risk customers, products and countries. The Typology Library's thresholds are starting values to set from your own risk assessment.
Rule Analysis	The tab on a Transaction Monitoring alert that shows the rule triggered, its window and frequency, the number of breaches and each breached condition. See Transaction Monitoring evidence tabs.
Sanctions	Legal restrictions on dealing with named people, organisations, vessels or countries. Sanctioned parties appear on watchlists and are what name screening looks for. See Watchlist Search.
Save as Draft	Saves a new typology with the status Draft, on the page after the conditions. It needs a schedule, and the page then becomes Update Typology. See Part 6: Save as draft.
Schedule	When a recurring job runs, shown as Current Frequency, Next Run and Last Run on Batch Ingestion, Batch Screening and Delta Screening. A schedule change takes effect after the next scheduled run. In Transaction Monitoring, a schedule has a name, an Execution Interval, a start time and an optional end time, and one schedule can drive several rules. See Change the ingestion schedule and Schedules: Schedule List.
Screening Configuration	The Name Screening page that holds the weightages of the screening fields (Name, Address, Citizenship, Gender, DOB) and their sub-fields. See Screening Configuration.
SEGMENT	A tag on the Customer Profile and the case customer card that gives the customer's segment, for example Retail. See The Customer Profile.
Shadow, Shadow Mode	A typology status and Activation Mode. In Shadow Mode, "Alert generated against live data will be shown in rule detail page": the rule runs on live data and its alerts appear on the rule's page rather than flowing into Alert Manager. In the Activate Typology ticket, Data Difference shows Activation Mode changing from - to shadow. See Typology list and Request Shadow activation.
Skipped Rows	The rows of a Batch Ingestion file that were not loaded. When above 0, the number is a link that downloads the error rows CSV. See Batch Ingestion.
SLA	Service level agreement. Alerts show an SLA Deadline (On Track or Breached); each alert band sets an SLA Deadline in days, hours and minutes; each Maker Checker activity sets an SLA in hours. See Alerts list.
Smurfing	Many very small payments, often made by several people, that together move a large amount. Rule 8 counts a sender's transactions under ₱1,000 in the last day. See Rule 8 · Smurfing.
Spike	A sudden rise against a customer's own history. Rule 9 compares the sender's 7-day total with their 90-day total. See Rule 9 · Spike against own history.
Static, Dynamic	On a filter row, Static compares the field with a value you type; Dynamic compares it with another field. In a condition the choice is Static Value or Variable. See Building blocks.
Status (case)	One of eight values: Not Started, Under Investigation, Pending Review, Escalated, STR Draft, STR Created, Closed, Reopened. Alerts use the same values except STR Draft and STR Created. See Case statuses and dispositions.
STR	Suspicious Transaction Report. Prepared from a case in Case Manager with the six-step STR wizard, "GoTRACS-compliant STR filing for AMLC". Cases with an STR show the status STR Draft or STR Created, and a filed report is listed, read-only, in Regulatory Reports. See File an STR and The STR register.
STR Type	The type of report chosen in step 2 of an STR: STRR (Regular STR), STRA (Per Account), STRHP (High Priority), STRHU (Highly unusual) or STRBR (Bulk Report). See Step 2: Report Type.
Structuring	Splitting money into several amounts that each stay below a level that would draw attention. Rule 1 counts a sender's transactions in a band just below an amount you review. See Rule 1 · Structuring.
Subject of Suspicion	The person or organisation whose activity the STR is about. In an STR, party role S. See Step 4: Transaction.
Subject parties	Step 5 of an STR: the parties auto-derived from the selected transactions, each with a party role and identity details. See Step 5: Subject parties.
Sum	A variable Function for numeric fields: the total of the field over the window, for example the amount a sender sent in 30 days (Rule 3). See Create a variable.
Suppression Window	A setting on a typology: a number (default 0) and a unit such as Hour or Day, for example 7 Day. An information icon (ⓘ) next to the label holds the field's help text. See Create Typology form.
Team Management	The Case Manager Config page that lists the hierarchy templates and opens the hierarchy builder. See Team Management: the hierarchy list.
THAN MULTIPLIER	In a condition that compares with another Variable, the factor applied to that variable: 0.5 means "at least half of it" (Rule 9). See Create Typology form.
Threshold	The value a condition compares a variable with, for example ≥ 10 receivers. Set it from your own risk assessment and check it with a Dry Run. See Tuning and false positives.
Ticket	A request raised for a Maker Checker activity and waiting for approval, identified by a Request ID (the ticket details show a longer ID beginning AMLTM_). A ticket starts as Pending; the Status filter lists eight statuses. See Tickets and Ticket statuses.
Time Window	The period a variable covers, set as a unit (Hours, Days, Weeks, Months or Years) and a range "Analyze Transaction from X to Y … ago". The range can end before now: 100 to 1 Days covers the 100 days up to yesterday. See Building blocks.
Transaction Monitoring	Checking customers' transactions for patterns that may be suspicious. In Fyscal ARCX, the module that holds the typologies, variables and schedules and raises alerts with IDs starting ALT-TMS. See Transaction Monitoring.
Transactor	The person who carries out a transaction, who may differ from the account holder. In an STR, party role T. See Step 4: Transaction.
Transnational organized crime	Serious crime planned or carried out across borders by organised groups. STR step 3 lists it as code MC1. See Step 3: Reason for suspicion.
Trigger time (T)	The time a rule's run starts. Variable windows are counted back from it; the form reads "This variable will be triggered time 00:00:00 on day T." See Building blocks.
True Match	A disposition value, chosen in the same places as False Match and Potential Match. In this guide, a case that is Closed with the disposition True Match shows File STR. See File an STR.
Tuning	Adjusting a rule's thresholds, windows, filters and Suppression Window so that it raises useful alerts. Run a Dry Run after each change. See Tuning and false positives.
Typology	A known pattern of money-laundering or terrorist-financing behaviour. In Fyscal ARCX, a Transaction Monitoring rule that looks for one, with an ID starting TMR-. It holds one or more conditions on variables, a typology type, a suppression window and a schedule, and has the status Draft, Shadow or Published. New typologies are saved as Draft and are activated through a Maker Checker request. The Typology Library gives tested examples. See Typology list and Typology Library.
Typology type	The category chosen for a typology on the Create Typology form, for example Structuring (TP100), Velocity (V-01) or Anomaly (TP103). The list shows No category when none was chosen. See Building blocks.
UID	A unique identifier. Watchlist records have a UID (for example 3601955), and so do Maker Checker activities (codes beginning ACT_). See Watchlist Search.
UTC	Coordinated Universal Time. Schedule run times in the Change Screening Schedule and Change Ingestion Schedule dialogs are given in UTC. See Delta Screening.
Variable	A named calculation with an ID starting VAR-, such as the number of transactions a sender made in the last 7 days. It is set by a Field, a Function (for example Count or Sum), a Group by field, a Time Window and optional Filters. Typology conditions test variables, and one variable can be used by many typologies. When a customer has no records in the window, the value is empty, not 0. See Variables list and Building blocks.
Velocity	Many transactions in a short time. Rule 2 counts a sender's transactions in the last day; Velocity (V-01) is also a typology type. See Rule 2 · Velocity.
Watchlist	The records that names are screened against, from the sources LSEG and Internal Watchlist. Each record has a UID, name, PEP status, country, category and date of birth. See Watchlist Search.
Watchlist Ingestion	The Data Ingestion page that lists each watchlist file loaded into the platform, with its source, status and rows processed. See Watchlist Ingestion.
Weightage	The share a screening field or sub-field carries, set in Screening Configuration. The field weightages add up to 100%. Manual Screening shows the weightage next to each field. See Screening Configuration.
Withdraw	The action in the maker's view of their own Pending ticket that withdraws the request; Remarks is required. See View a ticket.