QFX import problem and work around, possible bug or new feature?

GWB gwb at 2realms.com
Sat Oct 1 03:49:40 EDT 2016


How do you get to the "old" format website for Chase?

When I log in to Chase, I no longer see OFX as a possible download
format, only QFX.  As late as last March, both were available as
download formats, but no longer.  So would asking them to reinstate
the OFX format make any difference?  Or is the problem the actual OFX
standard now being used (2.2), or Chase's "interpretation" of the OFX
standard in their QFX files?

I download from several brokers, banks, cards and other fiduciaries
using OFX files.  They have all been pretty much bullet proof so far
in importing into Gnucash.

When I run diff on the older format QFX and OFX, I get this:

$ diff *.QFX *.OFX
20,24d19
< <FI>
< <ORG>ISC
< <FID>10898
< </FI>
< <INTU.BID>10898

That's it.  5 lines.  grep, awk and sed can get rid of the offending
MEMO and CATEGORY lines:

$ grep -vwE "(MEMO|CATEGORY)" Defective-File.QFX > Fixed-File.QFX

That seems to do the trick:

$ less Defective-File.QFX | grep MEMO
<MEMO>null
<MEMO>null
<MEMO>null
...

$ less Fixed-File.QFX | grep MEMO
$

I'll try to import both the defective and fixed files in the next week
and see what happens.  In the meantime, I might ask Chase to bring
back the old OFX download format.  I have no idea how secure or
insecure DirectConnect may be, but I'm not using it.  It's way easier
to download the transactions over a secure VPN or a double stunnel,
and that's pretty safe.

Macs can grep, awk and sed from the terminal.  Windows can as well
with cygwin.  But Chase is causing a lot of aggravation for their
clients who don't use those kinds of tools.

Gordon


On Fri, Sep 30, 2016 at 6:37 PM, gatzdon <gnucash at gatzafamily.com> wrote:
> You can add me to the list.
>
> Downloading QFX from the 'old' format website for Chase still works.
>
> Downloading QFX from the 'new' format website for Chase has the extraneous
> <CATEGORY><MEMO>null for each transaction.
>
> Importing the QFX results in null values for Description, but deleting each
> of these lines allows the QFX file to be imported normally.
>
> I did SM chase to complain, but assume nothing will become of it.
>
>
>
> --
> View this message in context: http://gnucash.1415818.n4.nabble.com/QFX-import-problem-and-work-around-possible-bug-or-new-feature-tp4686405p4686859.html
> Sent from the GnuCash - User mailing list archive at Nabble.com.
> _______________________________________________
> 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.


More information about the gnucash-user mailing list