SecuritiesMessageRejection

semt.001.001.01

Scope The SecuritiesMessageRejection message is sent by an executing party to the instructing party. Typically, this message is sent by an account servicer to the account owner. This message is used to reject a previously received message on which action cannot be taken. Usage The SecuritiesMessageRejection message can be sent 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. This could be because the Receiver does not expect the message, eg, there is 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, eg, 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
%% SecuritiesMessageRejection recursion level 0 with max 0
SecuritiesMessageRejection *-- "1..1" AdditionalReference2 : RelatedReference
SecuritiesMessageRejection *-- "1..1" RejectionReason1 : Reason
  

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

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
%% AdditionalReference2 recursion level 0 with max 1
class AdditionalReference2{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference2 *-- "0..1" IPartyIdentification1Choice : ReferenceIssuer
%% IPartyIdentification1Choice recursion level 1 with max 1
  

AdditionalReference2 members

Reason building block

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

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

RejectionReason1 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    SecuritiesMessageRejection --|> IOuterRecord : Implements
    SecuritiesMessageRejectionDocument --|> IOuterDocument~SecuritiesMessageRejection~ : Implements
    class IOuterDocument~SecuritiesMessageRejection~ {
        SecuritiesMessageRejection Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesMessageRejectionDocument *-- SecuritiesMessageRejection : 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.01">
    <semt.001.001.01>
        <RltdRef>
            <!-- RelatedReference inner content -->
        </RltdRef>
        <Rsn>
            <!-- Reason inner content -->
        </Rsn>
    </semt.001.001.01>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_MV4gpdFSEd-BzquC8wXy7w_952968106"
  nextVersions="_MaWw_NFSEd-BzquC8wXy7w_-365444555"
  name="SecuritiesMessageRejection"
  definition="Scope&#xD;&#xA;The SecuritiesMessageRejection message is sent by an executing party to the instructing party. Typically, this message is sent by an account servicer to the account owner.&#xD;&#xA;This message is used to reject a previously received message on which action cannot be taken.&#xD;&#xA;Usage&#xD;&#xA;The SecuritiesMessageRejection message can be sent 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. This could be because the Receiver does not expect the message, eg, there is 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, eg, if information is missing in an instruction message or because securities are not available for settlement."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlName="semt.001.001.01"
  xmlTag="semt.001.001.01"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_MV4gptFSEd-BzquC8wXy7w_1002836384"
    name="RelatedReference"
    definition="Reference to a linked message that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RltdRef"
    complexType="_RNE1Kdp-Ed-ak6NoX_4Aeg_-577369889" />
  <messageBuildingBlock
    xmi:id="_MV4gp9FSEd-BzquC8wXy7w_1267886367"
    name="Reason"
    definition="Reason to reject the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Rsn"
    complexType="_U3LIX9p-Ed-ak6NoX_4Aeg_-2025393824" />
  <messageDefinitionIdentifier
    businessArea="semt"
    messageFunctionality="001"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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