AML and KYC reviews an analyst can defend.

Run onboarding and alert reviews as a governed workflow where an agent assembles the case and runs screening, and an analyst owns the decision.

A compliance analyst's hands working through a clipped case file with a customer's identity document on top, the screening results list softly blurred on the monitor behind, under a desk lamp in an evening office.
§ 01 · How it works

One run, end to end.

Kora runs AML and KYC reviews as governed workflows: an agent gathers the case and runs the screening steps against sanctions, PEP, and adverse-media sources, drafts a risk assessment, and an analyst approves before a customer is onboarded or an alert is cleared, with a hash-chained, replayable record of the decision.

  1. Case opens

    A review starts

    An onboarding or an alert opens a case in the released workflow.

  2. AI agent

    Assemble and screen

    The agent gathers the customer data, runs sanctions, PEP, and adverse-media screening, and drafts the risk assessment.

  3. Analyst

    The analyst decides

    Flagged cases route to an analyst who approves, escalates, or files. The high-risk call stays human.

  4. Record

    A defensible decision

    The evidence reviewed, the rationale, and the outcome land in the append-only record.

A review can be reproduced for an examiner, not reconstructed. Hash-chained, replayable.

§ 02 · The approach

AML and KYC reviews

01Agent

The agent assembles the case

When an onboarding or an alert opens a case, the agent gathers the customer information, runs the screening steps against sanctions, PEP, and adverse-media sources, and drafts the risk assessment with its reasoning attached. Low-risk onboarding can clear on the rules you released, and no analyst ever starts from raw data.

A case review queue on a compliance analyst's monitor, most rows cleared with a small green check, and a stack of customer case folders with an identity card clipped to the top one in front of the screen.
02Analyst

Flagged cases go to an analyst

A screening hit, a mismatch in the file, or low confidence routes the case to an analyst instead of through. They see the evidence the agent gathered, the screening results, and its reasoning, and they make the call: approve, escalate, or file. Your analysts spend their judgment on the cases that carry risk, not on the ones that do not.

One customer case folder set apart on the desk with an amber flag tab and an identity document clipped inside, a pen beside it ready for an analyst, and a review list behind showing a single row banded in amber.
03Record

Every decision lands in the record

Agent or analyst, every review is written to an append-only, hash-chained record: the evidence gathered, the screening run, the rationale, who decided, and the outcome. A review can be replayed to show an examiner it happened as stated, and the next periodic or event-driven review starts from the same customer file.

A settled ledger of completed review entries on a desk monitor, the latest entry sealed with a small green mark, and a tray of closed case folders archived beside it.
What you get
  • Cases arrive assembled

    The agent brings the customer data, the screening results, and a drafted assessment, so review starts at the decision.

  • Judgment where the risk is

    Clear cases move on released rules, while every flagged one gets an analyst's call.

  • Defensible to an examiner

    One hash-chained, replayable record per review, showing the evidence, the rationale, and who decided.

  • A customer file that stays current

    Onboarding, periodic refresh, and event-driven reviews land in the same record, so the file always shows its defensible state.

§ 03 · FAQ

What compliance teams ask.

The questions AML and KYC owners raise when they evaluate Kora.

No. An agent gathers the case and drafts a recommendation, but an analyst approves onboarding, alert clearance, or escalation. The record shows the recommendation and the human decision.

The customer data gathered, the sanctions, PEP, and adverse-media screening, the risk rationale, the analyst who decided, and the outcome, all hash-chained and replayable.

It orchestrates across the screening, watchlist, and case-management systems you already run, gathering the case and writing the decision back. It governs the process and the evidence, it does not replace those systems.

Yes. Onboarding, periodic refresh, and event-driven reviews, sometimes called perpetual KYC, can run as the same governed workflow: the agent assembles what changed, screening runs again, and an analyst approves the outcome. Every review lands in the same hash-chained record, so the customer file always shows its current, defensible state.
§ 04 · Next step

Bring one alert.

In a demo, bring a case your analysts reviewed this week. We will run it as a governed workflow: the agent assembles and screens, the analyst decides, and the decision lands in a defensible record.