• ISO 20022 Payments Migration and Interoperability Considerations (published November 2022) 
• Best Praice Guidelines for the Payment Industry Migration to ISO20022 (published January 2022) (launches download)
• CBPR+ Data Integrity Market Practice Guidance (Swift user ID and Password required)

These guidelines for banks have been developed by CBPR+ to manage potential risks where enhanced data elements are truncated or dropped altogether at some point in the payment chain.

Truncation during Market Infrastructure transaction legs:

The industry guidance may also be applied to a transaction leg settled across a local Market
Infrastructure (i.e., currency clearing systems) that has not yet adopted the ISO 20022 standard.

1. Refer to the latest information available at the Swift Knowledge Centre, including Operations Guide, Service Description, Business Processing Rules and FAQ documents.
2. Understand the plans of your payment service providers like J.P. Morgan to align your plans accordingly. 
3. Have an implementation plan for fully transitioning to ISO MX messages and consider all potential operational and technology impacts. 
4. Develop a plan to add structured address data for your clients where they are debtor party, and work with your clients to start collecting and organizing beneficiary details in structured format. 
5. Be aware of market developments and recommendations during the implementation phase, including those related to industry truncation risks.

• Clients can choose to send us MT or MX messages during the co-existence period established by Swift (now through Nov. 2025).
• J.P. Morgan sends MX (pacs) messages to clients and counterparties, including for serial third party (pacs.008/009) credit advice messages, even where we receive the incoming message in a legacy MT format. MX (pacs) messages provide for enhanced data transparency and formatting, and we are committed to delivering these benefits at the earliest opportunity.
• Clients using the Forced MT103 service (including forced MT202 where provided) in lieu of receiving MT910, can migrate to camt.054. We recognize this will require time to implement, therefore we plan to retain this service (as MT message) until the end of the co-existence period. To help clients receive helpful information during the interim period, where possible, we will attempt to map enhanced data from inbound pacs messages into these messages, leveraging CBPR+ prioritization and including "+" when data cannot be included due to insufficient space. Please be aware after Transaction Manager (TM) enablement back in May 29, 2023 where a payment is MX originated even when J.P. Morgan send a Forced MT103 this may be intercepted by TM and sent to the recipient as a multiformat message, pacs.008 with the Forced MT103 embedded.
• Connection to the Swift FINPlus platform will enable Swift's In-Flow Translation service, which will allow you to receive the MX message with embedded MT message, if you are not ready to receive native MX payment messages. Please contact Swift to arrange this service,
• Check with your compliance team to understand your obligations related to enhanced data received within the MX messages.

MT9xx remains the default reporting option sent by J.P. Morgan:

• J.P. Morgan will continue to send MT9xx as the default option (note: this does not apply for serial third party credit advices where we will send pacs.008/009).
• Given the recent changes from Swift on CBPR+ that the November 2025 deadline only applies to MX payment instructions and the extension of the deadline for MX reporting messages for a future deadline. J.P. Morgan has decided to defer the rollout of MX reporting to only after November 2025 as the industry focuses on meeting the MX payment instructions deadline of November 2025.  After November 2025 you will be able to opt in to receive Cash Management messages (camt .052, .053 and .054) by contacting your J.P. Morgan representative; note that these messages will include information for transactions received via MX or MT messages.
• We have a camt.53 and camt.054 schema on our Swift MyStandards page, to clarify key formatting features, particularly for elements subject to interpretation.

Providing enhanced information within MT9xx messages between now and Nov. 2025:

• Since the adoption of camt. messages is expected to take place gradually, where possible we are adapting our MT9xx messages for credits, to append useful information from MX payment transactions, leveraging CBPR+ guidelines (access to Swift resources only for registered users):
  • Providing pacs End2End ID Transaction reference as the "Related Reference" (e.g., MT910 field 21, MT940 Field 61 subfield 7) for credit transactions within the MT9xx series messages (excluding scenarios where we already customize this for clients).
  • Mapping enhanced ISO data fields from the MX messages into the MT9xx series messages where there is enough space to do so (MT910 field 72, MT940 field 86) while avoiding impact to existing reference and data mapping features.
  • Including "+" at the end of fields where possible, when data cannot be included due to insufficient space; this may apply to Related Reference, Party and Agent details and Sender to Receiver / Detailed Transaction Information fields within MT9xx series messages. 
  • These features are available for most EMEA account locations from Q1 / Q2 2023.

Clients using the Forced MT103 service (including forced MT202 where provided) in lieu of receiving MT910, can migrate to camt.054. We recognize this will require time to implement, therefore we plan to retain this service (as MT message) until the end of the co-existence period. To help clients receive helpful information during the interim period, where possible, we will attempt to map enhanced data from inbound pacs messages into these messages, leveraging CBPR+ prioritization and including "+" when data cannot be included due to insufficient space. Please be aware after Transaction Manager (TM) enablement back in May 29, 2023 where a payment is MX originated even when J.P. Morgan send a Forced MT103 this may be intercepted by TM and sent to the recipient as a multiformat message, pacs.008 with the Forced MT103 embedded.

J.P. Morgan will continue to accept Swift MT210 messages in account locations where those messages are accepted today. J.P. Morgan will accept camt.057 messages instead of MT210 messages in those account locations; however, note only single camt.057 messages will be accepted and not multiple advices within the same message.

For returned payments, where  the most relevant reference information to clients (i.e., their original debit or credit references) to aid reconciliation and onward processing.

Information on our camt. 052/3/4 message formatting is provided within our camt.053 and camt.054 schema, on our Swift MyStandards page.

Updates available for EMEA accounts MT9xx reporting:

• Where possible, J.P. Morgan will identify a return transaction, either through receipt of a pacs.004 or through receipt of an MT103/202 with /RETN/ or /REJT/ code at the start of field 72.
• For both inbound (credit) and outbound (debit) transactions identified as returns, the following information will be included in the Sender to Receiver / Information for Account Owner fields, where available:
  • /RTN/ key word
  • End2EndID of Payment being returned (if not available, a space will be added)
  • Return Code and Code Name (where provided)
  • Returned Amount (e.g., “USD100,1” or “EUR100”,)
  • Originator Details
  • Original Instruction ID
  • Details will be delimited by a “/” and if any details are not available e.g., End2EndID or Originator Details, it will be indicated by a “ “ (space).
• J.P. Morgan will also attempt to provide the most relevant reference in field 21 of the MT900/910 and subfield 7 of the MT940:
  • For inbound (credit) return entries – we will aim to provide a client’s original Instruction ID (MX) or original Tag 20 (MT) reference from the original payment being returned
• For outbound (debit) return entries – we will aim to provide the Original Instruction ID provided by the client (if return message is sent as pacs.004) or a client’s Tag 20 (if return message is sent as MT).
• Example:
  72:/RTN/ /MS01 /USD999,/ / P333333333333 (sender’s Tag 20 Reference or equiv.)
  72:/RTN/ /BE02 /TEXT/BENEFICIARY CODE
  UNKNOWN/GBP8888,/ / 000001645022 (client’s original debit Tag 20 Reference or equiv.)

Other details: J.P. Morgan is now sending pacs.004 for returning settled payments. Clients wishing to receive these messages in MT format can do so by using the Swift in-flow translation service.

Clients can use pacs.004 message to initiate return messages via J.P. Morgan although it is also acceptable to continue using MT with /RETN/ codewords, or even initiate the return as a new payment.

Please reference the ISO codes for returns messages, as per industry guidelines.

For CBPR+ transaction legs, J.P. Morgan will initially issue recalls and rejections and respond to incoming requests (including incoming camt.056 FI to FI Cancellation message) using existing MT message types and practices. We will start sending the camt.056 and camt 0.29 (Resolution of Enquiry) messages as industry adoption increases.

Similarly, J.P. Morgan will continue to use the MT199 in most instances to reject payment requests for CBPR+ transaction legs and will start sending the pacs.002 negative Customer Status Report as industry adoption increases.

We do not plan to send (or receive) any optional pacs.002 positive or pending status reports in the future.

Please refer to the published market practice guidelines on use of enhanced ISO data elements. This guidance was expected to limit the use of enhanced ISO data elements until November 2023.

We're working hard to ensure the services driven by bilaterally agreed codewords for data patterns continue working seamlessly for clients moving to MX messages. If this applies to you and you would like more information, please refer to our Frequently Asked Questions. For more information on formatting bilaterally agreed codewords within the pacs.008 and 009 schemas, please refer to J.P. Morgan's Swift MyStandards schemas on Swift‍.‍com. If you require further clarification or need access to J.P. MyStandards, please contact your J.P. Morgan representative.

Transitioning existing RMAs to MX messages:

• RMAs allow the exchange of Swift messages over the Swift network.
• To smooth the transition between FIN and FIN+, Swift “bootstrapped” (copy/pasted) all participants’ FIN RMAs into their equivalent ISO RMAs. Swift already performed a few sessions to bootstrap RMAs for different ISO 20022 standard releases in recent years.
• The current MT9xx category of Swift FIN message types does not require an RMA, but the equivalent ISO camt message types does require an RMA. To lessen the operational impact, Swift provided an optional bootstrap event for camt.052/053/054 message types in recent years.

We strongly encourage our clients to opt-in—taking part in the bootstrap events, will save you time and the manual effort of bilateral RMA exchanges at the point of migration.

Please consult the Swift RMA Support Page for Swift plans.

• Check our testing guide, it aims to provide our clients with a useful reference point for their CBPR+ readiness, expanding on J.P. Morgan’s lessons learned as an industry leader in ISO 20022 adoption.
• Reference the Swift MyStandards schemas and the CBPR+ sample message library on Swift.com 
• Access J.P. Morgan's Swift MyStandards schemas on Swift.com (currently available for pacs.008, pacs.009, and camt.054 and camt.053) which identifies how to populate bilaterally agreed codewords and indicators in the new schemas. (You will need to request access to this user group on Swift.com) 
• Use Swift’s Sparring Partner tool, which may reduce the need for bilateral testing between Swift members. (For more information on this tool, please contact your Swift representative.) 
• To check possibility of bi-lateral testing with us in a UAT environment and to get access to J.P Morgan readiness Portal on Swift MyStandard, please contact your J.P. Morgan representative.

J.P. Morgan is planning to support receipt of the CBPR+ pain.001 v9 bank-to-bank relay message after Q2 2025. We will continue to send relay messages in the existing MT format. We are also not expecting to receive these messages before Q2 2025 and any usage of the CBPR+ pain.001 v9 message would need to be agreed bilaterally.

J.P. Morgan will continue to initiate charge claims via MT191 until approximately Q1-2025.

From November 2024. J.P. Morgan accepts incoming camt.106

J.P. Morgan's Gateway service enables us to capture a Client’s Fedwire- or CHIPS-initiated transactions through J.P. Morgan and complement those transactions with value-added services and products.

As the Federal Reserve Bank adopts the ISO20022 message format for the Fedwire Funds Service, clients should adhere to the Federal Reserve's formatting guidance to participate in the Fedwire service. J.P. Morgan’s Gateway service will be fully capable of supporting the ISO20022 message format with no special or additional formatting requirements to maintain its current functionality.

A new hybrid postal address  will be introduced in November 2025, allowing simultaneous usage of structured and unstructured elements, with structured Town Name and Country as mandatory minimum.

Timelines:

• Fully structured: already allowed today and preferred & recommended option in the future
• Fully unstructured: Only allowed until November 2026
• Hybrid address: Allowed as of November 2025 (no end-date)

The hybrid address format permits the concurrent use of structured elements within the Postal Address and the unstructured 'Address Line' element.

When utilizing a hybrid address, Town Name and Country are mandatory components within the Postal Address, similar to their requirement in a fully structured address.

The unstructured Address Line element in the hybrid address can consist of up to 2 lines, each containing up to 70 characters (2*70).

It is important that the structured address information provided in the respective structured elements is not duplicated in the Address Line elements.

For details please refer to The Payments Market Practice Group (PMPG) guidelines here.

CLS USD Nostro Services

• CLS USD Nostro Service clients can continue to use MT202 messages with current formatting to instruct their CLS USD Nostro Pay-ins.
• Alternatively, J.P. Morgan will accept CLS USD Nostro Pay-ins via pacs.009 (using the CLSTIME element - <SttlmTmReq> <CLSTm>) or Instructions for Next Agent containing the CLS codeword and time.
• If you want to use pacs.009, please contact your J.P. Morgan representative so we can coordinate accordingly.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

CLS Third Party Service

• Drawdowns used for the CLS Third Party Service will continue to be sent in MT format until further notice.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

CLSNow

• Clients can continue to use MT202 messages with current formatting to instruct CLSNow Pay-ins.
• Alternatively, J.P. Morgan will accept payments via pacs.009; please use existing codewords in Instructions for Next Agent.
• If you want to use pacs.009, please contact your J.P. Morgan representative so we can coordinate accordingly.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

CLSCCP

• Clients can continue to use MT202 messages with current formatting to instruct CLSCCP Pay-ins.
• Alternatively, J.P. Morgan will accept payments via pacs.009; please use existing codewords in Instructions for Next Agent.
• If you want to use pacs.009, please contact your J.P. Morgan representative so we can coordinate accordingly.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

• J.P. Morgan will liaise with each clearinghouse to discuss individual clearinghouse migration plans.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

• J.P. Morgan will liaise directly with SwapAgent to discuss migration plans.
• Impacts to other payment and reporting message types are covered in the general sections of this website.

CHIPS has migrated to ISO 20022 on April 2024 and has made provisions to allow ISO-enabled data from CBPR+ messages to be passed between clearing participants from March 20, 2023.

As announced in June 2022, Fedwire Funds Service is migrating to ISO 20022 in March 10, 2025. The FED has shared several new requirements. We encourage all FED participants to review those new requirements for go-live date. Here are some key reminders:

1. FED: cut-off times
   The FED will strictly enforce their cutoff time for 3rd party payments at 6.45 p.m. EST. Payments received after cut-off time will be held for next business day processing.
2. FED: IRS formatting guidelines
   It is necessary that IRS Tax Payments are formatted according to their specific guidelines. Please refer to IRS Tax payments section of the FED guidelines, including the name and address (access to Swift resources is for registered users only) or recent FED communication.
3. Changes to Postal Address Data Validation
   On September 3, 2024, The Federal Reserve deployed a change to relax the requirement to provide postal address information for certain parties. The FED made this change to help avoid disruptions during migration to ISO 20022 format on March 10, 2025. For more details please visit “Changes to Postal Address Data Validation for the Fedwire® Funds Service ISO® 20022 Implementation."

TARGET2 and EURO1 migrated to the new standard on March 20, 2023.

ECB announced earlier start times for TARGET2 and EURO1 settlement processing. As of March 20, 2023, both TARGET2 and EURO1 began settlement processing at 02:30 CET, instead of 07:00 CET for TARGET2 and 07:30 CET for EURO1. This means clients may receive inbound clearing credits from 02:30 CET onwards.

Also, TARGET2 will no longer accept unpublished 11-digit BICs within payment messages. This includes 11-digit BICs of valid 8-digit BICs.

• To ensure payment messages sent to J.P Morgan containing unpublished 11-digit BICs can still be settled through TARGET2, where we’re able to identify such instructions, the associated outbound payment message will be sent using the corresponding 8-digit BIC.
• Clients who want to continue using unpublished 11-digit BICs within payments settled via TARGET2 should take steps to publish the BICs with Swift.

CHAPS migrated to the new standard on 19 June 2023.

1. Effective May 1, 2025, the Bank of England (BoE) has mandated the use of enhanced data fields in CHAPS payment messages.
   From May 1, 2025, CHAPS payments will need to include:
   • Legal Entity Identifier (LEI) - for CHAPS payments between financial institutions
   • Purpose Code (PoP) - for CHAPS payments between financial institutions; only relating to property transactions

J.P. Morgan is updating technology, processes and procedures to meet the requirements of this mandate.

For more details please visit Bank of England announcement here.

2. This the link to Bank of England ISO 20022 landing page

The Philippine Payment and Settlement System (PhilPaSS) migrated to the new standard in July 2021.

The MAS Electronic Payment System (MEPS+) migrated to Like for Like (L4L) ISO messages in August 2022.

The Bank of Thailand Automated High-value Transfer Network (BAHTNET) migrated to the new standard in August 2022.

MYR migrated to the new standard in September 2022.

SAMOS migrated to the new standard in September 2022.

The High Value Clearing System (HVCS) migrated to the new standard in March  2023.

The NZ High Value Clearing System migrated to the new standard in March  2023.

FXYCS adopted ISO 20022 in 2013, using the ISO 20022 version available at the time. The following two-phase approach was agreed to for CBPR+ messages (MX):

1. During the co-existence period through November 2025, an agreed mapping of incoming MX into the current FXYCS ISO 20022 format will be implemented by clearing participants. No changes are expected in the existing FXYCS messages.
2. The Japanese community and the operator of FXYCS will agree on a future date to upgrade the current FXYCS format to a format that is interoperable with the current HVPS+ format.

The Hong-Kong Dollar Clearing House Automated Transfer System (CHATS) migrated to the new standard in April 2024.

Lynx migrated to the new standard in March 2023, in alignment with Swift’s implementation.

Adoption of the ISO 20022 standard for high-value and cross-border payment initiation is optional at this time and clients can continue using existing methods. However, we are prepared to support you if you decide to adopt ISO 20002 pain.001.v3 via a Host-to-Host connection or SwiftNet FileAct.

• Clients connecting to J.P. Morgan via Host-to-Host, FileAct, or EBICs can consider adopting the pain.001 v9 standard (which will enable clients to pass end-to-end enhanced elements such as Ultimate parties and Structured Remittance) and adhering to J.P. Morgan's formatting guidelines.
• Note that J.P. Morgan plans to align with the published industry guidance regarding enhanced data elements.
• Corporate CUG clients (Swift Standardized Corporate Environment — SCORE) connecting to us via Swift: be aware plans to migrate MT101 messages to the ISO 20022 format have not yet been finalized by the industry.

To learn more about ISO 20022 payment initiation options, including account locations where this is available, please contact your J.P. Morgan representative.

ISO 20022 increases the limit of characters that can be presented in Payment Clearing and Settlement messages. Clients may see a "+" symbol at the end of a field when data from an incoming ISO message exceeds the size limit of the current reporting format.

J.P. Morgan will offer a new version of Host-to-Host ISO 20022 camt.05x.001.02 reporting format (Cash Management messages), which will support the increased character limits and additional ISO 20022 data elements present in a Payments Clearing and Settlement messages.

As a new industry message type will be available for returned payments, where possible, we will enhance transparency of return payments within clients' billing invoices, where this doesn’t occur today.

J.P. Morgan Access users can view and print MX-formatted outgoing payment instructions in the Broaden Search section. The MX-formatted payment instructions can be used as proof of payment.