What’s inside: audit trail · monitoring
The question this file answersHow much of our annual review cycle is collecting the same documents we already hold?
Fits: compliance teams re-collecting the same papers every review cycle.
Typical, from the finance playbook — KYC work is continuous for banks and insurers and peaks at year-end. A periodic review means asking the client for papers again, re-running list checks and rebuilding a file the officer signed twelve months ago. The refresh queue swells exactly when onboarding does.
When the year-end refresh run starts, the officer opens a queue of files sorted by what moved — a new director, an address in a new jurisdiction, an adverse-media hit — with last year’s decision alongside. The unchanged files still need a signature, but they need a reading, not an afternoon of collecting.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
of refresh assembly time — the KYC range, not a refresh-specific figure; the decision stays the officer’s
Before: annual reviews rebuild a file the officer already approved last year. After: assisted-KYC studies (McKinsey, 2023) put 40–60% of KYC case time within reach — the officer reads the delta and still signs.
McKinsey KYC study (2023) reports 50–70% less per-case processing time with assisted KYC; the finance playbook uses 40–60%. Periodic re-verification is inside that KYC scope but is not measured separately — an industry range, not our measurement, and not a SAR-rate claim.
Nothing changes in the core system or the screening tools — Temenos, FIS, World-Check, Thomson Reuters or the ones you run. This is the same file-assembly build as our KYC onboarding file, run against clients you already hold:
Nothing changes a risk rating without a person.
Material change. Adverse media. SAR investigation. Regulator questions. The yes or no stays a named officer.
If historic files live in scanned PDFs with no index, the first refresh cycle is an audit of your archive before it is a saving. Regulators expect every automated step to be logged with its reasoning — that log is part of the build, and if your DMS cannot hold it, that is IT work first. The McKinsey range is for KYC case time as a whole; investigations and adverse-media judgement are outside it.
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.