Close

Purpose of Payment codes and Relationship details required for payments debiting Qatar accounts from 10 December 2022

Beginning 10 December 2022, in accordance with local regulations, Purpose of Payment codes and Relationship details will be required for ACH, Priority Payments & Inter-account transfers being sent from HSBC accounts in Qatar.

View full list of Purpose of Payment codes for payments ❯

To avoid any rejections or delays in sending your payments, we recommend that you review and, if necessary, update your payments and templates to include valid Purpose of Payment and Relationship details as follows:

    1. ACH Payments

    Please include the Relationship description under the ‘Relationship details and remittance information’ field.

    Here's what the required fields will look like:

    Purpose of payment field
    (select image to enlarge)

    2. Priority Payments - Domestic

    For payments within Qatar, you're currently required to select a code from the dropdown list in the ‘Purpose of payment’ field within the ‘Additional details’ section.

    Additionally, please make sure to include the Relationship description under the ‘Relationship details’ field.

    Here's what the fields will look like:

    new Purpose of payment field
    (select image to enlarge)

    3. Priority Payments - Cross-border

    For cross-border payments outside Qatar, the ‘Purpose of payment’ field within the ‘Additional details’ section will become mandatory and you'll need to select the appropriate code from the dropdown list.

    Also, please make sure to include the Relationship description under the ‘Relationship details’ field.

    Here's what the fields will look like:

    new Purpose of payment field
    (select image to enlarge)

    4. Inter-account transfers

    For inter-account transfers, the ‘Purpose of payment’ field within the ‘Additional details’ section will become mandatory and you'll need to select the appropriate code from the dropdown list.

    Also, please make sure to include the Relationship description under the ‘Relationship details’ field.

    Here`s what the fields will look like:

    new Purpose of payment field
    (select image to enlarge)

    5. Standing instructions, restricted templates and forward-dated payments:

    We recommend reviewing your standing instructions, restricted templates and forward-dated payments to ensure the Purpose of Payment and Relationship details are captured.

    Reminder: when you update a restricted template, standing instruction, or forward-dated payment, you’ll need to have another user approve the changes in the Authorisation summary service before the update is applied.

    6. Payments submitted using File upload or HSBC Connect:

    Beginning 10 December 2022, payment files submitted using File upload or through HSBC Connect will need to include mandatory Purpose of Payment codes and Relationship details. From 10 December, if you don't include these mandatory details, your payment instructions will be rejected.

    Review the table below for how to include Purpose of Payment codes in your payment files:

    i. For ACH payments and Priority payments (domestic in local currency):

    File format Input field for Relationship details Example
    iFile "Second Party Details Record (SECPTY)>'@LVP@'> field 44 Payment Details Line 1" Meaningful relationship detail;
    Free format text
    (Eg: Supplier, Employee etc)
    MEABASIC AF - Remittance Information 1 Meaningful relationship detail;
    Free format text
    (Eg: Supplier, Employee etc)
    XML v2.0 RemittanceInformation
    <RmtInf>
     <Ustrd>    		 <RmtInf>
     <Ustrd>Meaningful relationship detail (Eg: Supplier, Employee etc) </Ustrd>
    </RmtInf>
    XML v3.0 RemittanceInformation
    <RmtInf>
    <Ustrd>    		 <RmtInf>
     <Ustrd>Meaningful relationship detail (Eg: Supplier, Employee etc) </Ustrd>
    </RmtInf>
    Paymul Group 16 FTX+PMD
    Element C108-4440
    Free text 1    		 FTX+PMD+++Meaningful Relationship detail
    (Eg: Supplier, Employee etc)

    ii. For Priority Payments (domestic foreign currency and cross-border transactions):

    File format   Input field for Purpose of Payment Example
    iFile For PoP input Second Party Details Record (SECPTY) >'@HVP@'>
    field 65 Regulatory Reporting Line 1    		 Line1 - /ORDERRES/QA//PoP code.
    Example: /ORDERRES/QA//B1B01
    For Relationship detail input Second Party Details Record
    (SECPTY)>'@HVP@'> field 44 Payment Details Line 1    		 Meaningful relationship detail;
    Free format text up to 35 characters
    (Eg: Supplier, Contractor etc)
    MEABASIC For PoP input BD Regulatory Reporting Line 1 (5 char) /ORDERRES/QA//PoP code
    Example:
    /ORDERRES/QA//B1B01
    For Relationship detail input AH Payment Details Line 1 Meaningful relationship detail;
    Free format text up to 35 characters
    (Eg: Supplier, Contractor etc)
    XML v2.0 For PoP input Regulatory Reporting
    <RgltryRptg>
     <RgltryDtls>
      <Inf>
    (first or second occurrence of Inf)    		 <RgltryRptg>
     <RgltryDtls>
       <Inf>/ORDERRES/QA//Payment PoP code of 5 characters
       </Inf>
      </RgltryDtls>
    </RgltryRptg>
    For Relationship detail input Remittance Information
    <RmtInf>
     <Ustrd>    		 <RmtInf>
     <Ustrd> Meaningful relationship detail (Eg: Supplier, Contractor etc) </Ustrd>
    </RmtInf>
    XML v3.0 For PoP input Regulatory Reporting
    <RgltryRptg>
     <Dtls><Cd>    		 <RgltryRptg>
     <Dtls>
      <Cd>B1B01</Cd>
     </Dtls>
    </RgltryRptg>
    For Relationship detail input Remittance Information
    <RmtInf>
     <Ustrd>
    (first occurrence)    		 <RmtInf>
     <Ustrd> Meaningful relationship detail (Eg: Supplier, Contractor etc) </Ustrd>
    </RmtInf>
    Paymul For PoP input Group 15 - FTX+ABY Segment Number: 59 Element - C108-4440
    Free text[1]    		 FTX+ABY+++/ORDERRES/QA// Payment PoP code of 5 characters.
    Example:
    FTX+ABY+++/ORDERRES/QA//B1B01
    For Relationship detail input Group 16 FTX+PMT
    Element C108-4440
    Free text 1    		 FTX+PMT+++Meaningful relationship detail;
    Free format text up to 35 characters
    (Eg: Supplier, Contractor etc)
    MT101/MT103 For PoP input :77B:Regulatory Reporting Line 1 :77B:/ORDERRES/QA// B1B01
    For Relationship detail input :70:Remittance Information Line 1 :70:Meaningful relationship detail;
    Free format text up to 35 characters
    (Eg: Supplier, Contractor etc)

Find out more

If you have any questions, please contact your local HSBCnet Support Centre.


Back to top | Close

The postal address for related enquiries is:
HSBC Group Head Office
HSBC - Digital Channels, Wholesale
London UK E14 5HQ

This communication is provided by HSBC Bank plc on behalf of the member of the HSBC Group that has contracted with your organisation for the provision of HSBCnet services. HSBC Bank plc is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and Prudential Regulation Authority.

You received this email notification because you are a registered user of HSBCnet. Should you have any concerns regarding the validity of this message, please contact your local HSBCnet customer support.

We maintain strict security standards and procedures to prevent unauthorised access to information about you. HSBC will never contact you by email or otherwise ask you to validate personal information, such as your username, password or account numbers. If you receive such a request, please call your local HSBCnet customer support. Links within our emails will only take you to information pages.

If you wish to unsubscribe from receiving service information from HSBCnet, please select here.

© Copyright. HSBC Bank plc 2022. All rights reserved.

Privacy & Data Protection Statement | Terms & Conditions

Deutsche | En español | En français (Canadian) | En français (European) | 繁體中文 | 简体中文 | Bahasa Indonesia