Before onboarding the first customer

What this prepares

A permitted user can start a Customer Application, complete its configured KYC and workflow stages, and create the live customer without encountering missing policy or reference data.

Required before first use

• The company license is active. License creation already provisions the head office branch, base currency, standard ID sequences, default reference data, and the initial tenant roles.
• At least one active Customer Type exists for the kind of customer being onboarded: Individual, Corporate, or Group.
• An Authorized KYC Policy exists and is compatible with that customer kind.
• An Authorized Workflow Definition with owner type Customer Onboarding has an authorized initial stage and the stages, transitions, requirements, and actions needed by the intended journey.
• An Authorized Customer Onboarding Policy links the customer type, KYC policy, and workflow definition. If several policies apply to the same customer type, the user must be able to select the intended one; otherwise, configure an authorized default.
• The application branch exists and is within the maker's data-access scope.
• Every reference selected by the KYC and onboarding policies exists. This can include identity and document types, countries, sectors, industries, customer ratings, related-party roles, and group composition rules.

Configure these under Business Configuration → Customer Configuration, Identity & Compliance, and Workflow Configurations. See Customer configuration, Identity and compliance, Customer workflow policies, and Workflow definitions.

Access and operating roles

• The maker needs Create Customer Application and access to the selected branch.
• Users maintaining the application need Update Customer Application.
• Users routing or claiming stages need Assign Customer Application.
• Users making ordinary workflow decisions or creating the live customer need Process Workflow for Customer Application.
• Grant Waive Customer Application only to users expected to record an exception that the configured requirement or KYC check explicitly allows.
• Customer Application itself does not use L1, L2, or L3 maker-checker authorization. If onboarding creates an Account whose frozen approval count is greater than zero, provide the required Account checker authority for that separate Account lifecycle.

See Roles and permissions before testing with a non-administrator role.

Required only when using this feature

• If onboarding should request an account, configure the policy's Account post-action and complete the account readiness checklist.
• If a policy requires related parties or group members, configure the required roles, minimum and maximum counts, and whether each party must be an existing Customer or complete a linked Customer Application.
• If field agents will capture applications, also complete Before enabling Workbench and prepare the Customer module while online.

Verify the setup

1. Sign in as the intended maker.
2. Open Customer Relationship → Applications, then select New Customer. The resulting screen is titled New Customer Application.
3. Select the company when working at L0, then select a customer type. Confirm that the expected onboarding policy appears.
4. Select an in-scope branch. Confirm that the initial KYC fields change to match the selected policy.
5. Select Start Application and confirm that the controlled test application's reference is generated and its configured initial workflow stage is shown.

Do not use the standalone live-customer creation path as proof that onboarding is ready. The normal onboarding journey is the Customer Application and its configured KYC and workflow.