This functionality makes the broker fees information submitted on CME ClearPort API available to CME STP consumers. Detailed information on CME ClearPort API support of broker fees is available here.
Contents
Table of Contents |
---|
Testing and Certification
Certification is mandatory for CME STP customers planning to utilize the new broker fee attributes and the CommData element.
Testing is recommended to ensure a smooth experience for customers not planning to utilize broker fee attributes.
Contact Information
Trade Flow
Broker fee submission on new trades and fee updates on existing trades will be supported for Outrights, Spreads and Allocations via CME ClearPort API.
Flow from CME ClearPort API to CME STP to Customer
Gliffy | ||||||
---|---|---|---|---|---|---|
|
CommData Element
CME STP trade reports have a dedicated block, the CommData element, for broker fees. Valid attributes are:
Name | Abbr | Data Type | Description |
Basis | Basis | Integer | Type of Rate initially allowed for broker fees: 1 = Per Unit 2 = Percentage 8 = Per Contract |
Rate | Rt | Decimal | Rate per basis. For example, $1 per contract. |
Unit of measure | UOM | String | Unit of measure for trade. |
Unit of Measure Currency | UOMCcy | String | Currency unit of measure for trade. |
Currency | Ccy | String | Trade currency. Default is USD. |
Leg Reference ID | LegRefID | Integer | Trade leg identifier.Required on all CommData legs of a spread. |
Info |
---|
Where accounts are allocated on only one side of the trade, the broker can only submit broker fees at the side level (RptSide) and the same Basis, Rt, Ccy; and an enriched UOM and UOMCcy will be reported on CME STP at the Side/Leg level for each allocation. |
Note | |
---|---|
| |
| |
Certain fee updates may not be passed through. Broker fees will not be published on CME STP Trade Capture Reports resulting from the following post-trade allocations:
Although these post-trade activities may change the ownership of the trade, the Broker Fees will only be available to the original trade owner. |
FIXML Structure Rules
The order of elements is critical in FIXML so the new Broker fees element should always be in the following order:
- After RegTrdID and
- Before TrdRegTS
The new CommData element will be present in the RptSide messaging component.
Each CommData element will represent one Broker fee.
Sample Messages
Outright Crude Oil Trade - No Legs
Info |
---|
There are no LegRefIDs as this is an Outright.
|
Expand | |||||||
---|---|---|---|---|---|---|---|
Line 20 in this Trade Capture Report message sample introduces the new CommData block:
|
Spread Natural Gas Trade - Multiple Legs
Info |
---|
There are multiple LegRefID values as this is a Spread.
|
Expand | |||||||
---|---|---|---|---|---|---|---|
Lines 39-43 in this Trade Capture Report message sample introduces the new CommData block:
|