Iso20022

ResolutionOfInvestigationV04

camt.029.001.04

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
%% ResolutionOfInvestigationV04 recursion level 0 with max 0
ResolutionOfInvestigationV04 *-- "1..1" CaseAssignment3 : Assignment
ResolutionOfInvestigationV04 *-- "0..1" Case3 : ResolvedCase
ResolutionOfInvestigationV04 *-- "1..1" IInvestigationStatus3Choice : Status
ResolutionOfInvestigationV04 *-- "0..1" UnderlyingTransaction4 : CancellationDetails
ResolutionOfInvestigationV04 *-- "0..1" StatementResolutionEntry2 : StatementDetails
ResolutionOfInvestigationV04 *-- "0..1" ICorrectiveTransaction1Choice : CorrectionTransaction
ResolutionOfInvestigationV04 *-- "0..1" ResolutionInformation1 : ResolutionRelatedInformation
ResolutionOfInvestigationV04 *-- "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
%% CaseAssignment3 recursion level 0 with max 1
class CaseAssignment3{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
CaseAssignment3 *-- "1..1" IParty12Choice : Assigner
CaseAssignment3 *-- "1..1" IParty12Choice : Assignee
%% IParty12Choice recursion level 1 with max 1
%% IParty12Choice recursion level 1 with max 1

CaseAssignment3 members

Member name Description Data Type / Multiplicity
Identification Uniquely identifies the case assignment. IsoMax35Text - Required 1..1
Assigner Party who assigns the case. Usage: This is also the sender of the message.
Assignee Party to which the case is assigned. Usage: This is also the receiver of the message.
CreationDateTime Date and time at which the assignment was created. IsoISODateTime - Required 1..1

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
%% Case3 recursion level 0 with max 1
class Case3{
    Identification IsoMax35Text
    ReopenCaseIndication IsoYesNoIndicator
}
Case3 *-- "1..1" IParty12Choice : Creator
%% IParty12Choice recursion level 1 with max 1

Case3 members

Member name Description Data Type / Multiplicity
Identification Uniquely identifies the case. IsoMax35Text - Required 1..1
Creator Party that created the investigation case. IParty12Choice - Required 1..1
ReopenCaseIndication Indicates whether or not the case was previously closed and is now re-opened. IsoYesNoIndicator - Optional 0..1

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
%% IInvestigationStatus3Choice recursion level 0 with max 1

InvestigationStatus3Choice members

Member name Description Data Type / Multiplicity

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
%% UnderlyingTransaction4 recursion level 0 with max 1
UnderlyingTransaction4 *-- "0..1" OriginalGroupHeader5 : OriginalGroupInformationAndStatus
UnderlyingTransaction4 *-- "0..0" OriginalPaymentInstruction3 : OriginalPaymentInformationAndStatus
UnderlyingTransaction4 *-- "0..0" PaymentTransaction40 : TransactionInformationAndStatus
%% OriginalGroupHeader5 recursion level 1 with max 1
class OriginalGroupHeader5{
    OriginalGroupCancellationIdentification IsoMax35Text
    OriginalMessageIdentification IsoMax35Text
    OriginalMessageNameIdentification IsoMax35Text
    OriginalCreationDateTime IsoISODateTime
    OriginalNumberOfTransactions IsoMax15NumericText
    OriginalControlSum IsoDecimalNumber
    GroupCancellationStatus GroupCancellationStatus1Code
}
OriginalGroupHeader5 *-- "0..1" Case3 : ResolvedCase
OriginalGroupHeader5 *-- "0..0" CancellationStatusReason2 : CancellationStatusReasonInformation
OriginalGroupHeader5 *-- "0..0" NumberOfTransactionsPerStatus1 : NumberOfTransactionsPerCancellationStatus
%% OriginalPaymentInstruction3 recursion level 1 with max 1
class OriginalPaymentInstruction3{
    OriginalPaymentInformationCancellationIdentification IsoMax35Text
    OriginalPaymentInformationIdentification IsoMax35Text
    OriginalNumberOfTransactions IsoMax15NumericText
    OriginalControlSum IsoDecimalNumber
    PaymentInformationCancellationStatus GroupCancellationStatus1Code
}
OriginalPaymentInstruction3 *-- "0..1" Case3 : ResolvedCase
OriginalPaymentInstruction3 *-- "0..1" OriginalGroupInformation3 : OriginalGroupInformation
OriginalPaymentInstruction3 *-- "0..0" CancellationStatusReason2 : CancellationStatusReasonInformation
OriginalPaymentInstruction3 *-- "0..0" NumberOfCancellationsPerStatus1 : NumberOfTransactionsPerCancellationStatus
OriginalPaymentInstruction3 *-- "0..0" PaymentTransaction39 : TransactionInformationAndStatus
%% PaymentTransaction40 recursion level 1 with max 1
class PaymentTransaction40{
    CancellationStatusIdentification IsoMax35Text
    OriginalInstructionIdentification IsoMax35Text
    OriginalEndToEndIdentification IsoMax35Text
    OriginalTransactionIdentification IsoMax35Text
    OriginalClearingSystemReference IsoMax35Text
    TransactionCancellationStatus CancellationIndividualStatus1Code
    OriginalInterbankSettlementAmount IsoActiveOrHistoricCurrencyAndAmount
    OriginalInterbankSettlementDate IsoISODate
}
PaymentTransaction40 *-- "0..1" Case3 : ResolvedCase
PaymentTransaction40 *-- "0..1" OriginalGroupInformation3 : OriginalGroupInformation
PaymentTransaction40 *-- "0..0" CancellationStatusReason2 : CancellationStatusReasonInformation
PaymentTransaction40 *-- "0..1" ResolutionInformation1 : ResolutionRelatedInformation
PaymentTransaction40 *-- "0..1" IParty12Choice : Assigner
PaymentTransaction40 *-- "0..1" IParty12Choice : Assignee
PaymentTransaction40 *-- "0..1" OriginalTransactionReference16 : OriginalTransactionReference

UnderlyingTransaction4 members

Member name Description Data Type / Multiplicity
OriginalGroupInformationAndStatus Provides information on the original cancellation message, to which the resolution refers. OriginalGroupHeader5 - Optional 0..1
OriginalPaymentInformationAndStatus Provides information on the original (group of) transactions, to which the cancellation status refers. OriginalPaymentInstruction3 - Unknown 0..0
TransactionInformationAndStatus Provides details on the original transactions to which the cancellation request message refers. PaymentTransaction40 - Unknown 0..0

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
%% StatementResolutionEntry2 recursion level 0 with max 1
class StatementResolutionEntry2{
    OriginalStatementIdentification IsoMax35Text
    AccountServicerReference IsoMax35Text
    CorrectedAmount IsoActiveOrHistoricCurrencyAndAmount
}
StatementResolutionEntry2 *-- "0..1" OriginalGroupInformation3 : OriginalGroupInformation
StatementResolutionEntry2 *-- "0..0" Charges3 : Charges
StatementResolutionEntry2 *-- "0..1" IPurpose2Choice : Purpose
%% OriginalGroupInformation3 recursion level 1 with max 1
class OriginalGroupInformation3{
    OriginalMessageIdentification IsoMax35Text
    OriginalMessageNameIdentification IsoMax35Text
    OriginalCreationDateTime IsoISODateTime
}
%% Charges3 recursion level 1 with max 1
class Charges3{
    TotalChargesAndTaxAmount IsoActiveOrHistoricCurrencyAndAmount
}
Charges3 *-- "0..0" ChargesRecord1 : Record
%% IPurpose2Choice recursion level 1 with max 1

StatementResolutionEntry2 members

Member name Description Data Type / Multiplicity
OriginalGroupInformation Provides information on the original message. OriginalGroupInformation3 - Optional 0..1
OriginalStatementIdentification Unique identification, as assigned by the account servicer, to unambiguously identify the original statement. IsoMax35Text - Optional 0..1
AccountServicerReference Unique reference, as assigned by the account servicing institution, to unambiguously identify the entry. IsoMax35Text - Optional 0..1
CorrectedAmount Corrected debit or credit amount, compared to the original entry where the amount is incorrect.
Charges Provides information on the charges included in the original entry amount. Charges3 - Unknown 0..0
Purpose Underlying reason for the payment transaction. Usage: Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) creditor to provide information concerning the nature of the payment. Purpose is a content element, which is not used for processing by any of the agents involved in the payment chain.

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
%% ICorrectiveTransaction1Choice recursion level 0 with max 1

CorrectiveTransaction1Choice members

Member name Description Data Type / Multiplicity

ResolutionRelatedInformation building block

Reference of a return or a reversal initiated to fix the case under investigation as part of the resolution. Set of elements used to provide information on the return or reversal expected by the party that initiated the initial payment instruction after a cancellation or modification request. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ResolutionInformation1 recursion level 0 with max 1
class ResolutionInformation1{
    InterbankSettlementAmount IsoActiveOrHistoricCurrencyAndAmount
    InterbankSettlementDate IsoISODate
    ClearingChannel ClearingChannel2Code
}

ResolutionInformation1 members

Member name Description Data Type / Multiplicity
InterbankSettlementAmount Amount of money moved between the instructing agent and the instructed agent. IsoActiveOrHistoricCurrencyAndAmount - Optional 0..1
InterbankSettlementDate Date on which the amount of money ceases to be available to the agent that owes it and when the amount of money becomes available to the agent to which it is due. IsoISODate - Optional 0..1
ClearingChannel Specifies the clearing channel to be used to process the payment instruction. ClearingChannel2Code - Optional 0..1

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

Member name Description Data Type / Multiplicity
PlaceAndName Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. IsoMax350Text - Optional 0..1
Envelope Technical element wrapping the supplementary data. IsoSupplementaryDataEnvelope1 - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    ResolutionOfInvestigationV04 --|> IOuterRecord : Implements
    ResolutionOfInvestigationV04Document --|> IOuterDocument~ResolutionOfInvestigationV04~ : Implements
    class IOuterDocument~ResolutionOfInvestigationV04~ {
        ResolutionOfInvestigationV04 Message
     }

Document wrapper for serialization

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

classDiagram
    ResolutionOfInvestigationV04Document *-- ResolutionOfInvestigationV04 : 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.04">
    <RsltnOfInvstgtn>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <RslvdCase>
            <!-- ResolvedCase inner content -->
        </RslvdCase>
        <Sts>
            <!-- Status inner content -->
        </Sts>
        <CxlDtls>
            <!-- CancellationDetails inner content -->
        </CxlDtls>
        <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="_sRxjEFkyEeGeoaLUQk__nA_412404237"
  nextVersions="_wQzazRPeEeSVo-TFVwFHvA"
  previousVersion="_WFzdONE_Ed-BzquC8wXy7w_-198860277"
  name="ResolutionOfInvestigationV04"
  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 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 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 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 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.&#xD;&#xA;The Resolution Of Investigation 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 Cancellation Details component."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="RsltnOfInvstgtn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_sSOPAVkyEeGeoaLUQk__nA_196310710"
    nextVersions="_wQzazxPeEeSVo-TFVwFHvA"
    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="_sSYAAVkyEeGeoaLUQk__nA_-800761643"
    nextVersions="_wQza0RPeEeSVo-TFVwFHvA"
    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="_sShxAFkyEeGeoaLUQk__nA_-1797833996"
    nextVersions="_wQza0xPeEeSVo-TFVwFHvA"
    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="_sSq68FkyEeGeoaLUQk__nA_1500060947"
    nextVersions="_wQza1RPeEeSVo-TFVwFHvA"
    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="_sSq68lkyEeGeoaLUQk__nA_502988594"
    nextVersions="_wQza1xPeEeSVo-TFVwFHvA"
    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="_sRxjEVkyEeGeoaLUQk__nA_1883777532"
    nextVersions="_wQza2RPeEeSVo-TFVwFHvA"
    name="Assignment"
    definition="Identifies the assignment of an investigation case from an assigner to an assignee.&#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="_sbKvolkyEeGeoaLUQk__nA_1583838951" />
  <messageBuildingBlock
    xmi:id="_sRxjElkyEeGeoaLUQk__nA_1000544245"
    nextVersions="_wQza2xPeEeSVo-TFVwFHvA"
    name="ResolvedCase"
    definition="Identifies a resolved case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RslvdCase"
    complexType="_tijOcFkyEeGeoaLUQk__nA_-1838378407" />
  <messageBuildingBlock
    xmi:id="_sRxjE1kyEeGeoaLUQk__nA_3471892"
    nextVersions="_wQza3RPeEeSVo-TFVwFHvA"
    name="Status"
    definition="Indicates the status of the investigation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Sts"
    complexType="_tx5SAVkyEeGeoaLUQk__nA_-868345500" />
  <messageBuildingBlock
    xmi:id="_sR7UEFkyEeGeoaLUQk__nA_-110367174"
    nextVersions="_wQza3xPeEeSVo-TFVwFHvA"
    name="CancellationDetails"
    definition="Specifies the details of the underlying transactions being cancelled."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="CxlDtls"
    complexType="_sgYm0FkyEeGeoaLUQk__nA_-1571947250" />
  <messageBuildingBlock
    xmi:id="_sR7UEVkyEeGeoaLUQk__nA_-1107439527"
    nextVersions="_wQza4RPeEeSVo-TFVwFHvA"
    name="StatementDetails"
    definition="Details on the underlying statement entry."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="StmtDtls"
    complexType="_ttIGwFkyEeGeoaLUQk__nA_2058261380" />
  <messageBuildingBlock
    xmi:id="_sR7UElkyEeGeoaLUQk__nA_-2104511880"
    nextVersions="_wQza4xPeEeSVo-TFVwFHvA"
    name="CorrectionTransaction"
    definition="References a transaction initiated to fix the case under investigation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="CrrctnTx"
    complexType="_P7RPB9p-Ed-ak6NoX_4Aeg_445154531" />
  <messageBuildingBlock
    xmi:id="_sSFFEFkyEeGeoaLUQk__nA_1193383063"
    nextVersions="_wQza5RPeEeSVo-TFVwFHvA"
    name="ResolutionRelatedInformation"
    definition="Reference of a return or a reversal initiated to fix the case under investigation as part of the resolution."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RsltnRltdInf"
    complexType="_QJIE2tp-Ed-ak6NoX_4Aeg_-774810951" />
  <messageBuildingBlock
    xmi:id="_sSOPAFkyEeGeoaLUQk__nA_1613572307"
    nextVersions="_wQza5xPeEeSVo-TFVwFHvA"
    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="04" />
</messageDefinition>

ISO Building Blocks

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