DataSetMatchReportV03

Scope
The DataSetMatchReport message is sent by the matching application to the parties involved in a data set match.
This message is used to either
- inform about the successful match of data sets submitted with the instruction match or pre-match (DataSetSubmission message) and the related baseline,or
- inform about mis-matches found between data sets submitted with the instruction match or pre-match (DataSetSubmission message) and the related baseline.
Usage
The DataSetMatchReport message can be sent by the matching application to the party requesting a data set pre-match for a transaction established in the push-through mode. In the outlined scenario, the DataSetMatchReport message will either inform about the successful pre-match or list the mis-matches between the data set(s) conveyed with the DataSetSubmission message and the related baseline.
or
The DataSetMatchReport message can be sent by the matching application to the parties involved in a data set match for a transaction established in the push-through mode. In the outlined scenario, the DataSetMatchReport message will either inform about the successful match or list the mis-matches between the data set(s) conveyed with the DataSetSubmission message and the related baseline.
or
The DataSetMatchReport message can be sent by the matching application to the party requesting a data set match or pre-match for a transaction established in the lodge mode. In the outlined scenario, the DataSetMatchReport will either inform about the successful match or list the mis-matches between the data set(s) conveyed with the DataSetSubmission message and the related baseline.

Message Identifier: tsmt.013.001.03

Elements

Name	Type	Multiplicity	Definition
ReportIdentification	MessageIdentification1	[1..1]	Identifies the report.
TransactionIdentification	SimpleIdentificationInformation	[1..1]	Unique identification assigned by the matching application to the transaction. This identification is to be used in any communication between the parties.
EstablishedBaselineIdentification	DocumentIdentification3	[1..1]	Unique identification assigned by the matching application to the baseline when it is established.
TransactionStatus	TransactionStatus4	[1..1]	Identifies the status of the transaction by means of a code.
UserTransactionReference	DocumentIdentification5	[0..2]	Reference to the transaction for each financial institution which is a party to the transaction.
Buyer	PartyIdentification26	[1..1]	Party that buys goods or services, or a financial instrument.
Seller	PartyIdentification26	[1..1]	Party that sells goods or services, or a financial instrument.
BuyerBank	BICIdentification1	[1..1]	The financial institution of the buyer, uniquely identified by its BIC.
SellerBank	BICIdentification1	[1..1]	The financial institution of the seller, uniquely identified by its BIC.
ComparedDocumentReference	DocumentIdentification10	[2..∞]	Identifies the documents compared in this report.
SubmissionType	ReportType3	[1..1]	Specifies whether the data set was submitted for match or pre-match.
Report	MisMatchReport3	[1..1]	Description of the differences between the data set(s) and the baseline.
RequestForAction	PendingActivity2	[0..1]	Information on the next processing step required.