What's changing
As part of the global migration to enhanced ISO 20022 data standards, the way postal addresses are provided in international/Cross Border FT payment messages is evolving. Since November 2025, fully structured, hybrid and fully unstructured address formats have been in use. From November 2026, fully unstructured postal addresses will no longer be accepted.
Who is impacted
Customers creating international/Cross Border FT payments in ANZ Transactive APEA should review beneficiary and related party address details to ensure they are captured in a fully structured or hybrid format. This applies to payments using the Cross Border FT payment method.
What you need to do
- Review beneficiary and address book records used for international/Cross Border FT payments.
- Ensure the Town and Country or Region are available as structured address details.
- Where possible, capture additional address details in structured fields, such as Post Code, Street Name, Building Number and Floor.
- Use unstructured address lines only for information that cannot be reliably mapped to a structured field.
- Make updates early to reduce the risk of payment delays, rejection or manual repair after November 2026.
Supported address formats
| ADDRESS FORMAT | DESCRIPTION | MINIMUM REQUIREMENT |
| Fully structured (recommended) | Address data is entered into dedicated fields, such as Floor, Building Number, Street Name, Town Name, Post Code and Country or Region. | Town Name and Country or Region are mandatory. |
| Hybrid | Combines structured address fields with unstructured address lines for complex or non-standard details that cannot be reliably structured. | Town Name and Country or Region are mandatory. |
| Fully unstructured | Address information is entered only as free-text address lines. | Not accepted from November 2026 for international/Cross Border FT payment messages. |
What has changed in ANZ Transactive APEA
International/Cross Border FT payment screens have been enhanced to support fully structured and hybrid addresses. The following fields and behaviours will be available from mid-July 2026 and should be noted when creating a Cross Border FT payment.
| FIELD | DETAILS | SCREEN |
| Payment Name | Payment Name is optional and can be used to describe the payment. | |
| Payment Purpose | Payment Purpose is optional and captures the reason or nature of the payment; it may become mandatory in future for payments to some jurisdictions | |
| Beneficiary Name | Beneficiary Name now supports up to 140 characters. Beneficiary address details should be provided using fully structured or hybrid address fields. |
|
| Beneficiary Address details |
Structured address fields:
*Mandatory fields. Hybrid structured address: The hybrid address format enables you to combine structured and unstructured address data. At a minimum, the structured part must include the Town Name and Country. However, we strongly encourage you to provide as much address information as possible in the structured data elements such as Post Code, Street Name and Building Number, whenever this data is available in a structured form. |
|
| Clearing code type |
United States Routing Number indicates the Bank/Branch Code is for Fedwire/ABA payments. If left blank, the Bank/Branch Code is treated as a SWIFT BIC11 code. |
|
| Purpose Code |
This is an optional field to capture the reason / nature of the beneficiary level payment instruction. This field may become mandatory in some jurisdictions; ANZ will notify when this field becomes mandatory. |
Timeline
| TIMING | ACTION |
| Now to November 2026 | Review and update beneficiary and address book data. Ensure Town and Country or Region details are captured as structured data. |
| November 2026 | Fully unstructured postal addresses will no longer be accepted in international/Cross Border FT payment messages. Non-compliant payments may be delayed or rejected. |