User Guide. Beneficiary Registration Implementation Guide - Japan

Transcription

1 User Guide Registration Implementation Guide - Japan June 2017

2 Contents About... 1 Introduction... 1 Entitlements... 1 Upload a file... 2 File Specification of the CSV Format:... 1 Header... 1 Data Record... 1 File Error... 3 File Rejection... 4 Report Specification... 6 June 2017 i

3 About Introduction This message Implementation Guide (MIG) is prepare by HSBC for data being submitted through HSBCnet File Upload. The purpose of this document is to provide guidance for the creation of a Registration message to allow specific payment type to be processed in Japan. To create a payment using your Japan debit account, you will require the receiver of the payment to be a registered beneficiary. The following payment types require a registered beneficiary: Type of Payments Authorization Level Format Type -File Level Summary -ifile -File Level Details -XML (Version2 & Version 3) -Instruction Level Authorisation (ILA) -SWIFT (MT103) -Pre Authorisation -Paymul -Priority Payments (international) -Priority Payments Zengin (domestic) -Customer Transfers ACH Credits -File Level Summary -File Level Details -Instruction Level Authorisation (ILA) -Pre Authorisation -ifile -XML (Version 2 & Version 3) -Paymul -Zengin Entitlements System Administrators are required to grant entitlements to all Users who will be uploading Payment files. The entitlement can be granted via the File Upload entitlement screen by selecting the Payment checkbox in the Preauth level column. Payment Entitlement screen June

4 Users must also be entitled to the Payment Upload Report, which will be available in the Report and File download entitlement screen. The Payment Upload Report will provide acknowledgment/stats information for all upload Payment files. Report and file download entitlement screen *Additional details are available in the Entitlement User guide if needed. Upload a file To upload your file, select the file, format and authorisation level: File Types: Payment File Format: CSV Authorisation Level: Pre authorized Only one user is needed to upload the file, no authorisation is required. June

5 File upload Note: The maximum limit to include on one file is 5,000 beneficiary accounts. To create this file please see the file specifications listed below. Once you have uploaded the file Payment file via the File Upload service and the beneficiary accounts have been properly validated, HSBCnet will send an Acknowledgement Report in the Report & File Download service with the status notification of the file. If your file is unsuccessful then you will receive error message in your report explaining what went wrong. You must look at your rejection report to see what the error message is as some errors need you to resubmit the whole file and some need you to just resubmit the one instruction that had failed. Please see the section File Errors to see those error messages. June

6 File Specification of the CSV Format: Header Data Fields Mandatory/O ptional/ Conditional Length (bytes) Remarks Validations Identifier M 9A 'AUTHBENEH' File rejected if not present. Customer ID M 11X Customer to populate this value with - 'ABCXXXXXXXX' File rejected if not present or invalid customer id. File Reference M 35X JP File rejected if not present or unique at customer level. Customers debiting a Japan account to pay the below Accounts must use the prefix 'JP-' in their reference i.e. JP File Submission Date File Submission Time O 10n YYYY:MM:DD The format will be YYYY:MM:DD O 8n HH:MM:SS The format will be HH:MM:SS File Authorization Mode M 1A 'A' - Pre-auth Default pre-auth.file rejected if value present in anything other than 'A' or blank. Line Count M 6n Total number of lines present in file Rejected if not present or count is not correct. Number of beneficiary accounts to be processed M 6n Total Number of beneficiary accounts to be processed Rejected if not present or count is not correct. Local Language Character Set M 4X JIS1 Valid values are: GB01 Simple Chinese BG51 Traditional Chinese KR01 - Korean JIS1 - Japanese including Katakana U801 Universal Coding (UTF8 EBCDIC) Data Record Data Fields Mandatory/ Optional/ Conditional Length (bytes) Remarks Validations Identifier M 10A 'BENEDET' File rejected if not present. June

7 Data Fields Mandatory/ Optional/ Conditional Length (bytes) Remarks Validations list ID* C 12n Will be generated by system in case customer does not provide. If Id is provided, please use unique ID. For record deletion, this field is mandatory. Name M 105k Priority Payment and Customer Transfer - Maximum 35 bytes supported. Zengin Priority Payment -Maximum 35 half width Katakana characters or 35 bytes English characters allowed. ACH CR Payment -Maximum 30 half width Katakana characters or 30 bytes English characters allowed. Address Line 1 Address Line 2 C 35k Mandatory for oversea payment. C 35k Mandatory for oversea payment. Address Line 3 C 35k Mandatory for oversea payment. Payment Type M 50A PP (Priority Payment) PPZG (PP Zengin) ACH (ACH Credit) CT(Customer Transfer) Action M 1A A= ADD D=Delete 'Add' will include Account details. 'Delete' will remove Account details. Account Country M 2A Example: JP Item rejected if not present OR country code is invalid. Account Number M 35n File rejected if not present. Preceding zero if it is required. In case there is same account number used by different banks, please assign List ID and sort records input file with account number. Account Identifier M 10A I-IBAN B-BBAN L- Local account number BCUR-BBAN with currency BCHK-BBAN with check digit Item rejected if not present or value is incorrect. Bank Identifier Code C 12X Local Bank code OR BIC Zengin Account number format: If ' Account Identifier' is "L" then this field is mandatory - Local bank code must be populated. For Japan payments this field is mandatory.( Zengin Bank Code & Branch code preceding zero) The below BIC validation will ONLY be applicable Bank Identifier Type SWIFT or Sort Code: a)length of BIC code. b)country code in BIC code June

8 Data Fields Mandatory/ Optional/ Conditional Length (bytes) Remarks Validations Bank Identifier Type C 3A SWF for SWIFT BID for Bank Code FED for FedWire SRT for SortCode ABA for US CHIPS ABA BSB for Australian Bank State Branch (BSB) Code If ' Account Identifier' is "L" then this field is mandatory. Account no marker O 10x Not use AC1-AC9999 Same marker should be used for different account formats belonging to the same Account number and should be mentioned in sequence and not randomly. Same marker can only be used max 4 times in a file. Account Type C 2A CA' for Current Account 'SA' for Savings Account 'DA' for Direct Account 'OT' for Others If Customer has not provided any info, It would be Updated as SPACES in database. For Zengin Payment, this field is mandatory. Example View from Notepad File Error There are two sets of error messaged presented below. The first set of error message is referred to as first level checking error messages. If your file is presented with any of these error messages, this means your file is rejected and the whole file has to be re-submitted. June

9 Error Code Error Description Description 05 DUPULICATE FILE/INTERCHANGE File reference. File rejected if not unique at customer level. 07 INVALID RECORD COUNT Line count. Reject if count is not correct. 34 CUSTOMER ID IS UNKNOWN Invalid customer ID in the Customer ID field of the file. 88 AUTH LEVEL NOT APPLICABLE TO FILE TYPE File authorization mode. Reject the file if value present is anything other than A or blank. 96 CID NOT VALID FOR UPLOAD GIB ID Please verify the File reference information, it need it to begin with JP-. EA MANDATORY DATA MISSING Mandatory fields are missing. GQ DUPLICATE BENEFICIARY ACCOUNT NUMBER Duplicate beneficiary account number. Please assign unique List ID and upload if it really necessary for registration. T6 INVALID BENEFICIARY ACCOUNT Rejected if beneficiary account have an invalid format. File Rejection If your report contain any one of these second set of error messages then those specific instructions will need to be resubmitted. We refer to these error messages as instruction level rejections as they only reject that specific instruction and not the whole file. June

10 Error Code Error Description Description 75 INVALID BENEFIIARY BIC Length of BIC code(either 8 or 11) 79 MANDATORY DATA MISSING Mandatory fields should be present. i.e. Bank Identifier Code. Account Identifier is L then this filed is mandatory 80 INVALID ACCOUNT TYPE Account type has any other account type. 98 INVALID CODE TYPE Action Type is format is not A or D D6 GO INVALID BENEFICIARY ACCOUNT TYPE INVALID BENEFICIARY CODE IN IBAN Account Identifier must be present with valid value. Country code in IBAN should match country code mentioned in Bank Country Code in the file. GP INVALID IBAN LENGTH IBAN length validation. GQ GR DUPLICATE BENEFICIARY ACCOUNT NUMBER INVALID BENEFICIARY CODE IN IBAN Uploaded duplicate beneficiary details where Account number and Payment type matches record need to be rejected if Action field in the file A Country code must be the same as the first 2 characters of the beneficiary account. GT INVALID PAYMENT TYPE Check Payment Type. HU HX INVALID BENEFICIARY CODE IN BIC DUPULICATE BENEFICIARY ID Country code in BIC code should match country code mentioned in Bank country code in file. When customer upload a record, if (CUSTOMER+BENEFICIARY ID) already available in Database. IY IBAN VALIDATION FAILURE Check the countries permitted IBAN length. Instruction Level rejection example June

11 Report Specification PAYMENT BENEFICIARY FILE ACK Acknowledgements: File reference File level status '00' - Success '01' - Partially Rejceted '02' - Fully Rejected Error description Batch details (Line 2 onwards) Not to be populated when file level error occurs ID Name Payment Type Account Country Account Number Bank Identifier Code Record level status '00' - success 'XX' - error (where 'XX' = error code) Error description June