Cash Management

ResolutionOfInvestigationV09

camtarea

029message

001variant

09version

Cash Management

The answer to a camt.056 or camt.026. Negative answers carry a RejectionReason; positive ones are followed by a pacs.004.

Start with the payment story

Then the technical flows

Schema versions

SWIFT and ISO publish successive XSD revisions of the same business message (e.g. pacs.008.001.08 → .10 → .13; same pattern for camt and pain). Markets pin one via a usage guideline (EPC SEPA, CBPR+, Swiss SPS…) and may add a country suffix (pacs.008.001.08.ch.02) — the Document xmlns must match that XSD.

ISO catalogue (XSD) ↗SWIFT / CBPR+ ↗SWIFT & versioning glossary →

Catalogue entry camt.029.001.09 (variant 001, version 09).

Facts

Root element: RsltnOfInvstgtn
Direction: Bank → bank
Namespace: urn:iso:std:iso:20022:tech:xsd:camt.029.001.09
Variant (flavour): 001
Version: 09

investigationresolutionrecallcamtsct-inst

Elements a validator will insist on

Not the full XSD — the paths whose absence causes the rejections you actually see in production.

RsltnOfInvstgtn/Assgnmt/Id
RsltnOfInvstgtn/Sts/Conf

Usage in flows

ISO 20022 payload· XML

camt.029 resolution (accepted)

Sts/Conf=ACCR — the creditor bank agrees to return the funds. The pacs.004 follows separately; this message moves no money. Switch XML | JSON in the inspector without leaving this sample.

<Agt>

<BICFI>COBADEFFXXX</BICFI>

</FinInstnId>

</Agt>

</Assgnr>

<Agt>

<BICFI>DEMOFRPPXXX</BICFI>

</FinInstnId>

</Agt>

</Assgne>

</Assgnmt>

<Cretr>

<Agt>

<BICFI>COBADEFFXXX</BICFI>

</FinInstnId>

</Agt>

</Cretr>

</RslvdCase>

<Sts>

</Sts>

<CxlStsId>CXLSTS-0000771412</CxlStsId>

</TxInfAndSts>

</CxlDtls>

</RsltnOfInvstgtn>

</Document>

Open in Try editor →

Edit in the XML / JSON tab, then run the check.