CLOB Orders.
Algo Orders.
Please refer to Whisperer Enterprise - Supported Instruments for the full Enterprise table across all venues.
Please refer to Whisperer Enterprise - PartyIDs for the full Enterprise table across all venues.
Please refer to or Regulatory Fields for the full Enterprise table across all venues.
Please refer to Passthru Fields for the full Enterprise table across all venues.
Whisperer Enterprise has LSEG SPT implementation but LSEG is not ready to certify SPT product. So strictly SPT support is for UAT only and not for PROD. Latest Email confirmation from LSEG: Dear valued customer,
Through these changes, our intention is to focus on delivering faster, incremental change in the areas most important to our customers. As always, if you have any questions regarding the changes, please contact your account manager. |
Refer to Supported Order Types (Algo Orders) for details on how to use the |
In addition to standard Iceberg orders, LSEG FX also supports the specification of Iceberg orders with more complex attributes, which are offered as a standard Algo strategy.
The table below sets out the Iceberg order Strategy parameters and combinations currently supported.
| StrategyParameterName | StrategyParameterType | StrategyParameterValue | |
|---|---|---|---|
TargetStrategy | String | Iceberg | |
TipSpecificationType | String | Defined | Random |
FirstTip | Qty | Mandatory | - |
SecondTip | Qty | Optional | - |
ThirdTip | Qty | Optional | - |
MinimumRandomTip | Qty | - | Mandatory |
MaximumRandomTip | Qty | - | Mandatory |
Delay | Int | Optional | Optional |
LSEG supports a standard TradeCancel and TradeCorrect workflow for SPOT trades and an offset Trade Correct/Cancel workflow for NDFs.
For Spot trades, Clients will be notified of these in a separate ExecutionReport with ExecType = TradeCorrect or TradeCancel as appropriate.
| Trade Correction/Cancellation may occur up to two trading days after the trade execution. |
Depending on the scenario, possible fields to be modified are listed below:
LegLastPx or LegSettlDate, then a single ExecutionReport is sent with an ExecType TradeCorrect and OrdStatus Filled or PartiallyFilled depending on the quantity remaining on the order.LegLastQty, then the cancelled or reduced quantity will not be added to the order book. In this case, the Client will receive two ExecutionReports with variations outlined below:TradeCorrect (Quantity reduction) | Inactive order | Active order | ||
|---|---|---|---|---|
| ExecType | OrdStatus | ExecType | OrdStatus | |
| First ExecutionReport | TradeCorrect | PartiallyFilled | TradeCorrect | PartiallyFilled |
| Second ExecutionReport | Restated | Filled | Restated | PartiallyFilled |
| TradeCancel | Inactive order | Active order | ||
|---|---|---|---|---|
| ExecType | OrdStatus | ExecType | OrdStatus | |
| First ExecutionReport | TradeCancel | New | TradeCancel | PartiallyFilled |
| Second ExecutionReport | Canceled | Canceled | Restated | Filled |
First ExecutionReport will indicate the canceled or reduced qty in LegLeavesQty.
Second ExecutionReport is sent to reflect the reduced or cancelled quantity in LegOrderQty.
The LegLeavesQty and LegCumQty of an active order will always add up to its LegOrderQty.
ExecRefID - Trade Correct/Cancel ExecutionReports ExecRefID matches with the ExecID of the trade that is being cancelled or corrected.
BodyPassThruKey TrdMatchID - TrdMatchID of the Trade Correct/Cancel ExecutionReport matches with TrdMatchID of the trade that is being cancelled or corrected.
SecondaryExecID - SecondaryExecID of the Trade Correct/Cancel ExecutionReport matches with the SecondaryExecID of the trade that is being cancelled or corrected.
For NDFs, as opposed to standard Trade Correct/Cancel workflow, LSEG will deliver new offset trades to adjust the positions as necessary. This is due to the fact that NDFs are always Cleared and LSEG cannot amend or cancel an already Cleared trade.
Clients will be notified of Trade cancellation in an ExecutionReport with:
ClOrdID and OrigClOrdID of the offset trade will match with the original trade.ExecType and OrdStatus will be Trade and Filled respectively.ExecRefID of the offset trade will match the ExecID of the original trade.SecondaryExecID of the offset trade will match the BodyPassThruKey TrdMatchID of the original trade.LegSide of the offset trade will be the reverse of the original trade.BodyPassthruKey ClearedIndicator will be set to "Submitted".BodyPassthruKey ClearingIntention will be set to "IntendToClear".Text field of the offset trade is populated with "Offset Trade".In case of Offset Trade correction, Clients will receive two ExecutionReports:
Features not yet supported by LSEG FX:
Features not required by Whisperer Enterprise:
|
Clients must populate |