Hi SCHIRD,

Thanks for using Community Hub.

You're absolutely right in terms of the two different dates.

• The BookingDateTime is the “Date and time when a transaction entry is posted to an account on the account servicer’s books”
• The ValueDateTime is the “Date and time at which assets become available to the account owner in case of a credit entry, or cease to be available to the account owner in case of a debit transaction entry.”

There can be a slight mismatch in dates because of the these two options.  However, this shouldn't prevent you from matching the transactions in Sage Bank Feeds and you can complete all tasks as normal.

I hope this answer helps, if it does, please click Verify Answer.

Regards,

Andy
Sage UKI

Thanks for responding.

The dates being wrong in almost all transactions does not inspire me with confidence that I am getting the right transaction when there may be transactions of a similar value around the same date and where the dates cross over a month end, whether the transaction is in the right month. Also if I have to generate a transaction in Sage the wrong date will be put in by the program. 

As this is a new and improved version of an existing function I did expect better.

I was also disappointed by the fact that I was initially told by Sage help to refer back to the bank when it now appears not to be an issue with the data that they are supplying. You appear to be saying that it is wrong but I will just have to accept that.

As no-one else appears to have found this to be a problem I suppose that nothing will be done.