Iso20022

ResolutionOfInvestigation

camt.029.001.01

Scope The Resolution Of Investigation message is sent by a case assignee to a case creator/case assigner. This message is used to inform of the resolution of a case, and optionally provides details about.

Message Construction

Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification

classDiagram
     direction LR
%% ResolutionOfInvestigation recursion level 0 with max 0
ResolutionOfInvestigation *-- "1..1" CaseAssignment : Assignment
ResolutionOfInvestigation *-- "1..1" Case : ResolvedCase
ResolutionOfInvestigation *-- "0..1" IInvestigationStatusChoice : Status
ResolutionOfInvestigation *-- "0..1" PaymentInstructionExtract : CorrectionTransaction

Now, we will zero-in one-by-one on each of these building blocks.

Assignment building block

Note: the Assigner must be the sender of this confirmation and the Assignee must be the receiver. Represents the assignment of a case to a party. Assignment is a step in the overall process of managing a case. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CaseAssignment recursion level 0 with max 1
class CaseAssignment{
    Identification IsoMax35Text
    Assigner IsoAnyBICIdentifier
    Assignee IsoAnyBICIdentifier
    CreationDateTime IsoISODateTime
}

CaseAssignment members

Member name Description Data Type / Multiplicity
Identification Identification of an assignment within a case. IsoMax35Text - Required 1..1
Assigner Party that assigns the case to another party. This is also the sender of the message. IsoAnyBICIdentifier - Required 1..1
Assignee Party that the case is assigned to. This is also the receiver of the message. IsoAnyBICIdentifier - Required 1..1
CreationDateTime Date and time at which the assignment was created. IsoISODateTime - Required 1..1

ResolvedCase building block

Identifies a resolved case. Information identifying a case. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Case recursion level 0 with max 1
class Case{
    Identification IsoMax35Text
    Creator IsoAnyBICIdentifier
    ReopenCaseIndication IsoYesNoIndicator
}

Case members

Member name Description Data Type / Multiplicity
Identification Unique id assigned by the case creator. IsoMax35Text - Required 1..1
Creator Party that created the case. IsoAnyBICIdentifier - Required 1..1
ReopenCaseIndication Set to yes if the case was closed and needs to be re-opened. IsoYesNoIndicator - Optional 0..1

Status building block

Indicates the status of the investigation. Choice between different statuses of an investigation case. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IInvestigationStatusChoice recursion level 0 with max 1

InvestigationStatusChoice members

Member name Description Data Type / Multiplicity

CorrectionTransaction building block

References a transaction intitiated to fix the case under investigation. Details of a payment instruction. The information contained in this component is sufficient to retrieve a payment instruction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PaymentInstructionExtract recursion level 0 with max 1
class PaymentInstructionExtract{
    AssignerInstructionIdentification IsoMax35Text
    AssigneeInstructionIdentification IsoMax35Text
    CurrencyAmount IsoCurrencyAndAmount
    ValueDate IsoISODateTime
}

PaymentInstructionExtract members

Member name Description Data Type / Multiplicity
AssignerInstructionIdentification Identification of the payment instruction (eg, field 20 of an MT 103) when meaningful to the case assigner. IsoMax35Text - Optional 0..1
AssigneeInstructionIdentification Identification of the payment instruction (eg, field 20 of an MT 103) when meaningful to the case assignee. IsoMax35Text - Optional 0..1
CurrencyAmount Amount of the payment. Depending on the context it can be either the amount settled (UnableToApply) or the instructed amount (RequestToCancel, RequestToModify, ClaimNonReceipt). IsoCurrencyAndAmount - Optional 0..1
ValueDate Value date of the payment. IsoISODateTime - Optional 0..1

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the ResolutionOfInvestigation implementation follows a specific implementaiton pattern. First of all, ResolutionOfInvestigation impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ResolutionOfInvestigationDocument implements IOuterDocument. Because ResolutionOfInvestigation implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ResolutionOfInvestigation.

classDiagram
    class IOuterRecord
    ResolutionOfInvestigation --|> IOuterRecord : Implements
    ResolutionOfInvestigationDocument --|> IOuterDocument~ResolutionOfInvestigation~ : Implements
    class IOuterDocument~ResolutionOfInvestigation~ {
        ResolutionOfInvestigation Message
     }

Document wrapper for serialization

The only real purpose ResolutionOfInvestigationDocument serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:camt.029.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using ResolutionOfInvestigation.ToDocument() method. The returned ResolutionOfInvestigationDocument value will serialize correctly according to ISO 20022 standards.

classDiagram
    ResolutionOfInvestigationDocument *-- ResolutionOfInvestigation : Document

Sample of message format

This is an abbreviated version of what the message should look like.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.029.001.01">
    <camt.029.001.01>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <RslvdCase>
            <!-- ResolvedCase inner content -->
        </RslvdCase>
        <Sts>
            <!-- Status inner content -->
        </Sts>
        <CrrctnTx>
            <!-- CorrectionTransaction inner content -->
        </CrrctnTx>
    </camt.029.001.01>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_VIjx1tE_Ed-BzquC8wXy7w_2008786370"
  name="ResolutionOfInvestigation"
  definition="Scope&#xD;&#xA;The Resolution Of Investigation message is sent by a case assignee to a case creator/case assigner.&#xD;&#xA;This message is used to inform of the resolution of a case, and optionally provides details about.&#xD;&#xA;- the corrective action undertaken by the case assignee&#xD;&#xA;- information on the return where applicable&#xD;&#xA;Usage&#xD;&#xA;The Resolution Of Investigation message is used by the case assignee to inform a case creator or case assigner about the resolution of a:&#xD;&#xA;- request to cancel payment case&#xD;&#xA;- request to modify payment case&#xD;&#xA;- unable to apply case&#xD;&#xA;- claim non receipt case&#xD;&#xA;The Resolution Of Investigation message covers one and only one case at a time. If the case assignee needs to communicate about several cases, then several Resolution Of Investigation messages must be sent.&#xD;&#xA;The Resolution Of Investigation message provides:&#xD;&#xA;- the final outcome of the case, whether positive or negative&#xD;&#xA;- optionally, the details of the corrective action undertaken by the case assignee and the information of the return&#xD;&#xA;Whenever a payment instruction has been generated to solve the case under investigation, the optional CorrectionTransaction component present in the message must be completed.&#xD;&#xA;Whenever the action of modifying or cancelling a payment results in funds being returned, an investigating agent may attached some details in this message. These details facilitates the account reconciliations at the initiating bank and the intermediaries. It must be stressed that returning of funds is outside the scope of this Exceptions and Investigation service. The features given here is only meant to transmit the information of returns when it is available.&#xD;&#xA;The Resolution Of Investigation message must&#xD;&#xA;- be forwarded by all subsequent case assignee(s) until it reaches the case creator&#xD;&#xA;- not be used in place of a Reject Case Assignment or Case Status Report or Notification Of Case Assignment message.&#xD;&#xA;Take note of an exceptional rule that allows the use of Resolution Of Investigation in lieu of a Case Status Report. Case Status Report is a response-message to a Case Status Report Request. The latter which is sent when the assigner has waited too long (by his standard) for an answer. However it may happen that when the Request arrives, the investigating agent has just obtained a resolution. In such a situation, it would be redundant to send a Case Status Report when then followed immediately by a Resolution Of Investigation. It is therefore quite acceptable for the investigating agent, the assignee, to skip the Case Status Report and send the Resolution Of Investigation message directly."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlName="camt.029.001.01"
  xmlTag="camt.029.001.01"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_VIjx19E_Ed-BzquC8wXy7w_1748119447"
    name="Assignment"
    definition="Note: the Assigner must be the sender of this confirmation and the Assignee must be the receiver."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Assgnmt"
    complexType="_T9Dpetp-Ed-ak6NoX_4Aeg_588710247" />
  <messageBuildingBlock
    xmi:id="_VIjx2NE_Ed-BzquC8wXy7w_2105521252"
    name="ResolvedCase"
    definition="Identifies a resolved case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RslvdCase"
    complexType="_SpAnotp-Ed-ak6NoX_4Aeg_136183535" />
  <messageBuildingBlock
    xmi:id="_VIjx2dE_Ed-BzquC8wXy7w_921583023"
    name="Status"
    definition="Indicates the status of the investigation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="Sts"
    complexType="_UuYYstp-Ed-ak6NoX_4Aeg_788596093" />
  <messageBuildingBlock
    xmi:id="_VIjx2tE_Ed-BzquC8wXy7w_2123992930"
    name="CorrectionTransaction"
    definition="References a transaction intitiated to fix the case under investigation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="CrrctnTx"
    complexType="_VQgOUtp-Ed-ak6NoX_4Aeg_-769020295" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="029"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.