camt.031.001.06
Scope The RejectInvestigation message is sent by a case assignee to a case creator or case assigner to reject a case given to him. Usage The RejectInvestigation 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 ResolutionOfInvestigation message and the case has already been reopened;
- the case assignee has rejects an non-cash related query. The RejectInvestigation message covers one and only one case at a time. If the case assignee needs to reject several case assignments, then multiple RejectInvestigation messages must be sent. The RejectInvestigation 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 ResolutionOfInvestigation or CaseStatusReport 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
%% RejectInvestigationV06 recursion level 0 with max 0
RejectInvestigationV06 *-- "1..1" CaseAssignment5 : Assignment
RejectInvestigationV06 *-- "0..1" Case5 : Case
RejectInvestigationV06 *-- "1..1" InvestigationRejectionJustification1 : Justification
RejectInvestigationV06 *-- "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
| 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. 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
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Uniquely identifies the case. | IsoMax35Text - Required 1..1 |
| Creator | Party that created the investigation case. | IParty40Choice - 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 |
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 RejectInvestigationV06 implementation follows a specific implementaiton pattern. First of all, RejectInvestigationV06 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, RejectInvestigationV06Document implements IOuterDocument. Because RejectInvestigationV06 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type RejectInvestigationV06.
classDiagram
class IOuterRecord
RejectInvestigationV06 --|> IOuterRecord : Implements
RejectInvestigationV06Document --|> IOuterDocument~RejectInvestigationV06~ : Implements
class IOuterDocument~RejectInvestigationV06~ {
RejectInvestigationV06 Message
}
Document wrapper for serialization
The only real purpose RejectInvestigationV06Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:camt.031.001.06’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using RejectInvestigationV06.ToDocument() method. The returned RejectInvestigationV06Document value will serialize correctly according to ISO 20022 standards.
classDiagram
RejectInvestigationV06Document *-- RejectInvestigationV06 : 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.06">
<RjctInvstgtn>
<Assgnmt>
<!-- Assignment inner content -->
</Assgnmt>
<Case>
<!-- Case inner content -->
</Case>
<Justfn>
<!-- Justification inner content -->
</Justfn>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</RjctInvstgtn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_eX_Ok22PEei3KuUgpx7Xcw"
previousVersion="_nNMjZ6qDEeeMmtkfa8-zPg"
name="RejectInvestigationV06"
definition="Scope
The RejectInvestigation message is sent by a case assignee to a case creator or case assigner to reject a case given to him.
Usage
The RejectInvestigation 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 ResolutionOfInvestigation message and the case has already been reopened;
- the case assignee has rejects an non-cash related query.
The RejectInvestigation message covers one and only one case at a time. If the case assignee needs to reject several case assignments, then multiple RejectInvestigation messages must be sent.
The RejectInvestigation 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 ResolutionOfInvestigation or CaseStatusReport message."
registrationStatus="Registered"
messageSet="_moz48_2VEeGjgKzdN0DbWA"
xmlTag="RjctInvstgtn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_eX_OlW2PEei3KuUgpx7Xcw"
previousVersion="_nNMjaaqDEeeMmtkfa8-zPg"
name="Assignment"
definition="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."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Assgnmt"
complexType="_BzPdIW49EeiU9cctagi5ow" />
<messageBuildingBlock
xmi:id="_eX_Ol22PEei3KuUgpx7Xcw"
previousVersion="_nNMja6qDEeeMmtkfa8-zPg"
name="Case"
definition="Identifies the investigation case."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="Case"
complexType="_8BF4W248EeiU9cctagi5ow" />
<messageBuildingBlock
xmi:id="_eX_OmW2PEei3KuUgpx7Xcw"
previousVersion="_nNMjbaqDEeeMmtkfa8-zPg"
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" />
<messageBuildingBlock
xmi:id="_eX_Om22PEei3KuUgpx7Xcw"
previousVersion="_nNMjb6qDEeeMmtkfa8-zPg"
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="031"
flavour="001"
version="06" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.