Screening in the Panel
You can screen without calling the API. The screens under Sanction in the panel run the same screening as the Sanctions Screening API and show the result with the same fields.
Screens in the panel
| Screen | What it shows |
|---|---|
| Sanction Overview | Your organization's monitoring, case, alert and screening counts; recent screenings |
| Name Screening | Person or organization screening; risk domain selection, matches, coverage status and the PDF report |
| Wallet Screening | Crypto wallet address screening; list hits and your own list's hits in separate sections |
| Public Procurement | Public procurement ban screening; the debarment lists searched and the coverage note |
| Screening History | Earlier screenings |
Required panel permission: sanction:view_results.
Overview
The counters on Sanction Overview are read from your organization's real data:
| Counter | What it counts |
|---|---|
| Active Monitoring | Your customers under ongoing monitoring |
| Open Cases | Your open cases and how many of them are escalated |
| Alert Inbox | Your open alerts |
| Screenings Today | Screenings run today and how many of them were blocked |
Recent Screenings shows your organization's five most recent screenings. When a counter cannot be read, its tile says "Data unavailable"; it never shows zero instead.
Name screening
Risk domain selection
Use Risk domains on the form to narrow the screening. With every domain selected (Select all) the screening covers every risk domain; at least one domain must be selected. What the domains mean: Risk domains.
Result
- Merged match: a person or organization on several lists shows up as one match; every list it is on is listed on its own row with its program and sub-list.
- List publication: the result shows the revision of the list publication the screening read (List publication: revision …).
- Coverage warning: when coverage is not complete, a warning appears above the result:
- Incomplete coverage — some requested risk domains are not served by any list in this publication; the warning names the domains not screened. No match is not a clean result for those domains.
- Degraded screening — records with spelling variations may have been missed; run the screening again.
- Screening could not be completed: when screening could not run, the result is never shown as "no match"; if you see this warning, run the screening again.
Wallet screening
The result is shown in two separate sections:
- Listed parties holding this address — risk domain, the address as the list writes it and its network, every list the party is on.
- Your wallet list and crypto intelligence — hits from your own list and from crypto intelligence.
How the address is compared (letter case rules): Wallet screening.
Public procurement ban screening
The result shows the debarment lists searched and the lists a hit appears on.
The result carries a "Turkish public procurement bans (KİK) were not screened" warning: the KİK list has no official machine-readable source, so it is not part of the screening. No match is not a clean result for public procurement bans in Türkiye; you need to check EKAP separately.
PDF screening report
The PDF Report button on a name screening result downloads that screening's audit report. The report contains these sections:
| Section | Contents |
|---|---|
| Screening | Screening time, searched name, screening scope, channel, your own record id and the decision |
| List publication and coverage | The list publication read and its revision, coverage status, screened and unscreened risk domains, evidence record id |
| Matches | Each match with the lists it appears on and their listing details |
| Dataset provenance | Versions and publication dates of the lists the screening read |
| Notes | Notes that affect the assessment, such as incomplete coverage |
- Language: the report is produced in the panel's current interface language — Turkish, English, German, Spanish or Russian. If the panel is in any other language, the report is produced in Turkish.
- The report is not stored; it is regenerated from the screening record on every download.
- The report is a restricted audit document containing the subject's matches and your decision, and must not be disclosed to the data subject.
The PDF report can only be downloaded from a panel session. A token minted from an API key cannot fetch it; in your integration, keep the evidenceRef, publicationId and customerReference fields of the response for your audit trail.
Related
- Sanctions Screening — list coverage, the list publication and risk domains
- Sanctions Screening API — endpoints and response fields
- Screening History — past screening records