Verkflo is in early access. Book a demo

KYB automation for business customer onboarding

A KYB agent reads the company record, maps owners and controllers to the threshold in your policy and screens each person. Gaps in the ownership chain go to a reviewer with the evidence attached.

Book a demoSee use cases

Works with

and any system with an API via Custom REST

What KYB automation covers in Verkflo

A KYB review asks two questions about a business customer: is the company what it says it is, and who owns or controls it. The paperwork is the slow part. Registry extracts, shareholder lists and director IDs arrive in different formats, and each owner above your threshold needs screening.

Verkflo fetches the company and its beneficial owners from Sumsub, works through as many ownership layers as your procedure asks for, and screens each owner and director in ComplyAdvantage. Where a layer has no supporting document, the run stops and puts the gap in front of a reviewer. A company registry with an API can be added through Custom REST.

Suppliers go through similar checks: vendor due diligence reuses the company and owner steps for third parties. Individual customers are covered on KYC automation.

Who does what in a KYB review

  • The procedure

    Your KYB procedure names the company documents you need, the ownership threshold you apply, who counts as a controller and how far to trace a group structure.

  • What the agent does

    • Fetches the company and beneficial owner data from Sumsub

    • Builds the ownership chain down to the threshold your policy sets

    • Screens each owner and director in ComplyAdvantage

    • Lists missing registry extracts or shareholder records

  • What your team decides

    • Who the controllers are when ownership is unclear

    • Whether a complex or offshore structure is acceptable

    • Approval of business customers rated High risk

    • Cases to escalate to your MLRO or compliance officer

KYB and business checks you can run today

Business onboarding and supplier reviews share the company and owner steps.

Structures that need a person

Trusts, nominee holdings and circular ownership are where KYB files stall. You can write a rule that spots them, such as owners.exists(o, o.type == "trust"), and the run routes the file to a reviewer with the ownership chain and the source documents attached.

The reviewer's reasoning is stored with the run, next to the version of the procedure that sent the file to them. The Sumsub integration page shows the KYB call the agent uses.

Controls your auditors will ask about

These controls apply to each agent you build. Sample data

KYB automation questions

Which ownership threshold does the agent use?

The one in your policy. You write it into the procedure and the agent applies it at each layer. Changing it means publishing a new version, which runs in the sandbox first.

Can it reach company registries?

Through Custom REST, if the registry or your data provider offers an API. Sumsub's KYB data covers the company and its beneficial owners today.

What happens when ownership cannot be traced?

The run pauses, and a reviewer sees the layers found so far, the documents behind them and the gap. Their decision and reason are logged before the run continues.

Bring a business onboarding file

Walk us through a recent KYB case and we'll show it as an agent run, ownership steps included.

Book a demo