Skip to main content

Your ISO 20022 migration guide

As we adopt the ISO 20022 standard, here’s everything you need to know about what’s changing across our digital banking channels.

Understanding ISO address payment requirements and formats

With the adoption of the ISO 20022 standard, the industry is looking to streamline information to help reduce friction in the end-to-end payment journey. As a result, Swift and various domestic clearing schemes are introducing new data requirements.

Under ISO 20022 standards, a new hybrid address format will be supported from November 2025.

What this means for you

For any addresses you’re currently including in your payment instructions, you will need to apply the structured or hybrid address format.

To help you plan your payment file updates, here are the current timelines:

For all Priority Payments:

Now From November 2025 From November 2026
Address with Town Name and Country provided at minimum * Encouraged Encouraged Mandatory
Supported formats:
  • Structured
  • Unstructured
 Supported formats:
  • Structured
  • Unstructured
  • Hybrid
 Supported formats:
  • Structured
  • Hybrid

* The following address fields currently support structured address format only: Ultimate Debtor, Ultimate Creditor and Initiating Party.

After November 2026, HSBC will only process instructions that are submitted using either a hybrid or structured address format option.

 

Important: to make sure your payment files aren’t rejected, make sure you plan to include the mandatory information in line with the relevant deadlines. Don’t worry, we’ll remind you to update your payments as deadlines approach.

What you need to do

We recommend that you start looking at the data that you provide to us and, if applicable, work closely with your Enterprise Resource Planning (ERP) and/or Treasury Management System (TMS) providers to start making updates to comply with this mandatory industry requirement.

Here are examples of the different Swift ISO address formats:

‘Structured’ address
(supported now and in the future) 		‘Hybrid’ address
(supported from November 2025) 		‘Unstructured’ address
(not supported from November 2026)
Name JOHN SMITH
Postal Address
Street Name HOOGSTRAAT
Building Number 6
Postal Code 1000
Town Name BRUSSELS (required)
Country BELGIUM (required) 		Name JOHN SMITH
Postal Address
Postal Code 1000
Town Name BRUSSELS (required)
Country BELGIUM (required)
Address Line 1 HOOGSTRAAT 6
 Name JOHN SMITH
Postal Address
Address Line 1 HOOGSTRAAT 6
Address Line 2 BRUSSELS 1000 BELGIUM
or in ISO technical terms:

<Nm>JOHN SMITH</Nm>
<PstlAdr>
<StrtNm>HOOGSTRAAT</StrtNm>
<BldgNb>6</BldgNb>
<PstCd>1000</PstCd>
<TwnNm>BRUSSELS</TwnNm>
<Ctry>BE</Ctry>

</PstlAdr> 		or in ISO technical terms:

<Nm>JOHN SMITH</Nm>
<PstlAdr>
<PstCd>1000</PstCd>
<TwnNm>BRUSSELS</TwnNm>
<Ctry>BE</Ctry>
<AdrLine>HOOGSTRAAT 6</AdrLine>

</PstlAdr> 		or in ISO technical terms:

<Nm>JOHN SMITH</Nm>
<PstlAdr>
<AdrLine>HOOGSTRAAT 6</AdrLine>
<AdrLine>BRUSSELS 1000, BELGIUM </AdrLine>

</PstlAdr>

Note: while Swift will introduce support for Hybrid address from November 2025, you can provide hybrid address data in payment files before November 2025. We will make sure that payment files that include hybrid address data are processed in line with Swift rules.

With the new ISO 20022 standard, you will start to see the new UETR in your payment confirmations. A UETR is a string of 36 unique characters featured in all payment instruction messages carried over Swift and RTGS systems that support ISO 20022 standards. You can quote the UETR to our Client Services team when requesting payment investigation.

As part of updates we’re making to support the ISO 20022 standard, we are introducing Priority Payment screen changes in HSBCnet (outlined in the table below). These changes will introduce new mandatory fields for payments sent on behalf of your customer or a third party.

The beneficiary details in the ‘Pay to’ section will also include the new address fields shown below, but the ‘Town/city’ and ‘Country/territory’ fields will be optional until further notice. However, we encourage you to start including these details in your payment instructions once the fields become available.

Payment fields Current address fields Payment details required
Create payment or transfer
screen ❯ ‘Pay to’ section		 Beneficiary name*

Beneficiary address*
  • Address line 1
  • Address line 2
  • Country or territory
 Name*
(extended to support up to 140 characters)
Town / city
State / county
Country / territory
Additional address details
* Indicates a mandatory field

 

Here’s an example of what the new payment screens will look like in HSBCnet:

Here’s an example of what the new beneficiary record fields will look like in HSBCnet:

As part of our ongoing alignment with ISO 20022 standards, the way that instruction codes are used in payment instructions is also changing.

What’s changing?

In line with ISO 20022 standards, the following instruction codes will no longer be supported in payment instructions submitted in HSBCnet, the HSBCnet Mobile app, and HSBC Connect:

Instruction code Description
PHON Please advise account with institution by phone.
PHOI Please advise the intermediary institution by phone.
TELI Please advise the intermediary institution by the most efficient means.
TELE Please advise account with institution by the most efficient means.
REPA Payment has related e-Payments reference.
INS
(File Upload and HSBC Connect only)		 The instructing institution which instructed the sender to execute the transaction.

Important note: in line with the industry-wide adoption of the ISO 20022 standard, the /INS/ code will no longer be supported in the future. To help avoid payment rejection, please stop using this codeword.
ROC
(File Upload and HSBC Connect only)		 Ordering customer’s reference

Important note: in line with the industry-wide adoption of the ISO 20022 standard, the /ROC/ code will no longer be supported in the future. To help avoid payment rejection, please stop using this codeword.

 

All other codewords will remain available for use in HSBCnet and other HSBC payment channels.

Important instruction code notes:

  • If you use the HOLD code, CHQB should not be used (and vice versa).
  • If you use the TELB code, then PHOB should not be used (and vice versa).

Instruction code guidelines for payments submitted through HSBCnet File Upload and HSBC Connect:

In payment processing, there is a set priority for including instruction codes. If you’re including any of the following information in your payment files, then it will be given priority in this order:

Instruction field Instruction code Character limit
Contract number or Deal reference 16 characters limit
Instruction for Debtor Agent /REC/ Up to 140 characters
Purpose of Payment /BUSINESS/ or /PURP/ 4 characters
Instruction for Creditor Agent /ACC/ Up to 140 characters
Any other instruction codes will be prioritised after the above if space allows.

 

We recommend that you input instructions according to the above guidelines to make sure that important payment information isn’t dropped during processing.

As a reminder, please adhere to the following guidelines when using instruction codes:

  • Make sure to use an individual code only once in a payment instruction.
  • Avoid repeating the same instruction codes across multiple lines. Instead, enter new details in subsequent lines without repeating previously mentioned codes.
  • The /REC/ code should only be used when you have a specific instruction to provide HSBC to implement processing. If using /REC/, make sure to only include it once in a single payment to avoid processing issues.

For payments that need ‘Instruction to bank’ details

The instruction to bank section allows you to provide specific information to different financial institutions involved in completing payment settlement.

What to keep in mind:

  • Make sure to use an individual codeword only once.
  • To continue entering information from a previous line, just continue typing in the next line without repeating the codeword or adding forward slashes (/) in front.
  • Type forward slash (/) in a new line only to select a different codeword. Continue typing in the next line again without repeating the codeword.

Here are the Instruction to bank codewords available in HSBCnet:

Codeword Description
/ACC/ Instructions are for the account with institution, meaning the beneficiary bank.
/INS/ Instructing institution which instructed the sender to execute the transaction. This codeword should not be applicable to your payments unless they’re being sent from a financial institution.

Important note: in line with the industry-wide adoption of the ISO 20022 standard, the /INS/ code will no longer be supported in the future. To help avoid payment rejection, please stop using this codeword.
/INT/ Instructions are for the intermediary institution if you specified one.
/REC/ Instructions are for the receiver of your payment instruction, meaning HSBC Group.
/RTGS/ Transaction should be settled via real time gross settlement. Only applicable when you are paying domestically to a beneficiary bank that is not part of HSBC Group.

 

What you need to do

To prepare for this change, we recommend that you review your payment instructions as follows:

  • Payment templates:
    If you have any restricted or general templates created, we recommend that you create a new template or modify existing templates as soon as possible to help make sure you can continue to use your payment templates.

    If you’re using any of the unsupported codes in your templates, you’ll see an error message when you use the template after the updated screens become available. You’ll need to amend the template before you can proceed with payment processing.
  • Payments in ‘pending’ status:
    If you have payments in ‘pending’ status that include any of the unsupported instruction codes, you will be unable to authorise these payments after the updated screens become available. The payment will need to go back to the creator to update the instruction code(s) before it can be authorised.
  • Forward-dated payments and standing instructions:
    If you have any forward-dated payments or standing instructions that include any of the unsupported instruction codes, you will need to cancel and re-create these payment instructions to include a valid code(s) to prevent payment delays.
  • Payment files processed in HSBCnet File Upload and HSBC Connect:
    To prepare for the upcoming changes, we recommend that payment files comply with the requirements for payments as outlined above. Please review the updated File Format Specifications (formerly known as Message Implementation Guides) in the HSBCnet User Guides portal.

In early 2025, we’re updating beneficiary detail fields in HSBCnet’s ‘Beneficiaries’ service to support enriched ISO 20022 payment data.

What’s changing?

In line with ISO 20022 standards, we’re introducing the following address fields for beneficiary records:

Beneficiary fields Current name and address fields Updated name and address fields

Beneficiaries  ❯
Beneficiary record ❯
Beneficiary details section

 Beneficiary name*

Beneficiary address*
  • Address line 1
  • Address line 2
  • Country or territory
 Beneficiary name and short beneficiary name*
(extended to support up to 140 characters)
Town / city
State / county
Country / territory
Additional address details
* Indicates a mandatory field

 

Here’s an example of what the new beneficiary record fields will look like in HSBCnet:

Here’s an example of what the new beneficiary record fields will look like in HSBCnet:

When are the beneficiary record fields changing?

The enhanced beneficiary fields will be introduced in phases as follows:

For beneficiaries in the following countries/regions: Updated fields will be introduced on:
Thailand and the UK 1 February 2025
Mainland China, Japan, Mexico, Saudi Arabia, Taiwan, and Macau 15 February 2025
Australia, Canada, Hong Kong, Indonesia, Malaysia, Singapore, US, and Vietnam 29 March 2025

 

What you need to do

To avoid potential future delays when creating payments, we recommend that you review and update your existing beneficiary records once the new fields become available in the Beneficiaries service. Once available, you can create new beneficiary records using the updated fields. You can use these updated records for all payments going forward, whether they’re sent using the ISO 20022 standard or not.

We’re also in the process of updating payment instruction screens. Once the equivalent ISO 20022 beneficiary fields become available in payment screens, you will have the option to save updated beneficiary details after payment submission.

In addition to the above changes, there are also unique requirements that apply specifically to financial institutions that make payments on behalf of others. We’re updating HSBCnet screens and file specifications for payments made on the behalf of other parties to support enriched ISO 20022 payment data.

The enhanced payment screens will be introduced in phases.

New and updated fields for payment screens and templates:

In line with ISO 20022 standards, we’re introducing updated address fields and new regulatory fields for payments from accounts in the UK as follows:

Payment fields Current address fields Payment details required
  • Instructing Party (Ultimate Debtor) final party that bears the responsibility of making payment
  • Originating financial institution (where the address is populated)**
  • Final Beneficiary (Ultimate Creditor) party that is ultimate beneficiary of the payment
 Name*

Address*
  • Address line 1
  • Address line 2
  • Country or territory
 Name*
(extended to support up to 140 characters)
Town / city*
State / county
Country / territory*
Additional address details

* Indicates a mandatory field
** Applicable for Financial Institution customers

Note: the beneficiary details in the ‘Pay to’ section will include the new address fields as detailed in above table; however, providing details in ‘Town / city’ and ‘Country / territory’ fields is currently not mandatory.

Enhanced ‘Related reference’ field:

In line with ISO standards, the ‘Related reference’ field will support up to 35 characters.

Updating HSBC Connect and File Upload payment files

Here are some of the changes for CHAPS and international payments made on behalf of others:

 For files that include:  Here’s what you need to provide:
Forwarding agent* Forwarding agent name Include accompanying address in the structured address format, with a minimum of Town and Country code. 
Ultimate debtor Ultimate debtor name
Ultimate creditor Ultimate creditor name
Creditor Creditor name
Initiating Party
(XML v2 / XML v3)

Initiating Party can be formatted using one of the following options:

  1. Initiating Party ID with Initiating Party name and structured address (Name, Town/City and Country code are mandatory)
  2. Initiating Party ID (without Initiating Party name and address)
  3. Initiating Party ID with Initiating Party name only

Note: under ISO 20022, unstructured address is not supported in the Initiating Party section.
Debtor Agent

Choose one of the following options:

  1. Swift BIC (recommended)
  2. If you only provide the Clearing System Member ID, include ‘Name’ and structured address (with minimum Town and Country code)
Creditor Agent
Intermediary Agent1

For all UK CHAPS and international payments:
To avoid payment rejections in the future, we recommend that you start replacing unstructured address details in Address Line fields with the structured address. The unstructured address format for the above fields will not be supported by Swift in the future.

For all Instruction Level Authorisation (ILA) payment files:
In addition to the above ISO requirements, for all ILA payment files, you will need to start including ‘Name’ and structured address (with minimum Town and Country code) as part of the Beneficiary (Creditor) information.

* Please do not use the ‘Forwarding Agent’ field for nested-on-behalf-of payments (i.e., payments made on behalf of other originating FI/NBFI information). These payments should be sent using the pacs.008 XML format. Please contact us for more information around the ISO 20022 format.

We’ll start supporting payment files with the enhanced data in HSBCnet File Upload and HSBC Connect customers in phases. We expect to complete the rollout to all HSBCnet profiles with UK accounts by the end of April 2025.

Ultimate Debtor information in statement narratives:

If you’re making any domestic or cross-border payments on behalf of other instructing parties, the Ultimate Debtor information may be included after the /ULTD/ codeword in your statement narrative.

To prepare for the upcoming changes, make sure that payment files comply with the requirements for cross-border payments by November 2025.

We’re in the process of updating HSBC’s File Format Specifications guides (formerly Message Implementation Guides or MIGs) to include the latest changes. Updated guides for the following file formats will soon be available in HSBCnet’s User Guides portal:

  • XMLv2
  • XMLv3
  • iFile
  • Dynamic CSV 

Please review the updated specifications to see all the updated payment file requirements. The upgrade will be introduced to HSBCnet File Upload and HSBC Connect customers in phases.

Here’s where you can find the File Format Specifications guides in the HSBCnet User Guides portal:

  1. When logged on to HSBCnet, open the User Guides portal by selecting the ‘?’ or ‘Need help?’ button on any screen.
    User Guides portal
  2. Select the ‘File Upload’ tile
    File Upload
  3. In the File Upload page, select the ‘File Format Specifications’ tile
    File Format Specifications

If you don’t have access to HSBCnet, please contact your local HSBC Client Services team to request the guides.

From November 2024, the enhanced HSBCnet Priority Payment screens will start to become available for cross-border transactions from HSBC Thailand accounts.

To prepare for this change, we recommend that you review your HSBCnet payment instructions for cross-border transactions as follows:

  • Payment templates:

    If you have any restricted or general templates, you may not be able to use this template for payment creation after the new screen becomes available. We strongly recommend that you create a new template or modify the existing template as soon as the enhanced screen becomes available. This helps make sure you can continue to use your payment templates.

    You will need to modify existing restricted templates by replacing any unstructured address with the structured address, specifically providing inputs in the ’Town/city’ and ‘Country/territory’ fields.

    Here’s the structured address requirements:

    Payment parties Town / city field Country / territory field
    Beneficiary Optional Optional
    Instructing Party (if used) Mandatory Mandatory
    Originating Financial Institution (if used) Mandatory Mandatory
    Final Beneficiary (if used) Mandatory Mandatory

     

    Please note that in existing templates, beneficiary address will appear pre-filled in the ‘Non-standard beneficiary address’ section. However, we recommend that you begin updating the existing template and providing structured address details in ‘Town/city’ and ‘Country/territory’ fields.

  • Priority Payments in ‘pending’ status:

    If you have any Priority Payments with Instructing Party details in ‘pending’ status, we recommend that you submit them after the new screen becomes available to avoid payment rejections. If you complete these pending payments after the new screens are live, the payment creator will need to update the instruction using the new address fields before the payment can be authorised.

  • Forward-dated payments and standing instructions:

    If you have any forward-dated payments or standing instructions, they will be submitted with the payment information that has already been entered. We recommend that you cancel and re-create these payment instructions once the enhanced screen is available.

    For any standing instructions with Beneficiary and/or Instructing Party address details, you will need to re-create those instructions using the new fields once the enhanced screen is available. This will help you benefit from the enhanced name and structured address information.

Effective May 2025, the Bank of England is implementing mandatory enhanced data requirements for CHAPS payments that meet certain criteria.

Here’s what’s changing in early 2025

In support of these upcoming UK CHAPS requirements, we’re introducing two new fields to HSBCnet payment screens. The enhanced payment screens will be introduced in phases starting in January 2025. We expect to complete the rollout to all HSBCnet profiles with UK accounts by the end of April 2025.

The new fields will be introduced for payments and templates as follows:

New payment field When to use the new field
Purpose of Payment

Encouraged for all transactions

Required by Bank of England for FI-to-FI transactions.

Required by Bank of England for property transactions from May 2025.

To find a list of UK Purpose of Payment codes, please refer to the Bank of England’s website.
Legal Entity Identifier (LEI)

From May 2025, required by Bank of England for financial organisations that are regulated by the Prudential Regulation Authority (PRA) and authorised as deposit taking or broker dealers. If you are a financial organisation that is regulated by the PRA, you will need to provide your LEI and the beneficiary’s LEI when paying another PRA-regulated organisation.

Please contact your beneficiary to obtain their LEI.

To learn about LEI, please visit the GLEIF website.


Purpose code requirements for UK CHAPS and international payments

Effective May 2025, in line with Bank of England requirements, purpose codes will become mandatory for CHAPS payments between Financial Institutions, as well as for all property-related transactions. The purpose code is used to indicate the reason for the payment.

Here’s what the new Purpose of Payment field will look like in HSBCnet payment screens:

Purpose code  Name  Description 
HLRP Property Loan Repayment Transaction is related to a payment of a property loan.
HLST Property Loan Settlement Transaction is related to the settlement of a property loan.
PLDS Property Loan Disbursement Payment of funds from a lender as part of the issuance of a property loan
PDEP Property Deposit Payment of the deposit required towards purchase of a property
PCOM Property Completion Payment Final Payment to complete the purchase of property
PLRF Property Loan Refinancing The transfer or extension of a property financing arrangement to a new deal or loan provider, without change of ownership of property.

You can find the full list of purpose codes here:

Bank of England recommended purpose code list


How to include purpose codes in your payment files:

File format Input field for purpose codes 
XML v2.0
XML v3.0

The purpose code <Purp> tag should be included in the <CdtTrfTxInf> (Credit Transfer Transaction Information) block, positioned immediately after the CdtrAcct structure. Below is the correct structure:

     <Purp>

             <Cd>XXXX</Cd> <!-- Purpose Code for payment -->

      </Purp>
iFile

Second Party Detail. Regulatory Reporting Line 1/2/3 can be populated with following details.

/PURP/GB-XXXX

  • /PURP/ indicates Purpose code.
  • GB indicates used for GB country code.
  • XXXX is the actual code word for the payment.

Dynamic CSV

 Include the applicable code under the ‘Purpose Code’ column.
MT101 :70:/PURP/XXXX
MT103 :70:/PURP/XXXX


Legal Entity Identifier (LEI) requirement for UK CHAPS and international payments

From May 2025, Legal Entity Identifier information will also be required for financial organisations regulated by the Prudential Regulation Authority (PRA).

If you are a financial organisation that is regulated by the PRA, you will need to provide your LEI and the beneficiary’s LEI when paying another PRA-regulated organisation. Please contact your beneficiary to obtain their LEI.

Here’s an example of where you’ll find the new ‘Legal Entity Identifier’ field in HSBCnet:

How to include Legal Entity Identifiers in your payment files:

File format Input field for Legal Entity Identifier
XML v2.0

The LEI details can be provided for each applicable party tag and should be included in the <Id> (Party Identification) block. Below is the input structure for Creditor LEI:

<Cdtr>

<Id>

<OrgId>

<PrtryId>

<Id>F50EOCWSQFAUVO9Q8Z98</Id>   <!-- LEI value -->

<Issr>LEIC</Issr> <!--Code word for LEI input identification-->

</PrtryId>

</OrgId>

</Id>

</Cdtr>
XML v3.0

The LEI details can be provided for each applicable party tag and should be included in the <Id> (Party Identification) block. Below is the input structure for Creditor LEI:

<Cdtr>

<Id>

<OrgId>

<Othr>

<Id>F50EOCWSQFAUVO9Q8Z98</Id>   <!-- LEI value -->

<SchmeNm>

<Prtry>LEIC</Prtry> <!--Code word for LEI input identification-->

</SchmeNm>

</Othr>

</OrgId>

</Id>

</Cdtr>
Dynamic CSV

Include the debtor/creditor LEI under the ‘Debtor ID’ and ‘Creditor Organisation ID’ columns. The limit for this field is 20 characters.

When including an LEI, you also need to provide the code LEIC in the ‘Debtor Org ID Scheme Prtry’ and ‘Creditor Org ID Scheme Proprietary’ columns.
iFile

iFile does not support LEI. Please use another format.
MT101
MT103

MT101 and MT103 do not support LEI. Please use another format.

We’re introducing the new ISO 20022 enhancements for domestic RTGS (PhilPaSS) and international payments in the Philippines between April and June 2025.

Structured address fields for domestic RTGS and international payments from accounts in the Philippines will be introduced to HSBCnet payment screens and files in a phased manner starting in April.

To prepare for this change, we recommend that you review your domestic RTGS and international payments instructions as follows:

  • Payment templates:
    If you have any restricted or general templates already created, we recommend that you create a new template or modify existing templates as soon as the enhanced screen becomes available to help make sure you can continue to use your payment templates.
     
Payment parties Town / city field Country / territory field
Beneficiary Optional Optional
Instructing Party (if used)  Mandatory Mandatory
Originating Financial Institution (if used) Mandatory Mandatory
Final Beneficiary (if used) Mandatory Mandatory


Please note that in existing templates, beneficiary address will appear pre-filled in the ‘Non-standard beneficiary address’ section. However, we recommend that you begin updating the existing template and providing structured address details in ‘Town/city’ and ‘Country/territory’ fields.

  • Payments in ‘pending’ status:
    If you have any domestic RTGS or international payments in ‘pending’ status, we recommend that you submit them before the new screens become available to avoid payment rejections. If you complete these pending payments after the effective date, the payment creator will need to populate information in the new fields before the payment can be authorised.
  • Forward-dated payments:
    If you have any forward-dated payments they will be submitted with the payment information that has already been entered. We recommend that you cancel and re-create these payment instructions once the enhanced screen is available.

Please note that in existing templates, beneficiary address will appear pre-filled in the ‘Non-standard beneficiary address’ section. However, we recommend that you begin updating the existing template and providing structured address details in ‘Town/city’ and ‘Country/territory’ fields.

We’re introducing the new ISO 20022 enhancements for domestic RTGS (MEPS+) and international payments in Singapore between April and June 2025.

Structured address fields for domestic RTGS and international payments from accounts in the Singapore will be introduced to HSBCnet payment screens and files in a phased manner starting in April.

To prepare for this change, we recommend that you review your domestic RTGS and international payments instructions as follows:

  • Payment templates: 
    If you have any restricted or general templates already created, we recommend that you create a new template or modify existing templates as soon as the enhanced screen becomes available to help make sure you can continue to use your payment templates.
Payment parties  Town / city field  Country / territory field
Beneficiary Optional Optional
Instructing Party (if used) Mandatory Mandatory
Originating Financial Institution (if used) Mandatory Mandatory
Final Beneficiary (if used) Mandatory Mandatory

 

Please note that in existing templates, beneficiary address will appear pre-filled in the ‘Non-standard beneficiary address’ section. However, we recommend that you begin updating the existing template and providing structured address details in ‘Town/city’ and ‘Country/territory’ fields.

  • Payments in ‘pending’ status: 
    If you have any domestic RTGS or international payments in ‘pending’ status, we recommend that you submit them before the new screens become available to avoid payment rejections. If you complete these pending payments after the effective date, the payment creator will need to populate information in the new fields before the payment can be authorised.
  • Forward-dated payments:
    If you have any forward-dated payments they will be submitted with the payment information that has already been entered. We recommend that you cancel and re-create these payment instructions once the enhanced screen is available.

Please note that in existing templates, beneficiary address will appear pre-filled in the ‘Non-standard beneficiary address’ section. However, we recommend that you begin updating the existing template and providing structured address details in ‘Town/city’ and ‘Country/territory’ fields.

From July 2025, the enhanced HSBCnet Priority Payment screens will start to become available for cross-border transactions from HSBC France accounts.

To prepare for this change, we recommend that you review your international Priority Payment instructions as follows:

  • Payment templates:

If you have any restricted or general templates created, we recommend that you create a new template or modify existing templates as soon as the enhanced screens become available to help make sure you can continue to use your payment templates.

Payment parties  Town / city field  Country / territory field
Beneficiary Optional Optional
Instructing Party (if used) Mandatory Mandatory
Originating Financial Institution (if used) Mandatory Mandatory
Final Beneficiary (if used) Mandatory Mandatory

 

Please note that in existing templates, beneficiary address will appear pre-filled in the ‘Non-standard beneficiary address’ section. However, we recommend that you begin updating the existing template and providing structured address details in ‘Town/city’ and ‘Country/territory’ fields.

  • Payments in ‘pending’ status:

If you have any international payments in ‘pending’ status, we recommend that you complete them to avoid payment rejections. If you complete these pending payments after the new screens become available, the payment creator will need to populate information in the new fields before the payment can be authorised.

  • Forward-dated payments:

 If you have any forward-dated payments, they will be submitted with the payment information that has already been entered. We recommend that you cancel and re-create these payment instructions after the new screens become available.

In addition to the above ISO requirements, as per local regulatory requirement, the following beneficiary address fields continues to be mandatory for all cross-border payments to beneficiary accounts in Canada:

  • Street name
  • State / county
  • Post code / zip code

Disclaimer: This article includes links to third-party, non-HSBC, websites. No member of the HSBC Group (as defined below and including but not limited to HSBC Bank plc) is responsible for the content or accuracy of any of these linked third-party websites, nor is the HSBC Group responsible or liable for any software downloaded from those websites. Please read the linked websites' terms and conditions. The HSBC Group has no control over non-HSBC Group websites and is not liable for your use of them or any information you obtain from them.

References to 'HSBC Group' in this disclaimer means HSBC Holdings plc and each of its subsidiaries, related bodies corporate, associated entities and undertakings and any of their branches.