Trade Cancellation Event, Reason, Date and Comments

1

Hi Team,

In a trade capture report, please let me know how I can represent the

  • The event is a Cancel
  • Cancellation reason
  • Cancellation date
  • Cancellation comments

Regards
Rahul

2

Hi Rahul,

please refer to https://fiximate.fixtrading.org/ and lookup message type AE/TradeCaptureReport.
Cancel is represented as 487/TradeReportTransType=1(Cancel).
Reasons could be represented by 378/ExecRestatementReason.
For the date there are several fields, e.g. 60/TransactTime or 75/TradeDate. Check the description what matches your business case.
For the comments I did not find anything suitable in a quick check.

I am sure others will answer as well and correct or amend my posting.

Cheers, Jörg

3

or jump on a 35=8 and 150=H message and do some further readings on consecutive corrections as well.

1 Like
4

@rahulmohanraj I would like to add a few additional comments here:

  • TradeReportTransType(487)=1 (cancel) should be used when technically deleting a previous TradeCaptureReport(35=AE) message. It requires the use of TradeReportRefID(572) to refer to the TradeReportID(571) of the message you want to delete.This is the message level and applicable when you use a message chaining model.
  • If you rather want to cancel a trade on the business level (entity-based model), you can use TradeID(1003) and TradeReportType(856)=6 (Trade Report Cancel) or 7 (Trade Break) if the trade was already confirmed. In this case, you are not using the fields in the previous bullet.
  • Date and time of the event may also use the repeating group TrdRegTimestamps, especially when you need to convey more than just a single timestamp in the same message. TransactTime(60) is about the event that triggered the message to be sent. TradeDate(75) should not change and refers to the date of execution.
  • Comments would go into Text(58) on the side level (TrdCapRptSideGrp)
1 Like
5

@hanno.klein, thanks for correcting me. I had the feeling that I was too fast here…

6

@hanno.klein, @jorgthonnes, @111s Thank you, much appreciated.