From a high level, rules analyze activity over a set period of time, while behavior logic looks at activity in comparison to a customer’s historical or expected activity. Ultimately, both rules and behavior logic rely on thresholds, but they are used somewhat differently. There is a place for both types of analytics in BSA/AML software, giving financial institutions the ability to apply strategies most appropriate to their risk profile and the suspicious activity being perpetrated.
Rules tend to fall into three different categories: volume or frequency, structuring, or velocity. These rules identify anomalies, such as an abnormally high volume of transactions or patterns of transactions falling within an institution’s internal threshold. With the right solution, financial institutions have the ability to customize their parameters to find suspicious activity that may be undetected. Many people within the industry may refer to rules as simplistic “if, then” logic that may create excess false positives. If an institution’s parameters are too rigid, it may miss fraudulent activity just below the threshold.
Behavior-based logic, as the name suggests, relies on the customer’s historical or expected behaviors. This logic looks for deviations from accepted peer norms or from the customer’s historical patterns. When used in conjunction with rules-based, financial institutions can identify potential suspicious activity and the number of false positives that come with rules. There are drawbacks to behavior logic when used exclusively. Behavior-based logic looks for fluctuations of activity. Therefore, if the customer’s activity has been fraudulent from day one, this logic will likely not catch these activities, as they are perceived as “normal” behaviors.
Both rules- and behavior-based transaction monitoring have their benefits and shortcomings, and while they are not perfect solutions when used exclusively, a multidimensional analytical approach can help BSA officers identify activity that is legitimately suspicious.