New ID_Check v2.6.11 — a new ID recognition engine improves OCR for Korean documents, PII masking is now set from the dashboard, and submissions can be searched by custom fields (cf1–cf3). See what's new →
New ID_Check v2.6.11 — a new ID recognition engine improves OCR for Korean documents, PII masking is now set from the dashboard, and submissions can be searched by custom fields (cf1–cf3). See what's new →
Learn about the ongoing monitoring service that continuously re-checks registered users to detect changes in sanctions, PEP, reputation risks, etc.
ARGOS Ongoing Monitoring is a service that continuously re-checks users (submissions) registered by customers and sends notifications when changes occur in Sanctions, PEP, Regulatory Enforcement Lists, Reputation Risk Exposure (RRE), and Person of Interest (POI), etc.
Understanding Ongoing Monitoring is easier when divided into the following 3 units:
Worklist
A workspace for setting ongoing monitoring policies and registering monitoring targets. You can manage multiple Worklists within one Project.
Monitor Record
User information registered as monitoring targets. ARGOS performs regular screening on these Monitor Records.
Matches
Match results that appear when regular screening is performed on monitoring targets. Compliance operations teams perform AML work by reviewing these Match results.
Separate registration based on identity information
3
Periodic Screening & Open Matching
Goal: Perform matching on registered monitoring targets to determine “Match information requiring administrator review.”ARGOS re-screens all targets according to the set cycle, and when data changes are detected, creates alerts as Open matches.
4
Match Review (Judgment·Comment)
Goal: Determine “final match result” through administrator review of matches (OPEN).Open matches quickly verify facts and then judge as True Positive or False Positive.
Goal: Determine “re-execution process” based on administrator review results.ARGOS re-evaluates past judgments based on profile updates or score changes.
When there is no existing eKYC submission, you can incorporate externally collected targets into monitoring.A new submission ID is created and the entered identity information is registered as an Approved eKYC.
You can register as a new Record using an existing submission ID.Used when dividing eKYC completers into policy·segment-based worklists for monitoring, or for backfill of past data.
Registration RequirementsName, date of birth, gender, nationality all 4 must be present to register.
Operation Tips
Start daily operations from Match Open view for a clear queue.
Maintain tags with at least 3 axes: risk/country/reason. (e.g., risk:pep + country:ID + fp:dob-typo)
To manage Open volume below 80% of daily processing capacity, adjust both Worklist Threshold and Birthdate Matching together.
Match List is a screen that shows all match results that occur when a specific user matches lists such as sanctions, PEP, regulatory enforcement, reputation risk, POI, etc. in ARGOS Ongoing Monitoring.
Matches indicate “similarity possibility,” so compliance officer review is mandatory.
Indicates that the monitoring target showed similarity above a certain level when compared with the list, resulting in a review pending status.Open status means review is needed, so it is important to start review immediately.
✅ True Positive (TP)
Review confirmed that the target is exactly the matched person/institution.
Execute immediate actions such as offboarding, transaction restrictions, enhanced screening
Must record initials, date, reason, and evidence links in memo
❌ False Positive (FP)
Review confirmed that the match is a different person/institution.
Score may be high but decisively different target
Recording mismatch basis in memo is useful for future audit response and system Threshold adjustment
🗑️ Discarded
Indicates that the match is no longer a meaningful review target.
List was updated and item became unnecessary, or
Policy criteria changed and item was excluded from match conditions
Remove unnecessary items from queue to maintain efficient workflow
How do I prevent duplicate registration when operating multiple Worklists?
Since Worklists operate independently, the same user can enter multiple Worklists. To prevent this, establish a 1:1 mapping rule based on USER ID, and if purposes overlap, it’s good to merge Worklists or adjust filters.
If I lower the Threshold, alerts will be too many. What should I do when personnel is insufficient?
It’s effective to raise the Threshold to reduce alert numbers, or separate low-risk groups into separate Worklists and check at low frequency only. If alerts accumulate to a level where SLA cannot be maintained, queue management reflecting priority (Sanctions > PEP > Reputation) is needed.
Is a match score of 100 always True Positive?
No. Scores only show similarity possibility, and final judgment requires operator review. For example, same names with the same nationality may be False Positive.
Can a match reopen after being judged as False Positive?
Yes. Past False Positives can also reopen (Open) when match scores rise again or data is updated. In this case, review again.
Do I have to write memos?
Yes. Memo writing is recommended for all judgments. This is an essential procedure for internal audit·regulatory audit response.