CaseStatusReportV03

camt.039.001.03

Scope The Case Status Report message is sent by a case assignee to a case creator or case assigner. This message is used to report on the status of a case. Usage A Case Status Report message is sent in reply to a Case Status Report Request message. This message

covers one and only one case at a time. (If a case assignee needs to report on several cases, then multiple Case Status Report messages must be sent.)
may be forwarded to subsequent case assigner(s) until it reaches the end point
is able to indicate the fact that a case has been assigned to a party downstream in the payment processing chain
may not be used in place of a Resolution Of Investigation (except for the condition given in the next bullet point) or Notification Of Case Assignment message
may be skipped and replaced by a Resolution Of Investigation message when the request for a investigation status is received at the time the assigner has resolved the case. (In this case a Resolution Of Investigation message can be sent instead of a Case Status Report and the case may be closed.).

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
%% CaseStatusReportV03 recursion level 0 with max 0
CaseStatusReportV03 *-- "1..1" ReportHeader2 : Header
CaseStatusReportV03 *-- "1..1" Case2 : Case
CaseStatusReportV03 *-- "1..1" CaseStatus2 : Status
CaseStatusReportV03 *-- "0..1" CaseAssignment2 : NewAssignment

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

Header building block

Specifies generic information about an investigation report. Specifies generic information about an investigation report. For comparison, see the ISO20022 official specification

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

ReportHeader2 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.	IParty7Choice - Required 1..1
To	Party to which the status of the case is reported.	IParty7Choice - Required 1..1
CreationDateTime	Date and time at which the message was created.	IsoISODateTime - Required 1..1

Case building block

Identifies the investigation case. Set of elements used to identify a case. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Case2 recursion level 0 with max 1
class Case2{
    Identification IsoMax35Text
    ReopenCaseIndication IsoYesNoIndicator
}
Case2 *-- "1..1" IParty7Choice : Creator
%% IParty7Choice recursion level 1 with max 1

Case2 members

Member name	Description	Data Type / Multiplicity
Identification	Uniquely identifies the case.	IsoMax35Text - Required 1..1
Creator	Party that created the investigation case.	IParty7Choice - Required 1..1
ReopenCaseIndication	Indicates whether or not the case was previously closed and is now re-opened.	IsoYesNoIndicator - Optional 0..1

Status building block

Defines the status of the case. Defines the status of an investigation case. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CaseStatus2 recursion level 0 with max 1
class CaseStatus2{
    DateTime IsoISODateTime
    CaseStatus CaseStatus2Code
    Reason IsoMax140Text
}

CaseStatus2 members

Member name	Description	Data Type / Multiplicity
DateTime	Date and time of the status.	IsoISODateTime - Required 1..1
CaseStatus	Status of the case.	CaseStatus2Code - Required 1..1
Reason	Free text justification of the status.	IsoMax140Text - Optional 0..1

NewAssignment building block

Identifies the change of an assignment for an investigation case from an assigner to a new assignee. Usage: The Assigner must be the sender of this confirmation and the Assignee must be the receiver. Set of elements used to represent the assignment of a case to a party. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CaseAssignment2 recursion level 0 with max 1
class CaseAssignment2{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
CaseAssignment2 *-- "1..1" IParty7Choice : Assigner
CaseAssignment2 *-- "1..1" IParty7Choice : Assignee
%% IParty7Choice recursion level 1 with max 1
%% IParty7Choice recursion level 1 with max 1

CaseAssignment2 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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    CaseStatusReportV03 --|> IOuterRecord : Implements
    CaseStatusReportV03Document --|> IOuterDocument~CaseStatusReportV03~ : Implements
    class IOuterDocument~CaseStatusReportV03~ {
        CaseStatusReportV03 Message
     }

Document wrapper for serialization

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

classDiagram
    CaseStatusReportV03Document *-- CaseStatusReportV03 : 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.039.001.03">
    <CaseStsRpt>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <Case>
            <!-- Case inner content -->
        </Case>
        <Sts>
            <!-- Status inner content -->
        </Sts>
        <NewAssgnmt>
            <!-- NewAssignment inner content -->
        </NewAssgnmt>
    </CaseStsRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_PzltuNE-Ed-BzquC8wXy7w_86849110"
  nextVersions="_sVp9glkyEeGeoaLUQk__nA_-1954850313"
  name="CaseStatusReportV03"
  definition="Scope&#xD;&#xA;The Case Status Report message is sent by a case assignee to a case creator or case assigner.&#xD;&#xA;This message is used to report on the status of a case.&#xD;&#xA;Usage&#xD;&#xA;A Case Status Report message is sent in reply to a Case Status Report Request message. This message&#xD;&#xA;- covers one and only one case at a time. (If a case assignee needs to report on several cases, then multiple Case Status Report messages must be sent.)&#xD;&#xA;- may be forwarded to subsequent case assigner(s) until it reaches the end point&#xD;&#xA;- is able to indicate the fact that a case has been assigned to a party downstream in the payment processing chain&#xD;&#xA;- may not be used in place of a Resolution Of Investigation (except for the condition given in the next bullet point) or Notification Of Case Assignment message&#xD;&#xA;- may be skipped and replaced by a Resolution Of Investigation message when the request for a investigation status is received at the time the assigner has resolved the case. (In this case a Resolution Of Investigation message can be sent instead of a Case Status Report and the case may be closed.)."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="CaseStsRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_PzltudE-Ed-BzquC8wXy7w_108164602"
    name="Header"
    definition="Specifies generic information about an investigation report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_Rq4LdNp-Ed-ak6NoX_4Aeg_891312394" />
  <messageBuildingBlock
    xmi:id="_Pzu3oNE-Ed-BzquC8wXy7w_108164624"
    name="Case"
    definition="Identifies the investigation case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Case"
    complexType="_SpAnptp-Ed-ak6NoX_4Aeg_-1565053133" />
  <messageBuildingBlock
    xmi:id="_Pzu3odE-Ed-BzquC8wXy7w_86849420"
    name="Status"
    definition="Defines the status of the case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Sts"
    complexType="_T-GLS9p-Ed-ak6NoX_4Aeg_-1949574113" />
  <messageBuildingBlock
    xmi:id="_Pzu3otE-Ed-BzquC8wXy7w_108164716"
    name="NewAssignment"
    definition="Identifies the change of an assignment for an investigation case from an assigner to a new 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="0"
    xmlTag="NewAssgnmt"
    complexType="_T9Nac9p-Ed-ak6NoX_4Aeg_-1609381277" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="039"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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