Answers a camt.110 investigation through Swift Case Management with structured status, evidence, and links to the original payment and case.
DIRECTION: Sent through the Case Orchestrator by the institution answering or forwarding the investigation response.
Version + profile: camt.111 is a message-family identifier, not a complete version. The numeric .001.xx definition and field rules depend on the scheme, service, usage guideline, and implementation version named in each context; sample namespaces show only the illustrated version.
EVIDENCE AT ARM'S REACH
Start with the exact message version, then apply the scheme or network profile that governs your implementation.
An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.
Choose the exact message definition in the official catalogue. The base XSD checks XML structure; it does not prove compliance with a scheme profile.
The network profile that restricts how ISO 20022 payment and reporting messages are used for cross-border traffic.
Adds the November 2026 validation and structured-address changes; implement against the final SR2026 usage guidelines.
Final usage guidelines are published through MyStandards; the public release page gives the implementation timeline.
Open version sourceFedwire message versions, usage guidelines, implementation guidance, testing material, and the controlled route to proprietary schemas.
A fictional structured answer confirming that an investigated payment was credited. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:c322c0c4Customer and FI cancellation, resolution, return, reversal, and structured investigation messages.
crc32:f4772381Field correspondence, transformation treatment, and data-loss notes for Legacy answer compared with a structured investigation response.
crc32:efa3234eField correspondence, transformation treatment, and data-loss notes for Free-format category-1 answer compared with a structured investigation response.
crc32:f2fa44acField correspondence, transformation treatment, and data-loss notes for Category 2 query answer compared with a structured Case Management investigation response.
crc32:8d3c9dc6Field correspondence, transformation treatment, and data-loss notes for Residual Category 2 free-format answer compared with a structured investigation response.
crc32:59866077Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:8d2c6383Positive and negative test cases across validation, rejection, return, recall, reversal, investigation, reconciliation, migration, instant payments, and screening.
crc32:98c48cc7Verified profile constraints with versioned evidence and explicit operating conditions.
crc32:6f8b5902Positive and negative lifecycle tests linked to verified profile rules.
crc32:3b72999aDiscovery, controls, testing and operational-readiness checks for the profile.
crc32:d31e7e73Outcome-focused profile acceptance criteria with honest release gates.
crc32:0bf84f8fVersion, transformation, cutover and reconciliation controls.
crc32:e22fb314Evidence that must be obtained from the owner before production readiness can be claimed.
crc32:3955f552Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.
crc32:9d2559edGenerated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.
crc32:b811f27bCurated conceptual subset for the Case Management investigation response. The full message supports richer response, status, routing, and underlying-payment information; consult the current ISO definition and Swift usage guideline.
| FIELD | NAME | PRESENCE | WHAT IT MEANS |
|---|---|---|---|
Assgnmt/Id | Assignment identification | MANDATORY | Reference for the response assignment. |
Case/Id | Case identification | MANDATORY | Reference linking the response to the open case. |
OrgnlAssgnmt/Id | Original assignment identification | MANDATORY | Echoes the request assignment being answered. |
Undrlyg/OrgnlUETR | Original UETR | CONDITIONAL | Network reference of the payment under investigation. |
InvstgtnSts | Investigation status | MANDATORY | Whether the case is answered, pending, rejected, or otherwise advanced. |
Rspn | Structured response | MANDATORY | Answer and evidence supplied for the requested information. |
NxtActn | Next action | OPTIONAL | What the requester or another party is expected to do next. |
The whole camt.111 laid out as a parent-child tree: every field in its nesting, with a sample value and what it means. Expand a branch to drill in. Values are fictional (SYNTHETIC / TRAINING ONLY); this is a curated practitioner view, not the full schema.
Document—The root of an ISO 20022 message — the business payload, which a Business Application Header (head.001) accompanies as a separate document.InvstgtnRspn—Assgnmt—Assignment — the envelope of a camt case: who assigns the case to whom, and when.IdchoiceDEMO-CAMT111-001MandatoryReference for the response assignment.CreDtTm2026-07-18T10:42:00ZMandatoryCreation date and time — when this message was created (a UTC timestamp), separate from when the payment is executed.2026-07-12T09:01:00ZCase—IdchoiceDEMO-INVESTIGATION-001MandatoryReference linking the response to the open case.OrgnlAssgnmt—IdchoiceDEMO-CAMT110-001MandatoryEchoes the request assignment being answered.Undrlyg—Underlying — the original transaction the case is about.OrgnlUETR6f9619ff-8b86-4e9f-a6dd-2cce35e4b321ConditionalNetwork reference of the payment under investigation.InvstgtnSts—MandatoryWhether the case is answered, pending, rejected, or otherwise advanced.CdCOMPCode — a value taken from a defined code list.Rspn—MandatoryAnswer and evidence supplied for the requested information.AddtlInfBeneficiary account credited on 2026-07-18.Additional Information — free-text detail supplementing a reason or status code.NxtActn—OptionalWhat the requester or another party is expected to do next.CdCLSDCode — a value taken from a defined code list.ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pain/pacs/camt message-definition elements
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · cross-border agent chain and structured-data usage
Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.
Swift Standards MT (annual standards releases) ↗ — Swift · FIN block structure
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: One-line plain-language descriptions of the commonly-populated elements — a practitioner view, not the authoritative ISO 20022 / MT schema, which defines many more optional elements.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · camt.111 InvestigationResponse message definition
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
ISO 20022 Standards (Swift ISO 20022 adoption programme) ↗ — Swift · Exceptions and Investigations transformation and Case Management
Do not generalise the payment-instruction deadline to every FIN message. Swift publishes differentiated NAK, contingency-conversion, reporting, initiation and exceptions-and-investigations treatment.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: Field paths are a curated conceptual view of a versioned Case Management message; consult the current usage guideline for implementation.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.
Loading the discussion…