Videos
Automate Your KYC Process with Kognitos
An end-to-end KYC automation in Kognitos: extract from three ID documents, cross-validate the fields, and email the approval with risk level.
What's in this video
A 7.5-minute walkthrough of a Kognitos KYC automation. KYC processes are labour-intensive, error-prone, and slow customer onboarding when handled manually — this demo shows how an English-defined Kognitos process does the heavy lifting end-to-end.
Documents the automation processes
- KYC application form — name, gender, marital status, date of birth, nationality, passport number, address, and a signature.
- Passport — the proof of identity for the demo applicant.
- Driver's license — the address verification document.
What Kognitos does, step by step
- Identify each file: Kognitos recognises which document is the application, the passport, and the license without depending on filenames.
- Field extraction: extract the relevant fields from each document using OCR plus LLM-driven extraction.
- Cross-document matching: check that the name, gender, date of birth, address, and passport number agree across the three documents.
- Decision: approve or deny the KYC and set a risk level. In the demo: Verification completed, risk level Low.
- Recordkeeping email: email the operator a structured summary — every extracted field for each document, every per-field match check, the final KYC status, and the risk score.
Where this scales next
The same English process extends naturally to sanctions and watchlist screening, PEP (Politically Exposed Person) checks, and ongoing monitoring — all by adding English steps and API calls rather than rebuilding the workflow.
Questions answered in this video
Which documents does this KYC automation process?
Three: the KYC application form (name, gender, marital status, date of birth, nationality, passport number, address), the applicant's passport (proof of identity), and the applicant's driver's license (address verification).
How does Kognitos validate the KYC application?
It cross-checks the applicant's name, gender, date of birth, address, and passport number across all three documents. When every field matches, Kognitos marks the KYC verification as completed and assigns a risk level — Low in the demo.
What does the operator receive at the end of the run?
An email containing every extracted field from each document, every per-field match check (name, gender, DOB, address, passport number), the final KYC verification status, and the risk level — a full recordkeeping packet ready for audit.
Can this be extended to sanctions, PEP, and ongoing monitoring?
Yes. The video explicitly calls out that sanctions and watchlist screening, PEP checks, and ongoing monitoring can be added as additional English steps to the same Kognitos process — no separate platform required.