SWIFT Standard Release 2026
This document contains the description of the changes implemented on the product for Standard MT and MX Release 2026 with the timeline associated.
MT Release Impact
Index of Impact Levels
| Level | Description |
| Level 0 | This is a minor change that does not impact the format of the message. For example, the scope of the message is updated, which may have an impact on some automated applications. |
| Level 1 | This change relates to the use of the message format but does not affect the message structure or the FIN validation, for example, a definition or a usage rule is changed. |
| Level 1+ | An existing message type is removed from the network. |
| Level 2- | The change has a small effect on the message structure and the FIN validation, for example, field formats, qualifiers, or codes are added or deleted. |
| Level 2+ | The message layout or the FIN validation or both are significantly impacted, for example, fields or sequences (mandatory or optional) are added or deleted. |
| Level 3- | A new message type is created for use in a message user group (MUG) or the use of an existing message type is changed from use in a MUG to general use, that is, all users must be able to receive and process the new message. |
| Level 3 | A new message type is created for general use, that is, all users must be able to receive and process the new message. |
MT Release Change Requests
| Message Types (MT) | Short description of the modification | IPC Wire Services Impact | Impact |
| MT 300, MT 304, MT 305, MT 306, MT 320, MT 321, MT 330, MT 340, MT 341, MT 350, MT 360, MT 361, MT 362, MT 364, MT 365, MT 370, MT 600, MT 601, MT 620, MT 670, MT 671 |
Update J tags to add a new subfield for country. Cross-border and high-value payments will no longer allow unstructured postal addresses from Standards release 2026, category 3 and 6 should be updated to remain compatible with these downstream messages. |
Update on MT3xx libraries to allow new changes. | 2+ |
| MT 300, MT 304, MT 320, MT 321, MT 330, MT 340, MT 341, MT 350, MT 620 |
Add LEIC code to J tags for category 3 messages where this is not already available. |
Update on MT3xx libraries to allow new changes. | 2- |
| MT 707 |
Revised code name for field :71N: "Amendment Charge Payable by". Change the code OTHR description from "other party" into "other arrangement" in MT 707. |
CR 002008 - No impact on payment processing or mappings. |
1 |
| MT 700 MT 707 MT 710 MT 720 |
Revise field definition for :71D: "Charges" in MT 700, MT 707, MT 710, MT 720. Revise field definition for field 71D to "This field may be used to specify the party(s) responsible for the documentary credit charges”. |
No impact on payment processing or mappings. | 1 |
| MT 700 MT 705 MT 707 MT 710 MT 720 MT 760 |
Add a new designated field to specify the :45H: HS Code(s) as optional field – if applicable. |
Update on MT7xx libraries to allow new changes. | 2+ |
| MT 700 MT 707 MT 710 MT 720 |
Change length of field 78 to 30*65x. |
Update on MT7xx libraries to allow new changes. | 2- |
| MT 700 MT 707 MT 710 MT 720 |
Change the format of the field 78D (Instructions from intermediary/transferring bank) from 12*65x to 12*65z. |
Update on MT7xx libraries to allow new changes. | 2- |
| MT 700 MT 705 MT 707 MT 710 MT 720 |
Change in format of fields 44A, 44B, 44E, and 44F from 1*140z to 2*65z in multiple category 7 MTs. It is recommended to add a new designated field to specify the :44I: Incoterms as optional field – if applicable. |
Update on MT7xx libraries to allow new changes. |
2-
2+ |
| MT 700 MT 705 MT 707 MT 710 MT 720 MT 740 MT 760 MT 765 MT 767 MT 785 |
Party fields. Trade Finance users across the globe have expressed concerns about space issues they encounter with respect to party fields in the Trade Finance Message categories. Non-FI fields such as Applicant, Beneficiary etc. will be replaced by a sequence of five new fields. |
Update on MT7xx libraries to allow new changes. | 2+ |
| MT 700 MT 710 MT 720 |
Change character set from 3*35x to 3*35z of field 42C. |
Update on MT7xx libraries to allow new changes. | 2- |
MX Release Impact
MX Release New Message Types
| Message Type | Message Name | New Business Service | IPC Wire Services Impact |
| admi.024.001.01 | Notification of Correspondence | swift.cbprplus.02 | Usage guideline updated. |
| camt.025.001.08 | Receipt | swift.cbprplus.02 | Usage guideline updated. |
| camt.029.001.09 | Resolution of Investigation | swift.cbprplus.04 | Usage guideline updated. |
| camt.052.001.08 | Bank To Customer Account Report | swift.cbprplus.04 | Usage guideline updated. |
| camt.053.001.08 | Bank To Customer Statement | swift.cbprplus.04 | Usage guideline updated. |
| camt.054.001.08 | Bank to Customer Debit Credit Notification | swift.cbprplus.04 | Usage guideline updated. |
| camt.055.001.08 | Customer Payment Cancellation Request | swift.cbprplus.03 | Usage guideline updated. |
| camt.056.001.08 | FI to FI Payment Cancellation Request | swift.cbprplus.04 | Usage guideline updated. |
| camt.057.001.06 | Notification To Receive | swift.cbprplus.04 | Usage guideline updated. |
| camt.058.001.08 | Notification To Receive Cancellation Advice | swift.cbprplus.03 | Usage guideline updated. |
| camt.060.001.05 | Account Reporting Request | swift.cbprplus.04 | Usage guideline updated. |
| camt.105.001.03 | Charges Payment Notification | swift.cbprplus.01 | Usage guideline updated. |
| camt.105.001.03 | Charges Payment Notification Multiple | swift.cbprplus.mlp.01 | Usage guideline updated. |
| camt.106.001.03 | Charges Payment Request | swift.cbprplus.01 | Usage guideline updated. |
| camt.106.001.03 | Charges Payment Request Multiple | swift.cbprplus.mlp.01 | Usage guideline updated. |
| camt.107.001.01 | Cheque Presentment Notification | swift.cbprplus.03 | Usage guideline updated. |
| camt.108.001.01 | Cheque Cancellation or Stop Request | swift.cbprplus.03 | Usage guideline updated. |
| camt.109.001.01 | Cheque Cancellation or Stop Report | swift.cbprplus.03 | Usage guideline updated. |
| pacs.002.001.10 | FI to FI Payment Status Report | swift.cbprplus.04 | Usage guideline updated. |
| pacs.003.001.08 | FI to FI Customer Direct Debit | swift.cbprplus.03 | Usage guideline updated. |
| pacs.004.001.09 | Payment Return | swift.cbprplus.04 | Usage guideline updated. |
| pacs.008.001.08 | FI to FI Customer Credit Transfer | swift.cbprplus.04 | Usage guideline updated. |
| pacs.008.001.08 STP | FI to FI Customer Credit Transfer STP | swift.cbprplus.04 | Usage guideline updated. |
| pacs.009.001.08 ADV | FI Credit Transfer (Advice) | swift.cbprplus.adv.04 | Usage guideline updated. |
| pacs.009.001.08 COV | FI Credit Transfer (Cover) | swift.cbprplus.cov.04 | Usage guideline updated. |
| pacs.009.001.08 | FI Credit Transfer | swift.cbprplus.04 | Usage guideline updated. |
| pacs.010.001.03 | Interbank Direct Debit | swift.cbprplus.col.03 | Usage guideline updated. |
| pain.001.001.09 | Customer Credit Transfer Initiation | swift.cbprplus.04 | Usage guideline updated. |
| pain.002.001.10 | Customer Payment Status Report | swift.cbprplus.04 | Usage guideline updated. |
| pain.008.001.08 | Customer Direct Debit Initiation | swift.cbprplus.03 | Usage guideline updated. |
MX Release Change Requests
| Message Type | Short description of the modification | IPC Wire Services Impact | Impact |
| All CBPR+ usage guidelines |
Retirement of unstructured postal address option across CBPR+ usage guidelines for all parties and agents. All postal addresses must use the fully structured or hybrid option. This change is mandatory for all users of CBPR+ messages. |
SWIFT AI tool is integrated into IPCWS in order to help avoid sending unstructured address in MX message. Please contact the IBM Payments Center if you are interested. | 2+ |
| camt.057, camt.105, camt.105 MTP, camt.106, camt.106 MTP, camt.107, camt.108, camt.109, pacs.003, pacs.004, pacs.008, pacs.008 STP, pacs.009, pacs.009 ADV, pacs.009 COV, pacs.010, pacs.010 MC, pain.001, pain.008 |
Change Proxy Type to required (min 1, max 1). Change multiplicity of Proxy / Type from Min 0 Max 1 to Min 1 Max 1. Ensures that when a proxy is provided, the type of proxy is understood e.g. the proxy is an Email Address. |
Update camt & pacs & pain libraries to allow new changes. | 2+ |
| pain.001 |
Formalize rule: PaymentInformationIdentification equals MessageIdentification; OriginalPaymentInformationIdentification equals OriginalMessageIdentification. |
Update pain libraries to allow new changes. | 2+ |
| admi.024, camt.025, camt.029, camt.052, camt.053, camt.054, camt.055, camt.056, camt.057, camt.058, camt.060, camt.105, camt.105 MTP, camt.106, camt.106 MTP, camt.107, camt.108, camt.109, pacs.002, pacs.003, pacs.004, pacs.008, pacs.008 STP, pacs.009, pacs.009 ADV, pacs.009 COV, pacs.010, pain.001, pain.002, pain.008 |
Apply the same Data Type restriction for Related BAH as BAH. Implement CBPRplus restricted datatype to any BAH element which uses a Max35Text datatype inherited from the base message. |
Update camt & pacs & pain libraries to allow new changes. |
2-
2- |
| camt.029, camt.055, camt.056, camt.057, camt.058, camt.107, camt.108, camt.109, pacs.002, pacs.003, pacs.004, pacs.008, pacs.008 STP, pacs.009 COV, pain.001, pain.002, pain.008 |
Change multiplicity of Scheme Name from Min 0 Max 1 to Min 1 Max 1 for all agents and parties, and removal of the Proprietary choice under Scheme Name element. Where the datatype ISODate is used across the CBPR+ usage guidelines apply a new pattern that restricts illogical dates e.g. a year with more than four digits. Improving the validation across the FINPlus network. |
Update camt & pacs & pain libraries to allow new changes. |
2+
2+ |
| camt.052, camt.053, camt.054 |
Change pattern of the PageNumber element. Improve the pattern so a page number with value 0 (zero) is not allowed. Make ElectronicSequenceNumber mandatory in the CBPR+ camt.053 and CBPR+ camt.052. Remove the CBPR_Electronique_Or_Legal_Sequence_Number_FormalRule from the CBPR+ camt.053. Amend the datatype used in /Document/BkToCstmrAcctRpt/Rpt/Ntry/NtryDtls/TxDtls/FinInstrmId/Desc in the CBPR+ camt.052 from CBPR_RestrictedFINXMax35Text to CBPR_RestrictedFINXMax140Text_Extended. The CBPR_Page_Number_2_FormalRule and CBPR_Last_Page_Indicator_2_FormalRule in the CBPR+ camt.053 should be improved so rules are always validated correctly by the FINPlus network. |
Update camt libraries to allow new changes. |
2-
2+
2-
2+ |
| pacs.004; pacs.010; pacs.010 MC |
Improving the validation across the FINPlus network. ReturnIdentification in the CBPR+ pacs.004 becomes mandatory. OriginalInstructionIdentification in the CBPR+ pacs.004 and CreditIdentification in the CBPR+ pacs.010 are restricted to 16 characters from 35 characters. |
Update pacs libraries to allow new changes. | 2+ |
| pacs.003; pacs.004; pacs.008; pacs.008 STP; pacs.009 COV |
Mandate InstructedAmount or ReturnedInstructedAmount in relevant CBPR+ pacs messages. Compliance with CPMI data requirements. |
Update pacs libraries to allow new changes. Update MT to MX Mappings if needed. |
2+ |
| pacs.004 |
Remove the following element in the CBPR+ pacs.004: /Document/PmtRtr/TxInf/OrgnlTxRef/MndtRltdInf. There is no business case for using this element, as such it can be removed. The proprietary option will be removed from Clearing System Identification in the Original Transaction Reference block, it is currently available in four places. |
Update pacs libraries to allow new changes. |
2+
2+ |
| pain.001 |
When /Document/CstmrCdtTrfInitn/PmtInf/Dbtr/Id/OrgId/Othr is used to identify the Debtor, /Document/CstmrCdtTrfInitn/PmtInf/Dbtr/Id/OrgId/Othr/SchmeNm should be mandatory. Amend the datatype of EndToEndIdentification in the CBPR+ pain.001 from Max35Text to CBPR_RestrictedFINXMax35Text. Make the Reference mandatory under the Remittance Information/Creditor Reference Information in the CBPR+ pain.001. Where used, update the datatype ISODateTime to CBPR_DateTime in pain.001. |
Update pain libraries to allow new changes. |
2+
2-
2+
2- |
Standard Release 2026 Timeline
Implementation
The Product implementation for the Standard MT and MX changes is scheduled from June to September 2026.
IPC Wire Services Client Testing in UAT
Starting on 19 September 2026 (Tentative), the SWIFT Standard MT and MX Releases 2026 will be activated. All MT and MX messages processed in that environment will follow the new format validations.
Client tests must be completed by October 22, 2026 (Tentative).
Please Note: 19-Sep & 22-Oct dates are tentative because of CBPR+ translation library dependency.
Production Go Live
The Production Go Live is scheduled for 14th November 2026.
For any questions or if you require any assistance, please don’t hesitate to contact the IBM Payments Center.