swift-logo
ISO 20022: Exceptions and Investigations ISO 20022 FAQs

ISO 20022: Exceptions and Investigations

The migration to ISO 20022 standards for Exceptions and Investigations and payment cancellations messages is facilitated by the use of Case Management.

ISO 20022: Exceptions and Investigations

What is Case Management?

Case Management consists of two services – Case Orchestrator for E&I and Stop and Recall for payment cancellations. It is designed to streamline investigation processes to maximise efficiency and reduce operational costs. Thanks to smart message delivery, automation and improved end-to-end transparency, financial institutions can expect to reduce the time it takes to resolve enquiries.

What are the ISO 20022 messages for E&I / payment cancellations and their MT equivalents?

  • Payment Cancellations
    • camt.056 – Payment Cancellation Request (MT 192/292) 
    • camt.029 – Payment Cancellation Response (MT 196/296)
  • Exceptions and Investigations
    • camt.110 – Investigation Request (MT 195/198/295/298 & MT 199/299)
    • camt.111 – Investigation Response (MT 196/198/296/298 & MT 199/299)
  • Notifications
    • trck.003 – Tracker Alert Notification (MT 199)
    • trck.005 – Tracker Investigation Status Notification (MT 199)

Can institutions migrate to ISO 20022 for E&I without using Case Management?

Financial institutions can migrate to ISO 20022 for payment cancellations (camt.056/029) without needing to use Case Management, as these messages can be exchanged bilaterally. However, as part of the wider effort to optimise the processing of payment cancellations messages, the use of Stop and Recall will become mandatory for all payment cancellations from November 2027.

For Exceptions and Investigations, migration to camt.110/111 is only possible through the use of Case Management (Case Orchestrator). These messages cannot be exchanged bilaterally.

What are the migration timelines?

The timelines to migration to ISO 20022 for Exceptions and Investigations is as follows:

  • Today – Payment cancellation messages can be exchanged through the Stop and Recall Process (Tracker BIC) for CustomerCreditTransfer (CCT) payments with an active UETR in the Tracker in MT and ISO 20022 formats. These messages can also be exchanged bilaterally for all underlying transaction types. For E&I, the camt.110 investigation request and camt.111 investigation response messages can only be exchanged through the Case Orchestrator. These services are available to all financial institutions through onboarding to Case Management.
  • November 2026 – All institutions must be able to receive a camt.110 with in-flow translation – embedded MT 199 included in the camt.110. This milestone will provide full reachability to Case Management participants, as they will be able to initiate investigations through Case Management regardless of receiver’s adoption status.
  • November 2027 – Payment cancellation messages for all underlying transactions must be exchanged through Stop and Recall (Tracker BIC) and must be in ISO 20022 format only (camt.056/029).
  • November 2027 – All investigation requests and responses to be in ISO 20022 format (camt.110/111) routed through Case Management.
     

 

Is there a cost of in-flow translation for the camt.110 investigation request message?

In-flow translation for non-instruction messages remains free of charge. This includes the camt.110 investigation request. 

Can I opt out of in-flow translation for the camt.110?

All financial institutions can disable (and re-enable) in-flow translation. The embedded MT 199 in the camt.110 investigation request assists non-Case Management participants to continue the investigation through bilateral exchange of MT 199s over FIN.

What translation services are available for payment cancellation messages (camt.056/029)?

In-flow translation is enabled on camt.056/029 messages (embedded MT n92/n96), when exchanged bilaterally or via the Tracker BIC using Stop and Recall. When payment cancellations are exchanged via the Tracker BIC (using the Stop and Recall), receivers can set their reception preferences, opting to receive an MT or MX messages regardless of the sender’s original message format. The Tracker maps between MX and MT equivalents. This service will be maintained until November 2027, after which all messages must be in ISO 20022 format. 

How can I prepare for this migration?

The most effective way to prepare for this migration is to subscribe and onboard to Case Management. By adopting Case Management ahead of the November 2026 milestone, your institution will technically be set up to send and receive payment cancellation and E&I messages through the orchestration services (Stop and Recall and Case Orchestrator), which means you will already be compliant with both November 2026 and 2027 milestones.

For financial institutions not adopting Case Management, it is essential to get prepared for the upcoming milestones:

  • November 2026: Swift will make it possible to receive camt.110 with in-flow in November 2026. This will enable financial institutions to comply with the migration timelines without the need to onboard to Case Management. Testing capabilities to receive a camt.110 and respond with an MT 199 will be made available in advance of November 2026.
  • November 2027: All eligible financial institutions will become Case Management participants without the need to subscribe, as Swift will mass enable all banks to be able to send camt.110/camt.111 and camt.056/029 messages via Case Management.

When will MT messages for Exceptions and Investigation be phased out?

From November 2027, the use of MT messages for E&I will be fully phased out. Formatted MT messages for payment cancellations (MTn92 and n96) and E&I (MTn95 and n96) will be removed.

Free format messages (MT n99) will still be available but should not be used for E&I purposes.