Iso20022

NotificationOfCaseAssignmentV04

camt.030.001.04

Scope The Notification Of Case Assignment message is sent by a case assignee to a case creator/case assigner. This message is used to inform the case assigner that:

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
%% NotificationOfCaseAssignmentV04 recursion level 0 with max 0
NotificationOfCaseAssignmentV04 *-- "1..1" ReportHeader4 : Header
NotificationOfCaseAssignmentV04 *-- "1..1" Case3 : Case
NotificationOfCaseAssignmentV04 *-- "1..1" CaseAssignment3 : Assignment
NotificationOfCaseAssignmentV04 *-- "1..1" CaseForwardingNotification3 : Notification
NotificationOfCaseAssignmentV04 *-- "0..1" SupplementaryData1 : SupplementaryData

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

Header building block

Specifies generic information about the notification. The receiver of a notification must be the party which assigned the case to the sender. Specifies generic information about an investigation report. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ReportHeader4 recursion level 0 with max 1
class ReportHeader4{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
ReportHeader4 *-- "1..1" IParty12Choice : From
ReportHeader4 *-- "1..1" IParty12Choice : To
%% IParty12Choice recursion level 1 with max 1
%% IParty12Choice recursion level 1 with max 1

ReportHeader4 members

Member name Description Data Type / Multiplicity
Identification Point to point reference as assigned by the case assigner to unambiguously identify the case status report. IsoMax35Text - Required 1..1
From Party reporting the status of the investigation case. IParty12Choice - Required 1..1
To Party to which the status of the case is reported. IParty12Choice - Required 1..1
CreationDateTime Date and time at which the message 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
%% 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

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

Notification building block

Information about the type of action taken. Status of a case resulting from a case assignment. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CaseForwardingNotification3 recursion level 0 with max 1
class CaseForwardingNotification3{
    Justification CaseForwardingNotification3Code
}

CaseForwardingNotification3 members

Member name Description Data Type / Multiplicity
Justification Justification for the forward action. CaseForwardingNotification3Code - 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 NotificationOfCaseAssignmentV04 implementation follows a specific implementaiton pattern. First of all, NotificationOfCaseAssignmentV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, NotificationOfCaseAssignmentV04Document implements IOuterDocument. Because NotificationOfCaseAssignmentV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type NotificationOfCaseAssignmentV04.

classDiagram
    class IOuterRecord
    NotificationOfCaseAssignmentV04 --|> IOuterRecord : Implements
    NotificationOfCaseAssignmentV04Document --|> IOuterDocument~NotificationOfCaseAssignmentV04~ : Implements
    class IOuterDocument~NotificationOfCaseAssignmentV04~ {
        NotificationOfCaseAssignmentV04 Message
     }

Document wrapper for serialization

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

classDiagram
    NotificationOfCaseAssignmentV04Document *-- NotificationOfCaseAssignmentV04 : 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.030.001.04">
    <NtfctnOfCaseAssgnmt>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <Case>
            <!-- Case inner content -->
        </Case>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <Ntfctn>
            <!-- Notification inner content -->
        </Ntfctn>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </NtfctnOfCaseAssgnmt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_sYfPEVkyEeGeoaLUQk__nA_241653460"
  nextVersions="_eX_Oh22PEei3KuUgpx7Xcw"
  previousVersion="_KtIUxdE_Ed-BzquC8wXy7w_-2097745661"
  name="NotificationOfCaseAssignmentV04"
  definition="Scope&#xD;&#xA;The Notification Of Case Assignment message is sent by a case assignee to a case creator/case assigner.&#xD;&#xA;This message is used to inform the case assigner that:&#xD;&#xA;- the assignee is reassigning the case to the next agent in the transaction processing chain for further action&#xD;&#xA;- the assignee will work on the case himself, without re-assigning it to another party, and therefore indicating that the re-assignment has reached its end-point&#xD;&#xA;Usage&#xD;&#xA;The Notification Of Case Assignment message is used to notify the case creator or case assigner of further action undertaken 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;The Notification Of Case Assignment message&#xD;&#xA;- covers one and only one case at a time. If the case assignee needs to inform a case creator or case assigner about several cases, then multiple Notification Of Case Assignment messages must be sent&#xD;&#xA;- except in the case where it is used to indicate that an agent is doing the correction himself, this message must be forwarded by all subsequent case assigner(s) until it reaches the case creator&#xD;&#xA;- must not be used in place of a Resolution Of Investigation or a Case Status Report message&#xD;&#xA;When the assignee does not reassign the case to another party (that is responding with a Notification Of Case Assignment message with notification MINE - The case is processed by the assignee), the case assignment should contain the case assignment elements as received in the original query."
  registrationStatus="Registered"
  messageSet="_wRx2xk2rEeG_I4xRYCA_7g _urpIICeJEeOCeO5e7islRQ"
  xmlTag="NtfctnOfCaseAssgnmt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_sYoZAFkyEeGeoaLUQk__nA_-1955767076"
    nextVersions="_eX_OiW2PEei3KuUgpx7Xcw"
    name="Header"
    definition="Specifies generic information about the notification.&#xA;The receiver of a notification must be the party which assigned the case to the sender."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_toznclkyEeGeoaLUQk__nA_-1793756198" />
  <messageBuildingBlock
    xmi:id="_sYoZAVkyEeGeoaLUQk__nA_1455966933"
    nextVersions="_eX_Oi22PEei3KuUgpx7Xcw"
    name="Case"
    definition="Identifies the investigation case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Case"
    complexType="_tijOcFkyEeGeoaLUQk__nA_-1838378407" />
  <messageBuildingBlock
    xmi:id="_sYoZAlkyEeGeoaLUQk__nA_1342127867"
    nextVersions="_eX_OjW2PEei3KuUgpx7Xcw"
    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="_sYyKAFkyEeGeoaLUQk__nA_458894580"
    nextVersions="_eX_Oj22PEei3KuUgpx7Xcw"
    name="Notification"
    definition="Information about the type of action taken."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Ntfctn"
    complexType="_T-ZtQtp-Ed-ak6NoX_4Aeg_-1114775558" />
  <messageBuildingBlock
    xmi:id="_sYyKAVkyEeGeoaLUQk__nA_-135424207"
    nextVersions="_eX_OkW2PEei3KuUgpx7Xcw"
    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="030"
    flavour="001"
    version="04" />
</messageDefinition>

ISO Building Blocks

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