- contact@insightkycai.com
InsightKYC reads the passport and the certificate of incorporation, quoting every field from its line. It walks the company registry down every chain to the people who really own the customer, and screens each of them against sanctions, PEP and adverse-media lists with a score that shows its work. It rates the risk with a reason for every point and drafts the memo. Then it stops, and an analyst decides.
Most of an analyst’s day is preparation: retyping a passport, opening a registry extract, multiplying percentages down an ownership chain, clearing screening matches that are plainly someone else. The judgement, which is the part only a person can do, gets whatever time is left. Onboarding waits, and the file an examiner reads later doesn’t say why.
Reading documents, comparing them with the application, chasing the missing one. It is necessary, repetitive, and the reason a simple onboarding takes days.
An application names one shareholder. The registry shows a holding company offshore, and behind it someone who owns more than anyone on the form. Finding that by hand means multiplying down every chain.
When a customer goes wrong, the question is what the bank knew at the time. A note that says “screening clear” doesn’t answer it. A record of every match, disposition and control does.
One case for every onboarding, periodic review and event-driven review. Ten agents prepare each stage. A person accepts, rejects or asks about what they prepared, and makes every decision that matters.
A case opens from an application, from the customer book when a review falls due, or from a monitoring alert. The intake agent lists what is on file and what is missing.
Documents are read into fields, each quoted from its line. Checks compare them with the application: in date, same name and date of birth, MRZ check digits, a recent proof of address, and registry status.
The registry is walked down every chain to the beneficial owners. Every party is screened against sanctions, PEP and adverse media, and each match shows how name, date of birth and nationality compare.
A points model rates the customer, with the reason for every factor. High risk and PEPs need enhanced due diligence; prohibited countries and industries block approval.
Case controls from Rules Studio say what blocks a decision. High risk needs a second person. The decision record keeps every control, the rating and each disposition as they stood.
From the demo bank’s data: Kestrel Freight LLC declared Diego Hernandez at 30%. InsightKYC walked the registry, found a Cayman Islands holding company owning the other 70%, and the person behind it. It multiplies every chain, adds the holding company and its owner to the case, and raises the difference as a failed check.


An analyst can only disagree with a score they can read. Every screening match and every risk rating in InsightKYC comes with the reasons that produced it.
The demo bank’s fictional sanctions list holds nine entries that look like Tatyana Orlov. Eight share the first name but carry a different surname, so they never reach the queue. The one left agrees on everything.
The agent proposes a disposition. It cannot clear a strong sanctions match; a person records the outcome with a reason.
Mary Williams, a declared politically exposed person living in South Africa, from the demo bank. The model is a points table you set; the thresholds here are illustrative.
High at 50 points or more, medium at 25. A lead can override the rating, with a reason that goes on the decision record.


Each agent does one stage of the case and stops at a prepared decision: a request to send, a memo to accept, dispositions to apply. You accept, reject or ask a question. Every answer goes on the record, and how often people agree is how an agent earns more autonomy.

When something is missing, the agent that noticed drafts the request. It is held on the case for an analyst to edit and send. The customer answers through their own link, with no account to create, and what they upload is read and checked as it arrives.

The customer book sets each customer’s next review from its risk rating and turns a due review into a case. Monitoring reads transactions against what the customer declared, and an alert is either closed with a reason or opens an event-driven review.


The questions a CCO is asked are simple. InsightKYC keeps the evidence for each answer on the case, as it was when the decision was made.
The decision record: who submitted, who approved, every control’s outcome, the rating and each screening disposition, frozen at the decision.
High-risk and PEP cases are submitted by one person and approved by a lead who isn’t them. The system enforces it.
The book shows who is current, due soon and overdue, by rating, and opens the review case in one step.
Every agent step, what it prepared, who answered and how, and the agreement rate that decides whether it earns more autonomy.
A Python API, a React app and PostgreSQL, designed to run in your own cloud account against your own systems. Nothing in a case is a value the model made up.
A field comes from a document line, an owner from the registry, a match from a list entry. Checks, ownership arithmetic, scores and ratings are deterministic code, not the model.
InsightKYC reads applications, the registry, lists and transactions from your systems and keeps its own work in its own schema.
What blocks a decision and what needs a second person are case controls you can read, test and publish, not code.
Analysts prepare and submit. Leads approve, override and waive. Auditors read everything and change nothing.