CME STP FIX - TradeCaptureReport - BrokerTec FI
The Trade Capture Report Request (tag 35-MsgTyp=AE) message will be delivered FIX Client, to indicate their detailed trading activity on BrokerTec Markets on CME Globex and BrokerTec Direct.
Messages are comprised of component blocks, which may be non-repeating or repeating. Component block contain FIX fields/tags that define the trade characteristics.
Repeating component blocks are indicated by "(repeating)" in the gray highlighted definition row.
Some components, such as Instrument component, have a large number of fields, and are therefore allocated their own page.
The first defined component block level on any specification page is considered the highest level for that page. Component blocks may have sub-component blocks on the same page, as indicated by an arrow (→) preceding the field name.
A sub-component one level down contains an arrow preceding it in the field name, for example:
→ Sender ID
Two levels down will have two preceding arrows:
→→ Leg Underlying Product Code
The highest level on any page will not be preceded by an arrow, though it may still be a sub-component. For example, Instrument is a sub-component of Trade Capture Report Message, but because it is the highest level for that page, the Field Names will not be preceded by an arrow.
The first field in a repeating group is the leading tag, and mandatory when the corresponding tag indicating the number of blocks in the group (format = NuminGroup) is greater than 0. This allows implementations of the Protocol to use the first field as a "delimiter" indicating a new repeating group entry. If a repeating group field is listed as required, then it must appear in every repeated instance of that repeating group. Nested repeating groups are designated within the message definition with '→' and a repeating tag within a repeating group is designated with double indentation'→→'
FIX Tag | Field Name | Data Type | Description | Supported Values |
---|---|---|---|---|
571 | TradeReportID | String | Unique identifier of the TradeCaptureReport message. Use to check for duplicate Trade Capture Reports. Up to a maximum of 63 characters. |
|
1003 | TradeID | String | The unique ID assigned to the trade entity once it is received or matched by the exchange or central counterparty. However this value is not unique across all BTEC products i.e. Repo GC, Repo Special/GCF, and cash. |
|
1040 | SecondaryTradeID | String | Globally unique across different BrokerTec products and recommended to be used to uniquely identify a trade. For GC Repo, this tag in TradeCaptureReport (35=AE) ties to it's CollateralReport (35=BA). |
|
10036 | PackageID | String | This field points (forward) to tag 1040-SecondaryTradeID on the trade replacing this trade. This field is only populated when the trade has been replaced as a result of an amendment |
|
487 | TradeReportTransType | int | Identifies Trade Report message transaction type(Prior to FIX 4.4 this field was of type char) |
|
856 | TradeReportType | int | Type of Trade Report | 101 - Notification |
939 | TrdRptStatus | int | Trade Report Status |
|
568 | TradeRequestID | String | Trade Capture Report Request ID |
|
828 | TrdType | int | Type of Trade: |
|
880 | TrdMatchID | String | Identifier assigned to a trade by a matching system. |
|
820 | TradeLinkID | String | Used to link a group of trades together. Useful for linking a group of trades together for average price calculations. |
|
2490 | TradeNumber | String |
|
|
20011 | DealID | String | BrokerTec Deal ID, common to all participants within an entire trade (not only a match) |
|
17 | ExecID | String | Unique identifier of execution message as assigned by sell-side. Uniqueness must be guaranteed within a single trading day or the life of a multi-day order. Firms which accept multi-day orders should consider embedding a date within the ExecID field to assure uniqueness across days.(Prior to FIX 4.1 this field was of type int). |
|
527 | SecondaryExecID | String | Assigned by the Liquidity Provider (LP) who accepts the order. Will be populated with Liquidity Provider's (LP) ExecID (17) only on disclosed tickets. |
|
423 | PriceType | int | Code to represent the price type.(For Financing transactions PriceType implies the "repo type" - Fixed or Floating - 9 (Yield) or 6 (Spread) respectively - and Price (44) gives the corresponding "repo rate". |
|
1430 | VenueType | char | Identifies the type of venue where a trade was executed |
|
32 | LastQty | Qty | Quantity (e.g. shares) bought/sold on this (last) fill. |
|
31 | LastPx | Price | Price of this (last) fill. Will support values up to 9 decimal places of precision. |
|
75 | TradeDate | LocalMktDate | Indicates date of trade referenced in this message in YYYYMMDD format. Absence of this field indicates current day (expressed in local time at place of trade). |
|
715 | ClearingBusinessDate | LocalMktDate | The "Clearing Business Date" referred to by this maintenance request. |
|
442 | MultiLegReportingType | char | Used to indicate what an Execution Report represents (e.g. used with multi-leg securities, such as spreads, etc.). |
|
60 | TransactTime | UTCTimestamp | Timestamp when the business transaction represented by the message occurred. |
|
64 | SettlDate | LocalMktDate | Specific date of trade settlement (SettlementDate) in YYYYMMDD format. If present, this field overrides SettlType (63). This field is required if the value of SettlType (63) is 6 (Future) or 8 (Sellers Option). This field must be omitted if the value of SettlType (63) is 7 (When and If Issued)(expressed in local time at place of settlement) |
|
779 | LastUpdateTime | UTCTimestamp | Used to indicate the date and time that internal transaction processing of the trade or allocation completed. Should occur on or after the Transaction Time. | Format: YYYYMMDD-HH:MM:SS.sTZD (UTC time zone) Example: 20200520-01:14:39.126000000Z |
1832 | ClearedIndicator | int | Indicates whether the position or trade being reported was cleared through a clearing organization. |
|
10033 | DifferentialPrice | float | Represents the Differential Price for Spreads. |
|
10024 | DifferentialPriceType | int | This indicates the type of differential price represented in the Differential Type attribute. |
|
37711 | MarketDataTradeEntryID | String | Unique Trade Identifier that will match to a CME Globex order execution, associated market data message and STP messaging |
|
10053 | SplitIndicator | char | Indicates whether or not a trade is split |
|
20043 | AlternatePrice | Price | Alternate Price. Trade price in Price format or Yield depending on actual trade price 31-LastPx |
|
20056 | SettlementTradeID | String | Trade identifier as assigned by BrokerTec Clearing. |
|
30 | LastMkt | Exchange | Market of execution for last fill, or an indication of the market where an order was routed. MIC Code for BrokerTec Markets |
|
20400 | NonDisclosedIndicator | String | A flag indicating if this was a non-disclosed trade.
| Y |
20060 | VenueSubType | String | Identifies the sub-type of the venue where a trade was executed. |
|
1500 | MDStreamID | String | The identifier or name of the price stream. | e.g. "GOLD", "Z1AC" etc. |
| Instrument details | |||
916 | →StartDate | LocalMktDate | Start date of a financing deal, i.e. the date the buyer pays the seller cash and takes control of the collateral |
|
917 | →EndDate | LocalMktDate | End date of a financing deal, i.e. the date the seller reimburses the buyer and takes back control of the collateral |
|
711 | Underlying Instrument | |||
555 | Leg details of the Spread trade | |||
552 |
|
|
| |
2668 | TrdRegPublicationGrp |
|
|
|
→2669 | →TrdRegPublicationType | int |
| 2 - Exempt from publication |
→2670 | →TrdRegPublicationReason | int |
| 12 - Exempted due to European System of Central Banks (ESCB) policy transactions |
Related content
How was your Client Systems Wiki Experience? Submit Feedback
Copyright © 2024 CME Group Inc. All rights reserved.