Scope
An account servicer, for example, a registrar, transfer agent, first intermediary or custodian bank, sends the SecuritiesMessageRejection message to the sender (for example account owner, an investor, an issuer 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 sender doesn't comply with minimum requirements to allow processing at first intermediary level (for example for seev.045, seev.001, seev.031). The SecuritiesMessageRejection message must not be used to reject an instruction message (for example sese.023, seev.004, seev.047, seev.033) 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. The message should be used with the business Application Header.Outline
The SecuritiesMessageRejectionV04 MessageDefinition is composed of 2 MessageBuildingBlocks:
- Related Reference — Reference to a linked message that was previously received.
- Reason — Reason to reject the message.
SecuritiesMessageRejectionV04
SctiesMsgRjctn
Mandatory
Type: SecuritiesMessageRejectionV04
RltdRef
Mandatory
Rsn
Mandatory