SecuritiesMessageRejectionV03semt.001.001.03

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.

Outline

The SecuritiesMessageRejectionV03 MessageDefinition is composed of 3 MessageBuildingBlocks:

  • Message Identification — Reference that uniquely identifies a message from a business application standpoint.
  • Related Reference — Reference to a linked message that was previously received.
  • Reason — Reason to reject the message.

SecuritiesMessageRejectionV03

SctiesMsgRjctn
Mandatory

Type: SecuritiesMessageRejectionV03

Mandatory
Mandatory
Rsn
Mandatory
Executing PartyInstructing PartySecuritiesMessageRejectionV03
We use cookies to personalize content and ads, as well as to analyze our traffic. We also share information about your use of our site with our advertising and analytics partners who may combine it with other information that you've provided to them or that they've collected from your use of their services.
DenyAllow