Proposal summary

This proposal describes the  CTBC Bank EFT Template creation with Netsuite. The Payment file templates are used to generate EFT in different formats.

Requirement 

QIMA would like to create EFT File Formats for CTBC bank using the provided sample format in Netsuite.

Our Solution

Prerequisite

We need the Full level permission of the following for the Tech role for consultants:

1. Vendor
2. Bill and Bill Payment
3. Bill EFT Details
4. Bill EFT Payment Information
5. Company Bank Details
6. Electronic Payments Preference
7. Bank Details
8. Format Details
9. Payment Aggregation
10. Payment File Administration
11. Payment File Format
12. Approval Department
13. Approval hierarchy
14. Approval routing
15. Batch Details
16. Batch Transaction Information
17. Encryption Details
18. EP Company Information
19. EP Dummy List
20. EP Execution Log
21. EP Queue Settings
22. EP Thread Processing Results
23. Payment Batch

Description of task

The requirement can be achieved by creating an EFT template using the provided sample 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 template. Then that template needs to be tested by creating the vendor bills for the test vendor and need to do the bill processing for verification.

Field Mapping

Cell	Header	Netsuite field
A1	Static value “Report Generation”
A3	Static value “txt file conversion”
B1	Static value “Customer ID*”
C1		Company bank details.Bank Company Id
B2	Static value “CUSTOMER NAME*”
C2		Company bank details.Bank name
B3	Static value “DEBIT ACCOUNT No.*”
C3		Company bank details.Account Number
D1	Static value “BRANCH CODE*”
E1		Company bank details.Branch Number
D2	Static value “CURRENCY *”
E2		Company bank details.currency
D3	Static value “Application Date”
E3		Today’s date
F1	Static value “Payroll(Confidential)”
C4	Static value “Beneficiary Information”
F4	Static value “Beneficiary Bank Information”
A5	Static value “Value Date*(YYYYMMDD)”
A6		Payment file administration. Process date
B5	Static value “Amount*”
B6		Total bill amount
C5	Static value “Beneficiary Name*”
C6		Vendor. name
D5	Static value “Beneficiary Account*”
D6		Entity bank details.Account number
E5	Static value “Beneficiary Address*”
E6		Vendor.Address
F5	Static value “SWIFT Code*”
F6		Entity bank details.Swift code
G5	Static value “Beneficiary Bank*”
G6		Entity bank details.Bank Name
H5	Static value “Clearing Code(If any)”
H6		blank
I5	Static value “Bank Address”
I6		Entity bank details. Address1
J5	Static value “Beneficiary Bank Country Code*”
J6		Entity bank details.Country
K5	Static value “Detail Charge(BEN/SHA/OUR)*”
K6		We will add a new text field in entity bank details. The user needs to add BE/SHA/OUR in that field. The value will auto-populate to the template.
L5	Static value “Payment Details”
L6		Payment file administration. reference note
M5	Static value “Purpose of Remittance”
M6		blank
N5	Static value “Intermediary Bank Swift code”
N6		Entity bank details. New field Intermediary Bank Swift code
O5	Static value “MT202(Y/N)”
O6		We assume when generating the output file, the value will be “N”. And the user can change the value to “Y” by editing the file.

Note

• Since the output file type will be CSV, styling will not be applicable for the file.

Assumptions

• Need to create the payment template for all currencies.

Risk

• 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.
• Will not provide any validation for fields like minimum length and maximum length.