Changelog

3.8

Backoffice

Go!Scan

  • Ability to exclude/include sanction lists

  • Restrict screening for candidates having a birth date

  • Names variation: send multiple names variations and dob for a single customers

  • Bulk due diligence for alerts

Customers

  • Global customer search bar

  • Relations entity: define relation between entities and individuals, get a graph overview of your customers

  • Custom fields manager for customers and relations

  • Customers importation tool from CSV directly from the backoffice

  • Document manager: find all the documents related to a customer in a single page

General

  • New sessions, alerts, customers pages for a better experience and more clarity

  • Centralised webhooks and api management

Onboarding

  • Minor improvements on mobile and desktop

3.7

Name Search

Name Search now supports sanction lists (SAN) filter and Special Interest (SI) types filter.

The other enhancement concerns the Relatives or Close Associates (RCA): if you indicated that you are not interested in specific PEP roles, it will also hide the RCA of theses PEPs. Same for SI and SAN.

Click to get more about the Name Search

  • We added a penalty of up to 5% for name matching when names are inverted or when names are missing from the watchlist record (eg. “James Doe” will still match with a “Doe” where no first name exists from our watchlists but will get a penalty of 5%, where “Doe James” will also match but with a smaller penalty).

  • Names inversion are now supported by default, also typos in date of birth or partial date of birth.

  • Company Name Search now allows potentially missing words in result: eg. “Le Mercury AG” will match “Mercury”. Additional words are not ignored and participate in the overall score.

Backoffice

Our backoffice has been rebooted to provide you with the best User experience.

Click to get more about the new backoffice

  • Dark/Light mode for late working agents

  • Global customers search bar

  • New developers API keys management page

  • Clearer terminology on alerts and risks statuses



Still need help?

Contact us

Algoreg Guides