Iso20022

RejectCaseAssignment

camt.031.001.01

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

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
%% RejectCaseAssignment recursion level 0 with max 0
RejectCaseAssignment *-- "1..1" CaseAssignment : Assignment
RejectCaseAssignment *-- "1..1" Case : Case
RejectCaseAssignment *-- "1..1" CaseAssignmentRejectionJustification : Justification

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

Assignment building block

Identifies the assignment. 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

Case building block

Identifies the 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

Justification building block

Specifies the reason for not accepting a Case. Provides the reason for rejecting the case assignment. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CaseAssignmentRejectionJustification recursion level 0 with max 1
class CaseAssignmentRejectionJustification{
    RejectionReason CaseAssignmentRejection1Code
}

CaseAssignmentRejectionJustification members

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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    RejectCaseAssignment --|> IOuterRecord : Implements
    RejectCaseAssignmentDocument --|> IOuterDocument~RejectCaseAssignment~ : Implements
    class IOuterDocument~RejectCaseAssignment~ {
        RejectCaseAssignment Message
     }

Document wrapper for serialization

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

classDiagram
    RejectCaseAssignmentDocument *-- RejectCaseAssignment : 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.01">
    <camt.031.001.01>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <Case>
            <!-- Case inner content -->
        </Case>
        <Justfn>
            <!-- Justification inner content -->
        </Justfn>
    </camt.031.001.01>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_PxiCwtE_Ed-BzquC8wXy7w_-313128527"
  name="RejectCaseAssignment"
  definition="Scope&#xD;&#xA;The Reject Case Assignment 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 Case Assignment 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 the case assignee is unable to trace the original payment instruction or when the case assignee is unable, or does not have authority, to process the assigned case.&#xD;&#xA;The Reject Case Assignment message covers one and only one case at a time. If the case assignee needs to reject several case assignments, then multiple Reject Case Assignment messages must be sent.&#xD;&#xA;The Reject Case Assignment message must be forwarded by all subsequent case assignee(s) until it reaches the case assigner.&#xD;&#xA;The Reject Case Assignment message must not be used in place of a Resolution Of Investigation or Case Status Report message."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlName="camt.031.001.01"
  xmlTag="camt.031.001.01"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_PxiCw9E_Ed-BzquC8wXy7w_2109597961"
    name="Assignment"
    definition="Identifies the assignment."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Assgnmt"
    complexType="_T9Dpetp-Ed-ak6NoX_4Aeg_588710247" />
  <messageBuildingBlock
    xmi:id="_PxiCxNE_Ed-BzquC8wXy7w_2125297631"
    name="Case"
    definition="Identifies the case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Case"
    complexType="_SpAnotp-Ed-ak6NoX_4Aeg_136183535" />
  <messageBuildingBlock
    xmi:id="_PxiCxdE_Ed-BzquC8wXy7w_-1282168665"
    name="Justification"
    definition="Specifies the reason for not accepting a Case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Justfn"
    complexType="_VJDig9p-Ed-ak6NoX_4Aeg_-1410536131" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="031"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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