Iso20022

CancelCaseAssignmentV04

camt.032.001.04

Scope The CancelCaseAssignment message is sent by a case creator or case assigner to a case assignee. This message is used to request the cancellation of a case. Usage The CancelCaseAssignment message is used to stop the processing of a case at a case assignee when a case assignment is incorrect or when the root cause for the case disappears (such as the account owner was able to reconcile after sending a ClaimNonReceipt message). The CancelCaseAssignment message can be used to stop the processing of 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
%% CancelCaseAssignmentV04 recursion level 0 with max 0
CancelCaseAssignmentV04 *-- "1..1" CaseAssignment5 : Assignment
CancelCaseAssignmentV04 *-- "1..1" Case5 : Case
CancelCaseAssignmentV04 *-- "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

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 CancelCaseAssignmentV04 implementation follows a specific implementaiton pattern. First of all, CancelCaseAssignmentV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, CancelCaseAssignmentV04Document implements IOuterDocument. Because CancelCaseAssignmentV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type CancelCaseAssignmentV04.

classDiagram
    class IOuterRecord
    CancelCaseAssignmentV04 --|> IOuterRecord : Implements
    CancelCaseAssignmentV04Document --|> IOuterDocument~CancelCaseAssignmentV04~ : Implements
    class IOuterDocument~CancelCaseAssignmentV04~ {
        CancelCaseAssignmentV04 Message
     }

Document wrapper for serialization

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

classDiagram
    CancelCaseAssignmentV04Document *-- CancelCaseAssignmentV04 : 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.032.001.04">
    <CclCaseAssgnmt>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <Case>
            <!-- Case inner content -->
        </Case>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </CclCaseAssgnmt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_eX_OnW2PEei3KuUgpx7Xcw"
  previousVersion="_sXcGMFkyEeGeoaLUQk__nA_-930975995"
  name="CancelCaseAssignmentV04"
  definition="Scope&#xD;&#xA;The CancelCaseAssignment message is sent by a case creator or case assigner to a case assignee. This message is used to request the cancellation of a case.&#xD;&#xA;Usage&#xD;&#xA;The CancelCaseAssignment message is used to stop the processing of a case at a case assignee when a case assignment is incorrect or when the root cause for the case disappears (such as the account owner was able to reconcile after sending a ClaimNonReceipt message).&#xD;&#xA;The CancelCaseAssignment message can be used to stop the processing of 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 CancelCaseAssignment message covers one and only one case at a time. If several case assignments need to be cancelled, then multiple CancelCaseAssignment messages must be sent.&#xD;&#xA;The CancelCaseAssignment message must be forwarded by all subsequent case assignee(s) in the case processing chain until it reaches the end point.&#xD;&#xA;When an agent re-assigns the CancelCaseAssignment to a subsequent case assignee, this agent must send a NotificationOfCaseAssignment message to its assigner.&#xD;&#xA;When the CancelCaseAssignment instruction has been acted upon by the relevant case assignee, a ResolutionOfInvestigation message is sent to the case assigner or case creator, in reply.&#xD;&#xA;The CancelCaseAssignment message must not be used for other purposes. If, for example, a request to modify payment fails, and the case creator requests the cancellation of the payment, then a CustomerPaymentCancellationRequest or FIToFIPaymentCancellationRequest message must be used, with the case identification of the original RequestToModifyPayment message. In this context it is incorrect to use the CancelCaseAssignment message."
  registrationStatus="Registered"
  messageSet="_moz48_2VEeGjgKzdN0DbWA"
  xmlTag="CclCaseAssgnmt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_eX_On22PEei3KuUgpx7Xcw"
    previousVersion="_sXcGMVkyEeGeoaLUQk__nA_-410868205"
    name="Assignment"
    definition="Identifies the assignment of an investigation case from an assigner to an assignee.&#xD;&#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="_BzPdIW49EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_eX_OoW2PEei3KuUgpx7Xcw"
    previousVersion="_sXvoMFkyEeGeoaLUQk__nA_-1294101492"
    name="Case"
    definition="Identifies the investigation case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Case"
    complexType="_8BF4W248EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_eX_Oo22PEei3KuUgpx7Xcw"
    previousVersion="_sXvoMVkyEeGeoaLUQk__nA_1037902582"
    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="032"
    flavour="001"
    version="04" />
</messageDefinition>

ISO Building Blocks

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