MT199 / MT299 ↔ No single equivalent

Business purpose

MT199 (Category 1) and MT299 (Category 2) are free-format messages — an escape hatch for any correspondent-banking communication that did not fit a defined structured message type: investigation queries, cancellation requests, general remarks, gpi tracker notes, ad hoc clarifications.

What does NOT map cleanly

There is no single ISO 20022 message that 'is' the replacement for MT199/MT299 as a category, because ISO 20022 assigns one message per defined business function while MT199/299 accepted free text for any purpose. What replaces a given MT199/299 use depends entirely on what it was being used for: exceptions-and-investigations use routes to camt.110 (InvestigationRequest) / camt.111 (InvestigationResponse) via SWIFT Case Management; residual general/bilateral free-format traffic that is not an E&I case routes to admi.024 (introduced in the November 2025 Standard Release); cancellation-flavored use (overlapping MT192/292 territory) routes to camt.056/camt.029 instead; and gpi tracker update use routes to the trck.001-005 message/API family. A structured camt.110 auto-generated from an embedded, untranslated MT199 narrative via SWIFT's in-flow translation is technically valid XML but does not recover the lost structure — it is a stopgap, not a field mapping.

Migration notes

November 2025: admi.024 introduced for non-E&I bilateral free-format traffic. November 2026: institutions must be able to receive camt.110 with in-flow-translated (embedded) MT199 content — there is no reverse translation back to MT199. November 2027: full mandatory cutover — MT195/295 and MT199/299/999 for enquiry/investigation purposes are to be discontinued industry-wide.