Problems with qfx

[Kew, Martin Scott - kewms001]

Hi Marsh,

I think your problem is similar to mine where I got the same symptom from a test OFX file import from an ING account in Australian. I have been in email conversation with ING where they are now taking seriously the fact that ING OFX file is incorrectly formated. Apart from the formating error WRT transaction type picked up by David when I previously posted to this list. I ran my test file through the freely available Microsoft OFX Analyser with the attached result. I am currently waiting for ING's reply, when I get one I will post to this list.

Regards
Martin Kew

________________________________________
From: gnucash-user-bounces+kewms001=mymail.unisa.edu.au at gnucash.org [gnucash-user-bounces+kewms001=mymail.unisa.edu.au at gnucash.org] on behalf of David Reiser [dbreiser at earthlink.net]
Sent: Monday, 5 December 2011 1:22 PM
To: MarshFeldman at cox.net
Cc: gnucash-user at gnucash.org
Subject: Re: Problems with qfx

On Dec 4, 2011, at 9:12 PM, Marsh Feldman wrote:

> Hello,
>
> I'm a newbie with Gnucash. After setting up my accounts, I downloaded a 3-month statement in qfx format from ING Retirement. I then go File > Import > Import OFX/QFX... and select the file. A window pops up with a label "Generic import transaction matcher." But the content of the window is just blank.
>
> I opened the downloaded qfx file in MacVim, and it seems to be legit. (I don't know the details about what's in a qfx file. But what I see is a header with about ten fields separated by colons and then a bunch of what looks like XML.)
>
> Any help would be most appreciated.
>
>    Marsh


What types of transactions are in the report? Libofx should handle stocks and mutual fund buys and sells, but I don't think it handles bonds or options. Dividends and automatic dividend reinvestment should be handled correctly. I don't know about money market funds.

Check to make sure that the contents of the <FITID> field exist and are unique. That field may also end with </FITID>, but it might not, depending on what version of ofx ING thinks they're following.

A completely empty transaction matcher window suggests that libofx sees no valid transactions, or only transactions it doesn't understand. If ING customized something too much, libofx might have gotten confused.

I think libofx ignores lines outside the <OFX> ... </OFX> tags, but you could try removing other text if it exists before and after those tags. Certainly I have imported files beginning with the header information before the <OFX> tag (the header starts with: OFXHEADER:100), but I don't think libofx processes that info.

Dave
--
David Reiser
dbreiser at earthlink.net


_______________________________________________
gnucash-user mailing list
gnucash-user at gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OFX Result.png
Type: image/x-png
Size: 32832 bytes
Desc: OFX Result.png
URL: <http://lists.gnucash.org/pipermail/gnucash-user/attachments/20111205/cd23a5c0/attachment-0001.bin>