RequestForDuplicateInstruction

camt.033.001.01

Scope The Request For Duplicate message is sent by the case assignee to the case creator or case assigner. This message is used to request a copy of the original payment instruction considered in the case. Usage The Request For Duplicate message:

must be answered with a Duplicate message
must be used when a case assignee requests a copy of the original payment instruction. This occurs, for example, when the case assignee cannot trace the payment instruction based on the elements mentioned in the case assignment message
covers one and only one instruction at a time. If several payment instruction copies are needed by the case assignee, then multiple Request For Duplicate messages must be sent
must be used exclusively between the case assignee and its case creator/case assigner.

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

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

Assignment building block

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

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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    RequestForDuplicateInstruction --|> IOuterRecord : Implements
    RequestForDuplicateInstructionDocument --|> IOuterDocument~RequestForDuplicateInstruction~ : Implements
    class IOuterDocument~RequestForDuplicateInstruction~ {
        RequestForDuplicateInstruction Message
     }

Document wrapper for serialization

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

classDiagram
    RequestForDuplicateInstructionDocument *-- RequestForDuplicateInstruction : 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.033.001.01">
    <camt.033.001.01>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <Case>
            <!-- Case inner content -->
        </Case>
    </camt.033.001.01>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_RNxXSNE_Ed-BzquC8wXy7w_-694421225"
  name="RequestForDuplicateInstruction"
  definition="Scope&#xA;The Request For Duplicate message is sent by the case assignee to the case creator or case assigner.&#xA;This message is used to request a copy of the original payment instruction considered in the case.&#xA;Usage&#xA;The Request For Duplicate message: &#xA;- must be answered with a Duplicate message&#xA;- must be used when a case assignee requests a copy of the original payment instruction. This occurs, for example, when the case assignee cannot trace the payment instruction based on the elements mentioned in the case assignment message&#xA;- covers one and only one instruction at a time. If several payment instruction copies are needed by the case assignee, then multiple Request For Duplicate messages must be sent&#xA;- must be used exclusively between the case assignee and its case creator/case assigner."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlName="camt.033.001.01"
  xmlTag="camt.033.001.01"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_RNxXSdE_Ed-BzquC8wXy7w_1708467998"
    name="Assignment"
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Assgnmt"
    complexType="_T9Dpetp-Ed-ak6NoX_4Aeg_588710247" />
  <messageBuildingBlock
    xmi:id="_RNxXStE_Ed-BzquC8wXy7w_1751874887"
    name="Case"
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Case"
    complexType="_SpAnotp-Ed-ak6NoX_4Aeg_136183535" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="033"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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