For compliance and engineering teams that treat no-hits as clears
When does a no-hit quietly become a false clear?
A false positive wastes an analyst's time. A false clear, a no-hit treated as a clearance when the screen was incomplete, is the one that reaches a customer. This page works through the scenarios where a clear is not defensible, and sets out the principle behind them: in EU sanctions law the prohibition is strict, so a screen that did not run, ran against the wrong list, or capped its own candidates does not cure anything.
Primary sources
- Council Regulation (EU) No 269/2014, Article 2, asset-freeze prohibition
Making funds or economic resources available to a listed person is prohibited outright. The obligation does not depend on whether a screen succeeded, so an incomplete or failed check does not turn a prohibited party into a cleared one.
- EBA/GL/2024/14, internal controls for restrictive measures
EBA guidelines (applicable from 30 December 2025) on the controls financial institutions need for screening: current-list ingestion, data quality, completeness, and disciplined alert handling rather than silent dismissal.
- Regulation (EU) 2024/886, Article 5d, screen current lists
The instant-payments obligation to re-verify immediately on a new or amended listing is the primary-law hook for screening against current, not stale, lists.
The principle: an unscreened check is not a clear
No single EU article says the words 'do not treat an unscreened check as clear.' The principle is derived. The asset-freeze prohibition is strict and does not turn on whether you screened; the EBA control guidelines expect screening against complete, current lists with alerts resolved rather than ignored. Put together, a no-hit is only meaningful if the screen behind it was actually complete.
So the useful question is never just 'did anything match?' It is 'was this screen complete enough that a no-hit means something?' The scenarios below are the cases where it is not.
Worked scenarios
| Scenario | Why the no-hit is not a clear |
|---|---|
| An in-scope source was unavailable at screening time | Coverage is partial, an unanswered list cannot support a clear. The gap is on the record, not hidden. |
| The list version screened was stale; a listing was added after | The screen ran against yesterday's world. A no-hit against a superseded list is not a current result. |
| An exact-only lookup was used | Exact matching misses aliases, transliterations and near variants. It is a narrow lookup, not a recall-oriented screen that can clear. |
| The candidate set was capped or truncated | The screen stopped early. A no-hit from an incomplete candidate set is not exhaustive. |
| A non-Latin name normalized to an empty query | Nothing was actually screened. The safe outcome is review, never a clear. |
| Ownership was never resolved (OFAC 50% Rule) | A name-level no-hit says nothing about who owns the party. Missing ownership data is unresolved, not clear. |
How to make a clear defensible
- 1Record coverage on every result, which sources answered, which were stale, which were unavailable or excluded.
- 2Fail closed: when an in-scope source is unavailable, return partial coverage and withhold clearance eligibility rather than presenting a clean-looking no-hit.
- 3Keep the candidate-set completeness and the screening mode on the record, so a capped or exact-only run cannot masquerade as a full screen.
- 4Route every incomplete case to review, and validate the resulting record against the open reference so a false clear cannot leave the building unnoticed.
Limitations
- The 'unscreened is not clear' rule is a derived compliance principle, drawn from strict-liability asset-freeze law plus EBA control guidance, not a single verbatim regulatory sentence. Treat it as principle, not quotation.
- Even a complete screen is bounded by list quality, matching and transliteration limits, and the ownership-data opacity of the 50 Percent Rule. Completeness reduces false clears; it does not eliminate all risk.
- This page is an implementation reference, not legal advice. Whether a specific result may be treated as clear is your decision under your policy.
Build the evidence, not just the alert
Questions
Isn't a no-hit obviously a clear?
Only if the screen behind it was complete. If a source was down, the list was stale, the mode was exact-only, or the candidate set was capped, the no-hit reflects an incomplete screen, not the absence of risk.
How can I check my own records for false clears?
Run a decision record through the Clearance Validator. It recomputes eligibility from the coverage, mode, candidate completeness and evidence, and flags a record that asserts a clear it has not earned.
What should happen when a source is unavailable?
Coverage should read partial and clearance eligibility should be withheld until the source answers. An unavailable list must never be silently treated as returning no matches.
This page is an implementation reference for engineering and compliance teams. It is not legal advice and does not certify any regulatory outcome. Regulatory obligations, their interpretation, and the decision to treat any result as clear remain yours. Verifex supports the workflow and preserves the evidence; it does not make the compliance decision.