Introduction |
This option allows you add a new retail user record. The admin will be able to create a retail user only after linking a CIF ID, that is, as a first step the admin needs to give a CIF ID and based on the CIF ID, the CRM related details would be displayed to the admin by making a FI call to CRM. During user creation or modification, the bank admin will not be allowed to modify the CRM related details and these would be un-editable fields. The CRM related details include the CIF ID, First Name, Middle Name, Last Name, Address, City, State, Country, and Zip which are fetched from CRM database through FI. The CIF ID that was linked during the user creation would be made as the primary CIF ID for the user. |
Navigation |
The following is the navigation for this option:
|
What you can do |
The table below provides a brief description of the data that must be specified on the screen and the functions you can perform: |
Field |
Description |
CIF ID |
Select the required CIF ID from the list. Click Lookup to get the CIF IDs that are registered for e-Banking. Note: This is a mandatory field. |
Bank Id |
The unique ID of the bank. This field cannot be edited. |
CIF ID |
The primary CIF ID linked to the retail user. Note: This is a mandatory field. |
Retail User |
The ID of the retail user to be created. This field cannot be edited. |
First Name |
The first name of the retail user. Note: This is a mandatory field. |
First Name (Alternate Language) |
The first name of the retail user in a language other than the language set as the default. |
Middle Name |
The middle name of the retail user. |
Middle Name (Alternate Language) |
The middle name of the retail user in a language other than the language set as the default. |
Last Name |
The last name of the retail user. Note: This is a mandatory field. |
Last Name (Alternate Language) |
The last name of the retail user in a language other than the language set as the default. |
Salutation |
From the drop-down list, select the salutation to be used for the retail user. For example, Mr., Dr., Prof., and so on. |
Category Code |
The category code the retail user is classified. |
Anniversary Date |
The wedding anniversary date of the customer. |
Email Id |
The email ID of the retail user. |
Amount Format |
From the drop-down list, select the amount format. After user’s login, they can view the amount in this format. |
Date Format |
The customer's preferred date format. The format specified will be used to print reports or display balances to the customer. |
Language Id |
The ID of the language to be used for communication with the customer. |
Available Languages |
Select the language from the list of languages available in the application. |
Administration ID |
Select the Relationship Manager ID. This group id will be used by the retail user for correspondence. |
Brand Id |
Select the brand ID from the list of brand IDs. Note: Based on the selected brand ID, the look and feel of the retail user’s screen is decided. |
Menu Profile |
Select the menu profile for the retail user. The options display only retail user related menu profiles. |
User's Interests |
Select the interests of the user . |
Multi Currency Transaction Allowed |
Indicate if the multi-currency transactions are allowed to the customer account. |
Disabled for Transaction |
Indicates whether the retail user is enabled or disabled for the transaction. As this screen is used for creating a retail user and still password is not set and user is not enabled, retail user cannot perform a transaction, hence this field will always be Y and this is a non editable field. |
Address |
The address of the retail user. |
Address (Alternate Language) |
The address of the retail user in language other than the default language. |
Address for Correspondence |
Specify the address for correspondence. This can be any address like residential, official, and so on. |
City |
Specify the city of the retail user. |
City (Alternate Language) |
Specify the city of the retail user in an alternate language. |
State |
Select the state where the customer is located. Note: This is an optional field. |
Country |
Select the country to which the retail user belongs. |
Zip |
The pin/zip code of the area where the retail user is located. |
Phone No. |
The phone number of the retail user. (Generally this will be user’s land line number). |
Mobile Phone No. |
The mobile phone number of the retail user. |
Fax No. |
The fax number of the retail user. |
Gender |
Specify the gender of the retail user. |
Customer Status |
Specify the status of the retail user, bank will categorize the customers as A class, B class based upon bank’s policies. |
Income Range |
Specify income range of the retail user. |
Residential Status |
Indicate the residential status of the customer. |
Date of Birth |
Specify the date of birth of the retail user. This must be in M/D/YY format. |
Number of Household |
Specify the number of house hold for retail user. |
Occupation |
Select the kind of occupation of the retail user. |
Marital Status |
Select the marital status of the retail user. |
Educational Level |
Select the educational level of the retail user. The bank must set the education level as A for Master degree, B for Bachelors, and so on. |
Passport Number |
Specify the passport number of the retail user. |
Passport Issue date |
Specify the passport issue date of the retail user. |
Passport Details |
Specify the passport details of the retail user. |
Passport Expiry Date |
Specify the date on which the passport expires. |
Pan / National ID |
The permanent account number or National ID number assigned to the customer for income tax payment. |
Transaction Limit Scheme |
The transaction limit that is the applicable to the user can be selected from the drop-down. The periodic limit maintained in the selected transaction limit will be applicable to the user for those transactions and the channel through which the transactions are done. |
Entry Limit Scheme |
The entry limits applicable to the user can be selected from the drop-down. |
Authentication Mode |
The type of authentication used for activities like login and non financial transactions. Valid values: Password Secure Token Digital Certificate SMS based Mobi Token Device based Mobi Token Note:
|
Authorization Mode |
The type of authorization required. Valid values: Password Secure Token Digital Certificate SMS based Mobi Token Device based Mobi Token Note:
|
Secondary Authentication Mode |
The secondary authentication mode can be selected from the drop-down. Valid Values: Password Secure Token Digital Certificate SMS based Mobi Token Device based Mobi Token |
Authorization Mode Precedence |
From the drop-down list, select whether authorization level for the retail user. Valid values: User level Transaction level |
Applicable Amount for Workflow |
The amount applicable for the workflow can be selected from the drop down. Valid Values: Total Batch Amount Highest Batch Amount |
Trace Account |
Whether trace account to be enabled for the user or not, can be specified through “Yes” or “No” option. If trace account is enabled, user has to specify the accounts he has to designate as trace accounts under the Personal Profile option. Whenever there is a transaction failure, application reverses the transaction in the specified trace account, so that it is easier for the user to track the funds. |
Accessible Financial Transaction Types |
The financial transaction types to be accessible to the user can be selected from the list box. |
Register For Alerts |
|
Register For Alerts |
Select the value to register for alerts. |
Scheme ID |
The scheme ID for the alert to charge collection. |
Don’t Disturb Time |
The do not disturb period for alert delivery. |
|
|
|
|
|
|
|
|
Click |
To |
Submit |
Insert the new retail user ID created in the database. |
Reset |
Reset the contents of the page. |
Back |
Return to the previous screen without saving the changes. |