# SessionRejectReason = SendingTime Accuracy Problem

**URL:** <https://forum.fixtrading.org/t/sessionrejectreason-sendingtime-accuracy-problem/2707>\
**Category:** General Q&A\
**Tags:** general-qa, xid\_166270, imported\
**Created:** [November 5, 2010, 7:06pm UTC](https://forum.fixtrading.org/t/sessionrejectreason-sendingtime-accuracy-problem/2707 "2010-11-05T19:06:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![robertmitchell45](https://avatars.discourse-cdn.com/v4/letter/r/ec9cab/32.png) [@robertmitchell45](https://forum.fixtrading.org/u/robertmitchell45)\
**Post date:** [November 5, 2010, 7:06pm UTC](https://forum.fixtrading.org/t/sessionrejectreason-sendingtime-accuracy-problem/2707/1 "2010-11-05T19:06:31Z")

</div>

Imported from previous forum

---

<div class="post-metadata">

**Author:** ![hansialexander\_x](https://avatars.discourse-cdn.com/v4/letter/h/a9a28c/32.png) [@hansialexander\_x](https://forum.fixtrading.org/u/hansialexander_x)\
**Post date:** [December 11, 2015, 6:15am UTC](https://forum.fixtrading.org/t/sessionrejectreason-sendingtime-accuracy-problem/2707/2 "2015-12-11T06:15:22Z")

</div>

Hi,

If SendingTime/OriginalSendingTime format is incorrect, what should be the SessionRejectReason?

Is it [6 = Incorrect data format for value] or [10 = SendingTime Accuracy Problem] ?

Example-  
If inbound message contains 52=20151240-10:56:14.722, where valid format is “YYYYmmdd-HH:MM:SS.sss” and date (dd) contains value 40.

Thanks.

---

<div class="post-metadata">

**Author:** ![yuvalcohen](https://avatars.discourse-cdn.com/v4/letter/y/9fc29f/32.png) [@yuvalcohen](https://forum.fixtrading.org/u/yuvalcohen)\
**Post date:** [December 15, 2015, 4:03pm UTC](https://forum.fixtrading.org/t/sessionrejectreason-sendingtime-accuracy-problem/2707/3 "2015-12-15T16:03:57Z")

</div>

Hi Hansi,  
In your example the format is incorrect. As date must be in the range: [01 - 31].

Whilst if you have recieved today @ noon time a message having a timestamp of yesterday’s (or tomorrow’s) noon time, than it is an accuracy problem.

---

<div class="post-metadata">

**Author:** ![robertmitchell45](https://avatars.discourse-cdn.com/v4/letter/r/ec9cab/32.png) [@robertmitchell45](https://forum.fixtrading.org/u/robertmitchell45)\
**Post date:** [November 5, 2010, 7:06pm UTC](https://forum.fixtrading.org/t/sessionrejectreason-sendingtime-accuracy-problem/2707/4 "2010-11-05T19:06:31Z")

</div>

When would I use this? How can I differentiate between clock synchronization issues and network congestion problems and would I care even if I could tell one from the other?

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [November 5, 2010, 7:17pm UTC](https://forum.fixtrading.org/t/sessionrejectreason-sendingtime-accuracy-problem/2707/5 "2010-11-05T19:17:06Z")

</div>

[original email was from John Harris - [john.harris@bondmart.com](mailto:john.harris@bondmart.com) ]  
Problems might arise that can be explained neither by clock synchronization nor network congestion. For example, the sending time might be quoted as a time in the future, or as a time prior to transact time in the case of an execution report (which would be nonsensical). Inaccurate sending times might be a function of mischief as well.

> When would I use this? How can I differentiate between clock synchronization issues and network congestion problems and would I care even if I could tell one from the other?

---

<div class="post-metadata">

**Author:** ![hansialexander\_x](https://avatars.discourse-cdn.com/v4/letter/h/a9a28c/32.png) [@hansialexander\_x](https://forum.fixtrading.org/u/hansialexander_x)\
**Post date:** [December 25, 2015, 5:22am UTC](https://forum.fixtrading.org/t/sessionrejectreason-sendingtime-accuracy-problem/2707/6 "2015-12-25T05:22:12Z")

</div>

Thanks a lot Yuval.