Automated Swift Case Management
Aquila automates Swift Case Management from capture to closure
Aquila automates the full exceptions and investigations lifecycle, capturing camt.110 investigation requests as they arrive, routing them through Swift’s Case Orchestrator, and producing camt.111 responses without manual rekeying, so investigations are handled as structured messages rather than as free format enquiries worked by hand.
It sits alongside the existing core banking platform rather than replacing it, which means a bank can meet the mandate without taking on a core transformation programme at the same time.
How Aqua Global Can Help
Exceptions and investigations have stayed manual while the rest of the payment chain has automated around them, and the move to Case Management turns that work into structured ISO 20022 messaging carried over FINplus. Aquila gives operations teams the controls to make that shift without adding headcount.
01
camt.110 and camt.111 Automation
Aquila captures inbound camt.110 investigation requests, matches them to the original payment, and produces camt.111 responses from the same platform, so an investigation is handled as structured data rather than retyped into a separate workflow.
02
Routing Through Case Orchestrator
Cases are routed through Swift’s Case Orchestrator with status tracked throughout, giving operations teams a single view of which investigations are open, who is holding them and what stage each one has reached.
03
Three Integration Paths
Banks can work through the Aquila interface, integrate directly over API, or connect across FINplus, which lets each institution adopt Case Management at the level of automation that suits its operating model and its existing systems.
04
Retirement of Legacy MT Investigations
Aquila manages the transition away from MT192, MT292, MT195, MT295, MT196 and MT296, and away from the use of MT199 and MT299 for exceptions and investigations, so moving off the legacy formats becomes a configuration exercise rather than a rebuild.
05
Stop and Recall in ISO 20022
Payment cancellations move to Stop and Recall in ISO 20022 only, and Aquila produces and consumes those messages natively alongside the investigation flow, which keeps cancellation and investigation activity together in one place.
06
No Core Replacement Required
Aquila sits between the core banking platform and the Swift network, so Case Management can be adopted without touching the core, and a typical deployment is measured in months rather than the multi year timeline a core change would demand.
The two dates that matter
The first milestone falls on 12 June 2027, when banks must be able to receive camt.110 investigation requests, with in flow translation embedding an MT199 for institutions that are not yet live on Case Management. The full mandate follows in November 2027, when camt.110 and camt.111 must be sent and received through Case Management over FINplus, in flow translation ends, and the legacy MT investigation messages are withdrawn.
A good deal of published material still shows November 2026 for that first milestone. That date travelled with Standards Release 2026 when the release was deferred, and Swift confirmed on 21 September 2026 that the deferred package, which includes exceptions and investigations messages, now goes live on 12 June 2027. June 2027 is sooner than the November date most banks have in mind and it is shorter than a typical implementation, which is why the planning work is worth starting now.
Join our webinar with Swift
We are hosting a thirty minute session with Swift on Thursday 19 November 2026 at 2pm GMT, covering what the camt.110 and camt.111 mandate requires, how the June and November 2027 milestones fit together, and what banks should already have under way.
Iouri Galitchenko, Case Product Manager at Swift, joins Nick Fernando, Co-Founder and Director at Aqua Global, with time set aside for questions from attendees.
Get in touch
Explore our comprehensive suite of solutions designed to streamline your financial operations.
Frequently Asked Questions related to Swift Case Management
What is Swift Case Management?
Swift Case Management is a centralised model for handling payment exceptions and investigations, replacing free format MT enquiries with structured ISO 20022 messages carried over FINplus. Investigation requests are sent as camt.110 and responses as camt.111, and cases are routed and tracked through Swift’s Case Orchestrator so that every party to an investigation works from the same status.
When does Swift Case Management become mandatory?
There are two dates. From 12 June 2027 banks must be able to receive camt.110 investigation requests, with in flow translation embedding an MT199 for institutions not yet live on Case Management. From November 2027 the mandate is full, meaning camt.110 and camt.111 must be sent and received through Case Management over FINplus, in flow translation ends, and the legacy MT investigation messages are withdrawn. Material still showing November 2026 for the first milestone is out of date, because that milestone moved when Standards Release 2026 was deferred.
What are camt.110 and camt.111?
camt.110 is the ISO 20022 message used to raise an investigation request against a payment, and camt.111 is the message used to respond to it. Together they replace the free format MT enquiry and response messages banks have relied on for exceptions and investigations, and because both carry structured data they can be matched to the original payment and processed automatically rather than read and rekeyed by an operations team.
Which legacy MT messages are being withdrawn?
MT192, MT292, MT195, MT295, MT196 and MT296 are removed, and MT199 and MT299 are retired for exceptions and investigations purposes. Payment cancellations also move to Stop and Recall in ISO 20022 only, so a bank still relying on those formats for cancellations or investigations will need an alternative in place before November 2027.
Do banks need to replace core systems to adopt Swift Case Management?
No. A messaging and investigations layer can sit between the core banking platform and the Swift network, consuming and producing camt messages without the core being changed. Aquila works this way, which is what allows a bank to meet the mandate on its own timetable rather than waiting for a wider core transformation programme to complete.
How long does Swift Case Management take to implement?
Implementation is measured in months rather than weeks, which matters because the first milestone on 12 June 2027 sits closer than the November 2027 date most banks are planning against. Starting the scoping work early leaves room for testing and for the operational change that comes with moving investigations from free format enquiries to structured messages.