Discussion Forums

Re: ClOrdID [11] value in trade capture reports
Natan Kugel / BGC Partners <>
22 Jul 2010 8:39AM ET

> What about using a venue assigned unique identifier that doesn't change like Tag 37 (OrderID)?

The Trade Capture Report needs to carry the following references
1) ExecID [17] to point to the Execution Report Trade;
2) OrdID [37] to point to the exchange / broker associated ID - from client's prospective this is possibly a chain of order ammendments;
3) ClOrdID [11] as the associated order has been submitted electronically.

Honoring the ClOrdId [11] an providing the matching the value with the original execution report has advantage of
1) unambiguously pointing to the appropriate link in the chain of ammendments made by client.
2) avoids race conditions in synchronizing back office sub-system with real-time trading / matching engine. Depending on the time Trade Capture Report is issued (if the client order is still alive) the current value in tag 11 may refer to any link in the chain and not necessarily be the last in the lifetime of the order. More over, the matching engine may be in he process of handling Cancel Replace request.


ClOrdID [11] value in trade capture reports
Natan Kugel / BGC Partners   21 Jul 2010 5:06PM ET
Re: ClOrdID [11] value in trade capture reports
Natan Kugel / BGC Partners   21 Jul 2010 5:09PM ET
Re: ClOrdID [11] value in trade capture reports
Aaron Pryce / Consultancy   21 Jul 2010 8:20PM ET
Re: ClOrdID [11] value in trade capture reports
Natan Kugel / BGC Partners   22 Jul 2010 8:39AM ET
Re: ClOrdID [11] value in trade capture reports
Aaron Pryce / Consultancy   22 Jul 2010 4:19PM ET
Re: ClOrdID [11] value in trade capture reports
Natan Kugel / BGC Partners   22 Jul 2010 4:38PM ET
Re: ClOrdID [11] value in trade capture reports
Aaron Pryce / Consultancy   22 Jul 2010 5:57PM ET
Re: ClOrdID [11] value in trade capture reports
Hanno Klein / Deutsche Börse Systems   23 Jul 2010 9:56AM ET