[Deprecated] Offboarding

Process Overview

The offboarding process is asynchronous and involves validation of entity and the reason.

Upon successful completion of the process, a notification is sent to the partner via a webhook call:

• Offboarding Notification

• Customer Notification

• Natural Person Notification

• Beneficial Owner Notification

• Proxy Notification

The offboarding process supports following types of entities:

• Legal entity customers

• Natural person customers

• Joint persons customers

• proxies

• beneficial owners

Regardless of the type, the sequence of actions for offboarding is similar. Partners are required to give the reason of the offboarding and then initiate the offboarding process.

Prerequisites

• The partner is responsible for closing all customer products before starting the offboarding.

Statuses

The offboarding process has the following statuses:

• INVALID: Process not started due to invalid data during offboarding initiation.

• CREATED: Offboarding created but not yet started.

• PENDING: Process started. For Immediate, this means offboarding execution is in progress. For Ordinary, the process waits for the scheduler to trigger execution two months after offboarding initiation.

• REJECTED: Offboarding rejected after process initiation.

• CANCELED: Offboarding canceled; cancellation is only possible for Ordinary offboarding.

• APPROVED: Offboarding completed successfully.

Closure Types

There are two closure types for Offboarding: Ordinary and Immediate. The closure type is derived from thereason field:

• Ordinary:

  • CANCELLATION_BY_PARTNER_ORDINARY

• Immediate:

  • CUSTOMER_REQUEST_IMMEDIATE

  • CANCELLATION_BY_PARTNER_IMMEDIATE

  • DEATH_IMMEDIATE

  • DISSOLUTION_IMMEDIATE

  • INSOLVENCY_IMMEDIATE

  • COMPANY_STRUCTURE_CHANGES_IMMEDIATE

Changes for Customer during process

During the offboarding process, the customer undergoes the following changes:

1. Temporary Status: OFFBOARDING

   • While the offboarding process is in progress, the customer is assigned a temporary status: OFFBOARDING.

   • This status prevents any new products from being added to the customer during the offboarding process.

2. Cancellation Date

   • The cancellation date is set for the customer in the following way:

     • For Immediate Offboarding:

       • The cancellation date is set to the date when the offboarding process begins.

     • For Ordinary Offboarding:

       • The cancellation date is set to two months after the offboarding initiation date, when the process is scheduled for execution.

Process flow

• Immediate:

  • All validations are performed immediately, and the offboarding is executed right away.

  • The customer's cancellation date is set to the date the offboarding execution begins.

• Ordinary:

  • Initial data correctness validations are performed, excluding checks for whether all customer products are closed.

  • The customer's cancellation date is set to two months after the offboarding initiation date.

  • The process waits for a scheduler to trigger the remaining validations and offboarding execution.

  • At the scheduler-triggered execution, all validations are rechecked, including verifying whether all customer products are closed.

  • If products aren't closed, the process remains in the PENDING status. Currently, process resumption isn't possible.

Validations

The offboarding process involves the following validations:

1. Entity Status Validation

   Before proceeding with the offboarding process, the system must validate whether the entity to be offboarded has an eligible status.

   The following statuses are allowed for customer offboarding:

   • ACTIVE

   • ESTATE

   • SUSPENDED

   • SUSPENDED_COMPLIANCE

   The following statuses are allowed for proxy offboarding:

   • ACTIVE

   • SUSPENDED

   • SUSPENDED_COMPLIANCE

   The following statuses are allowed for beneficial owner offboarding:

   • ACTIVE

   • SUSPENDED_COMPLIANCE

2. Entity Existence Validation

   The system must verify whether the entity that is being offboarded exists in the database.

3. Offboarding Reason Validation

   A valid offboarding reason must be provided for the entity being offboarded. The valid reasons are documented in the table below:

   Offboarding Reason	Natural Person Customer	Joint Person Customer	Legal Entity Customer	Proxy	Beneficial Owner
   CUSTOMER_REQUEST_IMMEDIATE	valid	valid	valid	valid	invalid
   CANCELLATION_BY_PARTNER_IMMEDIATE	valid	valid	valid	valid	invalid
   CANCELLATION_BY_PARTNER_ORDINARY	valid	valid	valid	invalid	invalid
   DEATH_IMMEDIATE	valid	invalid	invalid	valid	invalid
   DISSOLUTION_IMMEDIATE	invalid	invalid	valid	invalid	invalid
   INSOLVENCY_IMMEDIATE	invalid	invalid	valid	invalid	invalid
   COMPANY_STRUCTURE_CHANGES_IMMEDIATE	invalid	invalid	valid	valid (signatory)	valid

4. Custody type for left guardians related to customer of offboarded guardian

   The system must verify whether the custody type for left guardians related to the customer of the offboarded guardian is set to SINGLE_CUSTODY.

5. Proxy type validation

   The system must verify whether the proxy type is other than LIQUIDATOR.

6. Customer Products Status Validation

   The system must verify whether all customer products are in status: CANCELLED.

If any data is invalid during the validation stage, the offboarding process will set the status:

• INVALID if the process has not started.

• REJECTED if the process has already started.