KYB onboarding
for Singapore.
Choose a workflow that can explain the business, its owners and the decision.
Evaluating KYB onboarding in Singapore? Work through the evidence, ownership gaps and review decisions behind a business application. Then use the demo scorecard to assess how WIDTH fits your operating model.
Do the application and company record agree?
What evidence explains the ownership chain?
Is it the same person, and who resolves it?
Which evidence supports the outcome?
What should a Singapore KYB workflow cover?
KYB onboarding should connect the business record, ownership and control, relevant people, screening evidence and review outcome. For a Singapore payment or fintech team, the buying question is whether that workflow handles your actual customers and exceptions—not simply whether it can retrieve a company record.
Define the relationship
Merchant acquiring, business accounts and corporate counterparties have different operating needs. Specify what the customer will do, where it operates and which information your policy requires.
Make gaps visible
Distinguish information received, independently checked, disputed and still missing. A submitted document and an accepted piece of evidence are different states.
Keep the rationale
The reviewer needs to see why a case was approved, escalated or declined, who made that decision and which evidence was available at the time.
This guide is for teams based in Singapore evaluating corporate onboarding, including customers incorporated overseas. It is not a checklist that makes every Singapore business subject to the same rules. For the core product offering, see WIDTH KYB Onboarding.
What ACRA information can—and cannot—resolve
A local workflow should distinguish company information from evidence about ultimate ownership and control. That distinction matters when the applicant has a corporate shareholder, conflicting documents or a recently changed structure.
| Evidence | What it helps establish | What remains to review |
|---|---|---|
| ACRA Business Profile | Basic entity particulars, such as UEN, name, registration date and information about position holders or owners. [1] | Reconcile the record with the application. Decide what additional evidence is needed for ownership, control and the proposed relationship. |
| ACRA Central RORC | ACRA’s database of registrable controllers. It is not available to the public. [2] | Ask what lawful sources a provider actually uses. A registry connection does not, by itself, demonstrate public access to this database. |
| Applicant’s ownership evidence | A declared structure and supporting material that can explain corporate parents and relevant individuals. | Check the chain against appropriate sources; investigate missing links, inconsistent names and control arrangements. |
| Screening and reviewer notes | The potential match, the information used to assess it and the reviewer’s conclusion. | Resolve identity uncertainty and document the reason for the outcome. A name match is not a finding of wrongdoing. |
ACRA sources describe the information products and access limits; the review suggestions are an evaluation framework. Applicable due-diligence controls depend on the activity, jurisdiction and relationship. The FATF Recommendations are an international framework, implemented through measures adapted to national circumstances. [3]
A Singapore merchant with an overseas owner
A fictional Singapore merchant applies to a payment provider. Its declared shareholder is an overseas company. An ownership chart reaches two individuals, but one supporting document is missing. A director’s name also produces a potential screening match.
The chart records a declaration. It does not establish verified beneficial ownership or determine who meets your applicable control criteria.
What a useful demonstration should show
- Keep entity identity separate from ownership. A matching Singapore record should not silently close the unresolved overseas link.
- Attach the missing request to the right party. The applicant and reviewer should know which evidence remains outstanding and who must provide it.
- Investigate the director match. Compare available identifiers, record the evidence and assign the decision to an authorised reviewer.
- Make the decision reproducible. Show the policy applied, remaining gaps, escalation and rationale for the final outcome.
This is an evaluation scenario, not a WIDTH customer result or an instruction to approve or reject a particular business. Relationship visualisation can add context; confirm the supported sources and workflow in a Graph Intelligence demonstration.
The review note should answer four questions
- What agrees?
- The application’s company identifiers match the evidence reviewed.
- What is unresolved?
- The overseas ownership link and one individual’s outstanding document.
- What action follows?
- Request specific evidence and assign the potential match for review.
- What supports the outcome?
- The evidence, policy and approval rationale retained with the case.
One platform. One workflow. One source of truth.
WIDTH is an All-in-One Compliance and Risk Decision Intelligence Platform. Its published KYB documentation describes corporate information, connected related parties, documents and forms within an asynchronous onboarding workflow. [4]
- 01 · ENTITY
Company information
Start with the corporate particulars for the application.
- 02 · PEOPLE
Related parties
Add directors, shareholders and beneficial owners to the corporate workflow.
- 03 · EVIDENCE
Documents and forms
Collect required material for the entity and related parties.
- 04 · CHECKS
Screening step
The documented flow includes an automatic screen check.
- 05 · OUTCOME
Decision step
Complete the configured process and its decision stage.
Test the workflow against your case
Use the scenario above to discuss evidence requests, reviewer access and exception handling. Confirm source availability, configuration, integration and commercial scope for your deployment.
See the WIDTH KYB product overview for the core offering, KYC Onboarding for individual verification and Case Management for investigation workflows. These are related capabilities to evaluate; their inclusion and configuration should be confirmed in the proposal.
What determines a KYB implementation timeline?
A useful implementation estimate starts with customer scope, collection journey, policy, integration and testing. Connecting software is one milestone; making a complete, reviewable business-customer decision is another. Ask for a plan that names the owner and acceptance evidence for each stage.
| Stage | Your team prepares | Acceptance evidence to request |
|---|---|---|
| 1. Define the first customer journey | Entity types, customer activity, incorporation and operating markets, expected volume and required checks. | A written scope showing supported cases, unavailable sources and the fallback when information cannot be retrieved. |
| 2. Map evidence and review policy | Entity/party requirements, document rules, ownership/control criteria, escalation and approval roles. | The missing-document and potential-match scenarios reach the correct reviewer without appearing complete. |
| 3. Connect collection and records | The applicant journey, reference identifiers, existing customer systems, access and handover requirements. | The entity, parties, documents and outcome can be reconciled to the correct application; retries do not create confusing duplicate cases. |
| 4. Run acceptance testing | Representative clean, incomplete, conflicting, layered-ownership and changed-information cases. | Each agreed scenario has a recorded result, an accountable owner and a resolved defect or accepted limitation. |
| 5. Pilot and release | A bounded first cohort, reviewer training, escalation contacts and fallback process. | The teams approve the release criteria, support arrangements and method for retrieving decision evidence. |
This is a planning framework, not a promised WIDTH delivery schedule. Separate vendor dependencies, your internal approvals and applicant response time when discussing dates.
Keep changes connected to the business record
Ask what happens when a director leaves, an ownership declaration changes or new screening information arrives. The useful outcome is a reassessed relationship with a traceable decision, rather than an alert that nobody owns.
Evaluate event-triggered and periodic review together. Confirm which events can be detected, which require customer input, and which sources and review intervals your policy relies on.
Replace one director in the test case
- Can the team identify what changed and when?
- Which party information and checks need updating?
- Who owns the follow-up and approval?
- Can the previous evidence and rationale still be retrieved?
These are acceptance questions. They do not assert that every change is automatically detected or that monitoring removes periodic-review obligations.
A KYB demo scorecard for your shortlist
Use the same fictional application with each provider. Record demonstrated, needs configuration, not demonstrated or out of scope, and add the evidence or next action. A promise on a slide is not a demonstrated result.
Record the results during your demonstration, add evidence and use the follow-up list to plan the next conversation. Print or save a PDF when you want a copy to share with your team.
Singapore KYB onboarding questions
Is an ACRA Business Profile enough for KYB?
It can support entity verification, but a company record does not by itself resolve the full ownership chain, connected-person checks, customer risk or the onboarding decision. Use it alongside the evidence and controls appropriate to your business relationship. ACRA’s information-products page describes what its Business Profile contains.
Can a KYB provider access Singapore’s Central RORC publicly?
No. ACRA states that its Central Register of Registrable Controllers is not available to the public. Ask a provider to identify the lawful sources behind its ownership information, rather than assuming that an ACRA connection grants access to that database.
Can a Singapore KYB workflow review foreign corporate owners?
It can be designed to include foreign corporate owners, but the available records, evidence and verification steps depend on the jurisdiction and provider. Ask the provider to demonstrate the relevant ownership chain, show source limitations and explain the process when information cannot be obtained.
Is one beneficial-ownership percentage enough for every case?
No single percentage should be assumed to resolve every ownership or control question. Your compliance team needs to define the applicable criteria for the activity, jurisdiction and relationship, including relevant control arrangements. Configure and test the workflow against those criteria.
How long does KYB onboarding implementation take?
There is no reliable universal duration without a defined scope. Collection, policy, integration, data availability, testing and internal approvals affect delivery. Request a phased plan with responsibilities and acceptance criteria, and distinguish implementation time from the time an applicant takes to supply evidence.
Does KYB monitoring replace periodic review?
Not automatically. Ask which events the service can detect and how reviewers reassess changed information. Event-triggered review and periodic review should be designed together around applicable requirements, customer risk and source availability.
How should we compare KYB software pricing in Singapore?
Compare the defined workflow and included services, not only a headline per-check price. Confirm entity and related-party checks, source charges, ongoing services, implementation and support. Request a proposal using your markets, volumes and exception scenarios.
What should we bring to a WIDTH KYB demonstration?
Bring a representative business application, ownership structure, required evidence, review policy and integration needs. Use fictional or appropriately anonymised examples. Work through the scorecard to confirm demonstrated behaviour, configuration needs, source limitations and commercial scope.
Bring your KYB case. Test the whole workflow.
Discuss how WIDTH’s corporate onboarding fits your entity types, ownership structures and review requirements. Leave the conversation with a clearer scope, rather than another list of features.
Prepare three things
- One straightforward and one complex customer case.
- Your evidence, escalation and approval requirements.
- The systems and team handovers the workflow must support.
See risk earlier. Decide smarter.
Sources and scope
Sources checked 3 November 2026. The worked case, review note, planning framework and scorecard are illustrative evaluation aids. They are not customer results, a regulator-approved checklist or a claim that every described behaviour is available in every WIDTH configuration. Confirm applicable obligations and deployment scope with the relevant teams.
- ACRA: Types of information products — Business Profile and other company-information products.
- ACRA: Central Register of Registrable Controllers — purpose and public-access limitation.
- FATF Recommendations — international framework and national implementation context.
- WIDTH KYB developer documentation — documented corporate onboarding stages. See also the KYB product overview.