Problem Note 69240: Alerts are not being generated for scenarios that use rule conditions that check for equality in SASĀ® Anti-Money Laundering
Alerts are not generated for scenario rule conditions that check for equality ("==") in SAS Anti-Money Laundering.
Here is an example using a Low Total Assets scenario in the TM Daily Unusual Behavior flow. The scenario uses the following condition to generate alerts:
month_count > 0 AND (total_average_assets/month_count) <= max_avg_assest_threshold
If the total_average_assets = 5000.00 and month_count = 1, an alert is not generated even if it satisfies the condition. This behavior occurs because SAS Visual Investigator stores all non-integer values in floating point representation, causes the calculation 5000/1 to be 5000.000000000001, which is not <= 5000.
On the other hand, if the total_average_assets = 4999.99 and month_count = 1, an alert is generated.
The following scenarios are affected:
- TM Daily ATM
- High-Velocity ATM Withdrawals
- TM Daily High Risk Products
- TM Party Percentage of High-Risk Funds
- TM Daily Loans
- Early termination of multiple loans
- TM Daily Movement of Funds
- Party velocity of volume deposits and wire withdrawals
- TM Daily Unusual Behaviour
- Transactions in round amounts by risk classification
- High-risk deposits
- Transactions in round amounts
- Low total assets
- TM Daily Wires
- Activity dominated by wire transfers
- Activity dominated by wire transfers by risk classification
- TM Monthly Unusual Behaviour
- High account turnover
- High-velocity funds
- Large wire transfers relative to net worth
- TM Monthly Wires
- Increase in wire activity
A workaround is to use the ROUND() function on rule conditions that reference a column or an expression that uses decimal values.
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
SAS System | SAS Anti-Money Laundering | Linux for x64 | 8.3 | | Viya | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2023-06-21 12:20:12 |
Date Created: | 2022-05-26 13:10:40 |