bdl-cdr · cdr centrale des risques. cdr ref. # cdr reference number. it is the unique...

BDL-CDR

USER'S GUIDE

Centrale des Risques

Version 1.0 December 2018

BDL-CDR-CRM-UG V1.0.docx

of 130

1 Index

1 Index ...................................................................................................................................................... 2

2 Introduction ........................................................................................................................................... 6

3 CDR Overview ........................................................................................................................................ 7

3.1 Definition and Acronyms ................................................................................................................... 8

4 Main Screen ........................................................................................................................................... 9

4.1 Common Header.............................................................................................................................. 12

4.2 Main Functions Menu ...................................................................................................................... 12

4.3 Operational Area ............................................................................................................................. 12

4.4 Navigation bar ................................................................................................................................. 13

4.5 Connection Status ............................................................................................................................ 13

4.6 Language Bar ................................................................................................................................... 13

4.7 Error messages ................................................................................................................................ 13

4.8 Log Out ............................................................................................................................................ 13

4.9 Paginator ......................................................................................................................................... 14

4.10 Select list .......................................................................................................................................... 14

4.11 Lookup List ....................................................................................................................................... 15

5 The work procedures on the BDL-CDR system are divided in three main groups: ............................. 16

5.1 Daily work procedures: .................................................................................................................... 16

5.1.1 Execute an inquiry request to get the CDR risk position of a client. ....................................... 16

5.1.2 Check BDL responses on the executed inquiry requests. ........................................................ 16

5.1.3 Send to BDL-CDR center a request to add a new name in the dictionary of names. .............. 16

5.1.4 Download the end of day files to integrate with the CDR 5.0 application. ............................. 17

5.1.5 Upload a bulk file of inquiry requests and execute them to get CDR risk positions. .............. 17

5.1.6 Run Reports. Described in APPENDIX B ................................................................................... 17

5.1.7 Reassignment of a dossier to another user of the CRM .......................................................... 17

5.2 Monthly work procedures ............................................................................................................... 17

5.3 Administration functions Described in 6.3 ...................................................................................... 17

6 List of Functions ................................................................................................................................... 18

6.1 Description of the functions available outside the process ............................................................ 19

6.1.1 Search Client Identity by using personal data ......................................................................... 19

6.1.1.1 Search Result: Physical Person as Beneficiaries .................................................................. 22

6.1.1.2 Search Result: List of possible Associates with minimum 5 matching fields with the search .

............................................................................................................................................. 22

6.1.1.3 Inquiry Details Single Counterpart (Physical Person) .......................................................... 23

6.1.1.3.1 Personal Information ..................................................................................................... 24

6.1.1.3.2 Risk Information ............................................................................................................ 24

of 130

6.1.1.3.3 Address information ...................................................................................................... 25

6.1.1.3.4 Sole proprietorship ........................................................................................................ 25

6.1.1.3.5 Inquiry History ............................................................................................................... 25

6.1.2 Prepare CDR number request (Physical Person) ..................................................................... 26

6.1.2.1 Create/Update Client Identity – Data Entry ........................................................................ 26

6.1.2.2 Create/Update Personal Information .................................................................................. 28

6.1.2.3 Create/Update Risk Information (Physical Person) ............................................................. 29

6.1.2.4 Create/Update Address Information (Physical Person) ...................................................... 29

6.1.2.5 Create/Update/Delete Sole Proprietorship ......................................................................... 30

6.1.2.5.1 Create/Update/Delete Sole Proprietorship – Details .................................................... 31

6.1.3 Search Client Identity by using company data ........................................................................ 33

6.1.3.1 Search Result: Moral Persons as Beneficiaries .................................................................... 34

6.1.3.2 Inquiry Details Single Counterpart (Moral Person) ............................................................. 34

6.1.3.2.1 Company Information ................................................................................................... 36

6.1.3.2.2 Risk Information ............................................................................................................ 37

6.1.3.2.3 Address information ...................................................................................................... 37

6.1.3.2.4 Physical Person Associates ............................................................................................ 38

6.1.3.2.5 Moral Person Associate ................................................................................................. 38

6.1.3.2.6 Inquiry History ............................................................................................................... 38

6.1.4 Prepare CDR number request (Moral Person) ........................................................................ 39

6.1.4.1 Create/Update Client Identity – Data Entry ........................................................................ 39

6.1.4.2 Create/Update Company Information ................................................................................ 41

6.1.4.3 Create/Update Risk Information (Moral Person) ................................................................ 41

6.1.4.4 Create/Update Address Information (Moral Person) .......................................................... 42

6.1.4.5 Create/Update/Delete Associate Relation – List ................................................................. 42

6.1.4.5.1 Create/Update/Delete Physical Associate – Details ...................................................... 45

6.1.4.5.2 Create/Update/Delete Moral Associate - Details .......................................................... 47

6.1.5 Search Client Identity by CDR number .................................................................................... 48

6.1.6 Create Dossier function ........................................................................................................... 49

6.1.7 Select Position Dates ............................................................................................................... 52

6.1.7.1 Position in sector ................................................................................................................. 53

6.1.7.2 Position with bank ............................................................................................................... 54

6.1.7.3 Position with others ............................................................................................................. 55

6.1.8 Client Position Report .............................................................................................................. 56

6.1.9 Prepare the New Name Request ............................................................................................. 60

6.1.10 Inquiry of Requests .................................................................................................................. 61

of 130

6.1.11 MES-TR management .............................................................................................................. 63

6.1.11.1 Upload bulk requests (MES-TR) ....................................................................................... 63

6.1.11.2 Manage bulk requests ..................................................................................................... 64

6.1.11.2.1 List of Errors button ..................................................................................................... 65

6.1.11.2.2 List of CDR Requests .................................................................................................... 67

6.1.11.2.3 Delete the selected file ................................................................................................ 68

6.1.12 Upload "MES-DR Risk" File by CRM ......................................................................................... 68

6.1.13 Download monthly return files ............................................................................................... 69

6.1.14 Download daily files from BDL ................................................................................................. 71

6.1.15 Inquiry Statistics on CRM User’s Process Workload ................................................................ 72

6.2 Description of the functions related to processes .......................................................................... 74

6.2.1 To Do List function ................................................................................................................... 74

6.2.1.1 Common functions .............................................................................................................. 77

6.2.1.1.1 Documents function ...................................................................................................... 78

6.2.1.1.2 Start Page function ........................................................................................................ 80

6.2.1.1.3 Decision Page................................................................................................................. 81

6.2.1.2 Specific functions ................................................................................................................. 84

6.2.1.2.1 CRM CDR Request PP/MP Process Flow ........................................................................ 84

6.2.1.2.1.1 Update CDR request ............................................................................................... 85

6.2.1.2.1.1.1 Personal Information ....................................................................................... 87

6.2.1.2.1.1.2 Risk Information .............................................................................................. 88

6.2.1.2.1.1.3 Address Information ........................................................................................ 89

6.2.1.2.1.1.4 Sole Proprietorship .......................................................................................... 89

6.2.1.2.1.1.4.1 Sole Proprietorship- Details ...................................................................... 90

6.2.1.2.1.2 Repeat the search ................................................................................................... 91

6.2.1.2.1.3 Print final Credit Report ......................................................................................... 93

6.2.1.2.1.4 Review Accepted cases ......................................................................................... 105

6.2.1.2.1.5 Review CDR Request ............................................................................................ 107

6.2.1.2.2 Dictionary Names Request Process flow ..................................................................... 110

6.2.1.2.2.1 Update New Names Request ............................................................................... 111

6.2.1.2.2.2 Review New Names Request ................................................................................ 112

6.2.1.2.3 Monthly Declaration Process flow .............................................................................. 113

6.2.1.2.3.1 Result of the Technical Validation ........................................................................ 114

6.3 Administration functions ............................................................................................................... 120

6.3.1 Auditing Log Report ............................................................................................................... 120

6.3.2 Assign Functions to Roles ...................................................................................................... 124

of 130

6.3.3 Management of Users to be used by the CRM...................................................................... 125

6.3.4 Assign Users to Groups in CRM ............................................................................................. 125

6.3.5 Reassignment of a dossier to another user of the CRM ........................................................ 128

7 APPENDIX A ....................................................................................................................................... 129

7.1 The Client Liabilities Positions ....................................................................................................... 129

8 APPENDIX B........................................................................................................................................ 130

8.1 List of reports ................................................................................................................................. 130

of 130

2 Introduction

The aim of this document is to help both the BDL members and MFI participating to use the New Centrale

Des Risques (BDL-CDR application).

This manual is intended to help the members of the Centrale Des Risques (CDR) to understand the concept of the New BDL-CDR application. The new application is based on a business process workflow module. The logic of the data entry and validation process of the client amounts will be performed through an integrated process managed entirely by the new system. This manual will provide the overall view of the application by showing:

the web page graphic layout;

the list of all the functionalities provided differentiated by in/out or in the processes managed by the workflow

the list of the managed data and information;

the description of the logical and functional controls;

the users and roles management.

of 130

3 CDR Overview

The Centrale Des Risques is an intermediate information centre between the banks and financial institutions, in which they interchange information permitted by the Code of Money and Credit about their clients' credits. Through this module, the Banks and Financial Institutions will be mainly able to:

perform inquiries on the positions of existing CDR clients;

execute requests and monitor the received responses in order to update the proprietary IT system with reference to: the data entry of New Clients ID Information (with attached Documents); update the information of existing CDR Clients (with attached Documents); Confirm the information of existing CDR Clients (with attached Documents).

Send monthly declaration of the CDR position and receive the Response files from the Central Bank with Data referred to the overall Banking Sector.

The operational activity of the business users will be performed following two main process flows available

in the CDR Internal System:

1. Daily Process flows, in order to manage the ID Client Information and get and/or update the CDR Number to be used during the Monthly Declarations and to inquire for clients risks.

2. Monthly Process flow, in order to declare the Client Positions in the overall Banking Sector.

In specific cases the application will also provide reports mainly referred to client positions, technical validation and auditing, the overall list is shown in the appendix.

of 130

3.1 Definition and Acronyms

BDL Banque Du Liban.

MFI Member of Financial Institutions.

FSI Financial Sector Institution. It identifies any Bank, Financial Institution, Leasing

Company, Brokerage Company, Comptoires etc.

CDR Centrale Des Risques.

CDR Ref. # CDR Reference Number. It is the unique identification number assigned by the

Centrale Des Risques to each Beneficiary (physical or moral person) and

Guarantors.

Counterparty Any Physical Person or Moral person that may be reported by a CRM to the BDL

either as a beneficiary of a Direct or Indirect Risk or as an Associate of a given

Beneficiary or as a Guarantor.

CRM FSI member of the CDR service.

Dossier It is the electronic file created by the system used by the CRM to send a request

for creating/updating a CDR Reference # or to submit the monthly declaration. It

will be available in a dedicated section of the main menu, named “To Do List”.

MIS Management Information System.

PP Physical Person (Individual).

MP Moral Person (Societé). It includes companies Societé de fait, government

entities, financial institutions, etc.

UID User Identification code.

of 130

4 Main Screen

Each time you need to access the BDL-CDR system you have to execute the following steps:

1) Insert the Smart card into the Reader and wait till the green led light on the reader stops blinking and

becomes off.

2) Launch the “VPN software” from: "Start All Programs Cisco Cisco Any Connect Secure Mobility

Client Cisco Any Connect Secure Mobility Client". This will prompt the following screen

3) Type or select the following: BDL-PROD-VPN and press "Connect".

4) Then you will be prompted to enter your PIN code. Enter your PIN and click "Ok" to proceed.

5) Then you will be prompted to select the authentication group as follows: Click "Ok" to proceed.

of 130

6) Wait till the VPN is established When the connection is established a lock sign will be visible as a

notification in the notification area of windows taskbar.

7) Then open your browser and type the following URL:

https://prd.sebil.bdl.gov.lb/cdrprod

8) You will be prompted to enter your PIN code. Enter your PIN and click "Ok" to proceed.

If your log-in is successful, you will be directed to BDL-CDR Landing Page from where you can start working

by selecting a macro function from the menu bar.

PRD-AnyConnect

of 130

The structure of the BDL-CDR main screen is based on the following components:

1. Common Header;

2. Macro Functions Menu/ Macro Functions Submenu;

3. Operational Area.

Macro

Functions

Submenu

Macro

Functions

Menu

Operational

Area

Common

Header

of 130

4.1 Common Header

The following header is available on Top of all screens of the application:

The information displayed in the screen header is the following:

On the left side: - The name of the User logged in; - The CRM member’s name; - The branch member’s name.

On the right side: - User log-in time (hh:mm:ss) ; - Consolidated Position dd/mm/yyyy: The date of the most recent situation date loaded into the

system; - Under Preparation dd/mm/yyyy: The current situation date for which the CRMs could send

positions.

4.2 Main Functions Menu The BDL-CDR operational menu will be generated according to the roles assigned to the user based on the configured profiles, the system will display on the Main Menu the following list of the macro functionalities that the user is able to perform according to:

a) Main Macro Functions Menu:

Every time a user clicks on a macro function available in the Main Menu Bar, on the left part of the screen

the system will display the related (configured) functions/activities that could be performed:

b) Submenu (based as example of Monthly Declaration macro function):

4.3 Operational Area

If a function requires a set of steps to complete, all the performed steps will be displayed in the Navigation

bar.

of 130

4.4 Navigation bar

With this bar the user could navigate and see the results of each performed activity, it will be possible to navigate between the previously visited pages of the application (bread crumbs) located just below the Main Menu. The "backward" and "forward" buttons of the browser should not be used for navigation. Example:

4.5 Connection Status

The rounding wheel available at the upper right side of each screen indicates the connection status between the workstation and the host server and indicates also that the system is running to execute the requested transaction. While running, the user is requested to wait until the system displays the requested page without clicking or press any button.

4.6 Language Bar

The user can choose their preferable language either English or French to view the layouts of the

application by clicking on one of option available:

4.7 Error messages

The system will validate data entered in specific fields. If the data contains error, a red error message (explaining the problem) will be displayed at the upper left side of the screen:

4.8 Log Out

To exit the BDL-CDR application, just press the button at the upper right side of the screen.

of 130

4.9 Paginator

In case the result of a request returns many rows that cannot be displayed in a single page, the system provides a multiple page form and the following paginator on the bottom part of the screen that allows the user to move forward and backward along the available pages:

This button is used to move forward one page;

This button is used to move backward one page;

This button is used to move to the last available page;

This button is used to move to the first page. The number of rows displayed for each page is 10. According to the search criteria that are applied by the user, if the results of the search contain a big number of rows, the system will limit them according to a parameter configured by the administrator of the application.

4.10 Select list

When it is necessary to assign/select a list of values referred to a field on the screen, a "Select" button is provided next to the field. By clicking on this button the following “Select List” popup will be displayed containing all the possible values that the user can select. Example of selection of users:

The left side of the popup contains the list of all available values for the concerned field. The values can be composed of:

Code and description sorted in ascending order by the code value;

Description only sorted alphabetically in ascending order.

of 130

The user can choose a single value or multiple values (not necessarily contiguous) by clicking on the appropriate line. With the following Buttons, it will be possible to:

- Move the value from the available list to the selected list;

- Move “all” values from the available list to the selected list;

- Move back “all” values from the selected list to the available list;

- Move back the value from the selected list to the available list. By double clicking on the value in the available list, the value will be moved into the selected list (right side). It is possible to perform the other way around.

With the button the value/values that are presented in the selected list will be considered as criteria for the selected field. If the user did not choose any items and press the “OK” button the system considers that all the values will be fetched.

With the button the user can discards the chosen selections.

4.11 Lookup List

For some fields related to predefined values in the database, the application provides a lookup button that displays a pop up list of all the available values. The user can restrict the contents of the list by writing the first few letters of the word in the field before pressing the lookup button.

of 130

5 The work procedures on the BDL-CDR system are divided in three main groups:

Daily work procedures

Monthly work procedures

Administrative functions

5.1 Daily work procedures:

5.1.1 Execute an inquiry request to get the CDR risk position of a client.

To execute the inquiry request of a client, the CRM user starts the transaction by searching for the concerned client in the CDR database. The client, that the CRM user is searching for, may or may not exist in CDR DB.

Based on the result of the search, the CRM user will have the possibility either to create a request for a new client or a request to update the information for an existing client.

Once the CRM user confirms the creation of the Request, a dossier is created in his “To Do List”.

At This stage, the BDL-CDR system allows the CRM user to print a provisional report of the client’s credit risk positions.

The CRM user has to open his To Do List to upload the required documents. Then the CRM user has to send the dossier to BDL-CDR center by confirming his decision in the “Decision Page”. Therefore the Dossier will be moved to the next stage of the workflow and it will disappear from his To Do List.

If the initiator of the dossier has the role of a supervisor, the dossier will be forwarded directly to BDL-CDR center. If the initiator of the dossier has the role of an officer, the dossier will be sent to his supervisor for validation who will forward it to BDL-CDR center.

The user at BDL-CDR center will process the request and send the Request answer to the initiator CRM user and it will appear in his To Do List. The request answer cases are either accepted so the CRM user will print the “Final Repot” or rejected so the CRM user will review the reason of the rejection and take a decision either by re-submit the request or cancel it.

5.1.2 Check BDL responses on the executed inquiry requests.

The CRM user has to check periodically his “To Do List” that contains:

Uncompleted requests

Requests returned from his supervisor and need to be checked.

Processed requests received from BDL-CDR center.

5.1.3 Send to BDL-CDR center a request to add a new name in the dictionary of names.

The CRM user has the capability to ask for a new name to be added in the dictionary of names :

To add a mandatory name the user by “ Prepare a request for a new name “ and send the request

to BDL-CDR center. Or the user can ask for a new name to be added in the dictionary of names by

filling it as forced text and send the request to BDL-CDR center.

of 130

5.1.4 Download the end of day files to integrate with the CDR 5.0 application. The CRM User is able to download the Files (COM_ID , COM_RQ , COM_PN ) prepared by BDL-CDR center to be imported into their system. (described in 6.1.12 Download daily files form BDL)

COM_ID file : it contains the answers to requests received from the CRM user and processed in BDL during the period from the previous preparation date till the date of preparation of the current file.

COM_RQ file : it contains the requests received from the CRM user during the period from the previous preparation date till the date of preparation of the current file.

COM_ PN file : it contains the requests received from the member and still pending in BDL as on the date and time of the preparation of the file.

5.1.5 Upload a bulk file of inquiry requests and execute them to get CDR risk positions.

This activity is described in 6.1.11 MES-TR management

5.1.6 Run Reports. Described in APPENDIX B

5.1.7 Reassignment of a dossier to another user of the CRM

The uncompleted dossiers in the To Do List of any CRM user can be reassigned to any other CRM

user by the user who has the role of “CRM WORKFLOW ADMINISTRATOR”. described in 6.3.5

5.2 Monthly work procedures Upload the Monthly Declaration file to send it to BDL . described in 6.1.12

Download the Monthly Declaration returned files from BDL. described in 6.1.13

5.3 Administration functions Described in 6.3 Activation of a user on BDL-CDR system .

Assign users to groups.

View all groups and their related functions.

of 130

6 List of Functions

From a logical point of view, all the available functionalities provided by the system can be classified in the

following types:

1. The list of functions that the business user can execute directly from the main and sub menu:

a) Inquiry

Client Inquiry

Search Client Identity by using personal data (Physical Person)

Search Client Identity by using company data (Moral Person)

Search Client Identity by CDR Number

Prepare a New Name Request

Inquiry of Requests (this is related to the to do list functions)

MES-TR PROCESS

Upload "MES-TR" File by CRM

List Status of the MES-TR file loading

MES-TR Technical Validation list of errors

MES-TR Technical Validation Errors Details

MES-TR list of Requests to be created

b) Download

Download Daily Files from BDL

c) Monthly Declaration

Download

Download Monthly Files from BDL

Upload

Upload "MES-DR Risk" File by CRM

d) Reports

CDR Inquiry Statistics

Statistics on CRM User’s Process Workload

2. Concerning the description of the functions that the user can execute when performing the

operational activity through the designed business processes handled by BDL-CDR, the function list

is divided into: common (always available) and specific (dedicated to specific process).

List of common functions available for every stage of the processes:

Flow

Documents;

Start Page;

Decision Page.

of 130

List of specific functions available according to the different stages of the managed processes:

Update CDR request (CRM CDR Request PP/ CRM CDR Request MP);

Repeat the search (CRM CDR Request PP/ CRM CDR Request MP);

Print final Credit Report (CRM CDR Request PP/ CRM CDR Request MP);

Review accepted cases (CRM CDR Request PP/ CRM CDR Request MP);

Review CDR request (CRM CDR Request PP/ CRM CDR Request MP);

Update New Names Request (Dictionary Names Request);

Review New Names Request (Dictionary Names Request);

Result of the Technical Validation (Monthly Declaration).

3. Concerning the Administrative functions, here follows the list:

6.1 Description of the functions available outside the process

6.1.1 Search Client Identity by using personal data

Here follows the screen provided to the CRM user in order to perform the search using personal data of the

client.

In order to search for a "Physical Person", the use has to fill all the mandatory fields marked with a “*”,

which are:

of 130

Client branch;

Inquiry purpose.

In case the user selects inquiry purpose = “declaration to CDR” or “update customer information”

(purpose = 0), he will not able to view and print the client position.

In other remaining cases (purpose = 1), the user will be able to view and print the client position.

Furthermore, the system will show the list of possible associates from the CDR database, according

to the criteria specified into the search transaction. The following message is displayed at the

bottom of the page: “In order to show the list of moral persons in which the physical person you are

searching for is an associate, you have to fill at least 5 searching criteria fields”.

Gender;

Family Name: Client Family Name (Mandatory). Filling, also partially this field and click on all

names available in dictionary will be shown, the user can select one of them;

First Name: Client First Name (Mandatory) also for this field the same rules of the previous one are

applied.

If the values for the Mandatory fields “Family Name” and the “First Name” are not defined in the

dictionary of names the error message “The Name has no correspondence in the dictionary” will be

displayed, and in this case the user has to start a new process in order to send to BDL a request of new

names using another specific entry menu “prepare request for a new name”. After the new names have

been created by BDL, the user can continue preparing the CDR New Number Request.

The remaining fields on the screen are optional, but it is highly recommended to fill them so that the user has a higher chance of getting the client he is looking for at the top of the search result list:

Father’s Name: Client father’s name can be selected from the dictionary of names, and if it is not

found, the value will not be accepted;

Mother’s Name: Client mother’s name can be selected from the dictionary of names, and if it is not

found, the value will not be accepted

Year of Birth: numerical;

Register Number: numerical ;

Place of Registration: Register Location, if it is not defined in the dictionary of addresses the value

will not be accepted.

For the Non Mandatory fields, the names also must be compliant with the dictionary of names maintained

by BDL. By using the Lookup button, the list with the existing names set by BDL is displayed and the

user can select the right one. In case a name is not registered in the dictionary of names, the user has to

delete the filled names and start a new search. For this reason, if the above scenario happens, the button

“Prepare a Request for New CDR Number” WILL NOT be enabled.

In order to show the list of possible associates, the following rules will be applied in order to calculate the

matching fields. The user must at least enter four matching mandatory fields

Gender;

Family Name;

First Name;

Father Name.

Plus, at least one additional match in one of the following fields:

of 130

Mother Name;

Year of Birth;

Registration Number (excluding the not numeric and not alphabetic characters).

After insertion of the above fields, it will be possible to click on button.

If the search does not provide any result, the following message will be displayed:

If no beneficiary clients are found: “No Beneficiary Clients found”.

If no associates are found:

“No Associates with 5 matching fields found”- if no associate clients with at least 5 of the above

search criteria are found in the CDR database;

“No enough search criteria fields to show the list of possible associates”- if at least 5 of the above

mandatory search criteria have not been filled by the user.

A dedicated button “Prepare a Request for New CDR Number” will be available to start the data entry to

create a new request.

If some results are found, the system will show a list of matching clients from the CDR database, by using

the following functions:

“Search result - Physical persons – Beneficiaries” (Client Identity list – PP as Beneficiary:

“Beneficiaries” tab);

“Search result - Physical persons – Associates” (List of possible Associates with minimum 5

matching fields with the search criteria: “Associates” tab.

The following scenarios may occur:

1. no beneficiaries are found and one or more associates are found: the “Search result - Physical

persons – Associates” is displayed and the message “No beneficiary clients found” is shown;

2. one or more beneficiaries are found and no associates are found: the “Search result - Physical

persons – Beneficiary” is displayed and the following messages are shown:

“No Associates with 5 matching fields found”- if no associate clients with at least 5 of the

above search criteria are found in the CDR database;

“No enough search criteria fields to show the list of possible associates”- if at least 5 of the

above search criteria have not been filled by the user.

3. Some Beneficiaries and Associates are found. The “Search result - Physical persons – Beneficiary”

and “Search result - Physical persons – Associates” are displayed, with the initial focus on the

“Beneficiaries” tab.

If none of the records or rows match with the client the user is inquiring about, the button “Prepare a

Request for New CDR Number” will be available to start the data entry to create a new request of CDR #.

of 130

6.1.1.1 Search Result: Physical Person as Beneficiaries

This function will display the result of the search by using personal data. It will show a list of beneficiary

clients that match with the search criteria.

The user has to select the client whose personal information matches the one he is looking for. Once a

client is selected the system will show the client details screen as defined in the CDR external database, by

using the “Inquiry Details Single Counterpart PP” functionality.

6.1.1.2 Search Result: List of possible Associates with minimum 5 matching fields with the search

of 130

This function will display the result of the search by using personal data, it will show a list of possible

associate clients with minimum 5 matching fields corresponding to the searching criteria, the total number

of matching fields will be shown in the first column.

For each row, the following additional information (indicators) will be provided for the moral persons with

whom the client might be an associate:

# cor.: total number of matching field;

Active Credits: Y/N - to indicate if the moral person in the list has at least a position loan in at least

one active situation date present in the CDR External DB;

Our Client: Y/N - to indicate if the moral person is a Client of the requesting bank or not (in the last

active situation date).

The possibility to click on the row in order to see the detailed data of the beneficiary moral person with

who that client might be a possible associate IS NOT enabled to the user.

6.1.1.3 Inquiry Details Single Counterpart (Physical Person)

This function will display the detailed data of the client. It will be available in case the user finds the client in

the above list of existing beneficiary clients and clicks on the related row.

The information related to a Physical Person is distributed within 4 tabs: "Personal Information", "Risk

Information", "Address Information", "Sole proprietorship". In case the purpose of the request allows the

printing of the risk position (the value of the inquiry purpose type is equal to 1) the “Inquiry History”

additional tab will be displayed.

By clicking on each tab, the system will display the following detailed inquiry pages (all information is read-

only). If the information of a certain tab is not available in the DB, the complete tab is hidden. If no inquiries

are present in the history, the tab will be displayed with the message “No CRM has inquired about this

client”.

On top of the page the following information is provided (read-only):

CDR Number;

Name;

Date of Birth;

Register.

The user has to press the “Prepare a Request for CDR Number” button in order to create the Request for

Validation or the request of Update and send it to BDL.

of 130

6.1.1.3.1 Personal Information

The page below displays the personal information of a Physical Person.

6.1.1.3.2 Risk Information

The page below displays the client risk information.

of 130

6.1.1.3.3 Address information

The page below displays the client address information.

6.1.1.3.4 Sole proprietorship

The page below displays the list of the Companies linked to a Physical person as a Sole proprietor.

6.1.1.3.5 Inquiry History

This function displays the client’s position inquiries that have been executed by any CRM during a pre-

defined period of time excluding the inquiries executed by the same CRM user during the defined period

and the inquiries executed by BDL not on behalf of a CRM.

of 130

The function displays: the date (Calendar date) on which the inquiries have been executed, the purpose that has been selected at the time of executing the inquiry and the number of the inquiries that have been executed on that date. The data is displayed by descending order of the inquiry date.

6.1.2 Prepare CDR number request (Physical Person)

By clicking on “Prepare a Request for CDR ID Update” (in case of existing client) or “Prepare a Request for

New CDR Number” (in case of new client) the system will allow the user to start the data entry in order to

create the dossier. Here follows the list of related functions.

6.1.2.1 Create/Update Client Identity – Data Entry

The data previously used in the search page will be auto-populated and protected.

On top of the page the following information is provided (read-only):

Client not found (create a new CDR): the search criteria will be displayed as a reminder:

- CDR Number (Empty);

- Name: Family name, First name – Father name (mother name);

- Date of Birth;

- Register: register number + register place.

Client found (update or validate CDR data): the existing data will be displayed on top of the screen:

CDR Number;

Client Name: Family name, First name – Father name (mother name);

Date of Birth;

Register: register number + register place.

Also in this case the information of a Physical Person is distributed in the following four tabs and can be

edited by the user: "Personal Information", "Risk Information", "Address Information", "Sole

proprietorship".

In order to allow the user to manage the tabs that are mandatory to complete the data entry, different

colors will be used by the system:

of 130

a. Each tab folder can have two different colors: white color to be used when the folder has been

visited and grey color when the folder has not yet been visited;

b. Every time the focus is on a specific folder, its label becomes blue and the label of the other ones

becomes black;

c. Every time a folder is visited, its color becomes white;

d. When all the tabs are colored with white color, then the button to go create the dossier will be

enabled (because it means that the user has checked all the data).

The first three tabs are mandatory (marked with a “*”). The fourth one "Sole proprietorship" is mandatory

only when the legal form of the beneficiary is "individual firm" (code: 21).

of 130

6.1.2.2 Create/Update Personal Information

In order to create or update the personal information of a Physical Person, the user has to complete the

data entry referred to the mandatory fields and then move to the next page.

The data of the grey fields (i.e. in the above screen, the gender, family name and first name) cannot be

updated since the user gets the result of the client search based these criteria.

The data entry of the names must be compliant with the dictionary of names maintained by BDL. By using

the Lookup button , the list with the available options configured by BDL is displayed and the user can

select the most appropriate one.

In case a name is not available in the dictionary of names, the system allows the user to key-in the names,

by using the “Free Text” button .

The requests, for which there are forced names, will be moved in a specific stage of the process managed

by BDL user authorized to verify the request of a new name(s) and update the dictionary of names.

Both values, Latin and Arabic, for the same field must be filled as forced free text or as dictionary names.

One inserted as free text and the other selected by the lookup is not allowed.

If a free text has been forced, in Latin or in Arabic, the free text value is accepted only if it is not present in

the dictionary of names, otherwise an error message will be displayed.

By pressing the button “Undo Update” the data entered only in this page will be deleted and the original

data previously used by the system will be restored.

of 130

6.1.2.3 Create/Update Risk Information (Physical Person)

The user has to complete the data entry and then move to the next page.



6.1.2.4 Create/Update Address Information (Physical Person)


In case the address is not available in the dictionary of addresses, the system allows the user to key-in the

names, by using the “Free Text” button .

of 130

The requests of forced addresses will be moved to a specific stage of the process managed by BDL user

authorized to verify the request of a new address and update the dictionary of addresses accordingly.

Both values, Latin and Arabic, for the same field must be filled as forced free text or as dictionary

addresses. One inserted as free text and the other selected by the lookup is not allowed.


the dictionary of addresses, otherwise an error message will be displayed.



6.1.2.5 Create/Update/Delete Sole Proprietorship

With this function the system allows the CRM user to insert (create), update or delete data referred to Sole

Proprietorships of a given Physical Person.

In case of existing CDR client, the system will display the list of the already existing Sole Proprietors

associated to the selected Client, if any.

In case of new client or exiting client with no already linked Sole Proprietors, the list will be empty and the

message “There are no Sole Proprietorships” will be displayed.

For each row, the following information is displayed:

Company Name;

Foundation Date;

Register of commerce Number;

Register of Commerce Place;

Legal Form.

of 130

The user has the following options:

Select a row from the list and click on “Update/Delete Sole”: to update or delete the data of the linked Proprietorship. The system will prompt the “Create/Update/Delete Sole Proprietorship – Details” page with the data of the Proprietorship to update or delete the company detailed data. This action will be allowed for each Sole Proprietorship selected from the list (one by one);

Click on “Create Sole”: to insert a new link with a Company. The system will prompt the “Create/Update/Delete Sole Proprietorship – Details” page to register the detailed data of the new company.

By pressing the button “Undo Update” the data entered in this page will be deleted and the original data

previously used by the system will be restored.

6.1.2.5.1 Create/Update/Delete Sole Proprietorship – Details

In case the user clicks on update/delete Sole the following screen will be shown:

Scenario A: Layout “Update/Delete Sole Proprietorship”

Scenario A: the user has pressed the button “Update/Delete Sole”.

1. The function will display the detailed data of the selected Sole Proprietorship;

2. The user can update all the data displayed in the form;

3. The following actions will be available to the user:

a. Click on “Modify” button to save the request of modification of the client data displayed in the form and go back to the list. The related relation record will remain in the list of the Sole Proprietorships;

b. Click on “Delete” button to delete the selected Sole Proprietorship;

c. Click on “Undo Update” button to restore the original data previously displayed;

d. Click on “Back to List” button to go back to the List. All the modifications (if any) done on the client data will be lost.

of 130

In case the user clicks on create Sole the following screen will be shown:

Scenario B: Layout “Create Sole Proprietorship”


data found will be restored.

According to the button pressed in the page Sole Proprietorship – List, the following scenario may occur:

Scenario B: the user pressed the button “Create Sole” – after having selected “individual firm” in the legal

form field at the “Personal information” tab.

1. The function will display all the fields empty;

2. The user can insert all the data in the form;


a. Click on “Add” button to save all the data entered in the form and go back to the list. The new client record will be added to the list with the link with the CDR Client;

b. Click on “Undo Update” button to restore the empty data previously displayed;

c. Click on “Back to List” button to go back to the List. All the modification (if any) done on the client data will be lost.

of 130

6.1.3 Search Client Identity by using company data

Here follows the screen provided to the CRM user in order to perform the search using company data of

the client.

In order to search for a "Moral Person", the user has to fill the mandatory fields marked with a “*”, which

are:

Client branch;

Inquiry purpose.

In case the user selects inquiry purpose = “declaration to CDR” or “update customer information”

(purpose = 0), he will not be able to view and print the client position.

In other remaining cases (purpose = 1), the user will be able to view and print the client position.

Furthermore, the system will show the list of possible associates from the CDR database, according

to the criteria specified into the search transaction. The following message is displayed at the

bottom of the page: “In order to show the list of moral persons in which the physical person you are

searching for is an associate, you have to fill at least 5 search criteria fields”.

Company Name: it is the name of the company, only the Latin character will be accepted. It could

be possible to use the '*' character to search for partial names.

The remaining fields on the screen are optional, but it is highly recommended to fill them so that the user will get the company he is looking for at the top of the search result list:

Legal Form: it is the legal Form of the company, and it should be chosen from the drop list click on

button;

Foundation Year: it is the year in which the company was established;

Reg. of Commerce Number: it is the Chamber of Commerce Registration Number of the company.

The search function has to allow to use “*” as a wild character;

Reg. Commerce Place: it is the place in which the Company was registered. It could be possible to

select one from the drop list clicking on the button.

During the search if the fields "Reg. of Commerce Number" and "Reg. Of Commerce Place" are filled the

mandatory filed “company name” can be left empty.

of 130

After insertion of the above fields it will be possible to click on button.

If the search does not provide any result the message “No Clients found” will be shown.

A dedicated button “Prepare a Request for New CDR Number” will be available in order to start the data

entry to create a new request.

If some results are found, the system will show a list of possible matching clients from the CDR database

through the “Search result - Physical persons – Beneficiaries” (Client Identity list – Physical Person as

Beneficiary: “Beneficiaries” tab).

6.1.3.1 Search Result: Moral Persons as Beneficiaries

This function will display the result of the search by company data. It will show a list of beneficiary clients

that match with the search criteria.

The user has to select the client whose company information matches the one he is looking for. Once a

company is selected the system will show the company details screen as defined in the CDR external

database, by using the “Inquiry Details Single Counterpart (Moral Person)” functionality.

6.1.3.2 Inquiry Details Single Counterpart (Moral Person)

This function will display the detailed data of the company. It will be available in case the user finds the

company in the above list of existing beneficiary clients and click on the related row.

The information related to a Moral Person is distributed within 5 main tabs: "Company Information", "Risk

Information ", "Address Information", "Physical Associate" and “Moral Associate”. In case the purpose of

the request allows the printing of the risk position (the value of the inquiry purpose type is equal to 1) an

additional tab “Inquiry History” will be displayed.

By clicking on each tab, the system will display the following detailed inquiry pages (all information is read-

only). If the information of a certain tab is not available in the DB, the complete tab is hidden. If no inquiries

are present in the history, the tab will be displayed with the message “No CRM has inquired about this

client”.

of 130

of 130

On top of the page the following information are provided (read-only):

CDR Number;

Company Name;

Foundation Date;

Register.

The user has to press the “Prepare a Request for CDR Number” button in order to create the Request for

Validation or the request of Update and send it to BDL.

6.1.3.2.1 Company Information

The page below displays company information of a Moral Person.

of 130

6.1.3.2.2 Risk Information

The page below displays the company risk information.

6.1.3.2.3 Address information

The page below displays the company address information.

of 130

6.1.3.2.4 Physical Person Associates

The page below displays the list of the Physical Associates linked to the selected company.

6.1.3.2.5 Moral Person Associate

The page below displays the list of the Moral Associate linked to the selected company.

6.1.3.2.6 Inquiry History

This function displays the client’s position inquiries that have been executed by any CRMs during a pre-

defined period of time excluding the inquiries executed by the same CRM user during the defined period

and the inquiries executed by BDL not on behalf of a CRM.

of 130

The function displays: the date (Calendar date) on which the inquiries have been executed, the purpose that has been selected at the time of executing the inquiry and the number of the inquiries that have been executed on that date. The data is displayed by descending order of the inquiry date.

6.1.4 Prepare CDR number request (Moral Person)

By clicking on “Prepare a Request for CDR ID Update” (in case of existing client) or “Prepare a Request for

New CDR Number” (in case of new client) the system will allow the user to start the data entry in order to

create the dossier. Here follows the list of related functions.

6.1.4.1 Create/Update Client Identity – Data Entry

The data previously used in the search page will be auto-populated (read-only).

On top of the page the following information are provided (read-only):

Client not found (create a new CDR): the search criteria will be displayed as a reminder:

- CDR Number (Empty);

- Company Name;

- Foundation Date;


Client found (update or validate CDR data): the existing data will be displayed on top of the screen:

- CDR Number;

- Company Name;

- Foundation Date;


The information of a Moral Person is distributed within 5 tabs and can be edited by the user: "Company

Information", "Risk Information", "Address Information", "Physical Associates", and “Moral Associates”.

In order to allow the user to manage the tabs that are mandatory to complete the data entry, different

colors will be used by the system:

a. Each tab folder can have two different colors: white color to be used when the folder has been

visited and grey color when the folder has not yet been visited;

b. Every time the focus is on a specific folder, its label becomes blue and the label of the other ones

becomes black;

c. Every time a folder is visited, its color becomes white;

d. When all the tabs are colored with white color, then the button to go create the dossier will be

enabled (because it means that the user has checked all the data).

The first three tabs are mandatory (marked with a “*”). The fourth and the fifth ones are mandatory based

on the legal form of the beneficiary.

of 130

of 130

6.1.4.2 Create/Update Company Information

In order to create or update the company information of a Moral Person, the user has to complete the data

entry referred to the mandatory fields and then move to the next page.

The data entry of the Company Name allows the search in the Dictionary of Names without the filter by

type (male, female, family). By clicking on the Lookup button the list of names will be available. The user

can select the most appropriate one that will be used to fill-in the Company Name by using names taken

from the dictionary. The name taken from the Dictionary will be added to the end of the text already

present in the field.



6.1.4.3 Create/Update Risk Information (Moral Person)


of 130



6.1.4.4 Create/Update Address Information (Moral Person)


In case the address is not available in the dictionary of addresses, the system allows the user to key-in the


The requests of forced addresses will be moved to a specific stage of the process managed by BDL user

authorized to verify the request of a new address and update the dictionary of addresses accordingly.

Both values, Latin and Arabic, for the same field must be filled as forced free text or as dictionary

addresses. One inserted as free text and the other selected by the lookup is not allowed.


the dictionary of addresses, otherwise an error message will be displayed.



6.1.4.5 Create/Update/Delete Associate Relation – List

With this function the system allows the CRM user to insert (create), update or delete data referred to

Physical/Moral associates of a given Moral Person.

of 130

Layout of the list of Personal Associates

Layout of the list of Moral Associates

In case of existing CDR client, the system will display the list of the already existing associates associated to

the selected Client, if any.

In case of new client or exiting client with no already linked associates, the list will be empty and the

message “There are no Physical Associates”/ “There are no Moral Associates” will be displayed.

The number of associates has to be equal or more than the minimum number of associates defined for

each type of legal form.

For each row, the following information is displayed:

- Physical Associates:

Family Name

First Name

Father’s Name

Mother’s Date

Date of Birth

Register Number- Place

Nationality

Gender

Associate Type

% of Participation

- Moral Associates:

of 130

Company Name

Legal Form

Foundation Date

Register of Commerce Number

Register of Commerce Place

Associate Type

% of Participation

The CRM user has the following options:

Select a row from the list and click on “Update/Delete Associate”: To update or delete the data of the selected linked Associate. The system will prompt the “Create/Update Associate – Details” page with the data of the Associate to update or delete the associate detailed data. This action will be allowed by selecting one Associate from the list at the time;

Click on “Create Associate”: To insert a new link with an Associate. The system will prompt the “Create/Update Associate – Details” page to register the detailed data of the associate.



of 130

6.1.4.5.1 Create/Update/Delete Physical Associate – Details

In case the user clicks on update/delete Associate the following screen will be shown:

Scenario A: Layout “Update/Delete Physical Associate”

Scenario A: the user has pressed the button “Update/Delete Associate”.

1. The function will display the detailed data of the selected Physical Associate; 2. The user can update all the data displayed in the form; 3. The following actions will be available to the user:

a. Click on “Save” button to save the request of modification of the client data displayed in the form and go back to list. The related record will remain in the list of the associates;

b. Click on “Delete” button to request the delete the selected Associate;

c. Click on “Undo Update” button to restore the original data previously displayed;

d. Click on “Back to List” button to go back to the List. All the modification (if any) done on the client data will be lost.

In case the client name is not available in the dictionary of names, the system allows the user to key-in the


The request, for which there are forced names, will be moved to a specific stage of the process managed by

BDL user authorized to verify the request of a new address and update the dictionary of addresses

accordingly.

Both values, Latin and Arabic, for the same field must be filled as forced free text or as dictionary names.

One inserted as free text and the other selected by the lookup is not allowed.

of 130


the dictionary of names; otherwise an error message will be displayed.

In case the user clicks on create Associate the following screen will be shown:

Scenario B: Layout “Create Physical Associate”


found at the entrance of the function will be restored.

Scenario B: the user has pressed the button “Create Associate”.




a. Click on “Save” button to save all the data entered in the form and go back to list. The new record will be added to the list with the link with the CDR Client;



of 130

6.1.4.5.2 Create/Update/Delete Moral Associate - Details

In case the user clicks on update/delete Moral Associate the following screen will be shown:

Scenario A: Layout “Update/Delete Moral Associate”

Scenario A: the user has pressed the button “Update/Delete Associate”.

1. The function will display the detailed data of the selected Moral Associate; 2. The user can update all the data displayed in the form; 3. The following actions will be available to the user:

a. Click on “Save” button to save the request of modification of the client data displayed in the form and go back to list. The related record will remain in the list of the associates;

b. Click on “Delete” button to request the delete the selected Associate; c. Click on “Undo Update” button to restore the original data previously displayed; d. Click on “Back to List” button to go back to the List. All the modification (if any) done on the

client data will be lost.

In case the user clicks on create associate the following screen will be shown:

of 130

Scenario B: Layout “Create Moral Associate”

Scenario B: the user has pressed the button “Create Associate”.

1. The function will display all the fields empty; 2. The user can insert all the data in the form; 3. The following actions will be available to the user:

a. Click on “Save” button to save all the data entered in the form and go back to list. The new record will be added to the list with the link with the CDR Client;



6.1.5 Search Client Identity by CDR number

The following screen is provided to the CRM user in order to perform a search using the CDR number of the

client.

By clicking on “Get Information” according to the type of result the following Detailed Client Inquiry pages

are provided:

Inquiry Details Single Counterpart (Physical Person), if the client is a Physical Person;

Inquiry Details Single Counterpart (Moral Person), if the client is a Moral Person.

of 130

In case there are no clients corresponding to the CDR number the message “No Clients found” will be

displayed and the button “Prepare Request New CDR Number” WILL NOT be enabled.

6.1.6 Create Dossier function

When all the tabs have been visited, the button “Create Dossier” and “Undo All Update” are displayed.

By clicking on “Undo All Update” the data entered in all pages will be deleted and the original data found at

the beginning of the function will be restored.

By clicking on “Create Dossier” button, the system will show the following message:

By clicking on “YES” button the request has been saved and it will be moved in To Do List of the User. A

new dossier/request with a specific number will be created and assigned in the To Do List function of the

related user (usually the same one that created the dossier).

Here follows the description of the logical scheme applied by the system according to the selected Inquiry

Purpose, with reference to the possibility for the user to print the below mentioned reports:

of 130

Search Customer

Select Inquiry Purpose = 1

No print report allowed

Customer is found?

Update Request New Request

YES NO

Customer has postion?

CDR-IR0 reportCDR-IRP/IRM report with empty position

NO

CDR-IRP/IRM report with Position with

Others

CDR-IRP/IRM report with Position with

Bank

CDR-IRP/IRM report with Position in

Sector

Buttons:- Position in Sector

- Position with Bank- Position With Other

YES

Button PrintButton Print

Provisional Inquiry Report

Select Inquiry Purpose = 0

Update Request/New Request

of 130

In case of Inquiry Purpose = 0, no actions will be available to the user (the above buttons will be hidden).

In case of Inquiry Purpose = 1, the following actions will be available to the user:

New request (Screen layout)

Click on “Print Provisional Inquiry Report” button to print the provisional CDR-IR0 report that states that the client the user is looking for does not have a file in the CDR database.

Update request (Existing Client without positions)

Click on “Print” button in order to print the provisional CDR-IRP reports with empty position, with a note stating “The client is defined as an ID in the CDR database, and was never declared as debtor”.

of 130

Update request (Existing Client with positions)

a) Click on “Position in Sector” button to print the provisional CDR-IRP position reports for the selected situation dates;

b) Click on “Position with Bank” button to print the provisional CDR-IRP position reports for the selected situation dates;

c) Click on “Position with Others” button to print the provisional CDR-IRP position reports for the selected situation dates.

6.1.7 Select Position Dates

After clicking on the above buttons to view the client position, the user should first select the dates on which he needs to see the client's liabilities.

The “Available Position Dates” list contains in descending order the available declaration dates provided by the system. The user can select one or more of these dates. In order to see the "Client Position" details the user has to press the "Display Positions" button. The authorized amounts in local and foreign currency (LA / XA) and the utilized amounts in local and foreign

currency (LU / XU) will be displayed separately for LL and FX respectively in millions of LL.

The liabilities information of any client is divided in two groups: Direct and Indirect, each group is also

divided into two sub-groups:

of 130

Direct

Direct Commitments

Received Guarantees

Indirect

Contingent Liabilities

Memorandum Accounts

For each of the above group, the total amount of the Risk Position of the client is provided.

6.1.7.1 Position in sector

This function shows the total of the client positions with all banks and financial institutions in Lebanon

(including the CRM that is executing the inquiry).

The system displays:

The CDR Number of the client;

The name of the client (the names will be concatenating in one unique fields either in case of PP and MP);

Date of birth (if PP) or Foundation date (if MP);

Register (address of the client if PP or Commercial registration if MP).

If more than one date is selected in the previous section, the user can click on the “situation date” drop down list to switch between the selected dates.

For the dates where the client doesn’t have any position, the following message will be displayed: “No

Liabilities for the selected date dd/mm/yyyy".

The client Risk positions (Authorized Amount, Utilized Amount, Monetary Margin), are detailed by liability

type (concatenated with the loan type), economic sector, currency, remaining period, risk classification and

Utilization Country. The positions are aggregated across all the CRMs of the client (if secret flag = Yes). All

amounts are expressed in millions of Lebanese pounds.

The user can Change the sorting of each column by clicking on its header.

of 130

To print the inquiry report CDR-IRP or CDR-IRM for the selected position date the user has to click on the

“Print Position” button.

If the user wants to print the inquiry report CDR-IRP or CDR-IRM for all the selected position dates the

“Print all Positions” button has to be clicked.

6.1.7.2 Position with bank

This function shows the client position within the inquiring CRM.











Utilization Country. All amounts are expressed in millions of Lebanese pounds.

The user can Change the sort of each column by clicking on its header.





of 130

6.1.7.3 Position with others

This function is ONLY available in the External CDR system. It shows the client position with all banks and

financial institutions in Lebanon excluding the CRM executing the inquiry.











Utilization Country. All amounts are expressed in millions of Lebanese pounds.

The user can Change the sort of each column by clicking on its header.





of 130

6.1.8 Client Position Report

After pressing the "Print Position" or the "Print All Position" button, a dialog box is popped up to let the

user choose to include in the report:

The client information sub report;

The address information sub report;

The list of possible associates (available only for Physical Person);

The history inquiry sub report.

The user will be able also to select in which language the report will be printed.

By pressing the "Print" button, a PDF report is produced and another pop-up window is displayed asking

the user to:

“Open” directly the PDF report, by pressing the "Open" button;

“Save” the PDF report on the computer, by pressing the "Save" button.

By selecting the "Open" button, the PDF report is opened with the following form. The message

“Provisional report” is displayed on the printed reports.

of 130

Example of the above mentioned report:

of 130

of 130

6.1.9 Prepare the New Name Request

The function allows the user to create a Request for new family and/or first names. The user should use this

function when he cannot create a request for new CDR number because the requested names do not exist

in the dictionary of names maintained by BDL.

The user has to complete the data entry with reference to the below mentioned information that are mandatory (marked with a “*”):

Gender;

First Name;

Family Name.

By using the Lookup button , the list with the available options configured by BDL is displayed and the

user can select the most appropriate one.

When a name is not defined in the dictionary of names, the user has to submit a request for a new name by

filling both values, Latin and Arabic, as a free text. After pressing the “Free Text” button , the fields will

be highlighted in red color.

When a free text has been forced, the free text value is accepted only if it is not present in the dictionary of

names, otherwise the error message “Family Name (First Name) field is already defined in the dictionary”

will be displayed. If both family and first names already exist in the dictionary of names, the user should not

use this function. He can use the existing names already defined in the dictionary and proceed to create the

request of new CDR number.

When at least one of the name fields is filled with a new name the user can click on the “Create Request”

button in order to create a Request.

If some mandatory fields are not filled, when pressing “Create Request”, the error message “The field(s) '..'

is(are) mandatory ‘..’" will be shown with the list of the missing fields.

By pressing the button, the following page will be displayed:

of 130

The request will be created and saved in the To Do List of the user, a new dossier will be generated and

managed through the workflow application.

With reference to the description of the activities related to the process, please refer to paragraph

Dictionary Names Request Process Description.

6.1.10 Inquiry of Requests

This function allows the user to monitor and print the list of the requests created by the users of the CRM.

In order to produce the report, the following selection criteria can be defined:

Period: (Date from – To) – The date when the request was created;

Branch: (from – to and All);

Request Type: one or all:

Request of New CDR Number – PP;

Request of New CDR Number – MP;

Request of confirm CDR Number – PP;

Request of confirm CDR Number –MP;

Request of update CDR Number – PP;

Request of update CDR Number – MP;

Creation of new names request;

Monthly declaration request.

Request status: A drop down list which contains all the possible status of a request;

CDR #: with the capability to inquiry a selected CDR client;

Client type: Physical Person or Moral Person;

CRM Internal Ref. Number;

Request number;

User ID: one or all.

of 130

After specifying the search criteria, by clicking on the “Search” Button the user will get the result as follows:

The user can change the sorting of each column by clicking on its header.

By pressing the button , the PDF report will be printed online with the following form:

of 130

6.1.11 MES-TR management

The "MES-TR" file is the file generated by the member IT systems and uploaded onto the BDL-CDR system

and contains bulk requests for credit inquiry report.

It contains the ID information of the clients and the related associates (if applicable) and is used to

minimize the data entry operation when searching for a client, defining a new ID and updating an existing

client ID.

Here follows the description of all the functionalities related to the MES-TR file management. The available

functions are:

Upload bulk requests (MES-TR) File

Manage bulk requests

6.1.11.1 Upload bulk requests (MES-TR)

This function allows the user to upload a file that contains a bulk of CDR requests.

By pressing the button , the user will be able to browse the file that exists on his personal

computer. By clicking on “Upload”, the file will be uploaded on BDL Server.

The name of the MES-TR file must contain a serial number to differentiate between multiple files uploaded

on the same date.

After the uploading, the file is stored in the CDR Stage folder and the acceptance data validation activity will

start automatically. The system will perform a set of controls on the structure and content of the file.

In case of error, the file will NOT be loaded and the list of errors will be displayed on the screen as follow:

The following information will be provided:

Validated Item: specific items that were verified during the Acceptance Validation which produced

an error;

Detected Errors: error that was found during the execution of the Acceptance Validation.

of 130

If there are no errors, the system will display a loading successful message and the validation activity will

start and performed in background. The system will perform a further set of controls that are mainly

focused on the technical structure of the file plus some controls related to the domain of the data.

The user can upload more than one file during the same day, including the same file after the end of the

technical validation. So, in case of many errors, the user has the possibility to delete all or some requests

contained in the loaded file and reload a new corrected version of the same file.

6.1.11.2 Manage bulk requests

This function allows the user to search in the List of all uploaded MES-TR files.

In order to view the list of the uploaded MES-TR files during a specified period, the user has to select the

following selection criteria (mandatory):

Date From - To (by default = today date for both).

After specifying the search criteria, the user will click on the button in order to get the results related to the list of uploaded files and some preliminary information about the contents of each file:

For each file, the system shows:

Loading Date (dd/mm/yyyy);

File Name;

File Status:

Acceptance Validation Failed;

Uploading (the uploading process in the DB is still in progress);

Processing (some records linked with this file that still needs to be deleted or processed in order to start a CDR Request process);

Processed (any record linked with this file has started a CDR Request process or has been deleted);

of 130

Deleted (when the user has logically deleted the file; the deletion of the file can't be reversed).

Total Number of Requests (Number of Discarded Requests + Number of Requests Processed + Number of Requests to be Processed + Number of Requests Deleted);

Number of Requests Discarded;

Number of Requests Deleted;

Number of Requests to be Processed;

Number of Requests Processed.

The user can select only one file at the time.

6.1.11.2.1 List of Errors button

By clicking on the system shows the list of Technical Validation errors (if any). This button is

allowed only with reference to files that are not in the status of “Uploading” or “Deleted”.

This page allows the user to verify the result of the validation performed on the file that was uploaded.

The main information of the submitted File will be displayed on top of the screen.

The types of controls that the system will perform will be based on specific criteria that can be customized

by BDL administrator that define which data will be automatically accepted and validated by the system

and which ones will be discarded.

When a record is discarded, it will not be loaded in the system and it will not be available in the list of CDR

Requests.

By pressing the button, the PDF report containing the full list of errors and related details is

printed online with the following form:

of 130

By double clicking on each row, the summary of the errors found during the technical validation is shown

for each record.

The main information of the submitted file is displayed on top of the screen. By clicking on the

previous list of errors is displayed.

of 130

6.1.11.2.2 List of CDR Requests

By clicking on the system shows the list of CDR Requests included in the file (MES-TR CDR

Requests File). This button is allowed only with reference to files that are not in the status of “Uploading”

or “Deleted”.

This page shows the list of requests loaded and available to be processed.

On top of the screen the main information of the submitted file will be displayed.

The user is able to manage the list of the requests in order to:

Start to process one or more requests in the list;

Delete or undelete one or more requests in the list.

The status of each request can be: unprocessed (yellow row), processed (green row), and deleted (red

row).

The user can select only one file at the time.

By pressing the button, the selected request in the list will be set as “deleted”.

By pressing the button, the selected request in the list will be set as “unprocessed”.

By pressing the button, the search functions will be launched and one of the following forms will

be invoked, according to the data in the selected record using the data of the selected requests:

1. The function “Search by CDR number” will be started, if the field CDR Number is filled;

2. The function “Search by using personal data” will be started, if the Client Operation Type = “P”;

3. The function “Search by using company data” will be started, if the Client Operation Type = “M”.

The system will auto-populate all the fields of the started function using the values received in the file, so

the search will be done using the received values with the possibility to overwrite any field value.

Whether the client is found, or not, by pressing the “Prepare Request for new CDR number” or “Prepare

Request to update ID” button, the system will prompt the data entry pages to insert, update or modify the

client information.

of 130

In case of mismatch between BDL and CRM data, the system will highlight the mismatching fields in red

color and will allow the user to toggle between BDL and CRM values by using the button displayed next to

field.

At the end of the process, when the request is created and the confirmation message is displayed, the

system will update the status of the request as “Processed”. The request is available in the To Do List of the

user. The user can print the inquiry reports according to the original purpose of the request.

When a request is processed, the selection check box is disabled and no operations are permitted.

6.1.11.2.3 Delete the selected file

By clicking on the selected file is deleted. The status of the file will be set to “Deleted”. It is allowed only on files that have no processed records and are not in the status “Uploading” or “Deleted”. The deletion of a file can't be reversed.

6.1.12 Upload "MES-DR Risk" File by CRM

This function allows the user to send the MES-DR file to BDL in order to start the Monthly Declaration

activity.

The user has to search the file into the disk Storage (or gateway), select and attach it in order to be

uploaded into the BDL Server. Here follows the screen related to the above mentioned function:

In order to upload the file, the following criteria have to be defined:

Type of Submission- the type of submission of the file for the current situation date:

a) First submission: this option is available only in case the file is submitted for the first time;

b) Re-submission: this option is available only if a first file has been submitted and rejected by

BDL.

By pressing the button, the user searches the file to be submitted. Then the user has to key in

the values of the total authorized & utilized amounts, the count / sum of all old clients and the count / sum

of all new clients. The user has to click on . After the uploading, the file is stored in the CDR Stage

folder and the acceptance validation on the data starts automatically.

of 130

According to the result of the uploading activity, the system will display the following information:

Credit Total Authorized: This is the total amount of authorized credits related to the declared bank;

Credit Total Utilized: This is the total amount of utilized credits related to the declared bank;

Count Old Clients: This is the count of the old clients related to the declared bank;

Sum Old Clients: This is the sum of the old clients related to the declared bank;

Count New Clients: This is the count of the new clients related to the declared bank;

Sum New Clients: This is the sum of the new clients related to the declared bank.

In case of error, the file will not be uploaded. A table at the bottom of the page will display the list of

detected errors and the process is considered finished.

For each error, the following information is provided:

Validated Item: this is the list of items verified during the Acceptance Validation;

Detected Error: this is the list of errors found related to each item during the execution of the

Acceptance Validation activity.

If there are no errors, the system will start the Technical Validation in background and a dossier will be

generated and assigned to the configured user that will find it in its To Do List (process flow type: “Monthly

Declaration”).

In order to verify the result of the technical validation the user has to click on the To Do List main function,

open the dossier and proceed with the foreseen process steps.

6.1.13 Download monthly return files

This function allows the user to download the monthly return files prepared by BDL and save them in the

CRM private download folder.

Here follows the screen related to the above mentioned function:

of 130

In order to download the monthly return file, the user has to select the Situation date: the system displays

by default the last situation date with files available for downloading. The user can select any previous

situation dates available in the list.

After specifying the search criteria, the user clicks on button in order to get the result as follows:

The table containing the information on the most updated files available for downloading for the selected situation date is displayed. The available files are listed in the following order:

1. COM-AV File; 2. COM-UP File; 3. COM-FF File (if prepared); 4. COM-IN File. 5. COM-RC File.

For each File, the following information is provided:

Communication Files:

File Type: this is the file type that has been prepared by BDL;

File Type description: this is the description of the File Type that has been prepared by BDL.

File Name: this is the file name assigned by the system to the given file type according to the

naming convention;

File Size: this is the size of the File;

Preparation Date: this is the Date of the preparation of the File;

Download Date & Time: this is the Date & Time of the download of the File (if already

downloaded);

Check button “File Available”: auto-populated and displayed in read-only mode. If the checkbox is

selected it means that the file exists in the CRM private Downloading Folder otherwise it has been

removed from the folder.

of 130

By pressing the “Download” button, a unique compressed file is downloaded containing all the listed COM

files. The “Save as” dialog page is prompted and the user can save the data in a specific folder.

After downloading the file, the “Last download date” of the downloaded file is refreshed in the “most

recent files” table as well as new row that is displayed in the “history list” table with the downloaded files

information.

In case the return code from the browser indicates a failure in the downloading of the file, the user can

repeat the downloading procedure. In case any error occurs after successful return code from the browser

or for any reason the user needs to download again the file, the same downloading procedure can be

repeated and, in case of successful download, a new record is inserted in the table.

When a new and most updated file is prepared by BDL, the new “Preparation Date” of the file will be

refreshed in the “most recent files” table and the “Download Date” is displayed empty. The user can

download the new version of the file by using the same procedure.

The user can see the history of the downloaded files for the selected situation date in the lower part of the

page. The following information is displayed:


File Type description: this is the description of the File Type that has been prepared by BDL;

File Name: this is the file name assigned by the system;

Preparation Date: this is the Date of the preparation of the File;

Download Date & Time: this is the Date & Time of the download of the File;

User: user who has downloaded the file.

6.1.14 Download daily files from BDL

This function allows the user to download the daily return files prepared by BDL and save them in the CRM

private download folder.

In order to download the daily return file, the following selection criteria has to be defined:

Preparation Date (from- to): default value is equal to the last download date;

File Type (All or one).

After specifying the search-criteria, the user clicks on button in order to get the result.

of 130

The page provides the table containing the information of the files available for downloading.

For each file, the following information is provided:

Communication File


File Type description: This is the description of the File Type that has been prepared by

BDL.

File Name: this is the file name assigned by the system to the given file type according to the

naming convention;

File Size: this is the size if the File;

Preparation Date: this is the date of the preparation of the File;

Download Date & Time: this is the Date & Time of the last download of the File (if already

downloaded).

The check button “Select to download” is enabled for all the files. The oldest not downloaded file is pre-

selected. Only one file per time can be selected (multiple selection is not allowed).

By pressing the “Download” button, the selected file is downloaded. The “Save as” dialog page is prompted

and the user can save the data in his folder.

The file will include a flag that indicates if a change was done by BDL on any field of the ID information sent

from the CRM user.

After downloading the file, the “Last download date” of the downloaded file is refreshed in the “most

recent files” table.

In case the return code from the browser indicates a failure in the downloading of the file and the user can

repeat the downloading procedure. In case any error occurs after successful return code from the browser

or for any reason the user needs to download again the file, the same downloading procedure can be

repeated and, in case of successful download, a new record is inserted in the table.

When a new and most updated file is prepared by BDL, the new “Preparation Date” of the file is refreshed

in the “most recent files” table and the “Download Date” is displayed empty. The user can download the

new version of the file by using the same procedure.

6.1.15 Inquiry Statistics on CRM User’s Process Workload

This function allows the user to print the statistics on CRM user’s process workload related to the requests

initiated by the users of the CRM with reference to the following processes:

of 130

CRM CDR Request PP;

CRM CDR Request PP;

Dictionary Names Request;

Monthly Declaration.

In order to produce an audit report, the following selection criteria can be defined:

Date from – to.

After specifying the search criteria, the user clicks on the button and the report is printed online with the following form:

CRM Officer

CRM Supervisor

of 130

6.2 Description of the functions related to processes

With reference to the process functionalities, the user has to click on the function named “To Do List” in

the main menu of the application.

Currently the available processes in the system are the following:

CRM - CDR PP Request: it is used to create or manage a CDR number related to a Physical Person.

The following type of requests can be created:

- New CDR number: the client does not exist in the system and the business user is asking BDL to

assign a CDR number;

- Update client information: the client exists in the BDL database and the business user needs to

update some information related to his ID information;

- Confirmation client information: the client exists in the BDL database and the business user

needs a confirmation from BDL concerning his ID information.

CRM - CDR MP Request: it is used to create or manage a CDR number related to a Moral Person.

The following type of requests can be created:

- New CDR number: the client does not exist in the system and the business user is asking BDL to

assign a CDR number;

- Update client information: the client exists in the BDL database and the business user needs to

update some information related to his ID information;

- Confirmation client information: the client exists in the BDL database and the business user

needs a confirmation from BDL concerning his ID information.

Dictionary Names Request: it is used to create a request of new names that do not exist in the

dictionary of names maintained by BDL. The request can be sent to BDL for the following type of

names:

- Family name;

- First name.

Monthly Declaration: it is used to send to BDL the monthly file containing the position of old and

new client for the situation date that is under preparation.

Every time the user selects a process type in the To Do List, only the requests of this type are displayed in

the working task area.

6.2.1 To Do List function

According to the configuration of the users, the ones with roles that allow them to manage processes can

have access to this part of the application which is dedicated to the business process management.

Here follows the screen layout of the To Do List function:

of 130

On the upper right side of the page, the list of available workflow/process types is displayed according to

the user profile.

The workflows types are the following:

CRM - CDR PP Request;

CRM - CDR MP Request;

Dictionary Names Request;

Monthly Declaration.

The item “All” is selected by default and, accordingly, the system displays the list of all types of requests

assigned to the user.

If a specific process is selected in the workflow list, then only the requests created and received within this

process are displayed in the list (filter function).

In this page the system will display:

the requests created by the user that need to be completed;

the requests received from BDL users can be:

Accepted: the user should complete his tasks according to the purpose of the request;

Rejected: the user should review the reason of the rejection and take action either by re-submitting or dropping the request.

The user may complete his tasks in different sessions of work during which, the request will be kept in his

To Do List and no other users can work on it. When the user has completed his tasks the request is moved

of 130

to the next stage foreseen in the designed workflow and it disappears from his To Do List. The request will

be included in the To Do List of the related user to whom the next stage of the workflow is assigned or it

will be sent to END.

When a request is selected in the To Do List, the following information of the selected request is displayed

on the left area of the page as follows (based on the different type of process):

CRM CDR Request PP process

CRM CDR Request MP process

Dictionary Names process

Monthly Declaration process

• Process Flow Name • CRM • Branch • Family Name • First Name • Father name • Mother name

• Process Flow Name • CRM • Branch • Company Name • Foundation date • Register number • Register place

• Process Flow Name • CRM • Branch • Family Name • First Name • Gender

• Process Flow Name • Situation Date • CRM code • CRM name • Request Scope

The rows are sorted by priority, in descending order, and by “Date of assignment” in ascending order.

All the requests in the To Do List are separated in two main sections:

In the first section, the requests coming from BDL;

In the second section, the requests coming from the CRM users.

Inside each section, four groups of requests are ordered by the following order/priority, in descending

order:

First: the requests created in the “Monthly Declaration” process;

Second: the requests created in the “Dictionary of names” process;

Third: the requests created in the below processes, when the purpose of the request is to manage the client Identity (inquiry purpose is = 0):

a. New CDR Request PP;

b. New CDR Request MP;

c. Update/Validate Client Request PP;

d. Update/Validate Client Request MP.

Fourth: the requests created in the below processes, when the purpose of the request is to inquire

and print the client positions (inquiry purpose is = 1):

a. New CDR Request PP;

b. New CDR Request MP;

c. Update/Validate Client Request PP;

d. Update/Validate Client Request MP.

In each group, the requests are ordered by date of assignment (related to the assignment of the current

task and user), in ascending order.

of 130

For each request (rows on the screen), the following information is displayed in the To Do List part of the

screen (columns):

Date of creation: the date when the dossier has been created;

Request ID Number: the number of the Request to be processed;

CRM Code: the code related to the CRM originating the CDR number request;

CRM Name: the name of the CRM originating the CDR number request;

Branch Code: the code related to the branch originating the CDR number request;

Branch Name: the branch of the CRM originating the CDR number request;

Client Name: the name of the Client:

PP: Family Name, First Name – Father Name (Mother Name) Concatenated;

MP: Company Name.

Request Scope: the scope of the request;

Situation Date: empty. Not Applicable;

Flow: the name of the workflow that will be processed;

Active phase: the current phase of the workflow;

Stage date: the date when the dossier reaches the current stage/phase;

Stage Time: the time spent processing the given dossier since it reached the current stage/phase;

Dossier Time: the time spent in processing the given dossier since the creation date;

Priority: the classification of the dossier based on the processing priority.

To start working on a request included in the To Do List, the user has two options:

Double click on the chosen row in the To Do List: the system will launch the first function listed in the Application Menu configured for the given stage of the process (see the table above mentioned). This option is normally used when the user starts working on a newly created request;

Select (single click on the concerned row) a request from the To Do List and click on one of the applications listed in the Application menu. These options can be used when the user wants to execute a specific activity on a request that is not yet completed.

In any case, when a given application has been launched, the behavior of the system is the same regardless

which option has been used.

After selecting a dossier indipendenthly from the type of process, if the user clicks on the function named

“Flow” in the right side menu, the system will display the logical flow of the related process.

Here follows the description of the different processes that have been designed in the application.

6.2.1.1 Common functions

Concerning the description of the functions that the user can execute when is performing the operational

activity through the designed business processes handled by CDR, here follows the list of common

functions always available, independently from the type of process involved.

of 130

6.2.1.1.1 Documents function

Second function present on the right side menu named “Documents” allows the user to attach the

requested documents by searching the files from the disk Storage (or gateway).

Here follows the screen of the function, according to the type of Legal Form of the Client, the system will

ask to upload a specific type of document:

The function shows the list of the requested documents to be uploaded, differentiated for each type of

client involved in the request: beneficiary and/or associates linked to the CDR number.

The user must upload the appropriate documents for the ones that are marked as mandatory .

By clicking on the upload icon , the window pop-up will appear allowing the user to search and upload

the PDF file:

of 130

The system has the capability to check the file type, according to the configured values.

The user has to select the Document type and fill the document number if it is requested according to the

legal form type.

After browsing in the local disk and selecting a document, the user has to click on button in order

to upload the document. The following confirmation message will be displayed:

By clicking , the file will be deleted.

After the file is uploaded, two additional buttons appear next to the loaded document that allows the user

to:

- Delete

- Download the uploaded documents.

Here follows the example of the above mentioned screen:

of 130

The system does not allow the user to move the request to the next stage if all mandatory documents have

NOT been uploaded.

6.2.1.1.2 Start Page function

This function shows the summary of the main information related to the selected dossier. The page

displays the data in two separate sections:

Request Information: this section shows the main information related to the request, including some characteristic of the request (i.e. the request includes new names/addresses);

Previous Stage Information: this section shows the main information related to the previous stage, the decision and the comments inserted by the previous user that has managed the dossier.

Example of the screen:

of 130

6.2.1.1.3 Decision Page

This function allows the user to take a decision with reference to the performed activity, the user has to

select one of the possible outcomes and if needed, add recommendations and notes in the assigned box.

The decisions available in this page are different according to the processes and the specific stage in which

the user is working on. Here follows the list of possible decisions that can be taken by the CRM user

differentiated by flow/process type:

1. FLOW: CRM CDR Request PP and CRM CDR Request MP

a) Stage: CRM Attach Documents.

Two possible decisions are available: “Confirm” and “Drop”. According to the selected decision, by

pressing the “Save and go to next” button, the request will be saved and sent to the next step of the

workflow according to the following rules based on the user’s CRM Inquiry Client Position/CRM

Managing Client Identity roles and CRM CDR number request Supervisor role:

CRM Inquiry Client Position/CRM Managing Client Identity role:

Confirm the request: the dossier will be moved to the CRM CDR number request Supervisor to verify the request.

Drop the request: the dossier will be sent to “End” stage and the process is terminated. If needed a New Request process should be initiated for the same client.

CRM CDR number request Supervisor role:

Confirm the request: the dossier will be moved directly to the BDL Officer.

Reject the request: the dossier will be rejected in case of any missing or wrong data and returned to the CRM user who initiated the request.

Drop the request: the dossier prepared by the CRM supervisors themselves will be sent to “End” stage and the process is terminated. If needed a New Request process should be initiated for the same client.

In all cases, the request will immediately disappear from the To Do List page of the current CRM user.

b) Stage: CRM Send Request to BDL.

Two possible decisions are available: “Confirm” and “Drop”. By pressing the “Save and go to next”

button, the request will be saved and sent to the next step of the workflow:

Confirm the request: the dossier will be moved to the BDL CDR Officer for subsequent activities.

Reject the request: the dossier will be sent back to the initiator CRM Officer who will be able to update the dossier if necessary and confirm again the request or finally drop it.

In both cases, the request will immediately disappear from the To Do List page of the CRM Supervisor.

of 130

c) Stage: Rejected Cases.

When the user receives the request rejected by BDL, two possible decisions will be available:

“Drop” and “Resubmit”.

1. Drop the request: the request will be sent to “End” stage and the process is terminated. The request will immediately disappear from the To Do List page of the user.

2. Resubmit the request: the request will be moved to the initial stage. The request will remain in the To Do List of the user.

d) Stage: Accepted Cases.

When the user receives the request accepted by BDL, the user can execute his tasks and end the

process by clicking on “Drop" and "Save and go to next step".

2. FLOW: Dictionary Names Request

a) Stage: Send Dictionary Request to BDL.

Two possible decisions will be available: “Confirm” and “Drop”. According to the selected decision, by

pressing the “Save and go to next” button, the request will be saved and sent to the next step of the

workflow:

of 130

1. Confirm the request: the dossier will be moved to BDL.

2. Drop the request: the dossier will be sent to “End” stage and the process will be terminated.

In both cases, the request will immediately disappear from the To Do List page of the user.

b) Stage: Rejected Cases.

When receiving the rejected requests from BDL, the user will be able only to end the process by clicking

on “Drop” and "Save and go to next step".

c) Stage: Accepted Cases.

When receiving the request accepted by BDL, the user can end the process by clicking on “Drop” and

"Save and go to next step".

3. FLOW: Monthly Declaration Process

a) Stage: Verify Background Control.

The system will enable the radio-button to “Confirm” the sending of the file to BDL or “Drop” the

request according to the results of the Validation process.

In case the request has been created by CRM Monthly Declaration Officer:

In case of errors, the CRM Monthly Declaration Officer can only drop the request by clicking on “Drop"

and "Save and go to next step". Even in case of no errors the user may decide to drop the request.

In both of the above mentioned cases, the dossier is sent to the “End” stage and the process is

terminated.

In case of first submission and no errors in the File for the current situation date, the CRM Monthly

Declaration Officer can decide to:

Send the request directly to the BDL Officer stage of the process by selecting the "Send the request to BDL officer" radio button and pressing the button "Save and go to next step”. The system will move the file to the "OK" folder.

Decline the request by selecting the "Decline the Request" radio button and pressing the button "Save and go to next step". The system will move the file to the rejected files folder.

In case no technical errors have been detected (blocking errors) and subsequent transmission (re-

submission) of the File for the current situation date: the request will be sent by the CRM Monthly

Declaration Officer to the CRM Monthly Declaration Supervisor in order to approve the request before

the submission to BDL.

In case the request has been created by CRM Monthly Declaration Supervisor:

If the technical validation succeeds, the request dossier will be sent directly to BDL Business Validation

officer either in case of first or subsequent submission. (In case of validation errors the request dossier

will be sent to end as per the normal process).

b) Stage: CRM Review file.

The CRM Monthly Declaration Supervisor will check the results of the Technical Validation and will

decide whether to:

of 130

Select the "Send the request to BDL officer" radio button: by pressing the button "Save and go to next step" the request will be sent to the BDL Business Validation officer.

Select the "Decline the Request" radio button: by pressing the button "Save and go to next step" the request will be sent back to the CRM Monthly Declaration Officer to inform him of the decision.

c) Stage: Rejected Cases.

When receiving the request rejected by the CRM Supervisor, the CRM Officer will be able only to end

the process by clicking on "Drop" and "Save and go to next step".

When receiving the request rejected by the BDL, the CRM Officer will be able only to end the process

by clicking on "Drop" and "Save and go to next step".

d) Stage: Accepted Cases.

When receiving the request accepted by the BDL, the CRM Officer can end the process by clicking on

"Drop" and "Save and go to next step".

6.2.1.2 Specific functions

Concerning the description of the functions that the user can execute when performing the operational

activity through the designed business processes handled by CDR, here follow the list of functions

depending on the type of process involved.

6.2.1.2.1 CRM CDR Request PP/MP Process Flow

of 130

Activity executed by CRM Activity executed by BDL Decisional Knot The CRM user is involved in the following stages of the above described flow:

CRM Attach Documents;

CRM Supervisor send Request to BDL;

Accepted Cases – Print;

Accepted Cases – Review;

Rejected Cases.

Here follows the list of functions that the CRM user can perform with reference to each process stage:

CRM Attach Documents

CRM Supervisor Send Request to BDL

Accepted Cases – Print Accepted Cases - Review Rejected Cases

• Documents • Start Page • Update CDR request • Repeat the search • Decision Page

• Documents • Start Page • Update CDR request • Repeat the search • Decision Page

• Documents • Start Page • Print final Credit Report • Decision Page

• Documents • Start Page • Review accepted cases • Decision Page

• Documents • Start Page • Review CDR request • Decision Page

6.2.1.2.1.1 Update CDR request

of 130

This function allows the user to update the data related to an already created request, before sending it to

BDL. Here follows the description of this function that is used both for Physical and Moral Person, the only

difference is represented by the contents of:

The first tab (Personal Information in case of Physical Person and Company Information in case of

Moral Person);

The last tab (Sole Proprietorship in case of Physical Person and Physical Associate and Moral Associate

in case of Moral Person).

According to that, here follow the description of the functionality related to the Physical Person that could

be considered exhausted.

of 130

6.2.1.2.1.1.1 Personal Information

The documents related to the beneficiary are displayed on the below part of the screen. By clicking on the

name of the document , the pop-up window containing the uploaded document is

displayed on the right side of the page:

The user can compare the content of the document with the data inserted in the request and apply some

amendments if needed.

of 130

By pressing the button, the data entered in this page will be deleted and the original data

found at the entrance of the function will be restored.

6.2.1.2.1.1.2 Risk Information

of 130

No need for this because the documents attached are only related to the ID and the ID does not contain

any risk information.

6.2.1.2.1.1.3 Address Information

Same as the previous tab.

6.2.1.2.1.1.4 Sole Proprietorship

of 130

The user has the following options:

Click on button to insert a link with a new Sole Proprietorship. The system will prompt the page to register the detailed data of the new company;

Select a row from the list and click on button to update or delete the data of the already linked Proprietorship. The system will prompt the page with the data of the Proprietorship to update or delete the company detailed data. This action will be allowed for each Sole Proprietorship selected from the list (one by one).

By pressing the button, the data entered in this page will be deleted and the original data

found at the beginning of the function will be restored.

6.2.1.2.1.1.4.1 Sole Proprietorship- Details

According to the button pressed in the page Sole Proprietorship – List, the following scenario may occur:

Scenario A: the user has pressed the button “Update/Delete Sole”.

1. The function will display the detailed data of the selected Sole Proprietorship;

2. The user can update all the data displayed in the form;


a. Click on button to save the request of modification of the client data displayed in the form and go back to list. The related relation record will remain in the list of the Sole Proprietorships;

b. Click on button to delete the selected Sole Proprietorship;

c. Click on button to go back to the List. All the modification (if any) done on the client data will be lost.

of 130

Scenario B: the user has pressed the button “Create Sole”.




a. Click on button to save all the data entered in the form and go back to the list. The new client record will be added to the list with the link with the CDR Client;

b. Click on button to go back to the List. All the modification (if any) done on the client data will be lost.

The documents related to the sole proprietorship are displayed on the below part of the screen. By clicking

on the name of the document , the pop-up window containing the uploaded

document is displayed on the right side of the page.



By pressing the button, the data entered in this page will be deleted and the original data found

at the entrance of the function will be restored.

The button and are enabled when the user has visited all the tabs.

When the user updates some data and clicks on , the request is saved and updated.

By pressing the button, the data entered in all pages will be deleted and the original data

found at the beginning of the function will be restored.

6.2.1.2.1.2 Repeat the search

This function allows the user to re-execute the search before sending the request to BDL.

The following functions are available:

of 130

“Search by using Personal Data”



displayed on the right side of the page.

The user can re-execute the search and compare the content of the document with the results found by the

system.

“Search by using Company Data”





system.

of 130

“Search by CDR Number”





system.

6.2.1.2.1.3 Print final Credit Report

This function allows the user to see the newly created/updated CDR information and to see and print the

positions of the client. Furthermore, the user can download the COM-I1 single file for this client containing

the client ID information and the risk positions in the active situation dates.

The print and download of the client data and positions is available only during the day when the user

prints or downloads the positions for the first time. It is important to mention that the data that will be

available for download is the client data available in the BDL DB at the end of the day when the request has

been processed by the BDL officers (either accepted or rejected). The file will include a flag that indicates if

a change was done by BDL on any field of the ID information sent from the CRM user. The user can

download the file the next day or any further day but the data will be always referred to the processed

date.

Example:

The user submits the request on 15/6/2015;

BDL processed the request on 16/6/2015;

The file will be prepared with the data saved on BDL’s DB during the night of 16th.

If the CRM user downloads the data on 21/6/2016, the data contained in the downloaded file will be referred to June 16th.

The buttons that allow the user to view and print the client positions are available according to the below

scenarios:

of 130

Scenario 1: client newly created. By clicking the “Print” button the user can print the inquiry report

CDR-IRP or CDR-IRM. By clicking the “download” button, the user can download the COM-I1 file with

empty positions.

of 130

of 130

Scenario 2: client found in the DB. By clicking the “Position in Sector”, “Position with Bank” and

“Position with Others” buttons the user can select the situation dates and print the reports CDR-IRP

or CDR-IRM. By clicking the “download” button, the user can download the COM-I1 file with the

selected positions.

of 130

of 130

Scenario 3- If the client is found in the DB but he is never declared as a debtor. By clicking the

button “Print” the user can print the inquiry reports CDR-IRP or CDR-IRM with empty positions and

with a note stating “The client is defined as an ID in the CDR database, and was never declared as

debtor”. By clicking the “Download” button, the user can download the COM-I1 file with empty

positions.

of 130

of 130

The reports printed at this step have a title to indicate that they are final reports and they contain the

inquiry history table that exclude the inquiry executed by the initiator user on the date of creation of the

request.

of 130

6.2.1.2.1.4 Review Accepted cases

This function allows the user to see the newly created/updated CDR information.

Physical Person

Personal Information

All the information is displayed in read mode.




The user can compare the content of the document with the data of the request that has been accepted by

BDL.

of 130

Risk Information






BDL.

Address Information


of 130





BDL.

Sole Proprietorship

All the information are displayed in read mode.

6.2.1.2.1.5 Review CDR Request

This function allows the user to review the request data that has been rejected by BDL. According to the

rejection remarks provided by the BDL, the user can review the request and decide whether to re-submit or

finally delete it. All data is displayed in read mode and the user cannot modify it.

Physical Person

Personal Information


of 130




The user can compare the content of the document with the data of the request that has been rejected by

BDL.

Risk Information

All the information are displayed in read mode.

of 130





BDL.

Address Information






BDL.

of 130

Sole Proprietorship


6.2.1.2.2 Dictionary Names Request Process flow

Activity executed by CRM Activity executed by BDL Decisional Knot

of 130

The CRM user is involved in the following stages of the above described flow:

Send Dictionary Request to BDL;

Accepted Cases;

Rejected Cases.


Send Dictionary Request to BDL Accepted Cases Rejected Cases

• Documents

• Start Page

• Update New Names Request

• Decision Page

• Documents • Start Page • Review new names request • Decision Page

• Documents • Start Page • Review new names request • Decision Page

6.2.1.2.2.1 Update New Names Request

This function allows the user to modify the data of the already created request, before sending it to BDL.



displayed on the right side of the page:

of 130



By clicking on , the request is saved and updated.

6.2.1.2.2.2 Review New Names Request

This function allows the user to review the request containing new names after it has been accepted or

rejected by the authorized user.

Accepted cases:

The accepted name is highlighted in green color. The user can view the result of the accepted request and

use the requested name in the CDR Request processes.

of 130

Rejected cases:

The rejected name is highlighted in yellow color. In case the user needs the name to be created he has to

create a new request and send it to the authorized user.

6.2.1.2.3 Monthly Declaration Process flow

Activity executed by CRM Activity executed by BDL Decisional Knot

The CRM user is involved in the following stages of the above described flow:

of 130

Verify background controls;

CRM review file;

Accepted Cases;

Rejected Cases.


Verify background controls

CRM review file

Accepted Cases Rejected Cases

• Documents • Start Page • Result of the Technical Validation • Decision Page

• Documents • Start Page • Result of the Technical Validation • Decision Page

• Documents • Start Page • Decision Page

• Documents • Start Page • Decision Page

6.2.1.2.3.1 Result of the Technical Validation

This function allows the user to verify the result of the technical validation performed by the system with

reference to the uploaded MES-DR File. These controls are mainly focused on the technical structure of the

file plus a control of the CDR #.

Validation file folder

No error:

of 130

With error:

On top of the screen the main information of the submitted File will be displayed.

For each row, the following information is provided:

Row Number: This is the number of the Rows in the submitted File;

Branch: This is the branch code-name related to the given row;

CDR number: CDR number of the given row;

Blocking Error Number: This is the total number of blocking errors occurred for each Row in the

submitted File;

Warning Error Number: This is the total number of no blocking errors for each Row in the

submitted File.

In case of error, the row related to each record will be red and it will not be possible to send the file to BDL.

By double clicking on each row, the summary of the errors for each record will be shown in order to allow

the user to analyze in depth the results. This page provides the list of errors for each record found during

the technical validation phase.

of 130

On top of the screen the main information of the submitted File will be displayed.

For each record the following information are provided:

Branch Code-Name: This is the code and the name of the Branch in which the error has occurred;

Row number: This is the number of the Row in the submitted File where the error has occurred;

CDR number: CDR number of the given row;

Field Name: This is the name of the field where the error has occurred;

Value: This is the value of the field where the error has occurred;

Control Description: This is the description of the control executed on the occurred error;

Error Message: This is the description of the error occurred;

Type of Error: This is the type of error (blocking/warning).

By clicking on “back” the previous page is displayed.

By clicking on “print report”, the PDF report containing the full list of errors and related details is printed

online with the following form:

of 130

Total by bank folder

This function allows the user to verify the totals calculated by the system and the totals received into the

uploaded MES-DR File. It shows the controls executed on the bank total records of the submitted File, from

the technical point of view.

No error:

of 130

With error:

This page will be always available to the user, whether there are errors or not. In case of error the

difference between calculated and received amount is highlighted in red color. In case of errors, the user

cannot proceed and he must reject the file through the “Decision Page” function.

The following information is provided in two separate sections:

a) Credit Control Section

Credit Total: This is the Total amount of Credits in this bank, segregated in Authorized and Utilized.

b) Client Control Section

Old clients: This is the Total number of the old clients in this bank, segregated in Count and Sum;

New clients: This is the Total number of the new clients in this bank, segregated in Count and Sum.

Total by branch folder

This page shows the controls executed on the branch total records of the submitted File, from the technical

point of view.

of 130

No error:

With error:

In order to check the technical validation of the branch control records, the user can filter the result of the

validation by branch:

Branches with error, to be displayed by default;

One or more branch;

All branches.

In case of no errors the following message is shown: "All Branches control records are validated".

of 130

This page will be always available to the user, whether there are errors or not. In case of error the

difference between calculated and received amount is highlighted in red color. In case of errors, the user

cannot proceed and he must reject the file through the “Decision Page” function.

The following information is provided in two separate sections:

c) Liabilities Control Section:

Direct Commitments: This is the Total amount of Direct Commitments in this branch, segregated in Authorized and Utilized;

Received Guarantees: This is the Total amount of Received Guarantees in this branch, segregated in Authorized and Utilized;

Contingent Liabilities: This is the Total amount of Contingent Liabilities in this branch, segregated in Authorized and Utilized;

Memorandum Accounts: This is the Total amount of Memorandum Accounts in this branch, segregated in Authorized and Utilized.

d) Clients Control Section:

Old Clients: This is the Total number of the old clients in this branch, segregated in Count and Sum;

New Clients: This is the Total number of the new clients in this branch, segregated in Count and Sum;

Old + New client in the previous situation: This is the total number of the clients (old and new) in this branch in the previous situation, segregated in Count and Sum;

Deleted Clients: This is the Total number of the deleted clients in this branch, segregated in Count and Sum.

6.3 Administration functions

Currently the Administration section of the application dedicated to CRM user is composite of the following

functions:

Auditing Log Report;

Management of Users to be used in the CRM;

Assign Users to Groups in CRM.

Here follows the description of the above mentioned functions.

6.3.1 Auditing Log Report

This function allows the user to check and control the activities executed on the CDR system by the users

that belong to its institution.

Only the users that are configured with a specific role will see in the Main menu this specific group of

functions, usually assigned to an administrator or supervisor.

of 130

In order to generate an audit report, the following selection criteria has to be defined (mandatory):

Date (from – to): the default value of “From Date” is the earliest date available in the LOG table and

cannot be less than this value. The default value of “To Date” is today's date and cannot be greater.

The user can change the values within this range;

Time (from – to): the default value of “From Time” is (00:00) and “To Time” is (23:59). The user can

change these values within this range.

The remaining criteria are not mandatory but if left empty all values will be fetched.

Branches: the users of a CRM are defined in their respective branches. The auditor can verify the

performed activity of the users of one branch or several branches. By default the field is empty. If

left empty, all the branches will be fetched. Otherwise, the user can click on the "Select" button to

choose one or more branches.

Users: the auditor can verify the work of one user or all the users of his institution. By default the

field is empty. If left empty, all users will be fetched. Otherwise, the user can click on the "Select"

button to choose one or more users.

Events: during the inquiry operation the activities that can be executed by the user on the system

are called events. The system provides a predefined list of events that the auditor can select from

to verify the work of a user. By default the field is empty. If left empty, all the events will be

fetched. Otherwise, the user can click on the "Select" button to choose one or several events.

CDR Number: the auditor can verify the inquiry operation executed on a specific CDR number. By

default the field is empty. If left empty, all values will be fetched. Otherwise, the user can choose

only one CDR number.

Event Type: the events defined in the event filed can be charged (billed) or free of charge (Not

Billed). This information is preset by the CDR administration at BDL. By default, this field is set to

"All" meaning all events will be fetched. Otherwise, the user can choose either "Billed" or "Not

Billed" from the drop down list.

of 130

After specifying the searching criteria, the user has to click on the “View” Button to get the “Transaction Result” as follows:

When the user clicks on the button located in the "Trx Description" field in a specified row, a window is popped up with a complete description of the logged Transaction (see example below).

By pressing the button, the report is printed online with the following form:

of 130

By pressing the button, an EXCEL report is produced and another pop-up window is

displayed to let the user choose whether to:

open directly the EXCEL report, by pressing the "Open" button;

save the EXCEL report on the computer, by pressing the "Save" button.

In case of clicking on the "Open" button, an EXCEL file will be opened with the following form:

of 130

6.3.2 Assign Functions to Roles

This function displays in view mode the access rights in the application for different functions based on

roles. If a user has multiple roles, his final access rights will be the aggregation of the permissions of all his

roles. For each role, the administrator can specify if a function can be visible or not and, if it is visible, if the

function will be enabled or not.

The administrator has to select the role for which he wants to view the functions:

When a role is chosen, the list of items that can be available in the main menu of the application is

visualized. The colors are used to show the status of each item for that role:

Red: not visible and not enabled;

Orange: visible but not enabled;

Green: visible and enabled.

By clicking on “+”, the complete tree will be displayed for each item:

of 130

6.3.3 Management of Users to be used by the CRM

This function allows the Administrator to activate and deactivate the users of the bank.

The user can only select or unselect the related checkbox present in the column CRM Activation in order to

activate or deactivate a user and click on the other columns are read only. When the “save”

button is pressed the updates are saved. In case of user deactivation the selected user will not be able to

enter in the application.

By clicking on the original data are replaced.

6.3.4 Assign Users to Groups in CRM

This function allows the Administrator to link the users to one or more groups. The CDR system manages

the following categories of users' groups:

of 130

CRM Inquiry Client Position: it will be assigned to users that are allowed to create and submit CRM

CDR PP/ MP requests (new CDR Number/ update existing client /confirm existing clients) with the

capability to view and inquire positions and receive related answers. They are also allowed to

create and submit requests of “Dictionary Names Request” process;

CRM Managing Client Identity: it will be assigned to users that are allowed to create and submit

CRM CDR PP/ MP requests (new CDR Number/ update existing client /confirm existing clients)

without the capability to view and inquire position and receive related answers. They are also

allowed to create and submit requests of “Dictionary Names Request” process;

CRM CDR Number request Supervisor: it will be assigned to users that are allowed to create

request as per the role: CRM Inquiry Client Position and are allowed to confirm the submission of

requests.

CRM reporting and auditing: It allows to inquiry and print the list of the Requests executed by the

CRM users. It allows the user to print the "Statistics on CRM User’s Process Workload" report

related to the Requests initiated by the CRM users. Also it allows the user to print the Auditing Log

report.

CRM Monthly Declaration Officer: it will be assigned to users that are allowed to create and submit

requests of Monthly Declaration files and receive related answers;

CRM Monthly Declaration Supervisor: it will be assigned to users that are allowed to submit

requests of Monthly Declaration as per the role: CRM Monthly Declaration Officer and are allowed

to confirm the requests of Monthly Declaration in case of re-submission or after the cutoff date;

CRM Security Configuration: it will be assigned to user that are allowed to manage (assign, decline,

activate, …) roles, groups, users and the related security rights, inside the same CRM;

CRM Workflow Administrator: it will be assigned to the user who will be allowed to reassign the

requests from a CRM Officer to another one, inside the same CRM.

BDL provides access rights for the CRM users according to their request. It is possible to assign one or some of them or all groups to a User.

A user can have multiple groups and the final access to functions will be dictated by the reunion of all its

groups’ permissions.

In order to execute the search, the user has to select the Branches.

After specifying the search criteria, the user clicks on in order to get the result as follows:

of 130

All the users and their related assigned groups for the selected branch(es) are shown.

When the user clicks on button, the following pop-up window is displayed with the list of

groups configured for the selected type of user:

The user can add or remove one or more groups linked to the selected user, moving each of them from the

left side to the right side (and vice versa).

By clicking on “Confirm” button the updates are saved.

of 130

6.3.5 Reassignment of a dossier to another user of the CRM

The user who has the role of “CRM WORKFLOW ADMINISTRATOR” can reassign any uncompleted

dossier of an officer to another one.

The user has to click on the function “Reassignment “then click on the sub-function “Organization

Structure” in his “To Do List”.

On the right, on the operational area there is a folder with the name of the bank and within this

folder it exists as a list of all active users on the BDL-CDR.

From this list, the “CRM WORKFLOW ADMINISTRATOR” user has to click on the officer user from

which he has to reassign a dossier or multiple dossiers. By clicking on for exp. user1, a list of all

uncompleted dossiers appears on the right for user1.

The “CRM WORKFLOW ADMINISTRATOR” user can select one or multiple dossiers needed to be

reassigned and then click on .

By clicking on a dialog box appears as shown down with 3 radio buttons:

To myself: It is selected when the selected dossiers are reassigned to the user who is doing

the reassignment workflow.

To other office or other assignment: It is selected when the selected dossiers have to be

reassigned to another active user in the CRM.

Balancing: It is selected when the selected dossiers have to be reassigned equally to

multiple active users in the CRM.

of 130

After clicking on the radio button and selecting the user/users to which the selected dossiers need to be

assigned, the “CRM WORKFLOW ADMINISTRATOR” user has to click the button to confirm the

reassignment or on to cancel it.

7 APPENDIX A

7.1 The Client Liabilities Positions This section indicates the consolidated client liabilities three different forms:

a) Liabilities positions in the whole banking and financial sector called "Position in Sector". b) Liabilities positions with the institution executing the inquiry called "Position with bank". c) Liabilities positions in the banking and financial sector except the institution executing the inquiry

called "Position with others". The Inquiry Report may include the client positions for up to three years back with two positions per year (June and December) plus the positions for the last three months. The client positions are detailed by liability type, economic sector, currency, remaining period and risk classification. All amounts are expressed in millions of Lebanese pounds. The liabilities information of any client is divided in two groups: Direct and Indirect, each group is also divided into two sub-groups:

Direct o Direct Commitments o Received Guarantees

Indirect o Contingent Liabilities o Memorandum Accounts

Therefore the complete situation of a client is presented in four different groups:

1. Direct Commitments: ACB - Credits against escrowed accounts, bank guarantees, treasury or state Bonds/Avances sur

comptes bloqués ou garanties bancaires ou bons du trésor ou autres titres gouvernementaux agréés

AVM - Advance on securities /Avances sur valeurs mobilières ASH - Advance against mortgage/Avances sur Hypothèques ASR - Advance on other real securities / Avances sur autres suretés réelles AGP - Advance on personal guarantee/Avances sur garanties personnelles ABL - Unsecured advance/Avances à blanc

of 130

2. Contingent Liabilities

EF - Financing commitments/Engagements de financement ES - Signature commitments/Engagements par signature OT - Forward operations/Operations à terme SE - Commitments on securities/Engagements sur effets IF - Commitments on financial instruments/Engagements sur instruments financiers AE - Other commitments/Autres engagements AC - Approvals and guarantees/Avals et cautions

3. Received Guarantees

TCB - Total of guaranties in escrow & similar accounts/Total des garanties en comptes bloqués et assimilés

TSR Total of other guarantees / Total des autres guaranties TBI- Total of mortgage securities / Total biens immobiliers

TVM-Total of securities / Total valeur immobilières

4. Memorandum Accounts DF - Assets as credits financed by fiduciary deposits/Crédits financés par dépôts fiduciaires CI - Bad debts/Créances Irrecouvrables CMC- Loans of the clients of Micro credit institutions/ Créances des clients des institutions du

Micro credit PGF- Loans and credits of the portfolio of fund management / Prêts et credits du portefeuille de

gestion de fonds Direct Commitments, Contingent Liabilities and Memorandum accounts are related to loan types which indicate the nature of the loan or facility granted to the client.

8 APPENDIX B

8.1 List of reports

FUNCTIONS REPORTS Print Provisional Inquiry Report CDR-IR0

Position with bank (provisional) CDR-IRP

Position in sector (provisional) CDR-IRP

Position with others (provisional) CDR-IRP

Position with bank (final) CDR-IRP

Position in sector (final) CDR-IRP

Position with others (final) CDR-IRP

Inquiry of requests Inquiry of requests

Inquiry Statistics on CRM User’s Process Workload Statistics on CRM Users Workload

Result of the Technical Validation MES-DR List of Errors

List of errors button (List of the loaded MES-TR files) MES-TR List of Errors

Print Client never declared as debtor (provisional) CDR-IRP

Print Client never declared as debtor (final) CDR-IRP

Auditing Log Report Log Registered