SecuritiesMessageRejectionV02

semt.001.001.02

Scope An account servicer, for example, a registrar, transfer agent or custodian bank, sends the SecuritiesMessageRejection message to the account owner, for example, an investor or its authorised agent, to reject a previously received message on which action cannot be taken. The message may also be sent by an executing party, for example, transfer agent to the instructing party, for example, investment manager or its authorised representative to reject a previously received message on which action cannot be taken. Usage The SecuritiesMessageRejection message is used for the following reasons:

• the executing party does not recognise the linked reference, so the executing party cannot process the message
• the instructing party should not have sent the message. Reasons that a receiver does not expect a message include no SLA in place between the Sender and the Receiver. The SecuritiesMessageRejection message must not be used to reject an instruction message that cannot be processed for business reasons, for example, if information is missing in an instruction message or because securities are not available for settlement.

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
%% SecuritiesMessageRejectionV02 recursion level 0 with max 0
SecuritiesMessageRejectionV02 *-- "1..1" MessageIdentification1 : MessageIdentification
SecuritiesMessageRejectionV02 *-- "1..1" AdditionalReference3 : RelatedReference
SecuritiesMessageRejectionV02 *-- "1..1" RejectionReason3 : Reason
  

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

MessageIdentification building block

Reference that uniquely identifies a message from a business application standpoint. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
  

MessageIdentification1 members

RelatedReference building block

Reference to a linked message that was previously received. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalReference3 recursion level 0 with max 1
class AdditionalReference3{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer
%% IPartyIdentification2Choice recursion level 1 with max 1
  

AdditionalReference3 members

Reason building block

Reason to reject the message. Reason to reject the message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% RejectionReason3 recursion level 0 with max 1
class RejectionReason3{
    Reason MessageRejectedReason1Code
    AdditionalInformation IsoMax140Text
}
RejectionReason3 *-- "0..1" AdditionalReference3 : LinkedMessagePreviousReference
RejectionReason3 *-- "0..1" AdditionalReference3 : LinkedMessageOtherReference
RejectionReason3 *-- "0..1" AdditionalReference3 : LinkedMessageRelatedReference
%% AdditionalReference3 recursion level 1 with max 1
class AdditionalReference3{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer
%% AdditionalReference3 recursion level 1 with max 1
class AdditionalReference3{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer
%% AdditionalReference3 recursion level 1 with max 1
class AdditionalReference3{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer
  

RejectionReason3 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    SecuritiesMessageRejectionV02 --|> IOuterRecord : Implements
    SecuritiesMessageRejectionV02Document --|> IOuterDocument~SecuritiesMessageRejectionV02~ : Implements
    class IOuterDocument~SecuritiesMessageRejectionV02~ {
        SecuritiesMessageRejectionV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesMessageRejectionV02Document *-- SecuritiesMessageRejectionV02 : 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:semt.001.001.02">
    <SctiesMsgRjctnV02>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <RltdRef>
            <!-- RelatedReference inner content -->
        </RltdRef>
        <Rsn>
            <!-- Reason inner content -->
        </Rsn>
    </SctiesMsgRjctnV02>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_MaWw_NFSEd-BzquC8wXy7w_-365444555"
  nextVersions="_b2f30QgJEeSFYfyUKDXKaw"
  previousVersion="_MV4gpdFSEd-BzquC8wXy7w_952968106"
  name="SecuritiesMessageRejectionV02"
  definition="Scope&#xD;&#xA;An account servicer, for example, a registrar, transfer agent or custodian bank, sends the SecuritiesMessageRejection message to the account owner, for example, an investor or its authorised agent, to reject a previously received message on which action cannot be taken.&#xD;&#xA;The message may also be sent by an executing party, for example, transfer agent to the instructing party, for example, investment manager or its authorised representative to reject a previously received message on which action cannot be taken.&#xD;&#xA;Usage&#xD;&#xA;The SecuritiesMessageRejection message is used for the following reasons:&#xD;&#xA;- the executing party does not recognise the linked reference, so the executing party cannot process the message&#xD;&#xA;- the instructing party should not have sent the message.&#xD;&#xA;Reasons that a receiver does not expect a message include no SLA in place between the Sender and the Receiver.&#xD;&#xA;The SecuritiesMessageRejection message must not be used to reject an instruction message that cannot be processed for business reasons, for example, if information is missing in an instruction message or because securities are not available for settlement."
  registrationStatus="Registered"
  messageSet="_wFQdsE2rEeG_I4xRYCA_7g _urpIICeJEeOCeO5e7islRQ"
  xmlTag="SctiesMsgRjctnV02"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_MaWw_dFSEd-BzquC8wXy7w_2101589408"
    nextVersions="_b2f30wgJEeSFYfyUKDXKaw"
    name="MessageIdentification"
    definition="Reference that uniquely identifies a message from a business application standpoint."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_MaWw_tFSEd-BzquC8wXy7w_-365444294"
    nextVersions="_b2f31QgJEeSFYfyUKDXKaw"
    name="RelatedReference"
    definition="Reference to a linked message that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RltdRef"
    complexType="_Q6vvAdp-Ed-ak6NoX_4Aeg_2101402955" />
  <messageBuildingBlock
    xmi:id="_Magh8NFSEd-BzquC8wXy7w_-365444259"
    nextVersions="_b2f31wgJEeSFYfyUKDXKaw"
    name="Reason"
    definition="Reason to reject the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Rsn"
    complexType="_RPdazNp-Ed-ak6NoX_4Aeg_680923273" />
  <messageDefinitionIdentifier
    businessArea="semt"
    messageFunctionality="001"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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