This blog marks the first in our three-part series exploring the shift to Swift Case Management, a new framework reshaping how banks handle exceptions and investigations (E&I). Over the coming months, we’ll look at what’s changing, how banks can prepare, and what the long-term implications will be.
In this first instalment, we focus on what Case Management is and why it’s being introduced. The current system for managing E&I is slow and heavily manual, leading to inconsistent processes across institutions. Swift’s new framework aims to change this by introducing a standardised model for exception handling that will become mandatory by November 2027.
The state of E&I today
While cross-border payments have become faster, E&I has not kept pace. A typical investigation still takes five to ten days to resolve, even though most international payments now settle within hours. When a payment query arises, banks must manually exchange free-form messages to find out what went wrong.
Each investigation can pass through several intermediaries. Staff often interpret incomplete data, send manual follow-ups, and rekey information between systems. These repetitive steps add delays and increase the risk of errors. Customers are left without visibility into payment status, leading to frustration and, in some cases, attrition. The impact is financial as well as reputational, with higher operational costs and potential penalty fees.
Why reform is needed
The biggest barrier to progress is standardisation. Over 72% of today’s E&I messages use free-form MT formats that were never designed for automation or structured data exchange. Without consistent formats or workflows, every institution handles exceptions differently – making it difficult to resolve cases quickly or share information efficiently across borders.
At the same time, expectations have shifted. Clients now want the same transparency as domestic real-time payments, while regulators are tightening requirements for resilience and data integrity. The industry needs a solution that makes E&I faster, more predictable, and auditable.
What Swift Case Management changes
Case Management is Swift’s answer to these challenges. It introduces a centralised, structured process for exception handling. Instead of sending unstructured MT messages, banks will now exchange standardised ISO 20022 case messages.
Each case carries a unique end-to-end reference number, giving all parties visibility over its status in real time. Automated routing ensures cases reach the right party, removing the need for manual forwarding. The framework also supports API connectivity, enabling integration into existing workflows and systems rather than relying on manual portals.
The implementation timeline
The transition is being phased to help institutions adapt.
- 2024–2025: Early adopters have already begun using Case Management as part of the initial rollout.
- November 2025–2026: General availability and mandatory receipt of case messages.
- End of 2027: Full enforcement; MT199/299 messages will be retired and ISO 20022 messaging required.
Banks must ensure their systems can send, receive, and interpret ISO 20022 messages, whether through API integrations or FINplus messaging. Workflows and exception-handling processes will also need updating to align with the new structure and maintain full auditability.
A critical step for the payments industry
Swift Case Management is one of the most significant operational changes to cross-border payments in years. It addresses longstanding inefficiencies and sets a clear direction for greater transparency and automation. The next two years will be crucial for understanding what this shift means in practice – both technically and operationally.
Our next blog in this series will explore how banks can prepare for the transition and how specialist providers can help them build systems ready for the 2027 deadline.
