Hi,

I just started using kmymoney on windows (4.8.1) and it's going pretty smoothly so far. I imported 15 years of data from quicken for about 30 accounts of varying types and it's been pretty good.

One thing I noticed as I'm catching up my downloads is the OFX importer puts everything as one day behind. For example, if I look online at my bank I see a Transaction Date of 2018.05.01 but it gets imported as 2018.04.30 into kmymoney.

I found this report https://mail.kde.org/pipermail/kmymoney ... 00104.html but that was from 2010 so I can't imagine it's the same problem.

Any suggestions?

Thanks,

David

once I figured out that ofx was just text, I removed the [-5:EST] from the dates and it imported ok. kind of a pain but at least I can work around it.

<DTPOSTED>20180104020000[-5:EST]

to

<DTPOSTED>20180104020000

There seems to be a problem somewhere in the combination of KMyMoney, libOFX and Windows

OFX specs wrote:Elements specified as type date or datetime and generally starting with the letters “DT” accept a fully
formatted date-time-timezone string. For example, “19961005132200.124[-5:EST]” represents October 5,
1996, at 1:22 and 124 milliseconds p.m., in Eastern Standard Time. This is the same as 6:22 p.m.
Greenwich Mean Time (GMT).

The timestamp in your example clearly shows January 4th 2018 @ 2 a.m. as the local time in EST which is 5 hours 'behind' UTC/GMT. I doubt that the problem is the uninitialized DST flag since that only produces an offset by 1 hour which does not affect the date at 2 a.m. So it could well be, that the timestamp is adjusted by -5 hours which ends up on the day before. I wonder, if these problems exist in a *NIX environment.

Nope, my 'solution' didn't quite work - since we're now in Daylight Time (GMT-7) any transactions dated during Standard Time (GMT-8) got assigned the previous day.

Instead of removing the [-5:EST] I now replace it with [-8] which fixes everything. e.g.:

<DTPOSTED>20180409000000[-5:EST]

to

<DTPOSTED>20180409000000[-8]

I see, the problem is that your bank is on the east coast while you live on the west coast. Their 12 a.m. is your 9 p.m. on the day before. Not much, we can do about at the moment. Your manual intervention might be necessary for a while. According to the OFX specs, you don't need to add the timezone name, though. Providing the offset as [-8] seems to be enough.

yes, exactly.

I'm fine with the manual intervention, just happy there is one!

In case someone is interested and can take a look at https://phabricator.kde.org/D13293 which adds a method to correct the time during import. I need some test results.