Swift has set 12 June 2027 as the new implementation date for the deferred Standards Release 2026, covering MT messages, securities and funds, tracker and investigations changes.
Swift has confirmed a new implementation date for the deferred Standards Release 2026, which will now go live on 12 June 2027.
The deferral originally came in August, when Swift accepted a community request to extend the structured address migration for ISO 20022 payment messages. Progress towards the November milestone had been uneven across all regions, with large parts of the industry still unable to meet the requirement, and several communities formally asked Swift and their domestic payment market infrastructures for additional time. Swift agreed to a controlled extension, deferring all payments changes while it consults banks, central banks, payment market infrastructures, market practice groups and corporates on the optimal timing and approach, with a further update due by December at the latest.
The remaining elements of Standards Release 2026 were decoupled so that they could move faster, initially earmarked for the first quarter of 2027. Following extensive engagement with the industry, including consideration of the European transition to T plus one and the operational pressure of implementing a release during other periods of significant activity, Swift has settled on 12 June 2027 instead. The deferred release covers all MT messages with the exception of Category 1, ISO 20022 securities and funds messages, tracker messages, and exceptions and investigations messages.
Swift has also been clear that institutions should keep pressing ahead with structured addresses, because those already able to send them can benefit today and domestic adoption remains a critical enabler of cross border progress. More than 98 per cent of payment instructions are now sent in the ISO 20022 format following last year’s transition from the MT standard.
For banks, the practical implication is that a substantial volume of change has moved into a period that was already busy, and the months in between are best spent on impact mapping, vendor conversations and testing rather than waiting for the date to come round. Aquila customers receive annual Swift standards updates through the data definition layer at least three months ahead of go live, with no software upgrade required.
The Swift announcement is available in full on swift.com.