Swift Mandates Bulletin

Navigating Upcoming

Swift Mandates (2025–2028) 

The global payments ecosystem continues to undergo one of the most significant transformation periods in SWIFT’s history. The SWIFT mandates in 2026 and beyond range from infrastructure modernization and evolving message requirements to new mandatory workflows and messaging capabilities. These changes are part of the SWIFT payments modernization initiative, and will affect how cross-border payments are sent, received, investigated, and managed.

Institutions that rely on SWIFT for their critical messaging must prepare for the impact of these developments on their operations, infrastructure, compliance, and long-term payment strategy.

Understanding what is changing—and preparing your
organization accordingly—will be essential in the years ahead
icon

What You Need to Know

SWIFT continues to modernize its global messaging network to improve transparency, resilience, and operational efficiency across cross-border payments.

  • ISO 20022 post-migration status and considerations
  • Implementation of structured payment investigation workflows
  • Changes to payment data requirements and address formatting
  • Modernization of network connectivity infrastructure
  • Continued innovation in fraud detection, payment transparency, and real-time settlement capabilities

Individually, each initiative delivers improvements to the global payments ecosystem. Together, they represent a multi-year transformation of how financial institutions interact with SWIFT.

For financial institutions and payment providers, preparing for these upcoming SWIFT changes should begin now. Executives should consider the following initial actions:

  • Evaluate your current SWIFT environment to determine readiness for ISO 20022 operations, Case Management adoption, and evolving data requirements.
  • Assess operational processes and systems that support investigations, exception handling, and message processing to ensure they can support new workflows.
  • Develop a migration and modernization plan for network connectivity and infrastructure as SWIFT upgrades toward new connectivity models.
  • Consider whether your current SWIFT operating model is sustainable, or whether working with a Service Bureau can simplify ongoing compliance and operational management.

Upcoming SWIFT Mandates Timeline
(2025–2028)

    Scroll Sequence
    Key SWIFT Milestones In More Detail

    ISO 20022 After
    the Coexistence Period

    • SWIFT's coexistence period between legacy MT payment messages and ISO 20022 officially ended in November 2025. Most cross-border payments now use ISO 20022's structured messaging format to enable richer, faster, and more secure global payments.
    • While the migration primarily affected bank-to-bank payment messaging, it also has implications for corporate payment initiation messages. Corporates submitting payment instructions must ensure their treasury and ERP systems generate properly structured payment data that aligns with the requirements of their financial institution counterparties.
    • Institutions that still rely on legacy MT messages may use SWIFT's Contingency Translation Service (CTS), which converts a limited scope of MT messages to ISO 20022 formats, for a limited time. However, ongoing reliance on SWIFT's translation services will increase operational complexity and costs.
    Learn More
    Key SWIFT Milestones In More Detail

    Case Management and
    Payment Investigations

    • SWIFT is introducing a new Case Management framework designed to modernize how payment investigations are handled across financial institutions.
    • Instead of relying on unstructured free-format investigation messages such as MT199, Case Management introduces structured workflows using standardized messages like CAMT.110 and CAMT.111. These changes aim to improve transparency, tracking, and resolution times for payment investigations.
    • Institutions may access Case Management through the available Case Manager portal using a GUI, but many organizations will integrate the platform directly into their internal systems using SWIFT APIs, allowing investigation workflows to be managed within existing operational tools.
    • Preparing for these changes will ensure investigation requests can be managed efficiently within the new structured environment.
    Key SWIFT Milestones In More Detail

    Infrastructure Modernization
    and Connectivity Changes

    • The upcoming Swift network changes will upgrade the network infrastructure to strengthen resilience and prepare for future cryptographic standards.
    • This modernization includes a transition away from legacy VPN connectivity toward SD-WAN-based connectivity options, included in Alliance Connect. These new connectivity models are designed to improve network performance, security, and scalability across the SWIFT ecosystem.
    • Financial institutions will need to evaluate their existing network architecture, infrastructure capabilities, and migration strategies. Planning may involve infrastructure upgrades, connectivity redesign, security assessments, and testing before migration.
    • The transition will occur over two years, with organizations expected to prepare and complete connectivity migrations within SWIFT's designated migration window.
    Key SWIFT Milestones In More Detail

    Data Quality and
    Address Standards

    • SWIFT is also improving payment data quality standards, particularly around party and address information within payment messages.
    • Historically, many payment messages used unstructured address fields, allowing multiple pieces of information to be entered as free text. Under evolving ISO 20022 standards, address data is increasingly expected to be captured in structured fields, such as street name, building number, city, postal code, and country.
    • These changes help improve compliance screening accuracy, straight-through processing rates, and payment transparency.
    • Organizations with legacy systems or inconsistent data standards may need to adjust upstream processes to ensure payment messages meet the new requirements.

    Key SWIFT Milestones In More Detail

    ISO 20022 After
    the Coexistence Period

    Key SWIFT Milestones In More Detail

    ISO 20022 After
    the Coexistence Period

    • SWIFT’s coexistence period between legacy MT payment messages and ISO 20022 officially ended in November 2025. Most cross-border payments now use ISO 20022’s structured messaging format to enable richer, faster, and more secure global payments.
    • While the migration primarily affected bank-to-bank payment messaging, it also has implications for corporate payment initiation messages. Corporates submitting payment instructions must ensure their treasury and ERP systems generate properly structured payment data that aligns with the requirements of their financial institution counterparties.
    • Institutions that still rely on legacy MT messages may use SWIFT’s Contingency Translation Service (CTS), which converts a limited scope of MT messages to ISO 20022 formats, for a limited time. However, ongoing reliance on SWIFT’s translation services will increase operational complexity and costs.

    While these initiatives strengthen the global payments ecosystem, they also introduce significant operational complexity for institutions managing SWIFT infrastructure internally.

    Organizations must now navigate multiple concurrent initiatives, including:

    • ISO 20022 data management and message transformation
    • Case Management adoption and investigation workflow changes
    • Infrastructure and connectivity modernization
    • Data quality and formatting requirements
    • Ongoing SWIFT releases, compliance mandates, and security controls

     

    Addressing all these mandatory SWIFT changes in 2026 and beyond will require coordination across technology teams, payment operations, compliance groups, and external counterparties.

    For many institutions, the challenge here will lie in the cumulative impact of managing multiple SWIFT initiatives at once, while maintaining secure and reliable messaging operations.

    As SWIFT requirements continue to evolve, internal teams must balance ongoing compliance, system upgrades, testing, and operational readiness alongside their core business responsibilities. This growing complexity is one of the reasons many financial institutions are reevaluating whether managing SWIFT infrastructure entirely in-house remains the most effective long-term approach.

    FAQs

    About Upcoming SWIFT Mandates

    SWIFT mandates in 2026 introduce structured payment investigation workflows through Case Management, require structured address data in payment messages, and continue enforcing ISO 20022 standards. Financial institutions must also prepare for connectivity and infrastructure changes that impact how payments are processed and investigated.

    By November 2026, financial institutions must be able to receive structured investigation messages (CAMT.110) through Case Management and support structured address data in payment messages. Institutions must also ensure their systems can process ISO 20022 messages correctly, ensure readiness for evolving API standards, and align with updated SWIFT platform requirements.

    SWIFT mandates affect both technology and operations. Financial institutions must support new message formats, update investigation workflows, and ensure data quality meets structured standards. These changes also require coordination across payments, compliance, and IT teams, increasing the need for system upgrades, process changes, and ongoing testing.

    To remain compliant, institutions must be able to process ISO 20022 messages natively and support structured data elements such as party and address information. This may require updates to payment systems, data models, and integrations to meet SWIFT validation and processing standards.

    Not immediately. Some institutions may still send a limited scope of MT messages through SWIFT’s Contingency Translation Service (CTS), which converts them into the ISO 20022 format. However, this approach increases cost and complexity and is not intended as a long-term solution.

    SWIFT Case Management is a structured framework for handling payment investigations using standardized messages such as CAMT.110 and CAMT.111. Over time, Case Management will replace free-format messages like MT199 and MT299 used for handling payment E&I. Financial institutions must be able to receive messages in the new format by November 2026, with additional requirements for structured responses introduced in 2027.

    Structured address data replaces free-text address fields with defined elements such as street name, building number, city, postal code, and country. This improves screening accuracy, validation, and straight-through processing.

    No. Infrastructure modernization is a separate initiative. While ISO 20022 focuses on messaging standards, SWIFT infrastructure changes involve upgrading connectivity, including a transition from VPN-based connections to SD-WAN-based models.

    Non-compliance may lead to payment disruptions such as rejections or delays, increased manual processing, and higher operational costs. Over time, reliance on temporary workarounds may become more costly and less sustainable.

    Organizations should assess their current SWIFT environment, including messaging, data quality, and workflows, and develop a roadmap for system updates, operational readiness, and testing. Many institutions also evaluate whether working with a SWIFT Service Bureau can reduce complexity and ongoing compliance burden.

    As SWIFT introduces new standards, workflows, and infrastructure requirements, managing these changes internally requires significant resources across technology and operations. As a result, many institutions choose to work with a SWIFT Service Bureau to simplify infrastructure management and maintain compliance with evolving SWIFT mandates.

    Why choose Axletree to

    manage your ongoing Swift mandates?

    Swift & Integration Expertise

    Swift & integration are our specialty – we can support your organization through these changes with out-of-the-box or tailor-made solutions, based on your requirements, and enable the seamless continuation of your critical Swift messaging.

    Unparalleled
    Expertise

    With decades of experience in financial messaging, Axletree understands the nuances of cross-border payments and evolving Swift standards—ensuring you’re always ahead of the curve.

    Cloud-based
    Scalability

    Our cloud-first approach allows you to scale seamlessly, delivering faster deployments, continuous updates, and robust security without disrupting your operations.

    24/7/365
    Global Support

    Rely on our around-the-clock technical specialists to resolve issues swiftly, reducing downtime and safeguarding critical payment flows.

    Reduced Infrastructure
Footprint

    By utilizing our cloud-based solutions, you cut down on maintenance, reducing your internal IT footprint and freeing up resources for growth.

    Advanced Security Measures

    Protect every transaction with end-to-end encryption, multi-factor authentication, and comprehensive audit trails that meet strict industry regulations.

    Future-proof Architecture

    Our solutions are built not only to help you meet the upcoming requirements, but to help you continue evolving ahead of the industry without breaking a sweat.

    Custom solutions for your industry’s challenges

    Ready to prepare your
organization for the next 
phase of SWIFT?

    The evolution of SWIFT messaging and infrastructure is already underway, and institutions that prepare early will be best positioned to navigate these changes successfully.

    Whether your organization is adapting to ISO 20022, preparing for Case Management adoption, or planning infrastructure modernization, Axletree’s Swift-certified experts can help guide your team through every step of the process.

    Contact Axletree today to learn how our experts can help you navigate the next generation of SWIFT connectivity.