We're updating the issue view to help you get more done. 

Transaction dates sometimes show wrong date due to UTC time and local timezone difference

Description

Here is what I think is happening. The due date we get from QB is just a plain date with no time or time offset. When a date like that is pulled into the client app (browser), we then convert that date into a date object. When that happens (by default) the date will become the plain date but in UTC time "2018-06-12T00:00:00z". The client browser (via Javascript) will then render that date in local time (without the time part). Thus, the date is showing in local time for a date that is based on UTC time. Less than ideal.

I believe the fix for this is going to be to convert the plain dates (with no time) to some base timezone other than UTC. The question of course is which one. GoToMyAccounts is used in a lot of countries, so we can't just assume that a fixed date (2018-06-12) should be EST or PST or something like that. We DO have a setting in the portal called home timezone in the region settings. However, I do not think it is being utilized in that way at this time.

The proper fix to all this is to use the home timezone as a time basis for fixed dates like invoice date and due date. That way, the date will always be based on the local time for the company.

Environment

None

Status

Assignee

Mark Sauer

Reporter

Mark Sauer

Labels

None

Fix versions

Priority

High