Swift Said There Was No Contingency. Then It Moved the Date.

On 27 August Swift told its community that it will defer all payments changes in Standards Release 2026, including the requirement to move from unstructured to structured postal addresses in ISO 20022 payment messages. Progress, it said, "remains uneven with large parts of the industry across all regions still unable to meet the requirement", and several communities had formally asked for more time.

Three months earlier Swift had published a call-to-action for the same deadline. It was specific: "After 14 November 2026, unstructured addresses will be removed." It was also explicit that there was no fallback. "There is no Swift contingency measure to process non-compliant messages."

The format migrated. The data did not.

The deferral announcement opens with a success. 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, which Swift says puts the industry in a strong position.

The address figures point the other way. In the May call-to-action Swift reported that April data showed 61.2 per cent of payments included unstructured Debtor postal addresses and 62.9 per cent included unstructured Creditor information. Inverted, that is 38.8 per cent and 37.1 per cent compliant, against a target of zero per cent unstructured.

The two sets of figures are not measured at the same moment. The 98 per cent is stated in the August announcement; the address percentages are April data quoted in May. Swift published no updated address figure alongside the deferral, so the most recent public number on the requirement that has just been postponed is four months old.

Taken together they describe a gap of roughly sixty percentage points inside a single migration. Adopting a message format is a systems change a bank can complete on its own. Populating that format with a structured address means obtaining the town and country of a beneficiary from a corporate customer, who has to hold it in an ERP or treasury system in the first place. The first is an IT project. The second is a data-collection problem that reaches past the bank to its clients and their records, and that is the one that has slipped.

What was deferred, and what was not

The announcement splits Standards Release 2026 into three.

Structured addresses are deferred with no replacement date. Swift will consult banks, central banks, payment market infrastructures, market practice groups and corporates to define the timing, and will "provide an update by December, at the latest, as part of its governance cycle". That is a date for announcing a date, and it falls 126 days after the deferral.

Other payments changes planned for November "will be phased separately", with no dates given in the announcement and customers directed to swift.com for details.

Securities, trade and other changes are being decoupled "so they can proceed faster" and will go live in Q1 2027, with an exact date to be set by mid-September. Swift names the move to T+1 settlement in some markets as one of the reasons those cannot wait. Note that Q1 2027 is later than the November 2026 cutover, so "faster" here means faster than the deferred payments track rather than earlier than originally planned.

The practical position for an institution reading this is that the announcement gives no component of Standards Release 2026 a November 2026 go-live date. Whether any part of the payments package still lands in November depends on the phasing detail Swift has published elsewhere, which this announcement does not summarise.

The contingency was the date

The May guidance was unusually direct about consequences. Payments without structured or hybrid address data "may be rejected or delayed as they move through the payment chain", and institutions were told to build processes to manage rejections and repairs. Corporates on MT101 were told they must upgrade to field 59 option F. The minimum data requirement was set at town name and country.

None of that has been withdrawn. What changed is the date on which it binds. Swift's position is that institutions which have already upgraded can use structured addresses on the network today, and it "strongly encourages" market infrastructures and institutions to keep going, because domestic adoption is what enables the cross-border requirement to work.

That is a reasonable ask and also an uncomfortable one. The firms that spent to hit 14 November now carry the cost without the deadline, and the firms that did not have been proved right to wait. Any future date has to be set against that.

What we could not verify

This report is based on two Swift announcements and no other source. We did not obtain the underlying readiness data behind the 61.2 and 62.9 per cent figures, the identity of the communities that requested the extension, or the domestic payment market infrastructures that Swift says it consulted. Swift names none of them.

We could not reach swift.com by direct request while preparing this piece and read both announcements through a browser session instead. We did not review the customer-area FAQs or the Quick Guides referenced in the May guidance, which sit behind the customer login.

The 2023 decision date and the November 2025 completion are as Swift describes them; neither announcement gives a day date for either, so this piece does not compute intervals from them.

What to watch

Mid-September, for the exact Q1 2027 date on the securities track, which is the nearest commitment in the announcement and the first test of whether the new timetable holds. December, for the structured address update, which Swift has bounded as "at the latest". And the next readiness figure Swift publishes, because 61.2 per cent unstructured in April is the number any new deadline has to be justified against, and it is the one figure the deferral did not update.