Skip to main content

Bulk customer status change

Update the status of multiple persons at once by uploading a CSV file. This is useful when you need to change statuses for a large number of persons without updating each record individually.

Please note, that this feature is available only to users with the CUSTOMER_ADMIN role.

Step 1: Prepare the CSV file

To change persons' statuses in bulk, you'll need to prepare a CSV file with exactly two columns:

Column name

Description

person_id

The ID of the person

status

The new status to assign

Make sure the column headers match these names exactly (lowercase, no extra spaces).

Finding person IDs: If you don't have your customers' IDs readily available, you can retrieve them from Entity Search. Export your persons from there, and the id column in the exported file contains the values you need. For more details on person IDs and other person data fields, see Person data requirements.

Available statuses: NEW, MONITORING, REVIEWED, SUSPENDED, TERMINATED, and TERMINATED_AND_REPORTED. Status values must be in uppercase and match exactly as shown.

Example:

person_id

status

P00123

REVIEWED

P00124

SUSPENDED

P00125

TERMINATED


Step 2: Upload the file

  1. In the UI, go to Data Upload.

  2. Drag or browse and choose your prepared CSV.

  3. Select Person status as the Data type.

  4. Choose the separator your file uses under Separate values using (comma is the default and recommended).

  5. Check the Data preview to make sure your columns are read correctly.

  6. Click Upload.


Step 3: Wait for processing

Once the file is processed, the status of each person listed in the file will be updated to the value in the status column. No other person attributes are affected, only the status changes.


Bulk status change audit trail

To review bulk status change activity audit trail, go to the Universal tab in the Head of Compliance dashboard. It shows who initiated each bulk status change, when, how many records were affected, the source file used, and a sample of updated entities.

Did this answer your question?