by Matt Rizzo

February 17, 2022

Version 8.1

InScope-AML users on our cloud-hosted environment now have access to this minor version of InScope-AML as an upgrade to version 8.0 released last month. This version together with version 8.0 will be released to on-premise customers over the course of the next few weeks.


Filtering and Exporting Process Log

InScope-AML runs a number of background processes (previously known as workflows) on a regular basis. Amongst other things, these processes drive the warnings on the dashboard by determining if changes made to the system (e.g. to an entity or to a rule) result in missing information or risk assessments being overdue. These background processes are also key to check the client base against external sources (e.g. UN/EU sanction checks). As from this release, the log of all processes shown on the dashboard can now be filtered by name or process type and exported to Excel.

One of the most common uses for generating this report would be to retrieve a log of every time the system ran external searches (e.g. sanction checks) against an individual or against the whole client base. For example, the screenshot below shows the Processes filtered by “Update Entity External Searches” which returns a log of all the instances where the external searches workflow was run against an individual entity or against the whole database.

Ignore Instance of Recurring Task

If your InScope-AML environment is configured to use the Tasks module, you will know that the system generates periodic tasks for each entity and only generates the next task once the current task is completed. There may be cases where the current instance of the recurrence needs to be skipped. InScope-AML now supports this by offering a “Mark as Ignored” button next to the “Mark as Done” button. Once a task is ignored, the task log will mark the status of the instance of the task as “Ignored” and then generate the next task based on the specific task frequency. An example of this is shown below.

Support for Company Owning Shares in Itself

Prior to this version, users could create structure charts that included cross-shareholding providing that within the structure no company held direct shares in itself. This feature has now been enhanced such that a company can now directly hold some shares in itself. Note that as with previous versions of InScope-AML, this concept of cross-shareholding is only supported if the number of shares is small. The system does not support having a company hold a large percentage of shares in itself since this would cause the system to fail when generating the beneficial ownership percentages.

Bug Fixes

Share this...

Facebook logo Pinterest logo X (formerly Twitter) logo LinkedIn logo

You May Also Like

by InScope-AML

June 18, 2024

Juggling through AML Compliance