ZagTrader

tsmt: Trade Services Management

tsmt.020 Mis Match Acceptance

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

tsmt.020 is the ISO 20022 MisMatchAcceptance message in the Trade Services Management business area (tsmt). The latest version is tsmt.020.001.02.

Message
MisMatchAcceptance
Latest version
tsmt.020.001.02
Submitting organisation
Not read from the catalogue
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What tsmt.020 is for

The MisMatchAcceptance message is sent by the party requested to accept or reject data set mis-matches to the matching application.

This message is used to accept mis-matches between data sets and the related baseline.

The MisMatchAcceptance message can be sent by the party requested to accept or reject data set mis-matches to inform that it accepts the data sets.

The message can be sent in response to a DataSetMatchReport message conveying mis-matches.

The information about the acceptance of the mis-matched data sets will be forwarded by the matching application to the submitter of the data sets by a MisMatchAcceptanceNotification message.

The rejection of mis-matched data sets can be achieved by sending a MisMatchRejection message.

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

tsmt.020 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
tsmt.020.001.02latestRegisteredLatest version set

tsmt.020 message structure

The building blocks of tsmt.020.001.02 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]
    • MisMtchAccptnc MisMatchAcceptance [1..1]
      • AccptncId Acceptance Identification [1..1]MessageIdentification1

        Identifies the acceptance message.

        • Id Identification [1..1]Max35Text

          Identification of the message.

        • CreDtTm Creation Date Time [1..1]ISODateTime

          Date of creation of the message.

      • TxId Transaction Identification [1..1]SimpleIdentificationInformation

        Unique identification assigned by the matching application to the transaction.

        • Id Identification [1..1]Max35Text

          Name or number assigned by an entity to enable recognition of that entity, eg, account identifier.

      • SubmitrTxRef Submitter Transaction Reference [0..1]SimpleIdentificationInformation

        Reference to the transaction for the requesting financial institution.

        • Id Identification [1..1]Max35Text

          Name or number assigned by an entity to enable recognition of that entity, eg, account identifier.

      • DataSetMtchRptRef Data Set Match Report Reference [1..1]MessageIdentification1

        Reference to the identification of the report that contained the difference.

        • Id Identification [1..1]Max35Text

          Identification of the message.

        • CreDtTm Creation Date Time [1..1]ISODateTime

          Date of creation of the message.

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

tsmt.020 questions

What is the latest version of tsmt.020?
The latest version in the ISO 20022 e-Repository release of 24 April 2025 is tsmt.020.001.02.
What is the root element of tsmt.020?
The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:tsmt.020.001.02, and its message element is MisMtchAccptnc (MisMatchAcceptance).
Is there an MT equivalent of tsmt.020?
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.