I take your point on time as having a potential effect on values per se. The majority of my transactions were done through a couple of Australian exchanges but also do include other international exchanges so there will be some incorrect times I believe.
It would create even more unwanted complexity to this whole reporting scenario to start to convert all the different time zones from around the world to the local Australian zone that the account is nominated in. Until there is a simple fix for this I decided that I would have to live with this shortcoming if I was to continue to use this software as there are many more problems to solve first.
It would be a wonderful addition and improvement to the Cointracking software if in the future it could convert the time zone that the trade was completed in to the equivalent time zone in the locally nominated time zone of the account at the time when these transactions were being imported via .csv or API etc.
Obviously all the exchanges would have to provide that time zone information within their TimeStamp data that they generate but it is an obvious improvement.

The majority of my transactions are completed via fiat to crypto exchanges and the .csv export that is generated from the exchange comes complete with the actual local time zone and the actual total Sale Value in AUSD of both crypto to crypto and crypto to fiat transactions.  The problem is Cointracking does not import this column that contains the Total Sales Value of each of the transactions.  Rather it inserts its own version of Sale Value and a completely differing version of a Purchase Value into the Assets Value boxes and this then creates problems as mentioned in the 1 BTC post. Neither of these 2 Cointracking inserted Values agrees with the actual correct value supplied by the Exchange. Why, who knows? This then requires a whole lot of manual cross checking and ultimately editing of every transaction which is very time consuming and should not be needed.