We have the same issue. We use ondemand.ca.com where the servers are based in the Eastern States (Australia) and we are based in Western Australia where there can be up to a 3 hour time difference.
In our custom reports we had to put in additional logic in the SQL:
trunc(sr1.cop_report_date)+1 status_date
trunc(i.target_resolution_date)+1 target_resolution_date,
trunc(i.impact_date)+1 impact_date,
First item was for the Status Report Date, and the other two were for Issue Dates.
Not saying this is a perfect solution and still unclear why it is required as JasperSoft should be able to work out where the user is located and correctly show the date, but this is what we had to implement.