Skip to main content

How Do I Verify a Company?

Company verification (KYB) is more complex than individual verification because it involves multiple entities. A single company may have directors, UBOs, and shareholders — each requiring their own checks. This guide walks through the full KYB flow in Studio.

What you’ll learn

  • How company data enters the system
  • What happens during a registry check
  • How directors and UBOs are extracted and screened
  • What the compliance report looks like
  • When cases are created in Case Management

The KYB flow at a glance

Walk through each stage

1

Company data is submitted

The flow begins when company data arrives — either from your application via the API or from a customer filling in a branded journey form.Key data points submitted:
  • Company name and registration number
  • Country of incorporation
  • Registered address
  • Website (optional)
Studio validates the input fields and starts executing the flow.
2

Registry check runs

The first node in a KYB flow is typically a Company Registry check. This calls the configured registry provider (e.g., Kyckr) to look up the company.The registry check verifies:
  • Registration status — is the company active, dissolved, or struck off?
  • Name match — does the submitted name match the registry name? Studio calculates a similarity score and flags mismatches below 70%
  • Registered address — does the address match?
  • Company type — what kind of entity is this?
A dissolved or inactive company generates a high-priority alert immediately. The flow continues to extract directors and UBOs, but the case will require manual review.
3

Directors and UBOs are extracted

If the registry check finds the company, Studio automatically extracts:
  • Directors and officers — names, roles, appointment dates
  • Shareholders — names, ownership percentages
  • UBOs (Ultimate Beneficial Owners) — individuals with 25%+ ownership or significant control
Each person becomes a case entity linked to the company case. Their role (Director, UBO, Shareholder) determines which checks are required.
RoleIdentityScreeningAddressAdverse MediaSource of Wealth
UBORequiredRequiredRequiredRequiredIf High Risk
DirectorRequiredRequiredN/ARequiredIf High Risk
ShareholderRequiredRequiredN/AN/AN/A
4

Each person is screened

Studio runs PEP/sanctions/adverse media screening on every extracted person. This typically uses a single API call per person to a screening provider like WorldCheck.Each screening result can return:
  • No Hit — no matches found
  • Hit — one or more matches found, with a match score and details
Hits generate alerts in Case Management with the match details, source data, and a confidence score.
5

Results are compiled

After all checks complete, Studio compiles a compliance report showing:
  • Company verification status — registry result, name match score, company status
  • Entity list — all directors, UBOs, and shareholders with their check results
  • Screening summary — how many people were screened, how many had hits
  • Overall decision — auto-approved (all clear) or review required (hits found)
If any issues were found, a case is automatically created in Case Management with all entities, checks, and alerts pre-populated.

What does the admin see in Studio?

After a KYB flow completes, the Studio dashboard shows:
  • Flow execution log — each node with its status (passed/flagged/failed), execution time, and provider response
  • Entity tree — the company and all extracted persons in a hierarchy view
  • Screening results — match summaries per person with hit counts
  • Journey status — approved, in review, or failed

What’s next?

Verify a Person

Walk through a KYC flow for individual identity verification.

Screen for Sanctions

Configure screening databases, thresholds, and match interpretation.

Manage Entities

Learn how to manage the UBO tree and entity checks in Case Management.

Run Checks

Understand how checks work once they land in Case Management.