Proposal For HSBC India EFT Template

Proposal summary 

This proposal describes the  HSBC India EFT Template creation with NetSuite. The Payment file templates are used to generate EFT in different formats. 

Requirement 

QIMA would like to create a EFT File Formats for HSBC India templates in CSV format in NetSuite. 

Our Solution 

The requirement can be achieved by creating a EFT template using the CSV format for all currencies based on the client’s requirement. Also need to create company bank details and entity bank details for the new Payment file templates. Then that templates needs to be tested by creating the vendor bills for the test vendor and need to do the bill processing for verification. 

Field Mapping 

Header Record: 

Cell	Data Field	Mandatory/Conditional	Value	Length	Validation
1	Identifier	M	Static value: BULKPAY CSV	Maximum length 11
2	Customer ID	M	Company bank details. Company ABC id	Maximum length 11	Maximum length 11
3	File Reference	M	Payment file administration(PFA).reference	Maximum length 35
4	File Submission Date	M	PFA. process date(format YYYY-MM-DD)
5	File Authorization Mode	M	Static value “F”

Transaction record: 

Cell	Data Field	Mandatory/Conditional	Value	length	Validation
1	Ach Transaction Type	M	Static value “IN-ACH-BSP”
2	Reference Number	M	Document number of transaction	Maximum length- 12
3	Batch Ref no	M	PFA. reference	Maximum length- 35
4	Bene Name	M	Vendor bank.Name	Maximum length- 140
5	Remitter A/c no	M	Company bank. Account number	Maximum length- 34	Maximum length- 34
6	Remitter Name	M	Company bank. Legal name	Maximum length- 140
7	Narration	O	Reference number of vendor bill.	Maximum length- 140
8	Value Date	M	PFA. Timestamp (creation date, format: MM/DD/YYYY)	Maximum length- 140
9	Amount	M	Total amount of payment including decimal point and decimal values(eg: 10.67)	Maximum length- 18
10	eMail Address 1	O	Vendor bank. email	Maximum length- 70
11	eMail Address 2	O	This field will be blank always
12	eMail Address 3	O	This field will be blank always
13	Advise Col1	O	Vendor bank details. Advice	Maximum length- 35	Maximum length- 35
14	Advise Col2	O	This field will be blank always
15	Advise Col3	O	This field will be blank always
16	Advise Col4	O	This field will be blank always
17	Advise Col5	O	This field will be blank always
18	Bene Bank Account number	M	Vendor bank. account number	Maximum length- 34
19	BeneRTGSCodes	M	Vendor bank details. IFSC	Maximum length- 34	Maximum length- 34
20	Bene Bank Name	O	Vendor bank. Bank name	Maximum length- 140	Maximum length- 140

Assumptions 

• We have added the field mapping of  Payment file templates in table. We will create a payment template for all currencies in CSV format based on field mapping. 
• We will not provide any validation for fields other than mentioned validations. 

• Since the email address fields are optional and vendor bank details record contains only one email field, we will add only one email value to the output file. And remaining 2 email fields will be always blank in output file. 
• Since the Advice fields are optional, we will add only one advice field to the vendor bank details. So user can enter value in that field if required. And that value will populate to the output file. And remaining 4 advice fields will be always blank in output file. 
• We will not add headings to the output file. 

Risk 

• If the value contains preceding zeros, when NetSuite generates output file, the preceding zeros will not show in the CSV file. 
• J&J will not create the actual company bank details and vendor bank details in this scope. QIMA has to create company bank details and vendor bank details with Actual details. 
• J&J created the field mapping on assumption based on provided field mapping. If the bank reject this template due to incorrect field mapping after the development, J&J might have to revise the template. That is not considered in this scope. So that additional effort will be billed as support hours.