camt.111 ISO-20022-Nachricht

Published on

07/09/2026

Updated on

07/09/2026

Reading time

4 min

The camt.111 is the ISO 20022 InvestigationResponse message. An institution uses it to answer a structured investigation request it previously received as a camt.110. Together the two messages form the core of Swift’s modernisation of Exceptions & Investigations (E&I) and replace the free-format MT communication used so far.

Definition

camt.111 belongs to the ISO 20022 Cash Management (camt) family and originates from the Exceptions and Investigations Modernisation message set submitted by the PaySEG E&I Work Group. The current version listed in the ISO 20022 catalogue is camt.111.001.03 (InvestigationResponseV03, last updated in March 2026) – one version ahead of its request counterpart camt.110.001.02.

In business terms camt.111 answers the question “What is the state of this investigation?” It carries both the processing status of a case and its substantive outcome – the requested information about a payment, a counter-query, or the rejection of the investigation.

Distinction from camt.029

The most common source of confusion in day-to-day operations concerns the two answer messages used around investigations:

camt.029 (Resolution of Investigation) answers a cancellation, i.e. a camt.056, as well as the classic enquiry messages camt.027 and camt.087.
camt.111 answers a camt.110 only, within Swift Case Management.

Neither message reports the status of the payment itself; that is the role of pacs.002 and pain.002.

Message structure

The structure of camt.111 mirrors that of camt.110 and adds the status component. Its main building blocks are:

InvstgtnRspn – the response block of the message.
RqstrInvstgtnId / RspndrInvstgtnId – investigation references of the requesting and the responding institution. They link the response to the original camt.110 and hold all messages of a case together.
InvstgtnSts – the processing status of the investigation, distinguishing an acknowledgement, an interim update, a final answer or a rejection.
Undrlyg – the underlying payment, either as a customer instruction or as an interbank transaction such as a pacs.008.
Rqstr / Rspndr – requesting and responding party, normally identified as an agent (financial institution).
ResponseData – the actual response content for the investigation type concerned.

Here too the bracket around the whole process is the UETR (Unique End-to-End Transaction Reference). It links the original payment, its status reports and all investigation messages into a fully traceable chain – the precondition for tracking a case by machine throughout its life cycle.

Message dialogue

An investigation is not a single question-and-answer exchange but a dialogue. Several camt.111 messages may be sent in response to one camt.110: typically an acknowledgement first, an interim update where processing takes longer, and finally the conclusive answer. Equally, the requesting institution may follow up within the same case using a further camt.110.

Delivery runs through the Case Orchestrator, the E&I component of Swift’s Case Management service. It routes request and response directly to the institution concerned instead of passing them from bank to bank along the payment chain. The second component of Case Management, the Stop and Recall process, covers payment cancellations and works with camt.056 and camt.029.

Usage

Swift CBPR+ and Case Management

In cross-border payments camt.111 is an integral part of the CBPR+ roadmap. A different timeline applies to the response than to the request:

November 2026 (SR 2026): only the receipt of camt.110 is mandatory at this stage. Institutions that have not yet migrated can respond during this phase via in-flow translation – the request is delivered as an MT 199 with the message embedded, and the answer is translated back accordingly. The translation is free of charge and can be switched off so that the investigation continues bilaterally.
November 2027 (SR 2027): camt.110 and camt.111 must be sent and received through Case Management. In-flow translation ends, MT messages of categories n95 and n96 are removed from the network, and free-format MT n99 is discontinued for E&I purposes. From that point camt.111 is the binding response message.

In mapping terms camt.111 takes the place of the former MT 196 (answers), while camt.110 replaces the MT 195 (queries). Transport is via FIN and FINplus.

Note that migration to camt.110 and camt.111 is foreseen only through Case Management. Migrating to ISO 20022 for payment cancellations alone is possible independently, but it does not replace the connection to the Case Orchestrator for investigations.

Fedwire Funds Service

camt.111 is also in use outside Swift CBPR+: in the ISO 20022 format of the Fedwire Funds Service, camt.110 and camt.111 replace most use cases of the former service message SVC 1090. There too it is explicitly foreseen that an institution sends several camt.111 messages in response to one request – for example an acknowledgement of receipt first and the final answer later.

SEPA and instant payments

camt.111 is not part of the European Payments Council rulebooks. It is used neither in the SCT nor in the SCT Inst scheme. Responses to investigations in the SEPA area continue to rely on camt.029 and the R-transactions with their SEPA reason codes. camt.111 is likewise not part of the TARGET – T2 message catalogue.

Relevance for banks and payment service providers

The response side is the more demanding part of the E&I migration, because it touches not only message processing but case handling itself. Every institution that deals with payment enquiries is affected – not only Swift gpi participants.

Status management instead of a single reply. camt.111 requires a statement on the processing state. Institutions that used to close investigations with one free-text answer will have to set and transmit interim states actively.
Case references in the back office. Request and response references must be bound to the case permanently so that follow-up enquiries are matched to the right case automatically.
Structured response content. The benefit of the reform only materialises when the answer sits in the intended fields rather than in a free-text field. In-flow translation produces a technically valid MT 199, but it renders structured content only to a limited extent.
Planning. Since November 2027 also marks the end of coexistence for E&I messages, the ability to respond should be planned together with the remaining ISO 20022 migration work.

Sources for specifications

Back to Glossary