Begin a new KYC analyst's first fortnight with provenance: which documents and data the onboarding agent may treat as evidence, and which it may not. Then teach ownership tracing and screening by checking the agent's work on closed files. In week two they decide live files with a senior analyst confirming each acceptance. Escalations to the MLRO stay supervised longer.
What does the onboarding agent do?
In a bank, payments firm or fintech with agents, the KYC agent typically collects identity and company documents, pulls registry data, screens names against sanctions and politically exposed persons lists, traces beneficial ownership through company layers, and drafts a risk rating with reasoning (depth 1 and 2). It may close obvious screening false positives within rules, with a sample reviewed by people. Accepting, refusing or escalating a customer stays with analysts.
A new analyst inherits files that are mostly assembled. Their value lies in what the agent cannot judge well: whether the ownership trace is complete, whether a document is adequate evidence, whether the risk rating makes sense. How the day shifts is set out in what changes in a KYC analyst's day when AI agents arrive. The KYC team lead owns onboarding; a certified senior analyst coaches.
What does each day bring?
- Day 1. Person (KYC team lead): explains provenance rules per check. A passport verified through a document check is signed. A utility bill uploaded by the customer is declared. A company registry extract is signed by the registry. A letter emailed by an introducer is external. Policy says which classes count for which check.
- Day 1 to 2. Person (new analyst): learns the agent's bounds: what it gathers, what it may close, what it must hold.
- Day 2 to 3. Agent, depth 2: drafts ownership traces and ratings on live files, decided by the coach while the new analyst follows.
- Day 4 to 5. Person (new analyst): re-traces ownership on closed files from source documents, comparing with the agent's trace to find where it stopped early.
- Week 2. Person (new analyst): decides live files, with the coach confirming each acceptance before it takes effect.
- Week 2. Person (new analyst): records reasons on every change: provenance accepted wrongly, trace incomplete, risk factor missed, false match, or analyst judgement.
- End of week 2. Person (KYC team lead): signs off acceptance of standard-risk customers. High-risk and escalations stay supervised.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Gather | Documents, registry data, with provenance | 1 | Requesting more evidence |
| Screen | Checks lists, closes obvious false hits | 2 | Real or unclear matches |
| Trace ownership | Follows company layers | 2 | Confirming completeness |
| Rate risk | Drafts rating with reasons | 2 | The rating |
| Decide | Nothing | none | Accept, refuse, escalate |
What must a new analyst check on every file?
Is each piece of evidence the right class? A declared document where policy needs a signed one is a gap, however convincing it looks.
Did the trace reach natural persons? Agents may stop at a holding company, especially one registered abroad. The analyst checks every layer.
Do the facts fit the stated business? A small trading company with large payments to unrelated jurisdictions needs a question, even if every document is in order.
Are screening closures sound? Where the agent closed a hit, the reason should be specific, such as different date of birth and nationality.
Is the rating explained? A risk rating with no reasons cannot be reviewed or challenged. The agent drafts reasons; the analyst checks that each one points to a fact in the file, and that those facts would lead a colleague to the same rating.
How should corrections be recorded?
With a reason code and no unnecessary personal data. Clear reasons let the agent owner change the agent's provenance rules or tracing method instead of every analyst fixing the same gap. "Analyst judgement" marks a decision within policy that should not become a rule.
Which controls and evidence should onboarding leave?
- Re-traced files. Evidence: the closed files and differences found.
- Confirmed acceptances in week two. Evidence: both analysts named.
- Provenance checked on every file. Evidence: the classes cited in each rating.
- Staged rights. Evidence: dated authority for standard risk, later for high risk.
What should the team lead measure?
Incomplete traces the new analyst caught. Files accepted with the wrong evidence class, which should be none. Screening closures the analyst reopened. Time per file. After sign-off, a monthly quality sample.
Where does it usually go wrong?
Accepting the assembled file. It looks complete; a new analyst accepts it. The re-trace exercise shows where agents stop early.
Treating screening as the whole job. Screening is quick to learn; ownership and risk judgement take longer.
High-risk files too soon. Two weeks covers standard risk, not complex structures.
The plans for a new credit analyst and a new fraud analyst cover neighbouring roles, the AI agent training plan template for KYC analysts sets the learning out, and how long it takes to train KYC analysts to supervise AI agents sets expectations beyond the first fortnight. The wider approach is in training teams for AI agents.
Where the Academy fits
Pryme Intelligence Academy's Operator track teaches how a governed agent decides and how provenance and bounds shape its verdicts, with module tests set in the learner's industry and role. A firm can choose to make acceptance rights depend on a current Certified Pryme Operator certificate, which is checkable at source and shows as lapsed once expired.
Questions people ask
Can the agent accept low-risk customers on its own?
Some firms may consider it for the simplest cases with strong evidence. Acceptance has regulatory weight, and most keep it with a person.
What if the registry data conflicts with the customer's documents?
Hold the file, record the conflict, and ask. Registry data is signed but can be wrong; the policy should say how conflicts are resolved.
When should a new analyst escalate to the MLRO?
When the policy says so, and whenever they are unsure. In the first weeks, escalate through the coach.