{"article":{"id":40389610533911,"url":"https://plaid.zendesk.com/api/v2/help_center/en-us/articles/40389610533911.json","html_url":"https://support.plaid.com/hc/en-us/articles/40389610533911-How-does-Monitor-support-ongoing-monitoring-requirements","author_id":1511728400882,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":40389574655511,"created_at":"2026-05-11T17:48:23Z","updated_at":"2026-06-01T02:00:08Z","name":"How does Monitor support ongoing monitoring requirements?","title":"How does Monitor support ongoing monitoring requirements?","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-06-01T02:00:08Z","user_segment_id":null,"permission_group_id":1121794,"content_tag_ids":[],"label_names":[],"body":"

You can toggle on Ongoing Monitoring to allow Monitor to rescan your entire user base daily against updated watchlists — meeting regulatory expectations for continuous screening without manual batch workflows. This means that if a user's name matches a newly added sanctions entry, they will typically be flagged within the next daily rescan cycle (within 24 hours of the list update being ingested by Plaid).

\n

\"\"

\n

Any new hits surface in the dashboard and via webhook, with a full audit trail of each status change for examiner or auditor review.

\n

If Ongoing Monitoring is not enabled, you will need to create a new screening manually to check a user against updated lists.

\n

If you want to stop rescanning a user, move the user to a program that has Ongoing Monitoring disabled. Call /watchlist_screening/individual/update with the watchlist_screening_id and the watchlist_program_id of a non-rescanning program.

\n

Plaid recommends maintaining at least two programs: one with rescanning enabled for active customers, and one with rescanning disabled for inactive or offboarded customers.

","user_segment_ids":[]}}