GEODICHOTOMIES IN THE CONFIGURATION
GEODICHOTOMIES IN THE CONFIGURATION OF DRAMATIC GEOPATHOLOGY
4.1 Geographical Isolation in the Face of the Community
88. Data extracted from legacy system must be in the following format:
Name of Field Length Legacy Mapping ALT.ACCT.ID As from legacy
system CUSTOMER 1-10 N ACCT NAME 1 35AN ACCT NAME 2 35AN SHORT NAME 35AN
CATEGORY 4 N
CURRENCY 3 AN
JOINT.HOLDER 1-10N RELATION.CODE 2N
PASSBOOK 1A
POSTING RESTRICT 2N ACCOUNT
OPENING DATE 8N ACCOUNT
MNEMONIC 10AN
89. It is preferable to have the data in comma-separated format.
90.Local data for Account
91. Information, which is specific for the bank, is defined in T24 local reference fields. The list of such fields, applicable content is attached.
92. Data for the Account, both the core and local fields must be provided in the order mentioned in comma-separated format. Care must be taken to ensure that the ‘,’
character does not appear within the data provided.
93.Interest and Charge Liquidation Account Link
94. The following information is required to link a different Interest posting account
95. Interest Liqu Acct – The account number, which must be used for Interest posting for this account. Must be an account defined in T24.
96. Charge Account – The account number , which must be used for Interest posting for this account. Must be an account defined in T24.
97. Data extracted from legacy system must be in the following format:
Name of Field Length Legacy Mapping ALT.ACCT.ID As from legacy
CHARGE.ACCOUNT As from the legacy system
98. It is preferable to have the data in comma-separated format.
99.Overdraft Link to Account
100. After creation of Accounts and Limits, the created overdraft limits must be linked to the accounts. While creating the link the following information must be provided.
101. Alt Acct Id – The original account number from the legacy system must go into this field.
102. Limit Ref — Applicable for overdraft accounts. Provide the limit reference and sequence number.
103. E.g. If the overdraft Limit reference is 100 and this is the first overdraft limit then the value must be provided as 100.01
104. Data extracted from the legacy system must be in the following format Name of Field Length Legacy Mapping
ALT.ACCT.ID As from legacy system
LIMIT.REF 1N
105. It is preferable to have the data in comma-separated format.
106. Limit Link for Export advances
107. After creation of Accounts and Limits, the created overdraft limits must be linked to the accounts. While creating the link the following information must be provided.
108. Alt Acct Id – The original account number from the legacy system must go into this field.
109. Limit Ref — Applicable for export advances accounts. Provide the limit
reference and sequence number. E.g. If the overdraft Limit reference is 500 and this is the first overdraft limit then the value must be provided as 500.01
110. Data extracted from the legacy system must be in the following format Name of Field Length Legacy Mapping
ALT.ACCT.ID As from legacy system
LIMIT.REF 1N
111. It is preferable to have the data in comma-separated format.
This user guide explains the data migration of Customer data from an existing legacy system to T24.
Data Takeover for Customer
This file holds the basic information for any Customer that the bank deals with:
Customers holding contracts and / or accounts
Correspondent banks
Brokers
Guarantors and any other entity that the bank does business with.
The following are the details required to create a customer in T24
Customer Number – Also known as the @ID, this must be a valid number, 1 to 10 digits long, and is used to uniquely identify the customer across the bank. It is also possible to allocate a specific range for special customers of the bank, if the bank has such practice.
Mnemonic – An alternative means of referencing the Customer, the value in this field allows easy retrieval of often used customer numbers. Mnemonic must be at least 3 and at most 10 characters long. Alphanumeric values and ‘.’ are accepted but the first character must be definitely alpha. If the bank does not have a specific requirement for mnemonics, the system can be made to generate this.
Short Name – Customer Short name, which will be used as enrichment in various applications when the customer number or mnemonic is input. Short name must be at least 3 and at most 35 characters long. & Character is allowed but is replaced with “ “ if short name is used in swift messages. / Character is allowed in the short name but not as the first character.
Note: While duplicates are allowed in short name, it is recommended that this field is kept as unique as possible for the user to identify the customer.
Name .1 – This is the correspondence name of the Customer. Name 1 must be at least 3 and at most 35 characters long. Validations are similar to Short name and special characters allowed are
& , /. When the length NAME.1 is not adequate NAME.2 can be input.
Street – Identifies the first line of the Customer’s main address. This field is mandatory input and accepts 3-35 long valid swift characters.
Town Country Post Code Country
The above 3 fields together with Street record the address of the Customer. Each of these can be 1-35 long valid swift characters.
Sector – Customers can be classified by Sectors in T24. This list of valid sector codes is crystallised during the Business Review process and the same as extracted is available
in Annexure —. If the legacy system does not have this classification, the bank may either opt to do this classification before inputting to T24 (recommended) or the system may be requested to put all customers in to pre defined one or 2 codes.
Account officer – Identifies the main Relationship Officer responsible for the customer.
The account officer information extracted from the legacy system must be mapped and
converted to valid T24 Account officer codes before Migration. This field forms the basis for the production of MIS reports and hence needs careful consideration while setting up. List of officers in the bank are collected during business review process is available in Annexure —.
Industry – Customers can be classified by Industry in T24. The list of valid Industry codes is crystallised during the Business Review process and the same as extracted from TAABS is available in Annexure —. If the legacy system does not have this classification, the bank may either opt to do this classification before inputting to T24 (recommended) or the system may be requested to put all customers in to pre defined one or two codes
Target – Classification code to assess the potential / worthiness of the Customer to the bank.
The Target information extracted from the legacy system must be mapped and converted to valid T24 target codes before migration. The list of valid target codes and associated
descriptions is available in Annexure —.
Customer Status – Identifies the current status of the Customer. The Customer status information extracted from the legacy system must be mapped and converted to valid T24 customer status codes before migration. The list of Status codes agreed during Business review is available in Annexure –
Nationality – Identifies the nationality of the Customer
Residence – Identifies the country of residence of the Customer.
Both these fields should be valid country codes. A list of country codes is in Annexure – Customer Liability – The liability customer must be a valid customer code. When the liability customer is the created customer himself, then the number from the customer id must be provided here. Please ensure that when data is provided, the liability customer is created before the current customer.
Date of Birth – The date of birth of the customer must be a valid T24 date.
Language – The language of correspondence for the customer.
Default to 1 English if only English is available
Contact date – The date customer was opened, must be a valid T24 date
Text – Multi valued free format narrative field to hold information about the customer.
Introducer – Name of the introducer, 35 character free format text is allowed as input.
RELATION information, if required can be uploaded after the successful migration of valid customer information.
The bank must provide the Customer information in the following format:
Name of Field Characteristic
It is preferable to have the data in comma-separated format.
Local data for Customer
Information, which is specific for the bank, is defined in T24 local reference fields. The list of such fields, applicable content is attached.
Data for the customer, both the core and local fields must be provided in the order mentioned in comma-separated format. Care must be taken to ensure that the ‘,’ character does not appear within the data provided. E.g. Customer Address.
Data Takeover for Customer Relation
Takeover of customer relationship can be performed only after taking over Customer information. The following information is required
Customer Number – The customer reference for which the relation is defined. 1 to 10 digits long.
Relation Code – Indicates the relation type of relationship this customer holds with the related customer. List of relationships is provided in Annexure —.
Rel Customer – The customer reference of the related customer.
It is possible to define multiple relationships for a customer.
Note : When taking over customer relation ship, it is sufficient to define one side of the relation ship. The reverse side is automatically derived and populated by T24.
When taking over relationship, data must be provided in the following format.
Name of Field Characteristic
It is preferable to have the data in comma-separated format.
Data takeover for Customer Address
This file holds the Customer address. This includes both
Additional Print address. The default print address is automatically copied over from the customer table.
Swift address of the customer.
The following are the details required for additional print address,
Address Key – The id of the DE.ADDRESS application. The must be of the following format
<<COMPANY.CODE>>. C-<<Customer Code>> . <<CARRIER>>. <<ADDRESS NUMBER>> The CARRIER must be PRINT. The address number must be 2-9.
Short Name – Customer Short name, which will be used as enrichment in various applications when the customer number or mnemonic is input. Short name must be at least 3 and at most 35 characters long. & Character is allowed but is replaced with “ “ if short name is used in swift messages. / Character is allowed in the short name but not as the first character.
Name .1 – This is the correspondence name of the Customer. Name 1 must be at least 3 and at most 35 characters long. & Character is allowed but is replaced with “ “ if short name is used in swift messages. / Character is allowed in the short name but not as the first character. When the length NAME.1 is not adequate NAME.2 can be input. Validation rules are similar to
NAME.1, except that NAME.2 is not mandatory.
Street Addr – Identifies the first line of the Customer’s main address. This field is mandatory input and accepts 3-35 long valid swift characters.
Town Country – Identifies the Town and country of Customer’s residence.
Post Code – Identifies the postcode of Customer address. 1-35 long valid swift characters. Non-Mandatory input.
Country – Identifies the Country of Customer address. 1-35 long valid swift characters.
Non- Mandatory input.
The bank must provide the information in the following format
Name of Field Characteristic
It is preferable to have the data in comma-separated format.
When taking over swift addresses the following information is required
@ID – The id of the DE.ADDRESS application. The id is of the following format
<<COMPANY.CODE>>. C-<<Customer Code>> . <<CARRIER>>. <<ADDRESS NUMBER>> The CARRIER must be SWIFT. The address number must be 1-9.
Delivery Address – Swift address of the customer. 8 or 11 characters for normal customers and 9 or 12 characters for companies.
Short Name – Customer Short name, which will be used as enrichment in various applications when the customer number or mnemonic is input. Short name must be at least 3 and at most 35 characters long. & Character is allowed but is replaced with “ “ if short name is used in swift messages. / Character is allowed in the short name but not as the first character.
Name of Field Characteristic
It is preferable to have the data in comma-separated format.
Data takeover of BIC Codes
Holds the list of BIC codes. The following fields are required to be passed for takeover
@ID
The BIC Id. Must be 8 or 11 characters long.
Tag
Tag identifier.
Institution Name
Name of the institution. 35 characters text field.
City
Name of the city, input is 35 characters text field.
Sub Type
The type of financial institution, 4 characters long.
Services
This field identifies the Value Added Service(s) the financial institution has subscribed to, 20 characters long.
Address
Address of the BIC, input is 35 characters long.
Location
The location of the BIC, input is 35 characters long.
POB Number
Post office box number for the BIC code, input is 35 characters long.
POB Location
Post office box location, input is 35 characters long.
POB Zip
This is the zip code for the Post Office Box that the financial institution may use, input is 35 characters long.
POB Country
The country where the Post office boxes reside, input is 35 characters long.
The bank must provide the BIC information in the following format
Name of Field Characteristic
SUB.TYPE 4AN
SERVICES 20AN
ADDRESS 35AN
LOCATION 35AN
POB.NUMBER 35AN
POB.LOCATION 35AN
POB.ZIP 15AN
POBCOUNTRY.COD
E 2A
It is preferable to have the data in comma-separated format.