Start a customer application

Starting an application creates a controlled Draft, assigns its generated application reference, and initializes the selected onboarding workflow at its authorized initial stage.

Access required

You need Create Customer Application and access to the selected branch. L0 users who can operate across companies also select the company; tenant users create within their own company.

Branch-scoped users can select an accessible branch. Self-scoped users can access the application they create, while later access can also be established through a relationship-officer, agent, or active workflow assignment.

Before you begin

Complete Before onboarding the first customer. If the application should also request an Account, complete Before opening the first account.

Start the application

1. Open Customer Relationship → Applications.
2. Select New Customer. The screen is titled New Customer Application.
3. At L0, select the Company.
4. On Application, select the Customer Type and Onboarding Policy.
5. Enter First Name and Surname for an Individual, or the Corporate Name or Group Name for the other customer kinds.
6. On Assignment, select the Branch. Optionally select a Relationship Officer and Agent from that branch.
7. If KYC Profile appears, complete every required policy-driven field.
8. If Account Request appears, choose whether onboarding should open an Account after the Customer is created. Complete the Account details when the applicant chooses Yes, request an Account.
9. Review Application Summary, then select Start Application.

How the selections work

Customer Type and Onboarding Policy

The policy list contains active Authorized policies compatible with the selected Customer Type. The selected policy controls:

• the Workflow Definition used by this application;
• the KYC Policy and policy-driven profile fields;
• whether Customer creation is automatic on approval or completed manually afterward;
• related-party and Group-member rules;
• whether an Account request action is available for the selected application.

The summary card shows the resolved customer kind, workflow, KYC Policy, and Customer creation mode. Customer Type and Onboarding Policy cannot be changed after the application starts, so confirm both before continuing.

Branch and assignments

Branch is required. It is the application's operating branch and is used by data-access checks and workflow action rules. Relationship Officer and Agent are optional and are filtered to the selected branch. Changing Branch clears both assignments and any Account choice so that dependent options can be resolved again.

The Relationship Officer and Agent selected here are application ownership relationships. They do not replace workflow-stage assignment.

KYC Profile

The KYC Profile tab appears when the selected KYC Policy has data requirements. remoteEaze shows only facts that apply to the selected customer kind and the policy's conditions. Branch country, sector, and industry can change which facts apply. All applicable required facts must be completed before the Draft can be created.

Identity evidence is captured later in the KYC workspace when the policy requires it; it is not entered as initiation evidence on this form.

Optional Account request

The Account Request tab appears only when an authorized CREATE_CUSTOMER_ACCOUNT workflow action applies to the selected policy, Customer Type, Branch, and Customer creation mode.

Choose either Yes, request an Account or No, continue without an Account. For a request:

• Product and Currency are required;
• the Product must be an Authorized customer-facing, non-system Product;
• the Currency must be enabled for the company;
• Account Condition is optional and must match the Product and Currency;
• Account Name is optional; leave it empty to use the generated name;
• the Account inherits the application's Branch.

The Account is not created at this point. remoteEaze revalidates and freezes the applicable action, configuration, rules, Account status, and required approval count when the Customer Application is submitted.

Duplicate check

Before creating the Draft, remoteEaze checks the identifying values supplied at this point, such as email or phone, against existing Customers and open Customer Applications. Rejected, Closed, and Withdrawn applications do not count as open duplicate applications. A match prevents the new application from being started; open the existing record and confirm the correct operational action.

Expected result

remoteEaze opens the generated application reference. The Application status is Draft, the workflow is Draft, and the authorized initial stage is recorded. The application can now be corrected, submitted, or withdrawn.

Continue with Complete customer data, KYC, and requirements and Assign, review, and progress an application.