What is Perpetual KYB?

  • Identity & compliance
  • Customer lifecycle controls
  • 3 min read

The short answer

Perpetual KYB uses continuing signals and review workflows to maintain business understanding between scheduled checks.

Perpetual KYB: why it matters

An onboarding or review decision can contain several different questions. Keeping this concept distinct helps the team assign the right evidence and decision owner, rather than rely on a single completed status.

How to assess it in practice

For perpetual kyb, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. Start by defining the question the team needs to answer. Identify the relevant record or evidence, check its scope and date, and retain the reasoning behind the result. If evidence conflicts, keep that conflict visible for review.

Worked example

Illustrative workflow: a team reviewing a business adds a separate check for perpetual kyb. The reviewer’s task is to for perpetual kyb, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. The outcome is recorded together with the supporting evidence; an unresolved question stays open rather than being converted into a positive result.

Illustrative scenario

A monitoring service covers registry changes but not a customer's new business purpose. Combine alerts with a route for collecting relationship information.

Distinctions that matter

Perpetual KYB belongs to the customer lifecycle controls topic family. Read Customer Acceptance Policy alongside it to understand the adjacent question. Each page has its own intended scope; shared context does not make the concepts equivalent.

Evidence and review output

Review these

  • Current relationship state
  • Policy and change triggers
  • Decision owner and completion evidence

The review should produce

A maintained relationship state with clear conditions for acceptance, continuation, restriction or closure.

Across this family

Lifecycle controls connect acceptance, changes, reassessment and exit. Define the responsibilities and completion evidence for each stage so an old approval is not reused for a materially changed relationship. Operational status should reflect conditions and unresolved issues that matter to the services being provided.

A note from practice

Continuous signals support perpetual KYB only when they feed an assessed and updated customer understanding. Define coverage gaps and fallback reviews because an event feed does not observe every relevant fact.

Limits and common mistakes

The practical boundary is important: For perpetual kyb, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. Do not substitute a related label for this check or assume that missing information is a negative finding. Source-specific and jurisdiction-specific rules require their own review.

Frequently asked questions

Which evidence should I review?

For this topic, focus on current relationship state, policy and change triggers, decision owner and completion evidence. The relevant source and dates should be retained with the finding.

How is Perpetual KYB different from Event-Driven Due Diligence?

Event-driven due diligence reassesses a relationship when a relevant change creates a new information need. The distinction matters because the evidence needed for that concept may not resolve the question addressed on this page.

What should the result of the review contain?

A maintained relationship state with clear conditions for acceptance, continuation, restriction or closure. Preserve material conflicts instead of replacing them with an unexplained success flag.

Continue learning

See the registry record behind every answer.

Primary, government-sourced data on 600M+ companies in 200+ countries, with full source attribution.