rmb payment purpose code requirements -...

RMB Payment Purpose Code Requirements

February 2014

RMB Payment Purpose Code Requirement

Published: February 2014 i

Disclaimer

This document is issued by HSBC Bank plc (‘HSBC’). HSBC Bank Plc is authorised by the Prudential

Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation

Authority (Registration Number 114216). This document is for information purposes only and does not

constitute or form any part of (i) any invitation or inducement to engage in investment activity, or (ii) any

offer, solicitation or invitation by HSBC or any of the HSBC Group for the sale or purchase of any

products, services and/or any investments.

HSBC provides this document to the recipient on an ‘as is’ basis and except as provided herein, does

not warrant that the contents of this document is accurate, sufficient or relevant for the recipient’s

purposes.

HSBC may have obtained information in this document from sources including from third party

suppliers, it believes to be reliable but which have not been independently verified. In relation to

information on products and/or services supplied by a third party supplier, the recipient should obtain

further information on these products and/or services directly from the supplier.

Please note that this document may contain hypertext links to websites operated by other members of

the HSBC group and third parties respectively. In relation to hypertext links to websites operated by

members of the HSBC group, please read the terms and conditions of the linked website. In relation to

hypertext links to websites operated by third parties, please note that: (1) the recipient should read the

terms and conditions of the website; and (2) HSBC does not have any control whatsoever over these

websites and shall not be liable for the recipient’s use of them.

HSBC will use its reasonable endeavours to ensure that the contents of this document are current at the

date of its first publication. HSBC gives no undertaking and is under no obligation to provide the

recipient with access to any additional information or to update all or any part of the contents of this

document or to correct any inaccuracies in it which may become apparent.

HSBC is not responsible for providing the recipient with any legal, tax or other advice regarding the

contents of this document and the recipient should make its own arrangements in respect of this

accordingly. This document has not been prepared to address the specific requirements or objectives of

any particular client. The recipient is solely responsible for making its own independent appraisal of an

investigation into the products, services and other content referred to in this document.

This document should be kept confidential and shall be used for internal business purposes only by the

recipient to whom it is provided and its officers, employees and agents. This document should be read

in its entirety and shall not be photocopied, reproduced, distributed or disclosed in whole or in part to

any other person without the prior written consent of the relevant HSBC Group member. This document

is proprietary to HSBC and the recipient agrees on request to return or, if requested, to destroy this

document and all other materials received relating to the information contained herein.

Except in the case of fraudulent misrepresentation and/or breach of these terms, no liability is accepted

whatsoever by HSBC and the HSBC Group for any direct, indirect or consequential loss arising from the

use of this document.

Please contact your local HSBC representative for further information on the availability of products

and/or services discussed herein in your region.

© Copyright. HSBC Bank plc 2014 ALL RIGHTS RESERVED


Published: February 2014 ii

Contents

File Format: IFILE .......................................................................................................... 1

File Format: MT103 ....................................................................................................... 2

File Format: SAP IDOC ................................................................................................. 4

File Format: H4WMT100 ............................................................................................... 6

File Format: ISO 20022 XMLv2 ..................................................................................... 8

File Format: ISO 20022 XMLv3 ..................................................................................... 9

File Format: PAYMUL / PAYEXT ................................................................................ 10


Published: February 2014 1

File Format: IFILE

For file format IFILE, the payment purpose code can be populated in any of the Bank to Bank

Information Lines i.e. field #55 to #59, as shown below.

List of supported Purpose of Payment codes are as below:

Purpose must be one of below:

1./BUSINESS/CAPITAL TRF

2./BUSINESS/CHARITY DONATION

3./BUSINESS/CURRENT ACC TXN

4./BUSINESS/GOODS TRADE

5./BUSINESS/SERVICE TRADE

Second Party Details Record for HVP and LVP payments

item# Inbound fields in i-File M/O NLS Format

Max Length (Eng)

(in bytes)

Remarks

55

Bank to Bank Information Line 1

O Y AN 35

Please input the above codes into this field or any subsequent fields below.

56


O Y AN 35

57


O Y AN 35

58


O Y AN 35

59


O Y AN 35



File Format: MT103

For file format MT103, the payment purpose code (in red colour) should be populated in tag 72, as

shown below.

Input Description Length Input field Remarks

:72:Bank to Bank information

35x*6 Line 1 : a) Beneficiary Country Code /REC/LCC-xx

where xx = beneficiary bank country code (eg HK, AU, CN) Line 1 information is mandatory for instruction level authorisation

Line 2 : a) 1st Exchange Contract and 1st Take Up amount //CN-12X15X b) Cheque / Draft issuances with delivery method /REC/xxx-yyy

a) 1st Exchange Contract and 1st Take Up amount Tag72 2nd line - 1st Exchange Contract and 1st Take up Amount 12X = contract number or dealer reference / name with left justified with trailing spaces 15X = Drawdown amount or exchange rate and left justified with trailing spaces b) Cheque / Draft issuance where xxx = CHQ or DFT for local currency cheque and demand draft respectively. where yyy = MTB - Mail to Beneficiary (default if blank) MTA - Mail to Applicant CAB - Collect at Br of A/C CTA - Courier to Applicant CTB - Courier to Beneficiary RTB - Registered Mail To Beneficiary

Line 3 : a) 2nd Exchange Contract and 2nd Take Up amount //CN2-12X15X

a) Tag72 3nd line - 2nd Exchange Contract and 2nd Take up Amount This should always appear on the line immediately after /REC/CN as the extension of the 1st exchange contract reference

/INS/xxxxx The code can be used in Tag72 line 2 and line 3 if the above codewords are not used. If the above are used, line 4 onwards can be used.

/ACC/xxxxxx The code can be used in Tag72 line 2 and line 3 if the above codewords are not used. If the above are used, line 4 onwards can be used.

/INT/xxxxx The code can be used in Tag72 line 2 and line 3 if the above codewords are not used. If the above are used, line 4 onwards can be used.




/REC/xxxxx The code can be used in Tag72 line 2 and line 3 if the above codewords are not used. If the above are used, line 4 onwards can be used.

CNY Payment purpose code a)Payment purpose code /BUSINESS/Purpose code

If the above input fields are not used, the input fields will be used for CNY payment purpose code mapping.

Purpose must be one of below: 1. /BUSINESS/CAPITAL TRF 2./BUSINESS/CHARITY DONATION 3. /BUSINESS/CURRENT ACCOUNT ITEMS 4./BUSINESS/GOODS TRADE 5. /BUSINESS/SERVICE TRADE



File Format: SAP IDOC

For file format SAP IDOC, the payment purpose code (listed below in red colour) can be

populated in any of IDOC field pair INSCODEx & INSINFOx, where x = 1,2,3,4.

For field INSCODEx, please provide ‘BUSINESS” as the value.

For field INSINFOx, please provide either one of the list, as listed below.

1. CAPITAL TRF

2. CHARITY DONATION

3. CURRENT ACC TXN

4. GOODS TRADE

5. SERVICE TRADE

Segment Desc.

iDoc Field Name

Field Pos.

Start Pos.

End Pos.

Field Length

Loop max

Data required in iDoc

payment instructions

INSCODE1 13 182 185 12 1 If this field is not used currently, please provide the value “BUSINESS” to define CN RMB Purpose of Payment.

You can choose to use other field-pair of INSCODE + INSINFO.


INSINFO1 15 244 272 29 1 For CNY payment purpose code mapping, Purpose must be one of below: 1.CAPITAL TRF 2.CHARITY DONATION 3.CURRENT ACC TXN 4.GOODS TRADE 5.SERVICE TRADE


INSCODE2 16 314 317 12 1 As explained above.


INSINFO2 18 376 404 29 1 As explained above.





Segment Desc.

iDoc Field Name

Field Pos.

Start Pos.

End Pos.

Field Length

Loop max

Data required in iDoc









File Format: H4WMT100

For file format H4WMT100, the payment purpose code (in red colour) should be populated in tag

72, as shown below.

Tag

Status Field length

Description Remarks

:72: M 24x Payment Currency, Credit Location and Bank ID :72:/REC/CCY:XXX LCC:YY <999999999999> where XXX is payment currency (required only if it is different from the transaction currency specified in Tag 32A) YY is Credit Location <999999999> is credit location's Bank ID

O 29x Advice to Beneficiary By phone -'/PHONBEN/xxx..xxx' where xxx..xxx is phone number By telex -'/TELEBEN/xxx..xxx' where xxx..xxx is telex number

The codewords will be displayed at "Advised by" column in HSBCnet payment screen MT100 HSBCnet /PHONBEN/ PHONE /TELEBEN/ TELEX

O 26x Advice to Beneficiary Bank By phone -'/PHON/xxx..xxx' where xxx..xxx is phone number By telex -'/TELE/xxx..xxx' where xxx..xxx is telex number

The codewords will be displayed at "Instruction Code" column in HSBCnet payment screen MT100 HSBCnet /PHON/ PHON /TELE/ TELE

O 29x Advice to Intermediary Bank By phone -'/PHONIBK/xxx..xxx' where xxx..xxx is phone number By telex -'/TELEIBK/xxx..xxx' where xxx..xxx is telex number

The codewords will be displayed at "Instruction Code" column in HSBCnet payment screen MT100 HSBCnet /PHONIBK/ PHOI /TELEIBK/ TELI

O 28x Cheque/Draft issued by Bank and Handling instruction. '/CHEQUE/xxx...xxx' where xxx...xxx is the description of the instruction as below: - 'Mail to Beneficiary' (default if xxx..xxx is empty) - 'Mail to Applicant' - 'Collect at Br of A/C' - Special instruction entered

The codeword /CHEQUE/ will be displayed as CHQB in "Instruction

Code" while the description of the instruction is shown in "Instruction to bank" as below: MT100 HSBCnet Mail to Beneficiary POST:Beneficiary Mail to Applicant POST:Applicant Collect at Br of A/C POST:Branch Pickup Special instruction entered POST:Special instruction entered (For Hongkong, CO - is not available until further notice DD - "Special instruction entered" is not available until further notice)

O 30x Exchange Contract and Exchange Control Reference - '//ECN:xxxxxxxxxx ECR:xxxxxxx' where the first xx..xx is the exchange contract number, the second xx..xx is the exchange control reference (Note that if no exchange contract number or no exchange control reference, the field will look like: '//ECN:xxxxxxxxxx' or '//ECR:xxxxxxx')



Tag

Status Field length

Description Remarks

O 35x CNY Payment purpose code a)Payment purpose code /BUSINESS/Purpose code

If the above input fields are not used, the input fields will be used for CNY payment purpose code mapping. Purpose must be one of below: 1. /BUSINESS/CAPITAL TRF 2./BUSINESS/CHARITY DONATION 3. /BUSINESS/CURRENT ACCOUNT ITEMS 4./BUSINESS/GOODS TRADE 5. /BUSINESS/SERVICE TRADE

- End of record



File Format: ISO 20022 XMLv2

For file format XMLv2, the payment purpose code (in red colour) should be populated in

<CdtTrfTxInf><RgltryRptg><RgltryDtls><Inf> tag, as shown below.


Payment purpose code for CN cross border RMB payment

35x <CdtTrfTxInf>

<RgltryRptg>

<RgltryDtls>

<Inf>

Purpose of Payment code must be one of below:

1./BUSINESS/CAPITAL TRF 2./BUSINESS/CHARITY DONATION 3./BUSINESS/CURRENT ACC TXN 4./BUSINESS/GOODS TRADE 5./BUSINESS/SERVICE TRADE



File Format: ISO 20022 XMLv3

For file format XMLv3, the payment purpose code (in red colour) should be populated in

<CdtTrfTxInf><RgltryRptg><RgltryDtls><Inf> tag, as shown below.


Payment purpose code for CN cross border RMB payment

35x <CdtTrfTxInf>

<RgltryRptg>

<Dtls>

<Inf>

Purpose of Payment code must be one of below:

1./BUSINESS/CAPITAL TRF 2./BUSINESS/CHARITY DONATION 3./BUSINESS/CURRENT ACC TXN 4./BUSINESS/GOODS TRADE 5./BUSINESS/SERVICE TRADE



File Format: PAYMUL / PAYEXT

For file format PAYMUL and PAYEXT, the payment purpose code (in red colour) should be

populated in segment FTX, as shown below.

Segment Group 15 – Dependant Segment Number : 59 Segment Status: Conditional Segment: FTX – Free Text Maximum No. of Occurrences: 5

This segment provides space for free text relating to the payment details.

Element Description Format Status Comments Separator

4451 Text subject qualifier AN..3 M ABY = Regulatory Reporting Information

+

4453 Text function, coded AN..3 N Not Used +

C107 Text reference N Not Used +

4441 Free text, coded AN..3 N Not Used

1131 Code list qualifier AN..3 N Not Used

3055 Code list responsible agency, coded

AN..3 N Not Used

C108 Text literal M

4440 Free text AN..70 M The code will be used for CNY payment purpose code mapping.

Purpose must be one of below:

1. /BUSINESS/CAPITAL TRF

2. /BUSINESS/CHARITY DONATION

3./BUSINESS/CURRENT ACC TXN

4./BUSINESS/GOODS TRADE

5./BUSINESS/SERVICE TRADE

:

Note: An additional GIS+37 is require to put in front of FTX+ABY.

rmb payment purpose code requirements -...

Documents