The Lab

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 1.5.16

Table of Contents

Workflow

DropCopy

Supported Instruments

Expand
Table Filter
totalrow,,,,,,,,,,,,
hidelabelsfalse
sparkNameSparkline
hidePanetrue
sparklinefalse
defaultlseg_ptg,MDBookType(PricingSession)&&MDEntryType(PricingSession)&&ExecutionVenue&&client_role&&MDBookType (SessionType == Pricing)&&MDEntryType (SessionType == Pricing)&&target_platform&&MDBookType&&MDEntryType
isFirstTimeEnterfalse
cell-width250,250
hideColumnstrue
customNoTableMsgfalse
disabledfalse
enabledInEditorfalse
globalFilterfalse
id1721905708257_-952198823
order0,1
hideControlsfalse
inversefalse,false
columnVenue
disableSavefalse
separatorPoint (.)
labelsVenue‚Hide columns
ddOperatorOR
datepatterndd M yy
updateSelectOptionsfalse
worklog365|5|8|y w d h m|y w d h m
isORAND
Table Excerpt Include
nameSupportedInstruments
merge-tablestrue
pageSupported Instruments
typepage

Please refer to Supported Instruments to view across all venues.

PartyIDs

Expand
Table Filter
totalrow,,,
hidelabelsfalse
sparkNameSparkline
hidePanetrue
sparklinefalse
defaultlseg_ptg
isFirstTimeEnterfalse
cell-width150
hideColumnsfalse
customNoTableMsgfalse
disabledfalse
enabledInEditorfalse
globalFilterfalse
id1721905721810_-1288440624
order0
hideControlstrue
inversefalse
disableSavefalse
separatorPoint (.)
labelsVenue
userfilterVenue
datepatterndd M yy
updateSelectOptionsfalse
worklog5|8|w d h m|w d h m
isORAND

Table Excerpt Include
copytabletrue
namePartyIDs
pagePartyIDs
typepage

Please refer to PartyIDs to view across all venues.

Regulatory Fields

Expand
Table Filter
totalrow,,,,,
hidelabelsfalse
sparkNameSparkline
hidePanetrue
sparklinefalse
defaultlseg_ptg
isFirstTimeEnterfalse
cell-width150
hideColumnsfalse
customNoTableMsgfalse
disabledfalse
enabledInEditorfalse
globalFilterfalse
id1721905742514_920978680
order0
hideControlstrue
inversefalse
disableSavefalse
separatorPoint (.)
labelsVenue
userfilterVenue
datepatterndd M yy
updateSelectOptionsfalse
worklog5|8|w d h m|w d h m
isORAND

Table Excerpt Include
copytabletrue
nameRegulatoryFields
pageRegulatory Fields
typepage

Please refer to Regulatory Fields to view across all venues.

Passthru Fields

Expand
Table Filter
totalrow,,,,,
hidelabelsfalse
sparkNameSparkline
hidePanetrue
sparklinefalse
defaultlseg_ptg
isFirstTimeEnterfalse
cell-width150
hideColumnsfalse
customNoTableMsgfalse
disabledfalse
enabledInEditorfalse
globalFilterfalse
id1721905765071_-459296783
order0
hideControlstrue
inversefalse
disableSavefalse
separatorPoint (.)
labelsVenue
userfilterVenue
datepatterndd M yy
updateSelectOptionsfalse
worklog5|8|w d h m|w d h m
isORAND

Table Excerpt Include
copytabletrue
namePassthruFields
pagePassthru Fields
typepage

Please refer to Passthru Fields to view across all venues.

Details

Clients will receive real-time trade Execution Reports on lseg_ptg session for the trades executed on the trading venue, along with the trade corrections and cancellations.

Post trade workflow for NDF is slightly different on LSEG, as they are cleared instruments and require Central Counterparty Clearing (CCP) acceptance once the trade is executed. 

SPT

Post trade workflow for spots is standard where each counterparty involved will be receiving single ExecutionReport.

NDF

For NDF trades, trade corrects and trade cancels, clients will be receiving two ExecutionReports on ptg session.

  1. First one is sent with ExecType as Trade indicating pending clearing by CCP.
  2. Second ExecutionReport will follow based on either clearing accepted or rejected.

Table below indicates the differences between two ExecutionReports.

ExecutionReports Fix Fields

Pending Clearing

(First Exec)

Clearing Accepted

(Second Exec)

Clearing Rejected

(Second Exec)

BPT Key - ClearedIndicatorSubmittedClearedRejectedExecRefID
ExecRefIDNot PresentContains TradeReportId(BPT) of the First ExecContains TradeReportId(BPT) of the First Exec
BPT Key - TradeReportTypeSubmitAddendumTradeBreak
ExecTypeTradeTradeCorrectTradeCancel
BPT Key - TradeReportTransTypeNewReplaceCancel
BPT Key - ClearingHouseUTINot PresentClearingNot Present
BPT Key - SubmissionToClearingNot PresentTimestamp of Submission to clearingNot Present
TextNot PresentNot PresentContains a reject code

Additional Information

Note
titleUnsupported Venue Functionality

Features not yet supported by LSEG FX:

  • Prime Broker Workflow.
  • Clearing Broker Workflow

Features not required by Whisperer Enterprise:

  • Whisperer does not support ApplicationMessageRequest and ApplicationMessageRequestAck offered by venue. Standard fix session recovery does ensure the missed TradeCaptureReports are sent to client as ExecutionReports with PossDupFlag set to True. Hence there is no need for client to explicitly request the missed trades using ApplicationMessageRequest.
Info
titlePrimeBroker and ClearingMember participants

Post trade session for Clearing Member can be configured to receive the ExecutionReport of their child Clearing Member Clients and similarly Prime Brokers and Prime of PrimeBrokers can receive their child PrimeBroker clients and Prime of Prime Brokers ExecutionReports. If ou wish to set this up, please contact LSEG directly.