Transaction Selection Feature
Financial Institutions have regulatory requirements to protect the financial system against abuse. One way that they do this is through transaction monitoring. The transaction selector control is a new feature added to the 2025.09 release of SAS Anti-Money Laundering that enhances the transaction monitoring process. This feature enables users to search for transactions that are related to an object, without the need for resource-intensive indexing, and then replicate them as internal Visual Investigator objects. This enables users to link the transactions to other objects in the system. The purpose of this post is to show how to use this new transaction selection feature.
With the new transaction selection feature, administrators can now add a toolbar item to objects, such as a case, for users to search for transactions based on filter criteria and create a relationship between the object and transactions.
In this example, the transaction selector button is added to the Case entity.
Select any image to see a larger version.
Mobile users: To view the images, select the "Full" version at the bottom of the page.
Notice the set of text fields and drop-down menus that are used to define the search criteria and customize the search results. These fields can be configured by the solution administrator.
For instance, you can conduct a wide search for all transactions in Core or select the option to search for only related transactions. You can limit the search further to triggering transactions only and/or productive scenario fired events only. In addition, you can search based on amount or lookback period.
Now, if you don’t filter on any of these search fields, the system searches against all the transactions in the Core database, which can affect performance. By default, a maximum of 1,000 results are returned in a search, but this limit can be configured by the solution administrator.
Let’s say that I want to search for transactions with an amount of at least $500, where the primary account name is Alfonso Fiorilli, who is the customer involved in this case.
I enter these values in the corresponding fields. Then, I click Next.
On the Select Transactions tab, I can individually select transactions, or I can select all transactions.
I select the three transactions that seem related to this case and click Next. Then, I can add a comment.
After I click Submit, the system looks up the selected transactions in Core and replicates them as internal Visual Investigator objects. The replicated transactions are added to the Selected Transactions tab within the case.
If I were to do a global search, I now have the option to select AML Transaction filter type, showing the three transactions I selected.
Customers typically keep 13 to 18 months’ worth of transactions in the AML Core database. The new transaction selection function delivers a capability to search against all transactions in Core to aid in the investigation process. In the future, this feature will also enable transactions to be included in regulatory reports that require it, such as the goAML report. To learn more about this report, view this post by Melissa Oswald: SAS Anti-Money Laundering and goAML.
To learn more information about the transaction selection feature and our SAS Anti-Money Laundering solution in general, please visit https://support.sas.com/en/software/sas-anti-money-laundering-support.html.
Find more articles from SAS Global Enablement and Learning here.
