Version 8.16

Generate Client Reports on Entity Profiles

A report functionality was added on the Overview screen of an entity’s profile, so users can extract a report which includes:

• Basic details
• Last risk assessment summary
• Custom fields and checklists
• Country fields
• Roles of entities and individuals in the client’s profile

The report will also include all of the above information for any connection linked with the client and will be exported in the same report.

Customisable stakeholder options

New stakeholder options have been added for users to select when assigning connections to entities in the system. Similarly to the already available option ‘Add Class of Beneficiaries’, users will be able to add other stakeholders as Settlors, Protectors, and Trustees by name only, without having to connect an existing entity from the system or create a new profile. These options have been added to cater for scenarios where structures contain complex cross-shareholding instances. This will allow users to be able to add and identify a stakeholder just by its name.

New Segment Filter Conditions for Screening *

A new filter condition for segment creation was added to the system, pertaining to the status of different potential hits generated from the ongoing monitoring process.. This new feature enables users to filter segments of entities from their database according to the status of existing hits in the system, as per below:

• Open;
• TRUE Positive;
• FALSE Positive;
• Review – TRUE Positive;
• Review – FALSE Positive;
• Discarded.

Self Service Comment Section

A comment section was added to the Self Service, which pops up when users are sending out a new request, so personalized notes can be added, similarly to what happens when users wish to send back a reviewed request. The notes added in such comment section will be included in the email message that gets sent to the Self Service Portal User.

Onboarding and Occasional Transactions Menu

A new column with the services to be provided has been added, as well as the option to export to excel the list of entities with such Relationship Status.

Minor Changes

There have also been a small number of minor changes to the system, such as:

1. Changes in the default titles of Email Templates for the invitation to the system, registration to the Self Service Portal and invoice requests.

2. Screening classifications can be set as mandatory when users mark a hit as a True Positive. This feature can only be enabled on request through our Support channel. *

3. Printing functionality was added to the One-Time Searches screen similarly to the printing option from the regular search screen. *

4. A new setting option to disallow users from entering characters other than alphanumeric, when populating ID numbers, has been added. This feature can only be enabled on request through our Support channel.

5. The user permission to view reports has now been extended to include reports generated through segments in the system.

6. The option to enable Self Service Portal users to upload Identification Documents through the portal has been moved to the Security tab within the Manage Self Service menu (pathway: Settings > Manage Self Service > Security).

7. The option to delete a Self Service Portal user which was added to the system is now allowed. Before, such users could only have their details edited and not deleted

8. With Version 8.16, clients now have the ability to specify how StartKYC updates affect the External Search creation logic. This feature can only be enabled on request by our Support team and only applies to clients with the older version of screening (v1).

   Historically, an External Search is created in InScope if one of the following occurs:

   • An entity receives new StartKYC results.
   • An entity receives updates to existing StartKYC results.
   • An entity receives both new StartKYC results as well as updates to existing StartKYC results.

   This new feature will now allow clients to instruct InScope-AML to only create new External Searches if new StartKYC results are received. This will cause InScope-AML to not create a new External Search record if only updates to existing StartKYC results are received.

   It’s important to note that if the client’s Search Profile makes use of multiple Search Providers, then a new External Search might still be created if the relevant conditions for opening an External Search are achieved for a Search Provider other than StartKYC.

9. Generic errors in the system were tailored to be more specific so users can easily understand what the issue is, for the following situations:

   • When creating a new country category, if the description was too long, the system would not allow users to save it and would generate a generic error. Now, the system displays an error which identifies the issue, so the users know what needs to be corrected before saving;
   • When adding countries in the related country types (e.g. Trading in), if a country was separately added and then n user would try to add a group of countries (e.g. European countries), to the same related country type, which would include the country already added, the system would not allow it and would produce a generic error. Now, the system generates a warning identifying the issue and instructing the user on how to proceed;
   • When adding an ID number in the system, if said ID had already been assigned to an individual in the system, to avoid duplicates, the user would not be able to proceed, and a generic error would be generated. Now, the system prompts a warning that indicates the ID number is already in use by another entity in the system.

Bug Fixes

• In the Warnings menu, when users were filtering by text to search for a specific set of warnings, words that were only included in the warning message, and not in the warning itself, would not retrieve results. Filtering by text exclusive of warnings messages is now possible.
• When exporting segments’ report to excel, the leading zeros in the identification and registration numbers of individuals and companies respectively, were automatically removed. This issue has been fixed so the data being exported matches the data in the system.
• There was a waiting time for users to be able to login into the system after another user logged out. This waiting period has been fixed so users can immediately access InScope-AML after another user logs out.
• The list of Nationalities in the system had some grammar incorrections, that have now been corrected.
• When users were switching the field ‘Document has Expiry Date’ from ‘Yes’ to ‘No’, since an expiry date has been previously provided, the system was retrieving an error and users would not be able to save the change of settings. This has been fixed, so when a user changes that setting from ‘Yes’ to ‘No’, the system automatically clears the expiry date field, and no error comes up so the user can save the changed settings.
• For client with the older version of screening (v1), a heavy workload during the screening process would cause the system to fail to properly close some External Searches, leaving them with the In Progress status. The bug has now been solved so the UI is no longer displaying older In Progress results.
• When the name of a risk pillar was changed/updated, the old name was also being updated in previously conducted CRAs. With this release, changing the pillar name no longer affects past CRAs and the pillar name as it was at the time when the CRA was carried out is retained.
• The Main Risk Category in the Countries screen, should have been displaying the highest risk category where a specific country falls in. However country categories with an override were not being considered as higher risk if a country also belonged to another country category with the same score. This has been fixed so, between two categories with the same risk score, the one with an override is displayed as the Main Risk Category.
• For clients with the old services screen, on restoring etities entities from the recycle bin, the relationship status would be changed to onboarding and services were getting removed by the system. This issue has been corrected so entities that are restored keep the original data from when they were deleted.
• For Self Service Portal clients, custom fields that become mandatory through triggers from other custom fields’ responses were not being marked as required when the users were submitting the request for revision, unless they would save the answers with triggers first. Now, if Self Service Portal users select an answer with a trigger, the applicable custom fields will be marked as mandatory without having to save the answers first.
• An option to select an individual’s nationality as unknown has been added, similarly to what was already in place for the country of birth and residence but was not made available at the time for nationality.

* This feature update does not apply to all clients. It depends on the screening provider chosen.