The annual Standards Release (MSR)
SWIFT updates its message standards once a year, and every connected institution moves to the new version on the same November weekend — the annual Standards Release.
L0 Explain simply
An everyday analogy: imagine a paper form used by thousands of offices around the world. It only works because every office prints the exact same version — same boxes, same order, same meaning. If one office quietly adds a box, its forms stop matching everyone else's. So the offices agree to change the form on one day each year, all together. SWIFT does the same with the messages banks send each other. Once a year it publishes an updated set of message standards — the annual Standards Release, or MSR (Message Standards Release) — and every connected institution moves to the new version on the same weekend. Changing together is the whole point: a payment written on Monday must still be readable by a bank that upgraded over the weekend.
L1 Core concepts
The Message Standards Release (MSR) is SWIFT's yearly update to the standards that define its messages. Standards change for three broad reasons: new business needs, such as a field a market has come to require; regulation, such as data that authorities now expect a payment to carry; and technical fixes that correct or clarify rules which proved ambiguous. Both the traditional MT message standards and the ISO 20022 base standards SWIFT maintains move on this same annual cycle, so an institution running both plans one combined change each year. A release is versioned and dated: a specification always belongs to a named release, and "which release does this belong to" is a routine first question when two banks compare how a field should be filled in.
L2 Practitioner view
The rhythm is predictable, which is what lets thousands of institutions coordinate. SWIFT announces the coming changes roughly twelve months ahead, finalises the detail about nine months before go-live, and activates the new release on a weekend in November — traditionally the third weekend. Standards Release 2025 (SR2025) went live over 22-23 November 2025, the same window in which the coexistence period between MT and ISO 20022 for in-scope cross-border payment instructions came to an end. Teams use MyStandards, SWIFT's online tool, to read each release, compare it against the previous version, and check their own systems and usage guidelines for readiness. In practice the work is a project: read the release guide, find the fields that changed, update mapping and validation, test against the new rules, and schedule the cutover for the activation weekend.
L3 Technical details
Each release is documented in a Standards Release Guide that lists every change message type by message type: fields added or removed, format changes, and new or amended network-validated rules — the checks FIN runs before it delivers a message, each with its own error code. On the activation weekend, SWIFT's central systems switch to enforcing the new rules; a message that satisfied last year's rules but breaks a new one will be rejected from the Monday. Because everyone activates at once, there is no long transition for the FIN rule set itself — the change is a step, not a ramp. For ISO 20022, SWIFT maintains base message versions and the CBPR+ (Cross-Border Payments and Reporting Plus) usage guidelines on a coordinated schedule, so cross-border communities know which message version is current. The authoritative documents sit behind a swift.com account, so public summaries — this one included — are not substitutes for the release guide itself.
L4 Standards & sources
Two SWIFT sources govern this topic. The Standards MT documentation, published through the annual Standards Releases on swift.com, is the authority for what changes each year in the MT message set: the Standards Release Guide, the field-level specifications, and the network-validated rules enforced on the activation weekend. The ISO 20022 adoption material describes how the same cycle maintains the ISO 20022 base standards and the CBPR+ (Cross-Border Payments and Reporting Plus) usage guidelines for cross-border payments, including the end of MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions in November 2025. Both require a swift.com account for full detail. Two practical cautions: release dates and scope are set by SWIFT and can shift, so confirm the current schedule rather than assuming last year's; and a specification is only meaningful paired with its release, because the same field can differ between one Standards Release and the next.
Sources & standards2
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Standards Release Guide; annual Standards Releases
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.
- Official requirement
ISO 20022 Standards (Swift ISO 20022 adoption programme) ↗ — Swift · ISO 20022 base standards and CBPR+ maintenance cycle
Programme milestones change over time; the coexistence period for in-scope cross-border payment instructions ended in November 2025. Check swift.com for the current timeline.
Sources for this topic3
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Standards Releases; Standards Release Guide
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.
- Official requirement
ISO 20022 Standards (Swift ISO 20022 adoption programme) ↗ — Swift · ISO 20022 adoption programme and coexistence timeline
Programme milestones change over time; the coexistence period for in-scope cross-border payment instructions ended in November 2025. Check swift.com for the current timeline.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The shared-form analogy compresses the release into a single yearly switch; in reality scope, dates, and the balance between MT and ISO 20022 changes vary release to release, and the authoritative documents require swift.com access. Timeline figures are approximate and set by SWIFT.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Deepest material on this page: L4 — Standards & sources. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.