Agentic AI
From six documents to a KYC decision: a case walkthrough
Follow a KYC onboarding case through document review, an information request, an MLRO decision and an evidence pack. The important work happens between receiving the documents and deciding what they establish.
Six documents have arrived. The customer declares an 80 percent holding; the commercial register shows 74 percent. The officer needs to decide which source to rely on, what to ask the customer and how to record the conclusion.
This cmpliance walkthrough follows one KYC/AML onboarding case through that review. It connects the documents to the officer's work, the customer's response, the decision by the money laundering reporting officer, or MLRO, and the resulting evidence pack.
youtubeFollow one KYC onboarding case through six uploaded documents, evidence review, a customer response and an MLRO decision to an evidence pack.https://www.youtube.com/watch?v=1bbh3ibnxxYWatch the KYC/AML onboarding walkthrough.
Start with what each document can establish
At 1:08, six documents enter the case. In cmpliance, the officer reviews the classified documents and extracted information alongside the source material.
An extracted value and a verified fact are different things. A document may identify an owner without establishing the complete ownership structure. A customer's statement may explain an activity without independently substantiating it. Even an accurately extracted statement can be out of date or insufficient for the question being asked.
The useful review question is therefore specific: what does this source allow me to conclude? It should be possible to inspect the source behind the answer, rather than treating the presence of a populated field as confirmation.
At 3:56, the walkthrough turns to evidence, sources and gaps. This is where the file becomes a review of claims rather than an inventory of attachments. The existing article on KYC evidence review beyond name screening explains the broader questions concerning identity, authority, ownership and expected activity. Here, the focus is on keeping those questions connected to the case as it moves forward.
Keep a gap visible when the case proceeds
At 5:00, the case proceeds to officer review after accepting residual risk. That transition deserves attention. Accepting a limitation does not make the missing evidence appear, and a change of case status should not make the limitation disappear from the record.
For a reviewer, a useful acceptance record explains what is missing, why it matters, what other evidence supports proceeding, and who takes responsibility for that judgment. Where further action is needed, the record should identify it. A residual-risk decision is a recorded judgment with a named owner; it is not a waiver of the due diligence the relationship requires.
The register disagrees with the customer
The officer needs to reconcile the customer's declaration with the register record. At 5:58, the officer confirms the register ownership fact. At 6:22, the customer's response is recorded and accepted.
Keeping those actions distinct matters. A response may answer the request while leaving a wider issue unresolved. The reviewer needs to compare it with the question that prompted the request and decide what, if anything, it changes.
The customer's response belongs alongside the register fact and the officer's conclusion. Keeping those records separate lets the MLRO see how the mismatch was handled, rather than infer from a closed request that every underlying concern was resolved.
Give the MLRO a reviewable case
At 7:16, the officer refers the case to the MLRO. The MLRO review and decision follow at 7:46.
This handoff is the point at which the preparation must be useful to someone other than its author. The MLRO needs the evidence relied on, the officer's work, the remaining limitations and the question requiring a decision. A referral that supplies only a proposed outcome forces the next person to rebuild the reasoning.
The walkthrough makes the human decision explicit. cmpliance holds the material and recorded actions around it, while the MLRO reviews the case and records the decision.
Carry the review into the evidence pack
The case reaches sealing and download at 8:36. At 9:12, the walkthrough opens the evidence pack. Its evidence matrix and decision trail bring the supporting material and review history into the resulting record.
A useful pack should explain the decision that was actually made, including its limits. It should not turn an accepted gap into a verified fact or make an earlier disagreement disappear because the case reached approval.
This is a practical test for your own onboarding process: give the completed file to a colleague who did not handle it. Can they trace one important ownership fact to its source, identify what the customer was asked, and explain why the case proceeded? Every answer that depends on the original officer's memory identifies something the record needs to preserve.
Why it matters for your team
cmpliance puts document classification and extracted information alongside the source material so officers can concentrate on questions such as this ownership mismatch. Agents prepare the evidence for review; the officer and MLRO decide what to rely on, and the evidence pack carries that work into the record.
See how cmpliance works and what makes an evidence pack audit-ready. Bring us the evidence gaps and handoffs your onboarding team needs to resolve.
Agents do the work. Humans make the call.
Receiving and classifying documents starts the review. It does not verify every fact they contain.
An accepted evidence gap needs a recorded rationale and accountable approval; it cannot waive required due diligence.
The evidence pack should preserve the sources, responses, human decision and remaining limitations from the case.
Frequently asked questions
→Does uploading the documents complete KYC?
No. The officer still needs to determine what the documents establish, resolve material contradictions and assess whether the evidence meets the requirements for the relationship.
→Can an officer accept missing evidence and proceed?
Only where the applicable requirements and the institution's policy permit proceeding. The record should identify the gap, supporting rationale and accountable approval. Required due diligence cannot be replaced by a residual-risk acceptance.
→What does the walkthrough cover?
It follows one case through document and evidence review, a customer response, MLRO review and decision, and an evidence pack containing the supporting material and review history.
