On Wed, 19 Jun 2013 04:02:42 +0000 <mdaleknochen...@gmail.com> wrote:
> https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #8 from mdaleknochen...@gmail.com --- > Thanks for the follow up. > > The exact message I encounter during my manual import is: > > 'Problem adding or matching imported transaction with id '': Unable > to add transaction with invalid postdate' > > My bank offers 3 formats during the manual download: "QIF", "OFC", > or a "CSV". It sounds like the OF? format is the richest so I have > trying to import that one into KMyMoney, but would go with either of > the others if it would be reliable. > > Regarding the test file, the bank will not change the data for a test > file. I did spend some time with the Notepad text editor, and saved > it as a text file, ANSI encoding, as well as Unicode encoding and it > appears to work with Unicode. Still, I am not comfortable sending you > a test file, so that is not an option. > > The best news: I did find some documentation on modifying the QIF > Profile (Tools || QIF Profile Editor || Date tab) and I spotted a > setup issue with the Date format. I changed it to match my QIF file > (mm/dd/yyyy), and it appears to solve the invalid postdate warning > on the QIF import. The OFX import is still a warning. > > Is there an OFX (OFC) Profile equivalent like the QIF I found? > > Thank you! > According to - http://support.microsoft.com/kb/890400 "The OFC format was replaced by the OFX format in 1997. The OFC format is supported by versions of Microsoft Money up to and including Microsoft Money 2004..." It might be worth asking your bank why they are so behind the times. Allan _______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
