UPDATE V8.22
What's new
InScope-AML version 8.22 will start being rolled out to our cloud environments in October 2026. On-premise environments will receive these updates shortly after and may be updated along with previous versions.
Feature Updates
Searches v2: Improved Handling of Updated Hits
Note: This update applies only to clients using Searches v2 and does not apply to the legacy Searches v1.
This release makes it easier to review hits that are updated after they were first raised. When a hit is updated, users can now see straight away how it was previously handled and exactly what has changed.
This removes the need to re-evaluate updated hits from scratch and allows previously reviewed hits to be resolved much more promptly.
Status tags on updated hits
When an existing hit receives an update, a tag now appears next to it showing how it stood before the update:
- Updated: shown when the hit was still open before the update. The tag includes the number of changes received.
- Previously False Positive: shown when a hit previously resolved as a false positive is reopened following an update. The hit returns to an Open status, and the number of changes is displayed.
- Previously True Positive: shown when a hit previously resolved as a true positive is reopened following an update. The hit returns to an Open status, and the number of changes is displayed.
These tags also apply to discarded hits. A hit may be discarded because it no longer meets the search parameter criteria, or because the service provider has removed the profile from its dataset under its methodology. If the discarded hit had previously been resolved, it keeps its Previously True Positive or Previously False Positive tag. Hits that were still open when discarded do not show a tag.

Summary of changes
Each updated hit now includes a summary of changes. The total number of changes are now shown on the hit summary. A detailed breakdown then lists what was added, removed or modified in the profile since the previous update, such as match scores, source links and profile information. Users no longer need to compare versions of a profile manually.

Removing screening classifications from discarded true positives
True positive hits may have screening classifications attached to them. If such a hit is later discarded, users now see an option to remove all screening classifications linked to that hit.

Minor Changes
Version 8.22 introduces a number of minor additions and improvements aimed at streamlining stakeholder requirements for specific company types, enhancing the detail captured in the screening policy document, and extending reporting within Searches v2.
Mandatory stakeholder warnings removed for companies In Dissolution
Companies with the status In Dissolution no longer show warnings for stakeholders set as mandatory.
Screening parameters added to the screening policy document
The screening policy document now includes the screening parameters configured in the system. These include the reporting thresholds, the date of birth range, the matching algorithm in use (eg. fuzzy or strict), as well as other configured settings.
New legal forms for companies
Three new legal forms are now available for companies: Branch, Overseas Company and Overseas Branch. When any of these is selected, mandatory stakeholder rules do not apply, and identifying shareholders or populating a structure chart is not a mandatory requirement.
Searches v2 printout now includes profile history
The Searches v2 printout previously contained the overview and match results only. It now also includes the history of the entity profile, covering all recorded activity except daily monitoring entries.
Bug Fixes
- Delivery channels not automatically screened: Entity profiles listed as delivery channels (intermediaries) were not being screened automatically while active. Active delivery channels are now placed under ongoing monitoring.
- Mandatory stakeholder warnings not clearing: Warnings for mandatory stakeholders remained after the mandatory requirement was removed. They now clear automatically.
- Searches v2 AI searches failing to create: Some AI searches failed to be created. A retry button now lets users trigger the search again manually.
- Risk pillars overflowing in the PDF client report: Risk pillars with many contributing parameters ran off the page in the PDF client report. A page break is now applied within the pillar so that it continues on the next page.

InScope users on our cloud-hosted environment now have access to this minor version of InScope as an upgrade to version 8.0 released last month. This

Information about new features included in version 8.0 that is being rolled out to our clients throughout January/February 2022.

New features REQ 2021 changes ‘View reports’ Permission Change in risk assessments sensitivity Account Numbers now mandatory based on rules Segments including corporate owners Bug

Back to Product Updates What’s new StartKYC credit balance counter We have added a counter under the settings menu of InScope-AML, to keep a track