Proposal summary
This proposal describes the HSBC China EFT Template creation with NetSuite. The Payment file templates are used to generate EFT in different formats.
Requirement
QIMA would like to create an EFT File Format for HSBC China bank in XML format in NetSuite.
Our Solution
The requirement can be achieved by creating an EFT template using the XML 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 for the testing purpose. 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
XMLV3 PP CNY.xml
<?xml version=”1.0″ encoding=”utf-8″?>
<Document xmlns=”urn:iso:std:iso:20022:tech:xsd:pain.001.001.03″ xmlns:xsi=”urn:iso:std:iso:20022:tech:xsd:pain.001.001.03″>
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>Payment file administration.ID , (35 characters)</MsgId>
<CreDtTm>Payment file administration.TIMESTAMP</CreDtTm>
<Authstn>
<Cd>Static value “AUTH”</Cd>
</Authstn>
<NbOfTxs>Total number of payments</NbOfTxs>
<InitgPty>
<Id>
<OrgId>
<Othr>
<Id>Company Bank details. HSBC CUSTOMER CONNECT ID</Id>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>Payment file administration. REFERENCE NOTE(16 characters)</PmtInfId>
<PmtMtd>Static value “TRF”</PmtMtd>
<PmtTpInf>
<SvcLvl>
<Cd>Static value “URGP”</Cd>
</SvcLvl>
</PmtTpInf>
<ReqdExctnDt>Payment file administration. PROCESS DATE</ReqdExctnDt>
<Dbtr>
<Nm>company bank.Statement Name</Nm>
</Dbtr>
<DbtrAcct>
<Id>
<Othr>
<Id>company bank.Account number</Id>
</Othr>
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>company bank .BIC</BIC>
<PstlAdr>
<Ctry>company bank.countrycode</Ctry>
</PstlAdr>
</FinInstnId>
</DbtrAgt>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>Payment.tranID</EndToEndId>
</PmtId>
<Amt>
<InstdAmt Ccy=”CNY”>payment.amount</InstdAmt>
</Amt>
<ChrgBr>Static value “DEBT”</ChrgBr>
<CdtrAgt>
<FinInstnId>
<Nm>vendor.name (140 characters)</Nm>
<PstlAdr>
<Ctry>vendor bank details. country code</Ctry>
</PstlAdr>
</FinInstnId>
</CdtrAgt>
<Cdtr>
<Nm>vendor bank details.name</Nm>
<PstlAdr>
<Ctry>vendor bank details.country code</Ctry>
</PstlAdr>
</Cdtr>
<CdtrAcct>
<Id>
<Othr>
<Id>vendor bank details. account number</Id>
</Othr>
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>Payment. Reference (140 characters)</Ustrd>
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>
Validation
| Field | Minimum Length | Maximum Length | |
| company bank . HSBC CUSTOMER CONNECT ID | 1 | 35 | Mandatory |
| company bank . Statement Name | 1 | Mandatory | |
| company bank . Account number | 1 | 34 | Mandatory |
| company bank .BIC | Mandatory | ||
| vendor bank details.name | 1 | 70 | |
| vendor bank details. account number | 1 | 34 |
Assumptions
- We have added the field mapping of Payment file template. We will create the a payment templates for all currencies in XML format based on field mapping.
- We will not provide any validation for fields other than the mentioned validations.
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.
- J&J created the field mapping on assumption based on bank file. 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.