Client Screening & Ongoing Monitoring

The data it contains consists of sanctions and watchlists, PEP records relating to relatives and close associates, and wanted lists, all of which are obtained from more than 3,000 sources in over 220 countries. Two things are not included in it: adverse media screening and monitoring is a separate product that is incorporated into the same customer profile, and document and biometric identity verification is entirely outside the scope of Complead, being managed by your IDV provider.

With a synchronous search the median time is 50 ms, which is fast enough to be sent as part of your onboarding request without the need for a loading screen. Bulk screening is carried out asynchronously and a report is provided for each batch.

Certainly, most teams begin by doing so. You can load the existing database using CSV, via an API or through a live sync with your main system. Entity resolution first removes duplicate entries, so even if the database contains 1.2 million records, it does not result in 1.2 million reviews.

The lists are updated every 15 minutes and your base is continually checked against any changes. The rescreening depth is based on the customer's risk level rather than being carried out on a fixed monthly basis, so customers with a high risk level do not have to wait for the same schedule as those with a retail profile.

A name which has been cleared remains cleared until the original record is altered, so each time the list is updated the same false positive does not reappear. Likewise, delistings work in the same manner and end the alert by giving a reason code instead of leaving it open.

Right, the internal blacklists, the lists provided by the local regulators and the customer-specific watchlists are just as much a part of the global data as the rest of it, are assessed using the same methodology, and are included in the same audit record.

There are four points, and none of them involves a lower threshold; score bands for each customer segment, together with secondary identifiers such as date of birth and nationality, are scored along with the name, there is one profile per entity rather than one per list, and pattern level bulk clearing is carried out once a match pattern has been tuned.

It depends on how you define it. Once authorised, Nova auto deals with the deltas, for example in the case of a confirmed delisting or when a pattern which has already been cleared is repeated. In all other cases the matter is passed on to a person, and each automated action is logged together with the signals that led to it, so that the record indicates what decision was made and by whom.

The name of the alert, who was responsible for it, their decision and when it was made, the list version that was in effect at that time, and the source text associated with the designation; the information can be exported in the form of an evidence pack either per case or per period.

Sandbox keys are handed out right away and the first live call takes place within 15 minutes. Production integrations, including the setup of monitoring webhooks, are usually completed in the same week. However, if your policy prohibits the sending of names, screening can be carried out using hashed identifiers. Information regarding data residency, retention and subprocessors can be found in the Trust Center.