WF-08 — KYC & Screening

Onboarding or material change → collect → extract/verify → screen → risk-rate → approve / EDD / case, under maker-checker, source-version and hold rules. Owner: Compliance — Ahmed Al Blooshi (MLRO) · maker Yusuf Karim · checker Noura Saeed · workflow definition v4.1 · effective 10 Jun 2026.

WF-08 CMP-01 CMP-02 CMP-03 CMP-04 CMP-05

KYC workspace AML cases

Profiles in flight

9 collect · 6 screening · 4 checker · 2 EDD

Median onboarding → clear

1.6d

Individuals 0.8d · corporates 3.9d

Screening hits open

3 likely false positive · 2 under review

Deals on compliance hold

Hold rule blocks contract release + receipts

Periodic reviews due ≤ 30d

2 overdue ▼ escalated to MLRO

Process map — happy pathPublished v4.1Simulated 08 Jun 2026 · pass

Onboarding / material change detected→ Collect — ID, address, UBO, source of funds→ Extract & verify (document intelligence)→ Screen — sanctions · PEP · adverse media→ Risk-rate (scored model, versioned)→ Checker approval (maker-checker)→ Cleared — profile active · holds lifted

Risk-rate = High / PEP confirmed→ Enhanced due diligence — EDD pack→ MLRO approval→ Approved with conditions — monitoring plan

Material changes re-entering the workflow: name/ID change, new UBO ≥ 25%, nationality change, adverse-media alert, sanctions-list delta (from WF-09). Hold rules keep dependent actions (contract release, receipt acceptance, payout) blocked until terminal state.

Exception paths4 defined

Screening hit→ Review — DOB / nationality / identifiers mismatch→ Dismissed as false positive — rationale + reviewer recorded

Hit confirmed / suspicion formed→ Escalate to MLRO→ AML case opened — evidence pack→ Exit / report decision — relationship blocked, no tipping-off

Review date reached (risk-based cycle)→ Refresh documents & rescreen→ Overdue — profile downgraded to hold, MLRO notified

Checker approval→ Source list version stale vs latest sync→ Approval blocked — rescreen against current source version

Owner & definition (§8.3 standard)WF-08 v4.1

Owner: Compliance — Ahmed Al Blooshi (MLRO)
Version: v4.1 · published 10 Jun 2026 by Vikram Nair (Config Admin)
Trigger: Party onboarding (customer, landlord, vendor, broker) or material change on an active profile
Preconditions: Party record exists in party master · consent captured · sanctions source sync healthy (source status)
States: initiated · collecting · verifying · screening · risk-rating · pending checker · EDD · cleared · on hold · case open · exited
Terminal outcomes: Cleared — active Approved with conditions (EDD) Exited / declined
Required evidence: Document images + extraction results, verification outcome, screening result with source list versions, hit-review rationale, risk score + model version, maker and checker identities, EDD pack and MLRO decision where applicable
Policy snapshot: Risk model and screening thresholds resolve from snapshot at initiation; sanctions-list version is a named legal re-evaluation rule — always screened against the current activated list

Controls (Table 14, expanded)Compliance dashboard

Control	Enforcement point	Evidence retained
Maker-checker	Clearance decision	Yusuf Karim (maker) ≠ Noura Saeed (checker); both recorded with timestamps
Source version pin	Screening	Sanctions/PEP list IDs + versions on every result (e.g. UN-CONS 2026-07-14, EU-2026-27)
Hold rules	Downstream actions	Contract release, receipts and payouts blocked while profile not cleared; hold reason visible
Extraction confidence	Verify step	OCR confidence per field; below threshold routes to manual verification (CMP-02)
Risk model versioning	Risk-rate	Score, factors and model version RM-3.2 persisted; overrides need reason + MLRO
Case confidentiality	AML case	Case visibility restricted to compliance role; no tipping-off; audit trail in audit explorer
Periodic review cycle	Post-clearance	Risk-based cycle High 12m · Medium 24m · Low 36m; overdue = automatic hold

Exception paths & recoveryReasons mandatory

Exception	Detection	Recovery	Owner
False positive	Hit with identifier mismatch (DOB, nationality, ID no.)	Dismiss with rationale in screening review; whitelist pairing to suppress identical future hits, reviewed quarterly	Noura Saeed
Escalation — confirmed hit	True match or suspicion after review	Open case in AML cases; freeze dependent transactions; MLRO decides exit/report; evidence export preserved	Ahmed Al Blooshi
Periodic review overdue	Review-date breach on cleared profile	Auto-hold; refresh + rescreen; clearance re-issued by checker; overdue list on RPT-20	Yusuf Karim
Stale source version	Checker gate compares list version vs latest activation	Rescreen against current list (from WF-09); decision re-taken	Compliance system
Document rejected	Verification fails (expired ID, unreadable)	Re-request from customer via portal; SLA clock pauses in collect state	Requesting agent

Timers & escalation (§8.3)Business calendar: UAE · Mon–Fri

Timer	Warning	Breach	Escalation
Collect → verifiedPauses while awaiting customer docs	1 bd	2 bd	Maker reminder → compliance team lead
Hit review SLA	4 bh	1 bd	Checker → MLRO; hold remains active throughout
Checker decision	1 bd	2 bd	Noura Saeed reminder → Ahmed Al Blooshi
EDD completion	5 bd	10 bd	MLRO weekly review; deal-side notified of continuing hold
Periodic review	−30d	due date	Overdue → auto-hold + MLRO digest + RPT-20 flag

Screening throughput and hit aging: RPT-21 · case aging and evidence export: RPT-22.

Screens involved6 screens

Step	Screen	Primary role
Collect · profile · holds	KYC Workspace	KYC maker (Yusuf Karim)
Extract & verify documents	Extraction & Verification	KYC maker
Screen · review hits	Screening Review	KYC checker (Noura Saeed)
Risk-rate · EDD pack	Risk & EDD	Checker / MLRO
Cases · exit / report decisions	AML Cases	MLRO (Ahmed Al Blooshi)
UBO & connected parties	Relationship Graph	Compliance analyst

Worked instance — Amina Noor onboarding · KYC-2026-0788Cleared 14 Jul 15:12

13 Jul 2026 10:20
Trigger — onboarding for deal DL-2026-0142
Amina Noor (PTY-0044821) · individual buyer · initiated by Omar Haddad · hold rule active: contract release + receipts blocked
13 Jul 2026 11:02
Collected
Emirates ID 784-19●●-●●●●●●●-● (front/back), proof of address, source-of-funds declaration (salary + savings) · consent recorded
13 Jul 2026 11:04
Extracted & verified
Document intelligence extraction 99.1% mean confidence · name/DOB match party master · ID expiry 2028-03-11 Valid
13 Jul 2026 11:05
Screened — 1 potential hit
Name similarity 0.71 to “A. Noor” (EU-2026-27 list) · DOB and nationality mismatch · sources UN-CONS 2026-07-14 · EU-2026-27 · UAE-LTL 2026-07-01
13 Jul 2026 14:30
Hit dismissed — false positive
Noura Saeed · rationale: different DOB (1991 vs 1958), different nationality, no secondary identifier match · rationale + reviewer stored
13 Jul 2026 14:31
Risk-rated
Score 22/100 → Low · model RM-3.2 · factors: resident, salaried, domestic funds, no PEP link · review cycle 36m
14 Jul 2026 15:12
Terminal — checker cleared
Maker Yusuf Karim → checker Noura Saeed SoD distinct · source versions current · holds lifted → WF-04 contract release unblocked · next periodic review 14 Jul 2029

Static render mockup — no live data. Source: ERP Modern Development Specification v2.0 (§8.2 Table 14, §8.3, CMP-01–CMP-05) · Covers: WF-08, CMP-01, CMP-02, CMP-03, CMP-04, CMP-05.