Who It’s For
- Firms that need consistent screening with documented decisions
- Teams overloaded by false positives who still need defensible controls
- Operators preparing for bank reviews, audits, or regulator requests
Compliance support for 700+ Cyprus entities. CySEC ASP License 135/196. Response within four business hours.
What You Get (Deliverables)
- Screening scope note (lists/jurisdictions, refresh frequency, approval limits)
- Matching settings sheet (thresholds, aliases, transliteration rules)
- Triage, escalation, and approval templates
- Registers: exceptions, decisions, and configuration changes
- Audit pack structure and sample evidence files
- Monthly reporting on volumes, hit rates, and ageing
Process
- Scope: confirm lists, jurisdictions, risk tiers, and approval limits.
- Calibrate: tune matching rules, roles, and change control.
- Pilot: run sample cases, record false positives, and document the final settings.
- Operate: triage alerts, capture evidence, escalate credible items, and maintain registers.
- Refresh: re-screen by risk tier and event triggers.
- Audit: compile packs with evidence, decisions, timestamps, and approvers.
Screening Modes & Triggers
| Mode | When Used | Data Sources | Output |
|---|---|---|---|
| Onboarding | Before approval for new clients/signatories/UBOs | Names/aliases, date of birth, nationality, addresses, IDs | Pass/Refer decision with evidence and a short note |
| Periodic refresh | Per policy by risk tier (12/24/36 months) | Client master + latest IDs | Refresh report and approvals |
| Trigger-based | Material change (ownership, geography, negative news) | Change requests, monitoring alerts | Targeted re-screen note and decision |
| Bulk portfolio sweep | Major list update or regulatory event | Full portfolio extract | Exception list with actions |
| Ongoing adverse media | Continuous monitoring (if configured) | News feeds/databases, keywords | Hits triaged to cases with references |
Configuration and evidence standards are aligned to your policy and the receiving bank/authority expectations.
Case Study
PEP Match on Prospective Partner UBO (Anonymised)
Client: Services company screening a prospective partner where the ultimate owner triggered a PEP match (anonymised)
The relationship raised a PEP alert. The risk was mishandling a false match (or ignoring a credible one), leaving the file indefensible to banks or auditors.
MegaServe confirmed identifiers (name variants/aliases, date of birth, nationality), captured screening sources, and wrote a clear triage note with the next steps. The case was escalated where required, approvals were recorded, and the decision was logged with timestamps and an evidence pack.
Result: a defensible decision (pause/proceed/escalate) supported by a clean paper trail that a reviewer can audit quickly.
Requirements (Kickoff Checklist)
| Inputs | Access & Tools | Evidence & Records |
|---|---|---|
|
|
|
Sensitive data should be shared via the VDR only. We provide an index and permissions model at kickoff.
Controls & Quality
- Two-person control for configuration/list changes and credible match decisions
- Role-based access with least privilege across tools and the VDR
- QA sampling of dispositions with corrective actions tracked
- Audit trail: evidence captures, timestamps, and approvers
- Assumptions and exceptions register reviewed on a defined cadence
Risk & Notes
- Sanctions-list lag: screening databases update on different schedules; a name cleared today may appear on a list tomorrow.
- False positives: common names can trigger matches; manual review is always required before acting on a hit.
- Ongoing obligation: one-off screening is not sufficient — Cyprus regulations require continuous monitoring of business relationships.
FAQs
Which lists do you screen against?
We align to your policy (for example UN, EU, UK, OFAC) and any local or sector regimes you specify. Coverage and refresh schedules are documented in the scope note.
Do you replace our Compliance/MLRO?
No. We operate the workflow and documentation. Final approvals remain with your designated officers.
Can you guarantee zero false negatives?
No. Screening is risk-based. We tune thresholds, enforce QA, and document assumptions to reduce error while avoiding excessive false positives.
How do you handle adverse media alerts?
We apply defined sources and criteria, triage hits to cases with evidence references, and escalate material items per policy.
What about data privacy?
We follow your retention policy, minimise data shared, restrict access by role, and keep an audit trail of access.
What is client screening and when is it required?
Client screening checks individuals and entities against sanctions lists, politically exposed person (PEP) databases, and adverse media sources. It is required at onboarding, periodically during the relationship (based on risk tier), and whenever a material change occurs — such as a new UBO, a change of jurisdiction, or a negative news event. Cyprus-regulated firms must screen as part of their AML obligations.
How do you price client screening?
We offer per-screen fees for one-off onboarding or trigger-based screens, and monthly retainers for ongoing portfolios covering a set volume of initial and refresh screens plus alert handling. Bulk portfolio sweeps (following a list update or regulatory event) are scoped case by case. Third-party screening tool subscriptions are billed at cost. We provide a written quote after the scoping call with no hidden charges.
See also
Client Onboarding Assistance Services · Know Your Client (KYC) Procedures · Sanctions Manuals & Compliance Guides
Other Jurisdictions (on request)
Where required, we coordinate client screening and due diligence through vetted associates in selected jurisdictions.