Conflict creation enhancements: We have updated the KYC and transaction monitoring rule triggers for handling conflicting values until resolution. For KYC rules, this means that conflicting data points will make rules trigger for all values. For example, if an individual’s establishment data indicates residence in both Sweden and Denmark, pings will be created for both values. For transaction monitoring rules, triggers will now use the most conservative value. For instance, if a KYC Form declares an expected monthly outgoing volume of 1,000 SEK in one submission and 10,000 SEK in another, the rule will trigger based on the lower value of 1,000 SEK until conflict has been resolved. 

Transaction types table: We have introduced a new table that allows you to view multiple configured transaction types at the same time, providing increased oversight. You can also select which values to display in graphs for enhanced analysis. Please see attached video illustrating this. 

Processing volume graphs: Processed volume can now be visualized in the transaction analysis view, available in both table and graph formats.

KYC Form supports transaction types: KYC Forms now support specifying different transaction types. For example, you can configure KYC Forms to ask about specific behaviors, such as the expected volume of Swish payments. This data can then be utilized in transaction monitoring and transaction analysis.

Updated Sanction view and AdverseMedia release: The sanction hit view has been updated to match the structure of the PEP view. Additionally, we have released an Adverse Media feature, allowing you to view and fetch adverse media data directly from the interface.

Data warehouse: We now offer the ability to set up client data in a data warehouse within our current subprovider, AWS. This feature enables:

• Faster and easier creation of custom reports.
• Integration with Power BI tools like Quicksight for client-specific dashboards, graphs, and tables.