ResolutionOfInvestigationV12

camt.029.001.12

Scope The ResolutionOfInvestigation 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.

• the corrective action undertaken by the case assignee;
• information on the return where applicable. Usage The ResolutionOfInvestigation message is used by the case assignee to inform a case creator or case assigner about the resolution of a:
• request to cancel payment case;
• request to modify payment case;
• unable to apply case;
• claim non receipt case. The ResolutionOfInvestigation 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. The ResolutionOfInvestigation message provides:
• the final outcome of the case, whether positive or negative;
• optionally, the details of the corrective action undertaken by the case assignee and the information of the return. Whenever a payment instruction has been generated to solve the case under investigation following a claim non receipt or an unable to apply, the optional CorrectionTransaction component present in the message must be completed. Whenever the action of modifying or cancelling a payment results in funds being returned or reversed, an investigating agent may provide the details in the resolution related investigation component, to identify the return or reversal transaction. These details will facilitate the account reconciliations at the initiating bank and the intermediaries. It must be stressed that the return or reversal of funds is outside the scope of this Exceptions and Investigation service. The features given here is only meant to transmit the information of return or reversal when it is available through the resolution of the case. The ResolutionOfInvestigation message must:
• be forwarded by all subsequent case assignee(s) until it reaches the case creator;
• not be used in place of a RejectCaseAssignment or CaseStatusReport or NotificationOfCaseAssignment message. Take note of an exceptional rule that allows the use of ResolutionOfInvestigation in lieu of a CaseStatusReport. CaseStatusReport is a response-message to a CaseStatusReportRequest. The latter which is sent when the assigner has reached its own time-out threshold to receive a response. 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 CaseStatusReport when then followed immediately by a ResolutionOfInvestigation. It is therefore quite acceptable for the investigating agent, the assignee, to skip the Case Status Report and send the ResolutionOfInvestigation message directly. The ResolutionOfInvestigation message should be the sole message to respond to a cancellation request. Details of the underlying transactions and the related statuses for which the cancellation request has been issued may be provided in the CancellationDetails component.

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
%% ResolutionOfInvestigationV12 recursion level 0 with max 0
ResolutionOfInvestigationV12 *-- "1..1" CaseAssignment5 : Assignment
ResolutionOfInvestigationV12 *-- "0..1" Case5 : ResolvedCase
ResolutionOfInvestigationV12 *-- "1..1" IInvestigationStatus5Choice : Status
ResolutionOfInvestigationV12 *-- "0..1" UnderlyingTransaction31 : CancellationDetails
ResolutionOfInvestigationV12 *-- "0..1" PaymentTransaction147 : ModificationDetails
ResolutionOfInvestigationV12 *-- "0..1" IClaimNonReceipt2Choice : ClaimNonReceiptDetails
ResolutionOfInvestigationV12 *-- "0..1" StatementResolutionEntry4 : StatementDetails
ResolutionOfInvestigationV12 *-- "0..1" ICorrectiveTransaction5Choice : CorrectionTransaction
ResolutionOfInvestigationV12 *-- "0..1" ResolutionData4 : ResolutionRelatedInformation
ResolutionOfInvestigationV12 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

Assignment building block

Identifies the assignment of an investigation case from an assigner to an assignee. Usage: 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. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CaseAssignment5 recursion level 0 with max 1
class CaseAssignment5{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
CaseAssignment5 *-- "1..1" IParty40Choice : Assigner
CaseAssignment5 *-- "1..1" IParty40Choice : Assignee
%% IParty40Choice recursion level 1 with max 1
%% IParty40Choice recursion level 1 with max 1
  

CaseAssignment5 members

ResolvedCase building block

Identifies a resolved case. Provides further details to identify an investigation case. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Case5 recursion level 0 with max 1
class Case5{
    Identification IsoMax35Text
    ReopenCaseIndication IsoYesNoIndicator
}
Case5 *-- "1..1" IParty40Choice : Creator
%% IParty40Choice recursion level 1 with max 1
  

Case5 members

Status building block

Indicates the status of the investigation. Specifies the status of an investigation case. For comparison, see the ISO20022 official specification

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

InvestigationStatus5Choice members

CancellationDetails building block

Specifies the details of the underlying transactions being cancelled. Identifies the underlying (group of) transaction(s) to which the resolution of investigation applies. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% UnderlyingTransaction31 recursion level 0 with max 1
UnderlyingTransaction31 *-- "0..1" OriginalGroupHeader14 : OriginalGroupInformationAndStatus
UnderlyingTransaction31 *-- "0..0" OriginalPaymentInstruction43 : OriginalPaymentInformationAndStatus
UnderlyingTransaction31 *-- "0..0" PaymentTransaction148 : TransactionInformationAndStatus
%% OriginalGroupHeader14 recursion level 1 with max 1
class OriginalGroupHeader14{
    OriginalGroupCancellationIdentification IsoMax35Text
    OriginalMessageIdentification IsoMax35Text
    OriginalMessageNameIdentification IsoMax35Text
    OriginalCreationDateTime IsoISODateTime
    OriginalNumberOfTransactions IsoMax15NumericText
    OriginalControlSum IsoDecimalNumber
    GroupCancellationStatus GroupCancellationStatus1Code
}
OriginalGroupHeader14 *-- "0..1" Case5 : ResolvedCase
OriginalGroupHeader14 *-- "0..0" CancellationStatusReason4 : CancellationStatusReasonInformation
OriginalGroupHeader14 *-- "0..0" NumberOfTransactionsPerStatus1 : NumberOfTransactionsPerCancellationStatus
%% OriginalPaymentInstruction43 recursion level 1 with max 1
class OriginalPaymentInstruction43{
    OriginalPaymentInformationCancellationIdentification IsoMax35Text
    OriginalPaymentInformationIdentification IsoMax35Text
    OriginalNumberOfTransactions IsoMax15NumericText
    OriginalControlSum IsoDecimalNumber
    PaymentInformationCancellationStatus GroupCancellationStatus1Code
}
OriginalPaymentInstruction43 *-- "0..1" Case5 : ResolvedCase
OriginalPaymentInstruction43 *-- "0..1" OriginalGroupInformation29 : OriginalGroupInformation
OriginalPaymentInstruction43 *-- "0..0" CancellationStatusReason4 : CancellationStatusReasonInformation
OriginalPaymentInstruction43 *-- "0..0" NumberOfCancellationsPerStatus1 : NumberOfTransactionsPerCancellationStatus
OriginalPaymentInstruction43 *-- "0..0" PaymentTransaction139 : TransactionInformationAndStatus
%% PaymentTransaction148 recursion level 1 with max 1
class PaymentTransaction148{
    CancellationStatusIdentification IsoMax35Text
    OriginalInstructionIdentification IsoMax35Text
    OriginalEndToEndIdentification IsoMax35Text
    OriginalTransactionIdentification IsoMax35Text
    OriginalClearingSystemReference IsoMax35Text
    OriginalUETR IsoUUIDv4Identifier
    TransactionCancellationStatus CancellationIndividualStatus1Code
    OriginalInterbankSettlementAmount IsoActiveOrHistoricCurrencyAndAmount
    OriginalInterbankSettlementDate IsoISODate
}
PaymentTransaction148 *-- "0..1" Case5 : ResolvedCase
PaymentTransaction148 *-- "0..1" OriginalGroupInformation29 : OriginalGroupInformation
PaymentTransaction148 *-- "0..0" CancellationStatusReason4 : CancellationStatusReasonInformation
PaymentTransaction148 *-- "0..1" ResolutionData4 : ResolutionRelatedInformation
PaymentTransaction148 *-- "0..1" IParty40Choice : Assigner
PaymentTransaction148 *-- "0..1" IParty40Choice : Assignee
PaymentTransaction148 *-- "0..1" OriginalTransactionReference35 : OriginalTransactionReference
  

UnderlyingTransaction31 members

ModificationDetails building block

Specifies the details of the underlying transaction being modified. Provides further details on the reference and status on the original transactions, included in the original instruction, to which the cancellation request message applies. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PaymentTransaction147 recursion level 0 with max 1
class PaymentTransaction147{
    ModificationStatusIdentification IsoMax35Text
    OriginalPaymentInformationIdentification IsoMax35Text
    OriginalInstructionIdentification IsoMax35Text
    OriginalEndToEndIdentification IsoMax35Text
    OriginalTransactionIdentification IsoMax35Text
    OriginalClearingSystemReference IsoMax35Text
    OriginalUETR IsoUUIDv4Identifier
    OriginalInterbankSettlementAmount IsoActiveOrHistoricCurrencyAndAmount
    OriginalInterbankSettlementDate IsoISODate
}
PaymentTransaction147 *-- "0..1" Case5 : ResolvedCase
PaymentTransaction147 *-- "1..1" OriginalGroupInformation29 : OriginalGroupInformation
PaymentTransaction147 *-- "0..0" ModificationStatusReason2 : ModificationStatusReasonInformation
PaymentTransaction147 *-- "0..1" ResolutionData4 : ResolutionRelatedInformation
PaymentTransaction147 *-- "0..1" IParty40Choice : Assigner
PaymentTransaction147 *-- "0..1" IParty40Choice : Assignee
PaymentTransaction147 *-- "0..1" OriginalTransactionReference35 : OriginalTransactionReference
%% Case5 recursion level 1 with max 1
class Case5{
    Identification IsoMax35Text
    ReopenCaseIndication IsoYesNoIndicator
}
Case5 *-- "1..1" IParty40Choice : Creator
%% OriginalGroupInformation29 recursion level 1 with max 1
class OriginalGroupInformation29{
    OriginalMessageIdentification IsoMax35Text
    OriginalMessageNameIdentification IsoMax35Text
    OriginalCreationDateTime IsoISODateTime
}
%% ModificationStatusReason2 recursion level 1 with max 1
class ModificationStatusReason2{
    AdditionalInformation IsoMax105Text
}
ModificationStatusReason2 *-- "0..1" PartyIdentification135 : Originator
ModificationStatusReason2 *-- "0..1" IModificationStatusReason1Choice : Reason
%% ResolutionData4 recursion level 1 with max 1
class ResolutionData4{
    EndToEndIdentification IsoMax35Text
    TransactionIdentification IsoMax35Text
    UETR IsoUUIDv4Identifier
    InterbankSettlementAmount IsoActiveOrHistoricCurrencyAndAmount
    InterbankSettlementDate IsoISODate
    ClearingChannel ClearingChannel2Code
}
ResolutionData4 *-- "0..1" Compensation4 : Compensation
ResolutionData4 *-- "0..0" Charges13 : ChargesInformation
%% IParty40Choice recursion level 1 with max 1
%% IParty40Choice recursion level 1 with max 1
%% OriginalTransactionReference35 recursion level 1 with max 1
class OriginalTransactionReference35{
    InterbankSettlementAmount IsoActiveOrHistoricCurrencyAndAmount
    InterbankSettlementDate IsoISODate
    RequestedCollectionDate IsoISODate
    PaymentMethod PaymentMethod4Code
}
OriginalTransactionReference35 *-- "0..1" IAmountType4Choice : Amount
OriginalTransactionReference35 *-- "0..1" IDateAndDateTime2Choice : RequestedExecutionDate
OriginalTransactionReference35 *-- "0..1" PartyIdentification135 : CreditorSchemeIdentification
OriginalTransactionReference35 *-- "0..1" SettlementInstruction11 : SettlementInformation
OriginalTransactionReference35 *-- "0..1" PaymentTypeInformation27 : PaymentTypeInformation
OriginalTransactionReference35 *-- "0..1" IMandateRelatedData2Choice : MandateRelatedInformation
OriginalTransactionReference35 *-- "0..1" RemittanceInformation21 : RemittanceInformation
OriginalTransactionReference35 *-- "0..1" IParty40Choice : UltimateDebtor
OriginalTransactionReference35 *-- "0..1" IParty40Choice : Debtor
OriginalTransactionReference35 *-- "0..1" CashAccount40 : DebtorAccount
OriginalTransactionReference35 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : DebtorAgent
OriginalTransactionReference35 *-- "0..1" CashAccount40 : DebtorAgentAccount
OriginalTransactionReference35 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : CreditorAgent
OriginalTransactionReference35 *-- "0..1" CashAccount40 : CreditorAgentAccount
OriginalTransactionReference35 *-- "0..1" IParty40Choice : Creditor
OriginalTransactionReference35 *-- "0..1" CashAccount40 : CreditorAccount
OriginalTransactionReference35 *-- "0..1" IParty40Choice : UltimateCreditor
OriginalTransactionReference35 *-- "0..1" IPurpose2Choice : Purpose
  

PaymentTransaction147 members

ClaimNonReceiptDetails building block

Specifies the details of the underlying transaction for which a claim non receipt has been initiated. Specifies whether the claim non receipt is accepted or rejected. For comparison, see the ISO20022 official specification

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

ClaimNonReceipt2Choice members

StatementDetails building block

Details on the underlying statement entry. Provides further details on the statement entry for the resolution of the investigation. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% StatementResolutionEntry4 recursion level 0 with max 1
class StatementResolutionEntry4{
    OriginalStatementIdentification IsoMax35Text
    UETR IsoUUIDv4Identifier
    AccountServicerReference IsoMax35Text
    CorrectedAmount IsoActiveOrHistoricCurrencyAndAmount
}
StatementResolutionEntry4 *-- "0..1" OriginalGroupInformation29 : OriginalGroupInformation
StatementResolutionEntry4 *-- "0..0" Charges6 : Charges
StatementResolutionEntry4 *-- "0..1" IPurpose2Choice : Purpose
%% OriginalGroupInformation29 recursion level 1 with max 1
class OriginalGroupInformation29{
    OriginalMessageIdentification IsoMax35Text
    OriginalMessageNameIdentification IsoMax35Text
    OriginalCreationDateTime IsoISODateTime
}
%% Charges6 recursion level 1 with max 1
class Charges6{
    TotalChargesAndTaxAmount IsoActiveOrHistoricCurrencyAndAmount
}
Charges6 *-- "0..0" ChargesRecord3 : Record
%% IPurpose2Choice recursion level 1 with max 1
  

StatementResolutionEntry4 members

CorrectionTransaction building block

References a transaction initiated to fix the case under investigation. Specifies the corrective transaction on which the investigation is processed. For comparison, see the ISO20022 official specification

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

CorrectiveTransaction5Choice members

ResolutionRelatedInformation building block

Reference to fix the case under investigation as part of the resolution. Specifies additional information as expected by the party that the investigation performs the expected actions for its resolution. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ResolutionData4 recursion level 0 with max 1
class ResolutionData4{
    EndToEndIdentification IsoMax35Text
    TransactionIdentification IsoMax35Text
    UETR IsoUUIDv4Identifier
    InterbankSettlementAmount IsoActiveOrHistoricCurrencyAndAmount
    InterbankSettlementDate IsoISODate
    ClearingChannel ClearingChannel2Code
}
ResolutionData4 *-- "0..1" Compensation4 : Compensation
ResolutionData4 *-- "0..0" Charges13 : ChargesInformation
%% Compensation4 recursion level 1 with max 1
class Compensation4{
    Amount IsoActiveCurrencyAndAmount
}
Compensation4 *-- "1..1" BranchAndFinancialInstitutionIdentification6 : DebtorAgent
Compensation4 *-- "0..1" CashAccount40 : DebtorAgentAccount
Compensation4 *-- "1..1" BranchAndFinancialInstitutionIdentification6 : CreditorAgent
Compensation4 *-- "0..1" CashAccount40 : CreditorAgentAccount
Compensation4 *-- "1..1" ICompensationReason1Choice : Reason
%% Charges13 recursion level 1 with max 1
class Charges13{
    Amount IsoActiveOrHistoricCurrencyAndAmount
}
Charges13 *-- "1..1" BranchAndFinancialInstitutionIdentification6 : Agent
Charges13 *-- "0..1" CashAccount40 : AgentAccount
Charges13 *-- "0..1" IChargeType3Choice : Type
  

ResolutionData4 members

SupplementaryData building block

Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
  

SupplementaryData1 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    ResolutionOfInvestigationV12 --|> IOuterRecord : Implements
    ResolutionOfInvestigationV12Document --|> IOuterDocument~ResolutionOfInvestigationV12~ : Implements
    class IOuterDocument~ResolutionOfInvestigationV12~ {
        ResolutionOfInvestigationV12 Message
     }
  

Document wrapper for serialization

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

classDiagram
    ResolutionOfInvestigationV12Document *-- ResolutionOfInvestigationV12 : 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.12">
    <RsltnOfInvstgtn>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <RslvdCase>
            <!-- ResolvedCase inner content -->
        </RslvdCase>
        <Sts>
            <!-- Status inner content -->
        </Sts>
        <CxlDtls>
            <!-- CancellationDetails inner content -->
        </CxlDtls>
        <ModDtls>
            <!-- ModificationDetails inner content -->
        </ModDtls>
        <ClmNonRctDtls>
            <!-- ClaimNonReceiptDetails inner content -->
        </ClmNonRctDtls>
        <StmtDtls>
            <!-- StatementDetails inner content -->
        </StmtDtls>
        <CrrctnTx>
            <!-- CorrectionTransaction inner content -->
        </CrrctnTx>
        <RsltnRltdInf>
            <!-- ResolutionRelatedInformation inner content -->
        </RsltnRltdInf>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </RsltnOfInvstgtn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_msyIgRlaEe2Do_UtrNmb2g"
  previousVersion="_IBkAo9cBEeq_l4BJLVUF2Q"
  name="ResolutionOfInvestigationV12"
  definition="Scope&#xD;&#xA;The ResolutionOfInvestigation 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 ResolutionOfInvestigation 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 ResolutionOfInvestigation 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 ResolutionOfInvestigation 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 following a claim non receipt or an unable to apply, 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 or reversed, an investigating agent may provide the details in the resolution related investigation component, to identify the return or reversal transaction. These details will facilitate the account reconciliations at the initiating bank and the intermediaries. It must be stressed that the return or reversal of funds is outside the scope of this Exceptions and Investigation service. The features given here is only meant to transmit the information of return or reversal when it is available through the resolution of the case.&#xD;&#xA;The ResolutionOfInvestigation 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 RejectCaseAssignment or CaseStatusReport or NotificationOfCaseAssignment message.&#xD;&#xA;Take note of an exceptional rule that allows the use of ResolutionOfInvestigation in lieu of a CaseStatusReport. CaseStatusReport is a response-message to a CaseStatusReportRequest. The latter which is sent when the assigner has reached its own time-out threshold to receive a response. 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 CaseStatusReport when then followed immediately by a ResolutionOfInvestigation. It is therefore quite acceptable for the investigating agent, the assignee, to skip the Case Status Report and send the ResolutionOfInvestigation message directly.&#xD;&#xA;The ResolutionOfInvestigation message should be the sole message to respond to a cancellation request. Details of the underlying transactions and the related statuses for which the cancellation request has been issued may be provided in the CancellationDetails component."
  registrationStatus="Registered"
  messageSet="_moz48_2VEeGjgKzdN0DbWA"
  xmlTag="RsltnOfInvstgtn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_msyIgxlaEe2Do_UtrNmb2g"
    previousVersion="_IBkApdcBEeq_l4BJLVUF2Q"
    name="PartialOrRejectedCancellationRule"
    definition="If Status/Confirmation is present and equal to PECR or RJCR then CancellationDetails must be present."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;&lt;ComplexRule xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[*]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/Status/Confirmation&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;WithInList&quot;&gt;&lt;leftOperand&gt;/Status/Confirmation&lt;/leftOperand&gt;&lt;rightOperand&gt;InvestigationExecutionConfirmation4Code&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;&#xA;" />
  <constraint
    xmi:id="_msyIhRlaEe2Do_UtrNmb2g"
    previousVersion="_IBkAp9cBEeq_l4BJLVUF2Q"
    name="MessageOrGroupResolvedCaseRule"
    definition="ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus, OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;&lt;ComplexRule xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[1]/OriginalGroupInformationAndStatus/ResolvedCase&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/ResolvedCase&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[1]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[1]/OriginalGroupInformationAndStatus[1]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;&#xA;" />
  <constraint
    xmi:id="_msyIhxlaEe2Do_UtrNmb2g"
    previousVersion="_IBkAqdcBEeq_l4BJLVUF2Q"
    name="MessageOrPaymentInformationResolvedCaseRule"
    definition="ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus, OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;&lt;ComplexRule xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[*]/OriginalPaymentInformationAndStatus[*]/ResolvedCase&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/ResolvedCase&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[1]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[1]/OriginalPaymentInformationAndStatus[1]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;&#xA;" />
  <constraint
    xmi:id="_msyIiRlaEe2Do_UtrNmb2g"
    previousVersion="_IBkAq9cBEeq_l4BJLVUF2Q"
    name="MessageOrInitiationTransactionResolvedCaseRule"
    definition="ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus, OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;&lt;ComplexRule xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[*]/OriginalPaymentInformationAndStatus[*]/TransactionInformationAndStatus[*]/ResolvedCase&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/ResolvedCase&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[1]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[1]/OriginalPaymentInformationAndStatus[*]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[1]/OriginalPaymentInformationAndStatus[*]/TransactionInformationAndStatus[*]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;&#xA;" />
  <constraint
    xmi:id="_msyIixlaEe2Do_UtrNmb2g"
    previousVersion="_IBkArdcBEeq_l4BJLVUF2Q"
    name="MessageOrInterbankTransactionResolvedCaseRule"
    definition="ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus, OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition&gt;&lt;ComplexRule xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Absence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[*]/TransactionInformationAndStatus[*]/ResolvedCase&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/ResolvedCase&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[1]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/CancellationDetails[1]/TransactionInformationAndStatus[*]&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;" />
  <messageBuildingBlock
    xmi:id="_msyIlRlaEe2Do_UtrNmb2g"
    previousVersion="_IBkAtdcBEeq_l4BJLVUF2Q"
    name="Assignment"
    definition="Identifies the assignment of an investigation case from an assigner to an assignee.&#xD;&#xA;Usage: 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="_BzPdIW49EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_msyIlxlaEe2Do_UtrNmb2g"
    previousVersion="_IBkngdcBEeq_l4BJLVUF2Q"
    name="ResolvedCase"
    definition="Identifies a resolved case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RslvdCase"
    complexType="_8BF4W248EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_msyImRlaEe2Do_UtrNmb2g"
    previousVersion="_IBkng9cBEeq_l4BJLVUF2Q"
    name="Status"
    definition="Indicates the status of the investigation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Sts"
    complexType="_NIe3H249EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_msyImxlaEe2Do_UtrNmb2g"
    previousVersion="_IBknhdcBEeq_l4BJLVUF2Q"
    name="CancellationDetails"
    definition="Specifies the details of the underlying transactions being cancelled."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="CxlDtls"
    complexType="_MIswYRlbEe2Do_UtrNmb2g" />
  <messageBuildingBlock
    xmi:id="_msyInRlaEe2Do_UtrNmb2g"
    previousVersion="_IBknh9cBEeq_l4BJLVUF2Q"
    name="ModificationDetails"
    definition="Specifies the details of the underlying transaction being modified."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="ModDtls"
    complexType="_LsO20RlbEe2Do_UtrNmb2g" />
  <messageBuildingBlock
    xmi:id="_msyInxlaEe2Do_UtrNmb2g"
    previousVersion="_IBknidcBEeq_l4BJLVUF2Q"
    name="ClaimNonReceiptDetails"
    definition="Specifies the details of the underlying transaction for which a claim non receipt has been initiated."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="ClmNonRctDtls"
    complexType="_EVNOIW4-EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_msyIoRlaEe2Do_UtrNmb2g"
    previousVersion="_IBkni9cBEeq_l4BJLVUF2Q"
    name="StatementDetails"
    definition="Details on the underlying statement entry."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="StmtDtls"
    complexType="_-RLPK249EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_msyIoxlaEe2Do_UtrNmb2g"
    previousVersion="_IBknjdcBEeq_l4BJLVUF2Q"
    name="CorrectionTransaction"
    definition="References a transaction initiated to fix the case under investigation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="CrrctnTx"
    complexType="_tNTsINizEeq5MfBBxQig1Q" />
  <messageBuildingBlock
    xmi:id="_msyIpRlaEe2Do_UtrNmb2g"
    previousVersion="_IBknj9cBEeq_l4BJLVUF2Q"
    name="ResolutionRelatedInformation"
    definition="Reference to fix the case under investigation as part of the resolution."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RsltnRltdInf"
    complexType="_L1v_MRlbEe2Do_UtrNmb2g" />
  <messageBuildingBlock
    xmi:id="_msyIpxlaEe2Do_UtrNmb2g"
    previousVersion="_IBknkdcBEeq_l4BJLVUF2Q"
    name="SupplementaryData"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="029"
    flavour="001"
    version="12" />
</messageDefinition>

ISO Building Blocks

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