GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX

ANNOTATED SAMPLE

camt.111 investigation response

A fictional structured answer confirming that an investigated payment was credited.

Contributor Shubham Mathure19 July 2026

Illustrative, non-production example. Values are fictional and the message is not validated for any specific network, scheme, or implementation guide.

EVIDENCE AT ARM'S REACH

DOWNLOAD AND GOVERNING SOURCES

Download the canonical fictional sample, then open the exact official definition and profile needed for implementation testing.

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.

XSD + definitionBase ISO 20022current

ISO 20022 message definitions and XSDs

Choose the exact message definition in the official catalogue. The base XSD checks XML structure; it does not prove compliance with a scheme profile.

Owner: ISO 20022 Registration Authority
Checked: 2026-07-12
Access: Official page · Public official catalogue; select the required message version before downloading.

OPEN OFFICIAL SOURCE

Usage guidelineCBPR+current

CBPR+ usage guidelines

The network profile that restricts how ISO 20022 payment and reporting messages are used for cross-border traffic.

Owner: Swift (CBPR+ working group)
Version: Standards Release 2025
Checked: 2026-07-19
Access: Login required · Full message-level guidelines require the relevant Swift MyStandards access.

VERSION TRACK

upcomingStandards Release 2026
Published
2026-03-20
Effective
2026-11-14
Supersedes
Standards Release 2025
Access
Login required
Checked
2026-07-19
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 source

OPEN OFFICIAL SOURCE

Usage guidelineFedwirecurrent

Fedwire Funds Service ISO 20022 implementation and technical documents

Fedwire message versions, usage guidelines, implementation guidance, testing material, and the controlled route to proprietary schemas.

Owner: Federal Reserve Financial Services
Checked: 2026-07-19
Access: Restricted access · Public FAQ and implementation guidance; proprietary XSDs require an eligible authorised contact and private MyStandards access.

OPEN OFFICIAL SOURCE

Teaching sampleScheme-neutral teachingcurrent

camt.111 investigation response — raw XML

A fictional structured answer confirming that an investigated payment was credited. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.

Owner: Payments Signal
Version: camt.111.001.03
Checked: 2026-07-19
Integrity: crc32:c322c0c4
Access: Payments Signal download · Original fictional teaching sample; no login required.

Lifecycle packScheme-neutral teachingcurrent

MX cancellation, return, reversal, and investigation lifecycle — ZIP pack

Customer and FI cancellation, resolution, return, reversal, and structured investigation messages.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:f4772381
Access: Payments Signal download · Original fictional teaching pack; no login required.

MappingCBPR+current

MT196 → camt.111 implementation mapping

Field correspondence, transformation treatment, and data-loss notes for Legacy answer compared with a structured investigation response.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:efa3234e
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

MappingCBPR+current

MT199 answer → camt.111 implementation mapping

Field correspondence, transformation treatment, and data-loss notes for Free-format category-1 answer compared with a structured investigation response.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:f2fa44ac
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

MappingCBPR+current

MT296 query answer → camt.111 implementation mapping

Field correspondence, transformation treatment, and data-loss notes for Category 2 query answer compared with a structured Case Management investigation response.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:8d3c9dc6
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

MappingCBPR+current

MT299 answer → camt.111 implementation mapping

Field correspondence, transformation treatment, and data-loss notes for Residual Category 2 free-format answer compared with a structured investigation response.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:59866077
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

Field matrixBase ISO 20022current

camt.111 field matrix

Curated field requirements, contexts, operational meaning, and implementation cautions.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:8d2c6383
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

Test packScheme-neutral teachingcurrent

Payment lifecycle test cases

Positive and negative test cases across validation, rejection, return, recall, reversal, investigation, reconciliation, migration, instant payments, and screening.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:98c48cc7
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

Field matrixFedwirecurrent

Fedwire Funds Service implementation pack field and process matrix

Verified profile constraints with versioned evidence and explicit operating conditions.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:6f8b5902
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

Test packFedwirecurrent

Fedwire Funds Service implementation pack test cases

Positive and negative lifecycle tests linked to verified profile rules.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:3b72999a
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

BA checklistFedwirecurrent

Fedwire Funds Service implementation pack BA checklist

Discovery, controls, testing and operational-readiness checks for the profile.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:d31e7e73
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

Acceptance criteriaFedwirecurrent

Fedwire Funds Service implementation pack acceptance criteria

Outcome-focused profile acceptance criteria with honest release gates.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:0bf84f8f
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

Migration notesFedwirecurrent

Fedwire Funds Service implementation pack migration notes

Version, transformation, cutover and reconciliation controls.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:e22fb314
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

Coverage gapsFedwirecurrent

Fedwire Funds Service implementation pack restricted and release-specific gaps

Evidence that must be obtained from the owner before production readiness can be claimed.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:3955f552
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

Profile packCBPR+current

CBPR+ implementation pack

Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:9d2559ed
Access: Payments Signal download · Original generated teaching pack; no login required.

Profile packFedwirecurrent

Fedwire Funds Service implementation pack

Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:b811f27b
Access: Payments Signal download · Original generated teaching pack; no login required.

 1<?xml version="1.0" encoding="UTF-8"?>
 2<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.111.001.03">
 3  <InvstgtnRspn>
 4
 5
 6
 7    <Undrlyg><OrgnlUETR>6f9619ff-8b86-4e9f-a6dd-2cce35e4b321</OrgnlUETR></Undrlyg>
 8
 9
10    <NxtActn><Cd>CLSD</Cd></NxtActn>
11  </InvstgtnRspn>
12</Document>

EVERY ANNOTATED FIELD

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.

FULL camt.111 REFERENCE →

COMMUNITY SIGNAL

Discuss this learning page

Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.

NEXT QUESTION REVIEWMonday, 27 Jul, 8:00 amMonday answer runs use source-supported educational material. Some questions may need owner review.

Public discussion

LOADING

Loading the discussion…