What’s inside: audit trail · output checking
The question this file answersWhy does a true sanctions match wait in the same queue as a homonym anyone would dismiss on sight?
Fits: banks, payment firms and fintechs where compliance files are still assembled by hand.
Typical, from the finance playbook's KYC/AML section, which names list checking but no alert volume. Payments and new parties are screened against World-Check, LexisNexis or your lists; true hits and homonyms share one queue, opened as if equal. It hurts when the regulator asks how long real hits waited.
At the start of the shift the officer's queue holds the names that survived a secondary check, each with the evidence already laid out, instead of every alert the list produced overnight. Every clearance, including the automatic ones, sits in the log with its reasoning for the regulator to read.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
the same list-checking step as KYC onboarding — no published figure for screening alerts
Before: true hits and homonyms sit in one queue and an officer opens both. After: no-hits clear with a logged comparison; the real names wait for the officer. No percentage — the only figure is about onboarding.
McKinsey KYC study (2023) reports 50–70% less case time on onboarding; it does not measure alert screening, so this file carries no percentage and the range stays on the KYC file. Not a false-positive promise.
Your screening and compliance tools stay — World-Check, LexisNexis, Thomson Reuters or the ones you run. This is the same list-checking step as in our KYC onboarding build, run on its own:
No true hit is ever closed by the model.
The true match. Alias judgement. Escalation. The regulator.
Not a false-positive promise.
If customer records lack dates of birth or countries, secondary checks cannot run and almost nothing clears automatically — that data gap is audit work first. Aliases, transliterations and partial identifiers stay a person's judgement, and the log of automatic clearances must be acceptable to your compliance function and regulator before the first live run.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Finance.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.