You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed for a while that the transaction dates produced by ledger-autosync are occasionally off by one as compared to what is shown online or in my bank statements.
At the top of an OFX file I downloaded at 10:30 this morning, I found this:
<DTSERVER>20170905173000.000
Since I am currently in the PDT zone, I believe this means that the downloaded transaction files are always given in UTC (at least for this bank).
Unfortunately I don't see any reference to time zone in the file itself, so the only way to get the offset is to compare DTSERVER with the local date.
Could ledger-autosync add an argument to specify the time offset from DTSERVER, and adjust output times accordingly?
The text was updated successfully, but these errors were encountered:
I have noticed for a while that the transaction dates produced by
ledger-autosync
are occasionally off by one as compared to what is shown online or in my bank statements.At the top of an OFX file I downloaded at 10:30 this morning, I found this:
Since I am currently in the PDT zone, I believe this means that the downloaded transaction files are always given in UTC (at least for this bank).
Unfortunately I don't see any reference to time zone in the file itself, so the only way to get the offset is to compare
DTSERVER
with the local date.Could
ledger-autosync
add an argument to specify the time offset fromDTSERVER
, and adjust output times accordingly?The text was updated successfully, but these errors were encountered: