Opens a structured payment investigation through Swift Case Management, replacing recurring MT195/199-style queries with a message that carries case, original-payment, request, and routing data in labelled elements.
DIRECTION: Sent through the Case Orchestrator by the institution opening or forwarding an investigation to the institution expected to answer.
Version + profile: camt.110 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 request for more information about a payment under investigation. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:d067048aCustomer and FI cancellation, resolution, return, reversal, and structured investigation messages.
crc32:f4772381Field correspondence, transformation treatment, and data-loss notes for Legacy payment query compared with a structured investigation request.
crc32:cf0328edField correspondence, transformation treatment, and data-loss notes for Category 2 query compared with a structured Case Management investigation request.
crc32:c5b42c10Field correspondence, transformation treatment, and data-loss notes for Free-format category-1 query compared with a structured investigation request.
crc32:4f8da59eField correspondence, transformation treatment, and data-loss notes for Residual Category 2 free-format query compared with a structured investigation request.
crc32:13f0a0ecCurated field requirements, contexts, operational meaning, and implementation cautions.
crc32:a55c2d8aPositive 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 request. The ISO message and Swift usage guideline contain more orchestration, party, status, and underlying-payment structure; validate exact paths against the version in force.
| FIELD | NAME | PRESENCE | WHAT IT MEANS |
|---|---|---|---|
Assgnmt/Id | Assignment identification | MANDATORY | Reference for the current case assignment. |
Case/Id | Case identification | MANDATORY | Stable reference for the investigation case. |
Undrlyg/OrgnlGrpInf/OrgnlMsgId | Original message identification | MANDATORY | Identifies the payment message under investigation. |
Undrlyg/OrgnlTxId | Original transaction identification | CONDITIONAL | Identifies the transaction within the original message. |
Undrlyg/OrgnlUETR | Original UETR | CONDITIONAL | End-to-end network reference used to locate the cross-border payment. |
InvstgtnTp | Investigation type | MANDATORY | Structured classification of the question being asked. |
ReqdInf | Requested information | MANDATORY | The specific evidence or clarification the assignee must provide. |
The whole camt.110 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.InvstgtnReq—Assgnmt—Assignment — the envelope of a camt case: who assigns the case to whom, and when.IdchoiceDEMO-CAMT110-001MandatoryReference for the current case assignment.CreDtTm2026-07-18T10:30: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-001MandatoryStable reference for the investigation case.Undrlyg—Underlying — the original transaction the case is about.OrgnlGrpInf—Original Group Information — identifies the original message a return or report refers to.OrgnlMsgIdDEMO-PACS008-001MandatoryIdentifies the payment message under investigation.OrgnlTxIdDEMO-TX-001ConditionalIdentifies the transaction within the original message.OrgnlUETR6f9619ff-8b86-4e9f-a6dd-2cce35e4b321ConditionalEnd-to-end network reference used to locate the cross-border payment.InvstgtnTp—MandatoryStructured classification of the question being asked.CdREQICode — a value taken from a defined code list.ReqdInf—MandatoryThe specific evidence or clarification the assignee must provide.AddtlInfConfirm beneficiary credit status and value date.Additional Information — free-text detail supplementing a reason or status code.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.110 InvestigationRequest 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…