OnBehalfOfSendingTime and SendingTime out of sync

, ,
1

Imported from previous forum

2

[ original email was from Jochen de Lima - jdelima@siac.com ]
In FIX 4.2, what if the OnBehalfOfSendingTime and SendingTime in a message are out of sync, i.e. A uses B as a hub, and A’s clock is ahead of B’s. Hipothetically:
OnBehalfOfSendingTime: 10:00:00 (UTC)
SendingTime: 9:59:00 (UTC)

Should that be treated as an error? My guess would be: depends on the application requirements. If it is, should a session rejection be issued with SessionRejectReason=11 (SendingTime accuracy problem)?

Thanks.
-Jochen

3

[ original email was from Ian Orford - ian.orford@ubs.com ]
Personally, I don’t think we’d treat this as an error.

I dont think we’d want to reject messages and potentially loose out on business just because the timestamp of an intermediary hub is incorrect or different from ours or our counterparty.

I think OnBehalfOfSendingTime is probably most useful when trying to work out whether the hub caused a significant delay in the delivery of the counterparty’s message.

> In FIX 4.2, what if the OnBehalfOfSendingTime and SendingTime in a message are out of sync, i.e. A uses B as a hub, and A’s clock is ahead of B’s. Hipothetically:
> OnBehalfOfSendingTime: 10:00:00 (UTC)
> SendingTime: 9:59:00 (UTC)
>
> Should that be treated as an error? My guess would be: depends on the application requirements. If it is, should a session rejection be issued with SessionRejectReason=11 (SendingTime accuracy problem)?
>
> Thanks.
> -Jochen
>
>