Know when a customer's
risk picture changes
Ongoing monitoring re-checks the entities on your Monitoring List against frequently updated watchlists and shows only what changed on each run.
An additional MemberCheck service on a 12-month subscription
Changes found for you
Every run re-checks your monitored entities and flags what moved.
Only what changed
New Matches, Updated Entities and Removed Matches, with profiles side by side.
Every review on record
Review Status and decision history are kept with each changed profile.
What monitoring tells you
The three changes a run can find
Each monitoring scan compares the monitored entity with the watchlist data and reports one of three change types.
A profile now matches
A profile newly added to the watchlists now matches the monitored entity.
Watchlist profile
- Name
- Daniel Okafor
- Date of birth
- 17 Jun 1982
A matched profile changed
A profile already matched to the monitored entity has been updated.
Latest
- Role
- Minister for Transport
- Status
- Current
Previous
- Role
- Shadow Minister for Transport
- Status
- Former
A matched profile was removed
A profile previously matched to the monitored entity has been removed from the watchlists.
Watchlist profile
- Name
- Lena Fischer
- Status
- Removed
A run that finds nothing new is recorded as No Changes.
By default the Monitoring Results list shows only runs with changes; All monitoring scans shows every run.
Put a customer under watch
Add a customer to monitoring
Five steps take one customer from a scan with a Client ID to an entry on the Monitoring List.
Scan with a unique Client ID
Run an individual PEP and sanctions scan and assign the customer's unique Client ID during screening.
- Individual PEP and sanctions scan
- Client ID required
- Assigned during screening
Switch on the Monitor toggle
The scan results row carries a Monitor toggle; switch it on to add the entity to the Monitoring List.
- Monitor toggle in Scan Results
- On to monitor, Off to pause
- Only active entities are monitored
Confirm any replacement
Adding an entity when the same Client ID already exists on the list prompts you to confirm replacing it.
- Same Client ID detected
- Confirmation prompt
- Replace the earlier entry
See the entry on the Monitoring List
The entity appears on the Monitoring List with who added it and when, ready for the next run.
- Monitoring List entry
- Added By recorded
- Date Added recorded
Make it automatic for new scans
The organisation setting Update Monitoring List for New Individual Scan can add single, batch and API scans to the Monitoring List automatically.
- Update Monitoring List for New Individual Scan
- Single, batch and API scans
- Yes, No or User Defined
Scan with a unique Client ID. Run an individual PEP and sanctions scan and assign the customer's unique Client ID during screening.
Scan
Scan with a unique Client ID
Run an individual PEP and sanctions scan and assign the customer's unique Client ID during screening.
- Individual PEP and sanctions scan
- Client ID required
- Assigned during screening
Client ID
CRN-104287
Name
Sarah Mitchell
Date of birth
04 Mar 1979
Address
Chatswood NSW
Toggle
Switch on the Monitor toggle
The scan results row carries a Monitor toggle; switch it on to add the entity to the Monitoring List.
- Monitor toggle in Scan Results
- On to monitor, Off to pause
- Only active entities are monitored
Client ID
CRN-104287
Name
Sarah Mitchell
Date of birth
04 Mar 1979
Address
Chatswood NSW
Confirm
Confirm any replacement
Adding an entity when the same Client ID already exists on the list prompts you to confirm replacing it.
- Same Client ID detected
- Confirmation prompt
- Replace the earlier entry
Adding an entity when the same Client ID already exists on the list prompts you to confirm replacing it.
Client ID
CRN-104287
Name
Sarah Mitchell
List
See the entry on the Monitoring List
The entity appears on the Monitoring List with who added it and when, ready for the next run.
- Monitoring List entry
- Added By recorded
- Date Added recorded
Client ID
CRN-104287
Name
Sarah Mitchell
Added By
A. Chen
Date Added
02 Feb 2026
Automate
Make it automatic for new scans
The organisation setting Update Monitoring List for New Individual Scan can add single, batch and API scans to the Monitoring List automatically.
- Update Monitoring List for New Individual Scan
- Single, batch and API scans
- Yes, No or User Defined
Administration > Organisations
Update Monitoring List for New Individual Scan
Review what changed
Review a detected change
Six steps take one flagged change from a completed run to a recorded, reviewed decision.
The run completes and flags a change
The monitoring scan finishes and flags the change type, for example Updated Entities.
- Monitoring Status Completed
- Updated Entities flagged
- Differences since the last run
Your team is notified
Email notifications and the API callback URL can alert the team when a change is detected.
- Email off by default
- Callback URL option
- Change type and scan id
Open the Monitoring Results row
The row shows the run date, the counts, Monitoring Status and the optional Review Status.
- Run date and counts
- Monitoring Status
- Review Status
Compare the profiles side by side
Open the updated entity to see the latest profile on the left and the previous one on the right.
- Latest profile on the left
- Previous profile on the right
- What changed highlighted
Record the decision
Record a due diligence decision of Match, Not Sure or No Match with a risk level and a comment.
- Match, Not Sure or No Match
- Risk level High, Medium or Low
- Comment recorded
Mark the review complete
Flip the Review Completed switch once every changed profile is assessed and Review Status turns to Reviewed.
- Review Completed switch
- Review Status to Reviewed
- Decision history kept
The run completes and flags a change. The monitoring scan finishes and flags the change type, for example Updated Entities.
Run
The run completes and flags a change
The monitoring scan finishes and flags the change type, for example Updated Entities.
- Monitoring Status Completed
- Updated Entities flagged
- Differences since the last run
Date
13 Oct 2026
Monitored
412
New
2
Updated
1
Removed
0
Notify
Your team is notified
Email notifications and the API callback URL can alert the team when a change is detected.
- Email off by default
- Callback URL option
- Change type and scan id
Email notifications
Sarah Mitchell CRN-104287
API callback URL
https://yourdomain.com/api/notification?clientId=ID.1150&entityType=Individual&type=Updated&scanId=1022922
Results
Open the Monitoring Results row
The row shows the run date, the counts, Monitoring Status and the optional Review Status.
- Run date and counts
- Monitoring Status
- Review Status
Monitored
412
New
2
Updated
1
Removed
0
Monitored
412
New
0
Updated
0
Removed
1
Compare
Compare the profiles side by side
Open the updated entity to see the latest profile on the left and the previous one on the right.
- Latest profile on the left
- Previous profile on the right
- What changed highlighted
Latest
Role
Minister for Transport
Previous
Role
Shadow Minister for Transport
Decide
Record the decision
Record a due diligence decision of Match, Not Sure or No Match with a risk level and a comment.
- Match, Not Sure or No Match
- Risk level High, Medium or Low
- Comment recorded
Decision
Risk
Comment
New ministerial role, EDD required
Sarah Mitchell CRN-104287
Complete
Mark the review complete
Flip the Review Completed switch once every changed profile is assessed and Review Status turns to Reviewed.
- Review Completed switch
- Review Status to Reviewed
- Decision history kept
Set it up once
The Compliance Officer's Monitoring Settings
One panel decides how monitoring runs, notifies and reviews changes for the whole organisation.
Monitoring Settings
Turn on Monitoring
Monitoring Frequency
Preset per organisation and changed with your Account Manager
Enable email notifications of monitoring updates
Sends to the Compliance Officer or the Organisation Email. Off by default.
Enable callback URL notification of updates detected
Must be reachable by GET without authentication. Off by default.
Update Monitoring List for New Individual Scan
Update Monitoring List for New Corporate Scan
Matching Scope
Carried by monitoring itself, for Date of Birth, Gender, Nationality, ID Number and corporate Registration Number
Turn on ongoing monitoring results review
Adds the optional Review Status column to Monitoring Results
Whitelist Policy
Apply excludes profiles previously assessed as No Match from monitoring results and rescans
Frequency is preset
Monitoring Frequency is read-only, from Daily to Semi Annually, and is changed with your Account Manager.
Matching Scope stands alone
Monitoring has its own Matching Scope, independent of the scan setting, with no User Defined because no user is present.
Whitelist carries decisions
Set to Apply, matches previously classified No Match are excluded from monitoring results and rescans.
Review tracking is optional
Turning on results review adds Review Status and the Review Completed switch, so progress can be tracked.
Through the year
The subscription year at a glance
Monitoring runs all year at your organisation's frequency, with notices before renewal and a full rescreen on the renewal date.
- All year
Monitoring runs at your frequency
Monitoring scans re-check the active entities on the Monitoring List against the frequently updated watchlists.
- 3 months before renewal
First renewal notice
A pre-renewal notification arrives, usually three months before the renewal date.
- 1 month before renewal
Second renewal notice
A second pre-renewal notification arrives, usually one month before the renewal date.
- Before renewal
Tidy the Monitoring List
Pause entities with the Monitor toggle, remove them individually, or Bulk Remove up to 10,000 Client IDs at once.
- Renewal date
Every active entity is rescreened
On the renewal date all active entities are rescreened against the entire watchlist database, excluding custom watchlists.
- Renewal date
Results show Rescanned
Rescan results appear as Rescanned in Monitoring Results and via the Monitoring Rescans filter in Scan Results, reporting Match or No Match.
- All year
Monitoring runs at your frequency
Monitoring scans re-check the active entities on the Monitoring List against the frequently updated watchlists.
- 3 months before renewal
First renewal notice
A pre-renewal notification arrives, usually three months before the renewal date.
- 1 month before renewal
Second renewal notice
A second pre-renewal notification arrives, usually one month before the renewal date.
- Before renewal
Tidy the Monitoring List
Pause entities with the Monitor toggle, remove them individually, or Bulk Remove up to 10,000 Client IDs at once.
- Renewal date
Every active entity is rescreened
On the renewal date all active entities are rescreened against the entire watchlist database, excluding custom watchlists.
- Renewal date
Results show Rescanned
Rescan results appear as Rescanned in Monitoring Results and via the Monitoring Rescans filter in Scan Results, reporting Match or No Match.
The rescan counts towards the new subscription term's scan usage and monitoring continues.
Alerts where your team works
How your team hears about a change
Detected changes reach your team by email or an API callback URL, and system notifications can also go to Slack or Mattermost.
Email notifications
Email goes to the Compliance Officer or the Organisation Email when a change is detected, off by default.
API callback URL
A callback URL on your system receives the change details, reachable by GET without authentication.
System webhooks
The Notifications tab supports Slack and Mattermost webhooks for system notifications.
Callback example
https://yourdomain.com/api/notification?clientId=ID.1150&entityType=Individual&type=Updated&scanId=1022922
clientId = ID.1150
The customer's Client ID
entityType = Individual
Individual or Corporate
type = Updated
Added, Updated or Deleted
scanId = 1022922
The monitoring scan id
- GET
/api/v2/member-scans/single/{id}Retrieve an individual monitoring scan - GET
/api/v2/corp-scans/single/{id}Retrieve a corporate monitoring scan
Delivery and records
Reports, downloads and who can do what
Monitoring activity is reportable, downloadable and governed by the same roles as the rest of MemberCheck.
Monitoring
Ongoing monitoring activities by day, fortnight, week, month, quarter or semi-annual period, with numbers monitored and detected changes.
Monitoring Group Summary
Lowest, highest and average actively monitored entities in the period, and the items screened for the annual rescan.
Organisation Activity
Includes the annual Monitoring Rescan activities.
Download from Monitoring Results and Monitoring List
Export the view as a document for record keeping and audit.
Very large volumes may be CSV only
Roles and permissions
Access follows the same MemberCheck roles.
Related solutions
Cover every angle of customer risk
Ongoing monitoring sits alongside these MemberCheck checks across the customer lifecycle.
MemberCheck
PEP & Sanctions Screening
Screen customers at onboarding against global watchlist data, the layer monitoring re-checks over time.
Learn moreMemberCheck
Adverse Media Screening
Run a scan-time media search, separate from ongoing watchlist monitoring.
Learn moreMemberCheck
Configurable Matching
Set how closely names and details must match during screening.
Learn moreFAQ
Frequently asked questions
Answers to common questions about MemberCheck ongoing monitoring.
What does ongoing monitoring do?
It re-checks the entities on your Monitoring List against frequently updated watchlists on a regular basis and flags each change as a New Match, an Updated Entity or a Removed Match, with a No Changes result when nothing has moved.
Is monitoring included in my subscription?
Ongoing monitoring is an additional service on its own 12-month subscription with a pre-defined number of scans. Existing accounts activate it through their Account Manager or sales, and scans and frequency can be adjusted to your needs and regulatory requirements.
How often are my customers re-checked?
Your organisation has a preset Monitoring Frequency, from Daily to Semi Annually, shown in Monitoring Settings and adjusted through your Account Manager. The annual rescreening on the renewal date is automatic.
What is the difference between a Monitoring Scan and a Monitoring Rescan?
Monitoring Scans check monitored entities against the frequently updated watchlists and highlight changes. Monitoring Rescans run once a year on the renewal date against the entire watchlist database and report only Match or No Match.
How do I add a customer to monitoring?
Assign a unique Client ID during screening, then switch on the Monitor toggle in Scan Results, or let the organisation setting add single, batch and API scans to the Monitoring List automatically.
How will my team find out about changes?
Optionally by email to the Compliance Officer or the Organisation Email, and via an API callback URL that carries clientId, entityType, the change type and scanId.
Can I pause or remove customers from monitoring?
Pause any entity with its Monitor toggle, remove entities individually, or Bulk Remove up to 10,000 Client IDs at once. Removal never affects scan history, and entities can be re-added from Scan Results.
Keep every customer under review
See how MemberCheck ongoing monitoring fits your compliance workflow.