DataSetMatchReportV03 (DataSetMtchRpt)

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.

Outline

The DataSetMatchReportV03 MessageDefinition is composed of 13 MessageBuildingBlocks:

Report Identification — Identifies the report.
Transaction Identification — Unique identification assigned by the matching application to the transaction. This identification is to be used in any communication between the parties.
Established Baseline Identification — Unique identification assigned by the matching application to the baseline when it is established.
Transaction Status — Identifies the status of the transaction by means of a code.
User Transaction Reference — Reference to the transaction for each financial institution which is a party to the transaction.
Buyer — Party that buys goods or services, or a financial instrument.
Seller — Party that sells goods or services, or a financial instrument.
Buyer Bank — The financial institution of the buyer, uniquely identified by its BIC.
Seller Bank — The financial institution of the seller, uniquely identified by its BIC.
Compared Document Reference — Identifies the documents compared in this report.
Submission Type — Specifies whether the data set was submitted for match or pre-match.
Report — Description of the differences between the data set(s) and the baseline.
Request For Action — Information on the next processing step required.