This module will not be further enhanced. Support is limited to defect fixing only.

Introduction to Customer Infrastructure

This module enables the Financial Institutions to collect and record mandatory Legal Id documents and address details of the customers.

Customer and CRM

There are different types of legal documents that need to be submitted by the customer according to the type of customer (individual, corporate, professional), nationality and residence of the customer.

When the place is updated, the system also updates the postal code, governance and delegation accordingly.

The customer age is checked while creating the customer, and there needs to be a guarantor in case the customer is a minor or dependant.

The structure of the fiscal Id, which is provided by the customer during the onboarding process is validated.

The CMBASE.STATE, TNCUIN.DELEGATION.DETAILS and TNCUIN.POSTAL.CODE applications have been created to store the details of the governorates, delegations, places and postal code.

The TNCUIN.CUSTOMER.PARAM application has been created to check if the customer is minor or major, and check if the necessary relationship is updated if the customer is minor or dependent.

The Governorate, Delegation and Postal Code fields are mandatory only for local residents. These are drop-down, no input fields.

The following are the benefits of the Customer and CRM functionality:

• Ability to validate the required legal documents of the customer.
• Ability to update the postal code, governance and delegation when the place is updated.
• Ability to check if the customer is a minor, and when the guarantor is mandatory.
• Ability to post restriction for the customer if attaining the age of 18 until the legal document is submitted.

Garnishment Handling

In Tunisia, there is a practice of recording the garnishment order issued against the customer and freeze the funds from the customer accounts. The funds have to be frozen until the judgement is received from the court. The judgement can either be to release the funds to the debtor or make the payment to the creditor who raised the garnishment order against the debtor.

The saisie judiciaire can be defined as a legal procedure by which a creditor can collect what a debtor owes by initiating a legal action.

There are four types of saisie judiciaire:

• Garnishment.
• Conservatory garnishment.
• Wage garnishment.
• Administrative opposition, which is a procedure initiated by the Public Purse in order to recover payments over fines against a debtor.

The administrative opposition is notified to the bank by a bailiff who presents a notification report informing the bank of the procedure. The bailiff delivers the notification report directly to the central service of the bank's head office or to the agencies.

The requisition is notified to the bank by two different means:

• An explicit requisition request letter indicating the data of the individual or corporate subject to the requisition.
• A summons to the go to offices of the organisation requesting the requisition to collect the requisition information.

The functionality allows users to create garnishment orders and freeze the funds from the customer accounts and freeze deposits. Also, it allows users to block and unblock securities, the details being available in the SC.BLOCK.SEC.POS application.

The locked amounts in the accounts can be increased or decreased, and further on released and if the judgement is against the debtor then the locked amounts will be transferred to the internal account.

The following applications and enquiries have been introduced for this functionality.

• The TNCUIN.GARNISH.ORDER application is used to create and amend the garnishment order.
• The TNCUIN.GARNISHMENT.PARAM application is used to parameterise the details for the garnishment order.
• The TNCUIN.LOCK.DETAILS live application is used to store the details of the locked account details.
• The TNCUIN.LOCKED.DETAILS enquiry displays the list of locked amounts for the customer and the garnishment order.
• The TNCUIN.GARNISH.ORDER,INITIATION version is created to create an SJ and OA.
• The TNCUIN.GARNISH.ORDER,AMEND version is used to amend the amount and other fields for SJ and OA.
• The TNCUIN.GARNISH.ORDER,JUDGE.SUMMONS version is used to update the judgement, summons and decision details for SJ and OA.
• The TNCUIN.GARNISH.ORDER,OTHER.ASSET version is used to update the asset details and amount that has to be considered for locking.
• The TNCUIN.GARNISH.ORDER,REQUISITION version is used to store the information of the requisition received by the bank. Users can create two requisition records for the same customer and the same order number but with a new sequence.
• The TNCUIN.GARNISH.ORDER,AMEND.REQUISITION version is used to amend the requisition.
• The TNCUIN.GARNISH.OPEN enquiry is used to launch the two opening versions.
• The TNCUIN.GARNISH.AMEND enquiry is used to launch the other versions (TNCUIN.GARNISH.ORDER,AMEND, TNCUIN.GARNISH.ORDER,JUDGE.SUMMONS, TNCUIN.GARNISH.ORDER,OTHER.ASSET, or TNCUIN.GARNISH.ORDER,AMEND.REQUISITION).
• The TNCUIN.GARNISH.ORDER,INITIATION.NONCUST version has been created to store a SJ and OA for non-customers.
• The TNCUIN.GARNISH.ORDER,REQUISITION version has been created to store the information of the requisition received by the bank.
• The TNCUIN.GARNISH.ORDER,AMEND.NONCUST version has been created to amend the amount and other fields for SJ and OA for a non-customer.
• The TNCUIN.GARNISH.ORDER,AMEND.REQUISITION.NONCUST version has been created to amend the requisition.
• The TNCUIN.GARNISH.OPEN.NONCUST enquiry provides a drill down to the TNCUIN.GARNISH.ORDER,INITIATION.NONCUST and TNCUIN.GARNISH.ORDER,REQUISITION.NONCUST versions.
• The TNCUIN.GARNISH.AMEND.NONCUST enquiry provides a drill down to the TNCUIN.GARNISH.ORDER,AMEND.NONCUST and TNCUIN.GARNISH.ORDER,AMEND.REQUISITION.NONCUST versions.