End of Unstructured Address

After November 2026, when sending an MT101 to J.P.  Morgan, please ensure that address data includes Town Name and Country as structured elements, even when submitted via semi-structured fields.

Example using the MT101 Field 59 (F-option) format for a hybrid postal address:

:59F:/BE30001216371411

1/JOHN SMITH

2/HOOGSTRAAT 6, 18TH FLOOR

3/BE/BRUSSELS, 1000

Where:

1/= Name (JOHN SMITH)

2/=Address Line (HOOGSTRAAT 6, 18TH FLOOR)

3/=Country Code (BE), Town Name (BRUSSELS), and Postal Code (1000)

1. If agents are identified by name and postal address in MT messages, the D option should be used, following the same structure as field 50/59F. This approach ensures frictionless processing by the Debtor Agent upon receipt, aligning with best practices for address data submission.
2. With the implementation of Standards Release (SR) 2026, from November 2026 onwards, only Option F in MT101 messages will enable the transmission of properly structured postal addresses—specifically, the line containing the Town Name and Country Code will be mandatory for cross-border payments. Only Option F provides the structure required for these transactions.
3. Some local payment methods—such as domestic transfers or SEPA—may still allow the initiation of payments using MT101 fields 50/59 with unstructured data. However, when address details are provided in an unstructured format, the bank processing the transaction will not be able to pass on these details—only the name of the party will reliably be transmitted. This limitation could lead to payment delays, rejections, or costly follow-up inquiries, especially for cross-border payments where structured address information is required

Swift will publish the SSR2026 guidelines on 19^th December 2025.