camt.110 ISO 20022 message

Published on

07/09/2026

Updated on

07/09/2026

Reading time

4 min

The camt.110 is the ISO 20022 InvestigationRequest message. It allows a financial institution to raise a structured enquiry about a payment that has already been executed or has failed. Together with its answer message camt.111 InvestigationResponse it replaces the free-format MT communication used so far and forms the core of Swift’s modernisation of Exceptions & Investigations (E&I).

Definition

camt.110 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.110.001.02 (InvestigationRequestV02, last updated in March 2026).

In business terms the message answers the question “What happened to this payment?” or “Please provide additional information on this payment.” It is therefore neither a status report nor a cancellation, but a self-contained investigation request within a case.

Distinction from neighbouring messages

Payment status is reported with pacs.002 and pain.002, not with camt.110.
Recall and cancellation use camt.056 (Cancellation Request) and camt.029 (Resolution of Investigation).
Investigations and case handling use camt.110 and camt.111. The classic enquiry messages camt.027 (Claim Non Receipt) and camt.087 (Request To Modify Payment) are unaffected and remain in use in the SEPA space.

A common source of confusion in day-to-day operations concerns the answer messages: camt.029 resolves a cancellation, camt.111 answers an investigation.

Message structure

camt.110 is deliberately highly structured. Its main building blocks are:

MsgId – technical message reference.
RqstrInvstgtnId / RspndrInvstgtnId – investigation references of the requesting and the responding institution, holding all messages of a case together.
InvstgtnTp / InvstgtnSubTp – type and sub-type of the investigation, expressed as codes instead of free text.
Undrlyg – the underlying payment, either as an initiation (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).
InvestigationReason with Rsn, RsnSubTp and AddtlReqData – reason for the enquiry plus a narrowly scoped field for supplementary information.

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 traceable chain. This is precisely what sets camt.110 apart from previous practice, where investigations travelled as unstructured text inside MT messages and had to be matched manually.

Typical investigation types

Sanctions and compliance queries
Anti-money laundering (AML)
Suspected fraud and financial crime compliance
Queries relating to fund transfer regulations
Miscellaneous cases such as charges, value dating or debit authority

Message dialogue

At Swift, migration to camt.110 and camt.111 is possible only through the Case Management service. It consists of two components: the Case Orchestrator for Exceptions & Investigations and the Stop and Recall process for payment cancellations. The Case Orchestrator delivers the request directly to the institution concerned instead of passing it from bank to bank along the payment chain.

The dialogue is iterative: several camt.110 messages may be sent for the same payment in order to raise different questions or to follow up. Likewise the responding institution may send several camt.111 messages – for example an acknowledgement of receipt first and the final answer later.

Usage

Swift CBPR+ and Case Management

In cross-border payments Swift has significantly upgraded camt.110: the message has moved from an optional component to a mandatory one. Two stages of the CBPR+ roadmap are relevant:

November 2026 (SR 2026): all institutions must be able to receive camt.110 through Case Management. Institutions that have not yet migrated are supported by in-flow translation, which converts the camt.110 into an MT 199 with the message embedded. This translation is free of charge and can be switched off so that the investigation can continue 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.

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

One planning caveat: following market feedback, Swift postponed the obligation to handle payment cancellations through the Stop and Recall process from November 2026 to November 2027. The obligation to receive camt.110 by November 2026 is not affected.

Fedwire Funds Service

camt.110 has also been adopted 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, multiple requests and multiple responses per payment are explicitly supported.

SEPA and instant payments

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

Relevance for banks and payment service providers

The change affects every institution that handles payment enquiries – not only Swift gpi participants. Three practical tasks follow from the receiving obligation from November 2026:

Connection to Case Management. Migration to camt.110 and camt.111 is not foreseen without the Case Orchestrator.
Processing rather than display. In-flow translation produces a technically valid MT 199, but the content of a highly structured camt.110 can only be rendered to a limited extent in free format. Institutions that merely display the translated message forfeit exactly the automation benefit the reform is built on.
Integration with the back office. Investigation references, investigation types and reasons should be carried into the existing case and complaint handling so that cases remain machine-traceable throughout their life cycle.

Since the November 2027 deadline also marks the end of coexistence for E&I messages, implementation should be planned together with the remaining ISO 20022 migration work.

Sources for specifications

Back to Glossary