What Standards Release 2026 means for financial institutions, and what to ask AutoRek at Sibos Miami
Financial institutions are managing significant operational change. From rising transaction volumes to richer data requirements and heightened customer expectations, organizations must adapt quickly while maintaining operational efficiency, control and resilience.
Standards Release 2026 sits within this broader transformation. Although ISO 20022 enables greater consistency and richer data, realizing its benefits requires more than updating messaging infrastructure. Firms must ensure the underlying information entering each message is complete, correctly structured, and operationally usable.
One important change is the removal of fully unstructured postal addresses from ISO 20022 messages. The requirement extends across corporate, securities, trade, FX and funds flows, making it relevant to a wide range of Swift participants rather than one segment of the financial services industry.
What does the address requirement mean
Fully unstructured postal addresses are being removed. Only fully structured or hybrid addresses will be accepted, with town name and country mandatory in their own dedicated fields at a minimum.
| Format | What it means | Status after the change | ||
| Fully structured | Each component sits in its own ISO 20022 field, including street name, building number, postcode, town name and country. . | Accepted: target format. | ||
| Hybrid | Town name and country are structured; remaining detail may stay in address lines. | Accepted | ||
| Fully unstructured | Address supplied only as free text across address lines. | Not Accepted: rejection risk | ||
The practical impact can extend across payment instructions, customer and beneficiary records, settlement activity, subscriptions and redemptions, margin and collateral processes, and corporate action proceeds. Each of these flows may rely on party information that must meet a defined structural standard rather than simply being readable by a person.
The timing of the address requirement is currently open. It was scheduled for 14 November 2026, but Swift has deferred it with no replacement date currently set, although a revised timetable is expected by December 2026 at the latest. That is a change of date, not of direction. The community mandate behind structured data stands, and the securities track it sits alongside has not moved outward.
Why this is a data problem, not just a messaging problem
It can be tempting to treat an ISO 20022 change as a connectivity project. However, the greater challenge often lies behind the gateway, within the systems that create instructions and the data those systems hold.
Party and address information may be distributed across customer and beneficiary records, investor and client masters, transfer agency systems, custodian data, settlement instruction repositories, fund administration files and records inherited through acquisitions or long-standing relationships. Much of this information may have originally been captured as free text.
Changing the format of the outbound message does not automatically resolve gaps in the underlying records. If individual address components were never captured, they cannot simply be recovered through message mapping. Firms may need to identify, validate, enrich, and restructure the source data before compliant messages can be created consistently.
ISO 20022 also introduces greater structural complexity. Richer message types can contain more than 1,500 tags, while different versions of the same message may circulate across multiple infrastructures. Reconciliation, reporting and control environments therefore need to interpret the relevant schemas correctly rather than relying only on pattern matching between fields.
Where operational risk can emerge
For banks, payment providers, asset managers, custodians, administrators and other Swift participants, the risk is likely to concentrate in several common areas:
- Customer, beneficiary, investor and counterparty records held as free text
- Payment and transaction instructions that depend on incomplete party information
- Data supplied by customers, counterparties or third-party service providers
- Onboarding and servicing channels that cannot capture structured address components
- Legacy platforms without dedicated fields for structured postal information
- Transformations that remove or truncate important data
- Exception queues that increase when incomplete messages begin to fail validation
Identified in our Infrastructure Gap: Capital Markets Operations 2026, data integration and compatibility were the most frequently cited operational challenge, at 41%. Meanwhile, The Future of Payments Operations 2026 report found 80% experience moderate to significant operational impact from fragmented payments data.
Once structured information becomes mandatory, non-compliant messages may require rejection and repair. Firms should therefore understand the potential volume of affected transactions and ensure operational teams can manage resulting exceptions without disruption for customers or counterparties.
A practical readiness agenda
Assess: Identify which Standards Release 2026 changes apply to your organization, channels, and transaction flows. Avoid assuming that one implementation date or requirement will apply in the same way across every service. Determine how frequently outbound messages contain unstructured party addresses and identify the systems, teams or third parties from which those records originate. The impact assessment should involve operations, technology, data, compliance, and customer servicing rather than being limited to messaging connectivity.
Remediate: Review and structure existing customer, beneficiary, investor and counterparty information, prioritizing records according to transaction volume, operational importance, and risk. Onboarding and servicing channels should capture and validate structured information at the point of entry. Firms should establish whether their core platforms and external providers can supply the required address components within the necessary planning window.
Engage: Communicate data requirements to customers, clients, administrators, correspondents, and counterparties early. Explain which address elements will be required and how that information should be supplied. At a minimum, firms will need reliable town and country data in dedicated fields. Requirements should be incorporated into interfaces and data exchanges rather than depending solely on manual interpretation.
Test: Testing should reflect real operational conditions. That means using realistic message formats, data quality scenarios, and transaction volumes rather than validating only a small number of ideal examples. Firms should test how incomplete records are identified, how rejected messages are routed, and how information is repaired, approved, and resubmitted.
Prepare to fail well: Even with extensive remediation, some inbound information may remain incomplete. Firms should establish controlled rejection and repair processes, provide testing capabilities in advance and resources for the operational transition, as well as the technical implementation.
Where AutoRek fits
AutoRek automates reconciliation, transaction matching and exception management across cash, equities, derivatives, fixed income, FX, collateral and digital assets. It can ingest, enrich, and normalize information from multiple sources to create controlled, audit-ready outputs without dependence on spreadsheets and manual workarounds.
- Swift-formatted data ingestion: AutoRek can consume Swift-formatted files and accommodate new or altered formats through mapping, reducing the need for wholesale re-platforming.
- Flexible data handling: AutoRek is designed to process information arriving in different structures and formats, helping firms bring data together for reconciliation, validation and control.
- Controlled exception management: Where missing or inconsistent information creates breaks, AutoRek provides a framework for managing investigation and repair through a controlled, auditable process.
These capabilities can support organizations across both payments and capital markets as they assess how ISO 20022 changes will affect operational data, reconciliation processes, and exception volumes.
Talk to AutoRek at Sibos
The AutoRek team will be at Sibos Miami from 28 September to 1 October 2026.
If your organization is assessing what Standards Release 2026 means for payments, reconciliation, reference data, transaction controls or exception management, visit AutoRek at Booth DISM12 to discuss how you can prepare.