Onboard a corporate customer

FlowSentry's client onboarding takes a new customer through capture, consent, identity checks, beneficial ownership, screening, risk and a decision, with a different person at each control point. This tutorial onboards a limited company. Individual customers follow the same path with fewer parties.

Before you start

• Client onboarding must be switched on for your institution. If you cannot see Applications under Customers, ask your administrator.
• Relationship manager (RM): captures the application.
• KYC reviewer: reviews it and sends it for approval. Risk managers, MLROs and Deputy MLROs can also review.
• Approver: a Senior approver, MLRO or Deputy MLRO approves or declines. High-risk approvals need step-up. The RM who captured the application can never approve it.

The application moves through these statuses: Draft → Submitted → In review → Pending approval → Approved (or Declined, or Withdrawn by the RM before review).

Part 1: The relationship manager captures the application

Start

1. Open Customers › Applications (/onboarding). The pipeline shows applications In progress, In review, Pending approval and Approved.
2. Select Start an application and choose the corporate journey your institution has set up. The application keeps the journey version it starts on, even if the journey changes later.

Capture the company's details

On Capture, fill in the company's details. Every change saves as you leave the field, so you can stop and resume at any time.

Record consent

On Consent, show the customer the Privacy notice and consent and select Record consent. FlowSentry records the notice version and your attestation.

Add the parties and run identity checks

On Parties and checks:

1. Add each party — the company itself, its directors, signatories and the individuals who own or control it — with their role and identifiers: national ID or passport for people, registration number and KRA PIN for the company.
2. Select Save party for each.
3. Run the identity checks your journey requires from each party's row — for example a national registry (IPRS), tax (KRA) or biometric check. Results show as Verified, Failed, Needs review or Pending. Inconclusive results, such as a face match below your institution's threshold, go to a KYC reviewer.

Map the ownership

On Ownership ("Ownership and beneficial owners"):

1. Select Add an ownership or control link for each relationship: who owns how much of whom (shares or votes), control by other means, or a nominee arrangement.
2. Attach evidence for each link, or attest to it where evidence is not available (for example Attest foreign layer for an overseas holding company).
3. Select Determine beneficial owners. FlowSentry calculates effective ownership through every layer — a 50% holder of a company that owns 40% of the applicant holds 20% — and marks each natural person who reaches your institution's beneficial-ownership threshold.
4. If no natural person reaches the threshold, choose Record senior managing official, as the regulations require.

Screen everyone

On Screening, select Screen all parties now. The company, its directors and its beneficial owners are screened against your lists in seconds. A potential match puts the application On hold until the hit is resolved in the screening workbench. If parties change later, the panel says so and you screen again.

Submit

Select Submit for review. You can Withdraw the application, with a reason, while it has not yet gone to review.

Part 2: The KYC reviewer checks it

1. Open the application from Applications or your notifications and select Start review.
2. Check each section: identifiers and identity check results, ownership evidence and attestations, beneficial owners and screening outcomes.
3. Clear any identity checks waiting in the IDV review queue (/onboarding/reviews) with Accept or Reject. You cannot decide checks on an application you captured.
4. On Risk and decision, select Preview risk. FlowSentry shows the band the customer would receive, the factors and their contributions, any floor rules that raised the band (for example, a foreign PEP among the beneficial owners forces High), and anything Outstanding before a decision.
5. If something is missing, select Return to RM with a reason. The application goes back to Draft for the RM to complete.
6. When the file is complete, select Send for approval.

Part 3: The approver decides

1. The approver opens the application from My approvals or their notifications. Its status is Pending approval.
2. They review the file, the risk preview and the reviewer's work.
3. They select Approve with an optional Decision note, or Decline with a Decline reason. Approving a high-risk application asks for step-up.

On approval, the customer is handed off into the customer register and, where your institution has connected it, to the core banking system. The customer is rated under your risk model; a High rating opens an EDD case. A declined application is recorded in the declined-business register.

Note: Approvers can also decline an application that is still in review if a serious issue emerges.

Part 4: After onboarding

• The customer appears on Customers (/customers) with their KYC status and risk band.
• Later changes to their KYC details are proposed and approved like any other KYC change. See Propose and approve a KYC change.
• If the customer's rating is High, the EDD checklist is worked on the EDD workbench (/risk/edd).

Related

• KYC and onboarding guide
• KYC reviewer, relationship manager and senior approver
• Review a screening hit