Clear several screening hits at once
Clear a group of obvious false-positive screening hits in one action, with four-eyes applied hit by hit.
tocOn this page
When a common name produces a run of hits that are clearly not your customer, you can clear them together instead of one by one. You give one reason code and one narrative for the group, and FlowSentry still applies your institution's four-eyes policy to every hit individually.
Before you start
- You need a role that reviews screening hits: Analyst, Senior analyst, MLRO or Deputy MLRO.
- Only hits in the Potential status can be bulk cleared.
- Check each hit before you tick it. Bulk clearing saves clicks, not judgement.
Clear hits in bulk
- Open Hits in the Screening module, or go to
/screening. This is the Screening workbench. - Choose the Open view.
- Narrow the list so it contains only the hits you mean to clear. Useful tools:
- Category (for example Sanctions, PEP or Internal), List and Status filters
- the search box, "Search subject, entry or list"
- the order: Risk (TFS first), Highest score or Oldest first.
- Open any hit you are unsure of and compare the subject with the list entry side by side. Come back to the queue when you are satisfied.
- Tick the Potential hits you want to clear.
- Select Clear as false positive.
- Choose one false-positive reason code and write a narrative that explains why these hits are not the listed party.
- Select Clear hits.
What happens next
The result tells you how many hits were:
| Result | What it means |
|---|---|
| Cleared | Cleared at once. The clear is remembered for that subject and list entry, and some are sampled for QA. |
| Sent to a checker | The hit became Clear proposed and now waits for a second person. |
| Skipped | The hit could not be cleared in this action, for example because it was no longer Potential. |
A hit is sent to a checker instead of being cleared at once when:
- it is on a statutory targeted financial sanctions (TFS) list, such as the UN Security Council list or Kenya's domestic designations, or
- its score is above the threshold set in your institution's Four-eyes policy (
/screening/policy).
Note: True matches and clears on statutory lists always need two people. Bulk clearing never changes that.
For the checker
A Senior analyst, MLRO, Deputy MLRO or Screening checker reviews each Clear proposed hit, normally from the Awaiting a checker view, and selects Approve clear. This needs a fresh second factor (step-up). You can never approve a clear you proposed yourself.
A clear is remembered
Once a hit is cleared, FlowSentry does not raise it again for the same subject and list entry unless one of them changes. If the list entry is later updated or removed, the hit page says so: "The list entry has changed (or been removed) since this hit was raised."
Tips
- Write a narrative a reviewer or examiner can follow without opening each hit, such as which attributes differ (date of birth, nationality, identifier, type).
- If one hit in a group looks different, leave it unticked and review it on its own page.
- If a known customer keeps matching the same list entry, consider a good-guy exclusion instead of clearing repeatedly.
Warning: Never bulk clear a hit you have not looked at. Every clear is recorded under your name in the audit trail.