Verkflo is in early access. Book a demo

Automate KYC onboarding reviews from your written procedure

A KYC agent follows your onboarding procedure on each applicant: it reads the documents, runs the screening, applies your rules and asks a reviewer wherever the procedure says a person decides.

Book a demoSee how it runs

Works with

and any system with an API via Custom REST

What is a KYC onboarding review?

  • The procedure

    A KYC onboarding review checks that a new customer is who they say they are before the account opens. An analyst collects the ID and proof of address, screens the person and gives a risk rating under your policy. The judgment calls sit in the screening hits and the high-risk files.

  • What the agent does

    • Pulls the applicant, ID and proof of address from Sumsub

    • Checks each document against the sections of your procedure

    • Screens the applicant, directors and owners in ComplyAdvantage

    • Applies your risk rules and drafts any request for missing documents

  • What your team decides

    • Whether a possible PEP or sanctions match is the same person

    • Approval of any applicant rated High risk

    • Whether a request for documents goes to the applicant

    • Escalations to your MLRO or compliance officer

Example runs for onboarding analysts, MLROs or compliance officers, and compliance operations

Sample data

KYC Review Agent

Reviews each new applicant against your onboarding procedure.

  • Sumsub
  • ComplyAdvantage
  • +1

Trigger: Sumsub · applicantReviewed

From a procedure KYC review · v1.3

Maya

New applicant: Halden Trading. Run the onboarding review.

KYC Review Agent

  1. Pulled the applicant, ID and proof of address from Sumsub
  2. Checked the documents against section 3 of the procedure
  3. Screened the director and owners in ComplyAdvantage: no hits
  4. Risk rating is Medium, so no reviewer is needed risk_rating != "High"

Approved. Halden Trading meets each check in v1.3 of the procedure, and the run logs the rule that skipped review.

4 steps · 0 reviews

KYC Review Agent

Reviews each new applicant against your onboarding procedure.

  • Sumsub
  • ComplyAdvantage
  • +1

Trigger: Sumsub · applicantReviewed

From a procedure KYC review · v1.3

Priya

New applicant: Ostrava Metals. Run the onboarding review.

KYC Review Agent

  1. Pulled the applicant and the director's ID from Sumsub
  2. Screened the director in ComplyAdvantage: 1 possible PEP match
  3. Paused for a reviewer: section 4 sends any screening hit to a person Waiting for a reviewerTom: different person, date of birth and country differ
  4. Recorded the decision and continued the checks
  5. Risk rating is Medium after review risk_rating != "High"

Approved after review. Tom ruled the possible match a different person. His reason and the match details are attached to the run.

5 steps · 1 review

KYC Review Agent

Reviews each new applicant against your onboarding procedure.

  • Sumsub
  • Google Drive
  • +1

Trigger: Sumsub · applicantReviewed

From a procedure KYC review · v1.3

Lena

New applicant: Harbor Lane. Run the onboarding review.

KYC Review Agent

  1. Pulled the applicant and the uploaded documents from Sumsub
  2. Proof of address is missing, which section 3 requires documents.missing.size() > 0
  3. Drafted the request for documents and saved it to the case folder
  4. Held the request for a reviewer to approve Waiting for a reviewerTom: approved, your team sends it

Waiting on the applicant. The request for the missing proof of address was approved and handed to your team to send. The run resumes when the document arrives.

4 steps · 1 review

Setting up the KYC Review Agent

Connect your systems

Pull applicants and documents from Sumsub, screen in ComplyAdvantage, keep evidence in Google Drive, and reach any other system with an API through Custom REST.

  • Sumsub
  • ComplyAdvantage
  • Google Drive

Write the rules

Write the branch conditions once in CEL. Each run logs the rule that sent it to a reviewer or let it skip review.

Sample data
screening.hits > 0 || risk_rating == "High"Ask a reviewer
documents.missing.size() > 0Request documents
risk_rating != "High"Approve

Add reviewers where the procedure says

The agent stops where your procedure says a person decides, shows the evidence it gathered, and resumes on the reviewer's decision.

Sample data

Review requested: Ostrava Metals

Reason
Possible PEP match on a director
Rule
screening.hits > 0
Procedure
KYC review · v1.3

Different personEscalate

Start it from the event

Start a review when Sumsub marks an applicant as reviewed, or when your onboarding system posts a new applicant to a webhook. A daily schedule picks up applicants still waiting on documents.

  • Sumsub · applicantReviewed
  • Daily at 06:00 · applicants awaiting documents
  • Inbound webhook · new applicant

Version and evaluate

Write test scenarios for a clean applicant, a screening hit and a missing document. Each new version of the KYC review runs them first, and a failing scenario blocks publishing.

Sample data

KYC review · v1.3Published

12/12 scenarios passed

KYC review · v1.2 Superseded

KYC review · v1.1 Superseded

Share with the team

Your compliance team authors the onboarding procedure, onboarding analysts review paused runs, and internal audit reads runs and versions with the Auditor role. Admins manage access per workspace.

  • Admin
  • Author
  • Reviewer
  • Auditor

Questions about KYC onboarding automation

Does the agent approve applicants on its own?

Only where your procedure allows it. In the clean example the rating is Medium and no rule calls for a person, so the agent approves and logs the rule it used. A screening hit or a High rating pauses the run.

Which systems does it read from?

Sumsub for the applicant and documents, ComplyAdvantage for screening and Google Drive for the case folder. Other systems with an API connect through Custom REST.

What happens when a document is missing?

The agent drafts the request and a reviewer approves it. Your team sends it, and the run waits until the document arrives.

Can we change the risk rules later?

Yes. Edit the procedure or its CEL rules and publish a new version. Finished runs keep the version they followed, and new runs use the new one.

Controls your auditors will ask about

These controls apply to each agent you build. Sample data

Related use cases

See all use cases

Run this procedure as an agent

Book a demo with your own version of this procedure, and we'll show it running with each step logged.

Book a demo