RejectInvestigationV03

camt.031.001.03

Scope The Reject Investigation message is sent by a case assignee to a case creator or case assigner to reject a case given to him. Usage The Reject Investigation message is used to notify the case creator or case assigner the rejection of an assignment by the case assignee in a:

request to cancel payment case
request to modify payment case
unable to apply case
claim non receipt case Rejecting a case assignment occurs when:
the case assignee is unable to trace the original payment instruction
the case assignee is unable, or does not have authority, to process the assigned case (indicate “You have by-passed a party”,
the case assignee has received a non expected message, and rejects the message with a wrong message indicator
the case assignee has not yet received the Resolution Of Investigation message and the case has already been reopened
the case assignee has rejects an non-cash related query The Reject Investigation message covers one and only one case at a time. If the case assignee needs to reject several case assignments, then multiple Reject Investigation messages must be sent. The Reject Investigation message must be forwarded by all subsequent case assignee(s) until it reaches the case assigner and must not be used in place of a Resolution Of Investigation or Case Status Report message.

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
%% RejectInvestigationV03 recursion level 0 with max 0
RejectInvestigationV03 *-- "1..1" CaseAssignment2 : Assignment
RejectInvestigationV03 *-- "1..1" Case2 : Case
RejectInvestigationV03 *-- "1..1" InvestigationRejectionJustification1 : Justification

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. Set of elements used to represent the assignment of a case to a party. For comparison, see the ISO20022 official specification

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

CaseAssignment2 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

Case building block

Identifies the investigation case. Set of elements used to identify a case. For comparison, see the ISO20022 official specification

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

Case2 members

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

Justification building block

Specifies the reason for the rejection of an investigation. Provides the reason for rejecting the case assignment. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% InvestigationRejectionJustification1 recursion level 0 with max 1
class InvestigationRejectionJustification1{
    RejectionReason InvestigationRejection1Code
}

InvestigationRejectionJustification1 members

Member name	Description	Data Type / Multiplicity
RejectionReason	Reason for the rejection of a case assignment, in a coded form.	InvestigationRejection1Code - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    RejectInvestigationV03 --|> IOuterRecord : Implements
    RejectInvestigationV03Document --|> IOuterDocument~RejectInvestigationV03~ : Implements
    class IOuterDocument~RejectInvestigationV03~ {
        RejectInvestigationV03 Message
     }

Document wrapper for serialization

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

classDiagram
    RejectInvestigationV03Document *-- RejectInvestigationV03 : 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.031.001.03">
    <RjctInvstgtn>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <Case>
            <!-- Case inner content -->
        </Case>
        <Justfn>
            <!-- Justification inner content -->
        </Justfn>
    </RjctInvstgtn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_QvEpGNE_Ed-BzquC8wXy7w_-1066047967"
  nextVersions="_sReoIlkyEeGeoaLUQk__nA_152798940"
  name="RejectInvestigationV03"
  definition="Scope&#xD;&#xA;The Reject Investigation message is sent by a case assignee to a case creator or case assigner to reject a case given to him.&#xD;&#xA;Usage&#xD;&#xA;The Reject Investigation message is used to notify the case creator or case assigner the rejection of an assignment by the case assignee in 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;Rejecting a case assignment occurs when:&#xD;&#xA;- the case assignee is unable to trace the original payment instruction&#xD;&#xA;- the case assignee is unable, or does not have authority, to process the assigned case (indicate &quot;You have by-passed a party&quot;,&#xD;&#xA;- the case assignee has received a non expected message, and rejects the message with a wrong message indicator&#xD;&#xA;- the case assignee has not yet received the Resolution Of Investigation message and the case has already been reopened&#xD;&#xA;- the case assignee has rejects an non-cash related query&#xD;&#xA;The Reject Investigation message covers one and only one case at a time. If the case assignee needs to reject several case assignments, then multiple Reject Investigation messages must be sent.&#xD;&#xA;The Reject Investigation message must be forwarded by all subsequent case assignee(s) until it reaches the case assigner and must not be used in place of a Resolution Of Investigation or Case Status Report message."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="RjctInvstgtn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_QvEpGdE_Ed-BzquC8wXy7w_708784134"
    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="_T9Nac9p-Ed-ak6NoX_4Aeg_-1609381277" />
  <messageBuildingBlock
    xmi:id="_QvEpGtE_Ed-BzquC8wXy7w_708784195"
    name="Case"
    definition="Identifies the investigation case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Case"
    complexType="_SpAnptp-Ed-ak6NoX_4Aeg_-1565053133" />
  <messageBuildingBlock
    xmi:id="_QvEpG9E_Ed-BzquC8wXy7w_-1066047903"
    name="Justification"
    definition="Specifies the reason for the rejection of an investigation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Justfn"
    complexType="_T-ZtQNp-Ed-ak6NoX_4Aeg_947706668" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="031"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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