On-Demand Customer Rescreening

Last updated: April 7, 2026

Introducing On-Demand Customer Rescreening 🚀

We're excited to introduce the new On-Demand Customer Rescreening feature, which allows you to instantly check for changes in your customers' risk profiles as and when you need to. 

 

What is On-Demand Customer Rescreening?

This feature provides a dedicated API endpoint that allows you to trigger an immediate rescreening of a specific customer against all applicable watchlists and profiles in the ComplyAdvantage database. T

 

Why is This Feature Important? (Impact)

Financial institutions must continuously monitor their customers' risk profiles. Previously, when you updated a customer's record (e.g., new identity info, an account becoming active), you would have to wait for the next scheduled daily monitoring run to see if that change impacted the screening results.

This new on-demand rescreening feature eliminates that delay, enabling you to:

  • Instantly Assess Risk: Immediately check for changes in screening results when a customer's information is updated on your side.

  • Enhance Operational Efficiency: Get real-time feedback on your customer data changes rather than waiting for a batch job.

How to Use On-Demand Customer Rescreening

This feature is available via a new API request, which is ideal for integration into your internal workflows.

When to Use It

You should trigger an on-demand rescreening in scenarios where a change to your customer's data might affect their risk profile, such as:

  • When a customer's key details are updated.

  • When a previously dormant client becomes active and monitoring is switched back on.

API Requirements & Response

To initiate an on-demand rescreen, you will need to call the dedicated API endpoint:

RequirementDetail

Prerequisites

The customer must have already been screened originally.

API Endpoint

POST /customer/{customer_id}/rescreen

Required Parameter

You must provide the Customer ID of the customer you wish to rescreen.

Upon calling the API, the system will rescreen the customer and check for changes in the screening results. The API will return the following key information in the workflow response:

FieldDescriptionPossible Values for "Alerting Impact"

Workflow ID

A unique identifier for the rescreening job.

N/A

Workflow Type

The type of workflow that was executed.

N/A

Alerting Impact

Indicates the outcome of the rescreening. This serves as your real-time notification.

New case created (Changes were detected) * No changes detected (No relevant changes were found)

System Behavior & Audit Trail

The system will respond to the rescreening results as follows:

  • Changes Detected (e.g., New case created): If relevant changes are detected (e.g., added and updated profiles), a new monitoring alert/case will be generated, clearly showing the changes in screening results. The user will be made aware of this change.

  • No Changes Detected (e.g., No changes detected): If no relevant changes in screening results are detected, the system will follow the current behavior and the client will be made aware there are no changes.

All rescreen events are fully tracked:

  • The event will be saved in the audit log.

  • It will show if changes were detected 

  • It will be visible in the customer audit viewÂ