@lubos i have previously addressed the issue of transactions in Manager not listed in the order they were entered.
below was your reply.
this issue has been giving a lot of headache recently where we have to crosscheck the data like in the bank transactions tab with the bank statement. checking a few transactions is okay but transactions over a period of time is really hard.
if i may suggest, please add an internal timestamp to the transactions captured from the user’s system clock (this would be applicable for desktop edition. cloud and server editions may use the server time). this timestamp need not be visible to the user.
the transactions shall be sorted in the order of date, timestamp, reference and then by amount.
the timestamp should be of the time the transaction is created in Manager and not when it is edited to update information. i can explain a few situations.
a transaction entered on 9th May will retain the timestamp of its creation even if the transaction has been edited later and the transaction date remains the same.
for the above, if the transaction is edited and the date is changed to a future date, then the timestamp will check the first record for the new date and add the timestamp prior to it.
if the transaction is edited and the date is changed to a previous date, then the timestamp will check the last record for the new date and add a successive timestamp to it.
users who do not want Manager to automatically sort their edited transactions wrt the timestamp can simply delete and reenter the incorrect transaction.
having a timestamp will ensure all transactions appear in order of any third party list like a bank statement.