ZagTrader

semt: Securities Management

semt.001 Securities Message Rejection

Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked

semt.001 is the ISO 20022 SecuritiesMessageRejection message in the Securities Management business area (semt). The latest version is semt.001.001.04, and 4 versions are in the repository.

Message
SecuritiesMessageRejection
Latest version
semt.001.001.04
Submitting organisation
Not read from the catalogue
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What semt.001 is for

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.

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.

Definition from the ISO 20022 e-Repository, release of 24 April 2025.

semt.001 versions

Every version published in the e-Repository, newest first. A message keeps its business purpose across versions; each new version is a separate schema with its own namespace.

VersionRegistration statusPublished in
semt.001.001.04latestRegisteredLatest version set
semt.001.001.03RegisteredLatest version set
semt.001.001.02RegisteredPrevious version set
semt.001.001.01RegisteredArchive

semt.001 message structure

The building blocks of semt.001.001.04 to three levels, with multiplicity ([0..1] optional, [1..1] mandatory, * any number) and the data type or component. Element names and definitions are from the ISO 20022 repository; usage guidelines such as CBPR+ or a market infrastructure's rules can restrict them further.

  • Document [1..1]
    • SctiesMsgRjctn SecuritiesMessageRejection [1..1]
      • RltdRef Related Reference [1..1]AdditionalReference14

        Reference to a linked message that was previously received.

        • Ref Reference [1..1]Max35Text

          Business reference of a message assigned by the party issuing the message.

        • RefIssr Reference Issuer [0..1]PartyIdentification247Choice (choice)

          Issuer of the reference.

          • AnyBIC Any BIC [1..1]AnyBICDec2014Identifier
          • PrtryId Proprietary Identification [1..1]GenericIdentification36
          • NmAndAdr Name And Address [1..1]NameAndAddress5
        • MsgNm Message Name [0..1]Max35Text

          Name of a message.

        • MsgNb Message Number [1..1]DocumentNumber5Choice (choice)

          Identification of the type of message.

          • ShrtNb Short Number [1..1]Exact3NumericText
          • LngNb Long Number [1..1]ISO20022MessageIdentificationText
          • PrtryNb Proprietary Number [1..1]GenericIdentification36
      • Rsn Reason [1..1]RejectionReason69

        Reason to reject the message.

        • Rsn Reason [1..1]MessageRejectedReason2Code

          Reason to reject the message.

        • AddtlInf Additional Information [0..1]Max350Text

          Additional information about the rejection reason.

        • LkdMsg Linked Message [0..1]LinkedMessage6Choice (choice)

          Identification of the invalid or unrecognised reference.

          • PrvsRef Previous Reference [1..1]AdditionalReference14
          • OthrRef Other Reference [1..1]AdditionalReference14
          • RltdRef Related Reference [1..1]AdditionalReference14

Have a semt.001 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.

semt.001 questions

What is the latest version of semt.001?
The latest version in the ISO 20022 e-Repository release of 24 April 2025 is semt.001.001.04.
What is the root element of semt.001?
The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:semt.001.001.04, and its message element is SctiesMsgRjctn (SecuritiesMessageRejection).
Is there an MT equivalent of semt.001?
No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.

All ISO 20022 messages · ISO 20022 code sets · MT messages

The ISO 20022 message definitions, element names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.