# How to communicate reason for TRADE\_CANCEL

**URL:** <https://forum.fixtrading.org/t/how-to-communicate-reason-for-trade-cancel/4807>\
**Category:** General Q&A\
**Tags:** general-qa, xid\_167811, imported\
**Created:** [May 20, 2009, 5:04pm UTC](https://forum.fixtrading.org/t/how-to-communicate-reason-for-trade-cancel/4807 "2009-05-20T17:04:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![staffanulfberg\_x](https://avatars.discourse-cdn.com/v4/letter/s/d9b06d/32.png) [@staffanulfberg\_x](https://forum.fixtrading.org/u/staffanulfberg_x)\
**Post date:** [May 20, 2009, 5:04pm UTC](https://forum.fixtrading.org/t/how-to-communicate-reason-for-trade-cancel/4807/1 "2009-05-20T17:04:35Z")

</div>

Imported from previous forum

---

<div class="post-metadata">

**Author:** ![staffanulfberg\_x](https://avatars.discourse-cdn.com/v4/letter/s/d9b06d/32.png) [@staffanulfberg\_x](https://forum.fixtrading.org/u/staffanulfberg_x)\
**Post date:** [May 20, 2009, 5:04pm UTC](https://forum.fixtrading.org/t/how-to-communicate-reason-for-trade-cancel/4807/2 "2009-05-20T17:04:35Z")

</div>

We sometimes need to cancel trades, and do this by setting ExecType in execution reports and trade capture reports to TRADE\_CANCEL.

However, we would also like to convey the reason for the cancellation, and I cannot find an appropriate FIX tag for that purpose. Is there one that I missed?

If not, what’s the recommended way to proceed? Just add one and keep the number and name local, or to try to add it to one of the 5/6/7/9nnn lists of custom tags?

Staffan

---

<div class="post-metadata">

**Author:** ![hanno.klein](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/hanno.klein/32/38_2.png) [@hanno.klein](https://forum.fixtrading.org/u/hanno.klein)\
**Post date:** [May 20, 2009, 6:41pm UTC](https://forum.fixtrading.org/t/how-to-communicate-reason-for-trade-cancel/4807/3 "2009-05-20T18:41:24Z")

</div>

The standard option is always to use the Text (58) tag. This will work if you do not need to convey other information in the context of a trade cancel. Adding one “locally” only works for internal tags \>10000, otherwise it needs to be one between 5000 and 9999 registered on the FPL website. I guess what you are looking for should be called TradeCxlReason and have a list of pre-defined values and Reserved100Plus datatype for user-defined values. The closest one I found is 6042 CxlReason which should apply for orders, quotes and trades (executions). I suggest to use that tag if you do not want to submit a gap analysis for an extension of the FIX standard.

Regards,  
Hanno.

> We sometimes need to cancel trades, and do this by setting ExecType in  
> execution reports and trade capture reports to TRADE\_CANCEL.
> 
> However, we would also like to convey the reason for the cancellation,  
> and I cannot find an appropriate FIX tag for that purpose. Is there one  
> that I missed?
> 
> If not, what’s the recommended way to proceed? Just add one and keep the  
> number and name local, or to try to add it to one of the 5/6/7/9nnn  
> lists of custom tags?
> 
> Staffan

---

<div class="post-metadata">

**Author:** ![staffanulfberg\_x](https://avatars.discourse-cdn.com/v4/letter/s/d9b06d/32.png) [@staffanulfberg\_x](https://forum.fixtrading.org/u/staffanulfberg_x)\
**Post date:** [May 20, 2009, 8:19pm UTC](https://forum.fixtrading.org/t/how-to-communicate-reason-for-trade-cancel/4807/4 "2009-05-20T20:19:19Z")

</div>

> The standard option is always to use the Text (58) tag. This will work  
> if you do not need to convey other information in the context of a trade  
> cancel.

Sure, but we want to have a more type safe way of doing this handling the canceled trades is an automated process.

> Adding one “locally” only works for internal tags \>10000,  
> otherwise it needs to be one between 5000 and 9999 registered on the FPL  
> website. I guess what you are looking for should be called  
> TradeCxlReason and have a list of pre-defined values and Reserved100Plus  
> datatype for user-defined values. The closest one I found is 6042  
> CxlReason which should apply for orders, quotes and trades (executions).  
> I suggest to use that tag if you do not want to submit a gap analysis  
> for an extension of the FIX standard.

Using 6042 seems just fine to me. Is there any other information apart from the tag name and number in the list on the web site, like what values are valid?

---

<div class="post-metadata">

**Author:** ![hanno.klein](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/hanno.klein/32/38_2.png) [@hanno.klein](https://forum.fixtrading.org/u/hanno.klein)\
**Post date:** [May 20, 2009, 9:13pm UTC](https://forum.fixtrading.org/t/how-to-communicate-reason-for-trade-cancel/4807/5 "2009-05-20T21:13:30Z")

</div>

> > The standard option is always to use the Text (58) tag. This will work  
> > if you do not need to convey other information in the context of a  
> > trade cancel.
> 
> Sure, but we want to have a more type safe way of doing this handling  
> the canceled trades is an automated process.
> 
> > Adding one “locally” only works for internal tags \>10000, otherwise it  
> > needs to be one between 5000 and 9999 registered on the FPL website. I  
> > guess what you are looking for should be called TradeCxlReason and  
> > have a list of pre-defined values and Reserved100Plus datatype for user-  
> > defined values. The closest one I found is 6042 CxlReason which should  
> > apply for orders, quotes and trades (executions). I suggest to use  
> > that tag if you do not want to submit a gap analysis for an extension  
> > of the FIX standard.
> 
> Using 6042 seems just fine to me. Is there any other information apart  
> from the tag name and number in the list on the web site, like what  
> values are valid?

Not that I am aware of. It would be in the field description. Apparently it was introduced as part of a repeating group to cancel rebills but you would use it as a standalone field. I still think it is better to re-use that field and not introduce a new user-defined field.
