Message TradeMatchReport (DC)

The TradeMatchReport (DC) message is used by exchanges and ECN’s to report matched trades to central counterparties (CCPs) as an atomic event. The message is used to express the one-to-one, one-to-many and many-to-many matches as well as implied matches in which more complex instruments can match with simpler instruments.

Added in protocol FIX.5.0SP2 (150)

Field or Component	Name	Description	Is Required	Added
Block	StandardHeader	MsgType=DC	Y	FIX.5.0SP2 (150)
Block	ApplicationSequenceControl			FIX.5.0SP2 (150)
880	TrdMatchID	Unique identifier common for all trades included in a match event.	Y	FIX.5.0SP2 (150)
574	MatchType			FIX.5.0SP2 (150)
856	TradeReportType			FIX.5.0SP2 (150)
715	ClearingBusinessDate			FIX.5.0SP2 (150)
828	TrdType			FIX.5.0SP2 (150)
829	TrdSubType			FIX.5.0SP2 (150)
75	TradeDate	Used when reporting other than current day trades.		FIX.5.0SP2 (150)
1301	MarketID			FIX.5.0SP2 (150)
1300	MarketSegmentID			FIX.5.0SP2 (150)
336	TradingSessionID			FIX.5.0SP2 (150)
625	TradingSessionSubID			FIX.5.0SP2 (150)
1430	VenueType			FIX.5.0SP2 (150)
1888	TradeMatchTimestamp			FIX.5.0SP2 (150)
60	TransactTime	Time of the match event or transaction that resulted in this match report.		FIX.5.0SP2 (150)
442	MultiLegReportingType	Differentiates match events involving complex instruments (MultiLegReportingType (442)=3(multileg security)) from those only involving simple instruments (MultiLegReportingType (442)=1(single security)). MultiLegReportingType (442)=2(individual leg of multileg security) should not be used.		FIX.5.0SP2 (150)
BlockRepeating	InstrmtMatchSideGrp	Conditionally required when TradeReportType (856) = Submit(0).		FIX.5.0SP2 (150)
Block	StandardTrailer		Y	FIX.5.0SP2 (150)