Background

To provide a normalised view of the ExecutionReport, there are corrections being made to the quantity fields to be inline with the schema. Details of changes to each field are listed below:

1. LegAllocCalculatedCcyQty - As per the schema, ABS (SUM (LegAllocCalculatedCcyQty))=LegCalculatedCcyLastQty. For the affected venues listed below the calculation does not match.
2. LegAllocQty - As per the schema, If ExecType=Calculated/Trade then ABS (SUM (LegAllocQty))=LegLastQty, otherwise ABS (SUM (LegAllocQty))=LegOrderQty. There are inconsistencies across the venues where the value is sent as 0 for cancelled/rejected orders.
3. LegCumQty - This is a mandatory field to be populated in the ExecutionReport and currently it is based on what venue sends and is not in line with the schema which is "Total quantity filled so far on this Leg of the Order".

Changes

1) LegAllocCalculatedCcyQty - ExecutionReport now reflects the signed value and the calculation is inline with the schema.

Affected Venues: autobahnfx_algo, baml, fxspotstream_algo, precision_algo, xtx_euthenia

2) LegAllocQty - ExecutionReport now reflects the signed value and the calculation is inline with the schema.

Affected Venues: All taker APIs

3) LegCumQty - This is now the cumulative qty of all the fills of the order if OrdStatus is PartiallyFilled/Filled/PendingCancel/Cancelled/PendingReplace/Expired and 0 otherwise.

Affected Venues: autobahnfx_rapid, baml, barx, citi_colo, rbc_trading, standardchartered_s2bx, statestreet_efx, t360_tex.

Timeline

At the client's discretion.

Clients are advised to contact the MarketFactory Delivery Team to enable this feature in UAT for testing and subsequently deploy the changes in production.