I have just noticed that when importing my transactions from banks the date gets offset by -1 day.

e.g. Date of transaction 4 June 09
OFX file contains for this transaction:

<STMTTRN>

<TRNTYPE>DEBIT</TRNTYPE>

<DTPOSTED>20090604000000</DTPOSTED>

<TRNAMT>

-40.00</TRNAMT>

<FITID>200906040000002</FITID>

<NAME>DD - XXXXXXXXXXXXXXXXX</NAME>

<MEMO>DD - XXXXXXXXXXXXXXXXX</MEMO>

</STMTTRN>


However, the ledger entry date gets set to 03/06/2009 when I accept.
I didn't notice this before...

This is consistent over all transactions - deposit, transfer and withdrawal.

How can I help run down this issue?
Thanks

I think Thomas is working on it to fix this issue for good.

We have seen this problem crop up once and again. It is probably related to the inconsistence in how the banks handle the dates and how libOFX tries to figure out what's the correct date.

Hei Ku wrote:I think Thomas is working on it to fix this issue for good.

Confirmed: he is

Great, thanks for the update.
If you need someone to test the fix I have a backup of my data and can re-run my ofx file against it.

Sorry to reopen this and not hassling - honestly...

But just so that I can carry on with OFX import while awaiting the problem to be fixed, it struck me that I can easily generate a SED script to edit my OFX file if I know what KMyMoney wants.

To save me going through a hit and miss exercise can anybody (who gets transactions imported correctly) tell me what date format they have in their OFX?
e.g. mine is:
<DTPOSTED>20090713000000</DTPOSTED>
But gets posted as:
12 July 2009 instead of 13 July 2009

Or Maybe its some other field (wrong or missing) in the OFX causing a date offset - time zone maybe?

Any hints appreciated.

You can try adding a timezone information so that it looks like this:

Code: Select all

<DTPOSTED>20090604000000[+2:MSZ]</DTPOSTED>

Make sure to use the correct timezone and offset. For the UK people it would be +1:BST these days and +0:GMT during the winter.

See if that makes a difference during import.

I tried the tz information but it doesn't affect the import.

However I found that changing e.g.:
<DTPOSTED>20090713000000</DTPOSTED>
to
<DTPOSTED>20090713235959</DTPOSTED>

Does fix my import issue and transactions changed in this way have imported to correct day (so far).

So a SED script to modify DTPOSTED for my OFX files will do the job as a temporary fix and should be easy.

Happy to try any other ideas...

Final solution:

DTSTART
DTEND
DTPOSTED
DTASOF

all changed from
YYYYMMDD000000
to
YYYYMMDD

I found this out from realising that OFX files from another of my institutions did import transactions with correct date. It had the DT fields in YYYYMMDD format (except DTSERVER which was a full YYYYMMDDHHMMSS field).

I haven't gone to the OFX spec so don't know if the institution is breaking rules by having the long date format. I'll check when I have some time if nobody knows but I doubt that it matters - MSMoney deals with it so they are not likely to be interested in changing,

So I hope this helps somebody else, I just run a sed script over ofx files from the one institution before importing and all is well.