Iso20022

NotificationOfCaseAssignment

camt.030.001.01

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
%% NotificationOfCaseAssignment recursion level 0 with max 0
NotificationOfCaseAssignment *-- "1..1" ReportHeader : Header
NotificationOfCaseAssignment *-- "1..1" Case : Case
NotificationOfCaseAssignment *-- "1..1" CaseAssignment : Assignment
NotificationOfCaseAssignment *-- "1..1" CaseForwardingNotification : Notification

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 is necessarily 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
%% ReportHeader recursion level 0 with max 1
class ReportHeader{
    Identification IsoMax35Text
    From IsoAnyBICIdentifier
    To IsoAnyBICIdentifier
    CreationDateTime IsoISODateTime
}

ReportHeader members

Member name Description Data Type / Multiplicity
Identification Identification of the report. IsoMax35Text - Required 1..1
From Party reporting the status of the case. IsoAnyBICIdentifier - Required 1..1
To Party to which the status of the case is reported. IsoAnyBICIdentifier - Required 1..1
CreationDateTime Creation date and time of the report generation. 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

Assignment building block

Identifies the current assignment of the case.

The Assigner must be the emitter of the notification. The Assignee must be another Party in the payment chain. 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

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
%% CaseForwardingNotification recursion level 0 with max 1
class CaseForwardingNotification{
    Justification CaseForwardingNotification1Code
}

CaseForwardingNotification members

Member name Description Data Type / Multiplicity
Justification Justification for the forward action. CaseForwardingNotification1Code - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    NotificationOfCaseAssignment --|> IOuterRecord : Implements
    NotificationOfCaseAssignmentDocument --|> IOuterDocument~NotificationOfCaseAssignment~ : Implements
    class IOuterDocument~NotificationOfCaseAssignment~ {
        NotificationOfCaseAssignment Message
     }

Document wrapper for serialization

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

classDiagram
    NotificationOfCaseAssignmentDocument *-- NotificationOfCaseAssignment : 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.01">
    <camt.030.001.01>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <Case>
            <!-- Case inner content -->
        </Case>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <Ntfctn>
            <!-- Notification inner content -->
        </Ntfctn>
    </camt.030.001.01>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_JvSziNE_Ed-BzquC8wXy7w_1651385282"
  name="NotificationOfCaseAssignment"
  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."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlName="camt.030.001.01"
  xmlTag="camt.030.001.01"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_JvSzidE_Ed-BzquC8wXy7w_-896449818"
    name="Header"
    definition="Specifies generic information about the notification.&#xA;The receiver of a notification is necessarily the party which assigned the case to the sender."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_RI5fwNp-Ed-ak6NoX_4Aeg_24374172" />
  <messageBuildingBlock
    xmi:id="_JvckgNE_Ed-BzquC8wXy7w_-710886689"
    name="Case"
    definition="Identifies the case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Case"
    complexType="_SpAnotp-Ed-ak6NoX_4Aeg_136183535" />
  <messageBuildingBlock
    xmi:id="_JvckgdE_Ed-BzquC8wXy7w_-367336847"
    name="Assignment"
    definition="Identifies the current assignment of the case. &#xA;&#xA;The Assigner must be the emitter of the notification.&#xA;The Assignee must be another Party in the payment chain."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Assgnmt"
    complexType="_T9Dpetp-Ed-ak6NoX_4Aeg_588710247" />
  <messageBuildingBlock
    xmi:id="_JvckgtE_Ed-BzquC8wXy7w_-354409827"
    name="Notification"
    definition="Information about the type of action taken."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Ntfctn"
    complexType="_VJDihdp-Ed-ak6NoX_4Aeg_92437135" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="030"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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