R54.16 - Unable to import QFX transactions - Unable to Verify Financial Institution (edit)

denlow

I am on Windows Home, Ver 10.0.22621. Quicken Classic Deluxe Ver R54.16. When I attempt to import a qfx file from Pima Federal Credit Union (Tucson, AZ) I get the error following message. I have been using this Credit Union for several years without problems until this last update. The same process with Capital One QFX files goes thru without issue.

Help

Quicken Jasmine

Hello @denlow,

This message usually means that there is an error in the QFX code.

Since the financial institution creates the QFX files, you will need to contact Pima Federal Credit Union for further assistance. It is recommended that you request to speak to a tier 2 agent or supervisor as they are generally more familiar with third-party applications such as Quicken.

I apologize that I could not be of more assistance.

Ps56k2

Open your downloaded QFX file with Notepad - it's just plain text -
look for the entry <FID>
is the 5-digit number the same as listed below ?

BUT - It does not appear that PIMA is configured to allow for QFX download and QFX IMPORT into Quicken -
This feature is missing - and is called "Web-Connect" - and has not been configured for it since last year…

Why are you manually downloading - when you can use the online One Step Update ?

here is the config info -

26949 26949 26949 Pima FCU
https://www.pimafederal.org/ 520-887-5010
https://www.pimafederal-digitalbanking.org/dbank/live/app/register ACTIVE
ACCOUNTINFO,BANKING&DIRECT
BANKING,ACCOUNTINFO&EXP-WEB-CONNECT

denlow

Thanks for your response.

I am not finding <FID> in the file. There is a <BankID>" *****4795" and <FITID> "739396"

I guess I will have to contact the credit union to see what has changed on their end.

I manually download when I go to the Credit Union's web site to view transactions / balances / etc. and then import into Quicken. Just my usual work flow. The OneStep update seems to try to contact all my institutions and accounts and it seems to generate more errors.

Ps56k2

interesting…. don't know how it's been working for you as a Quicken Import of a QFX data file -

Quicken FIDIR entry - Financial Institution Directory -

and the FIDIR entry for your CU downloaded QFX file should be "26949" as mentioned above -
Here is what our Chase QFX download looks like -
It should be right up near the beginning of the QFX file -
Your BANKID and FITID are related to the account transaction numbers and not the Quicken assigned FI DIR Number

OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:NONE
<OFX>
<SIGNONMSGSRSV1>
<SONRS>
<STATUS>
<CODE>0
<SEVERITY>INFO
</STATUS>
<DTSERVER>20190722120000[0:GMT]
<LANGUAGE>ENG
<FI>
<ORG>B1
<FID>10898 —- Chase #
</FI>
<INTU.BID>10898 —- Chase #
</SONRS>

Chris_QPW

For what it is worth, Quicken actually uses the INTU.BID number not the FID (but they are always the same number).

Also, if it is missing then this will certainly cause that error message.

And looking at the fidir.txt file entry for your financial institution I would say the reason it is missing is because Web Connect/QFX file isn't supported.

26949	26949	26949	Pima FCU	https://www.pimafederal.org/	520-887-5010	https://www.pimafederal-digitalbanking.org/dbank/live/app/register	ACTIVE	ACCOUNTINFO,BANKING&DIRECT	 	 	BANKING,ACCOUNTINFO&EXP-WEB-CONNECT	NOT_QBP	NA

ACCOUNTINFO,BANKING&DIRECT

BANKING,ACCOUNTINFO&EXP-WEB-CONNECT

Direct Connect and Express Web Connect only.

Which brings me back to suspect that you don't have a QFX file, you have a OFX file. An OFX file is just like a QFX without the financial institution information mentioned above.

mlipton

I am having the same issue - John Hancock. it downloaded fine for years, all of a sudden it won't download

Quicken support had me look for the intu in the text file, we couldn't find it.

John Hancock support had no idea what I was talking about.

what has changed??

Chris_QPW

For reference, even though the same file is downloaded into Quicken's configuration directories here is the link to the current fidir.txt file for Quicken Windows US:

https://ofx-prod-filist.intuit.com/qw2800/data/fidir.txt

For John Hancock there seems to only be support for 401K accounts:

09847	09847	09847	John Hancock Financial Services	https://www.jhinvestments.com/AccountAccess.aspx	1-800-695-7389	https://www.secureaccountview.com/BFWeb/clients/jhinvestments/index	ACTIVE	 	401K&WEB-CONNECT	 	 	NOT_QBP	NA

401K&WEB-CONNECT (Web Connect is downloading the QFX file and importing it)

If your account is a 401K (or 403b) account, then you there is most likely a different problem.

Syntax problems in a QFX file are reported in: Help → Contact Quicken Support → Log Files → Connection log

Any kind of syntax error will have to be fixed by the financial institution. And as for them knowing about Quicken, it is very typical that the first line support will know nothing about it, and you will have to ask for it to be escalated. Note that if the phone number above is different than the normal one you use it might a better number to call.

Ps56k2

@Chris_QPW - is there any way, other than "missing data elements" to tell the difference between a QFX file vs a OFX file ?
like the downloaded Chase QFX posted above ?

Chris_QPW

https://community.quicken.com/discussion/comment/20417322#Comment_20417322

Not really. In theory other than those fields they should be the same. I have heard that in some cases some OFX files aren't exactly the same and would cause problem in Quicken, but I think that has more to do with the fact that the OFX standard is pretty complex and as such both the program that write and the one that reads (Quicken vs Microsoft Money) might handle certain syntax differently.

EDIT: I left out the most obvious difference. A QFX's type is .QFX and an OFX is .QFX. But that is just "text".

QuickUserPSP

The QFX file is a proprietary variant of the OFX file. I think DC uses OFX and WC uses QFX. I have seen most issues with the file header which causes the OL-220 errors. Most QFX files use the old header format, but others like American Express Personal Savings uses the new OFX header format. Or at least tried to. That file is messed up and any attempts to get that file fixed falls on deaf ears. I have to go in and fix the file each time in order to get it loaded.

Chris_QPW

@QuickUserPSP Direct Connect uses QFX, and Web Connect uses the "response" of QFX. If you look at the OFX logs (how ironic is that that Intuit/Quicken Inc call it the OFX log) you will see that the response has the FID field in it. It is also ironic that they don't require the INTU.BID for Direct Connect (or at least don't show it in the log, but do require the FID. The OFX protocol is a SEND with the request for the transactions, and the RECV is basically the same as what is put into the QFX file.

As for the header/versions being used by the financial institutions shows how they really don't care to keep things up to date:

This is Citi Cards:

OFXHEADER:100
DATA:OFXSGML
VERSION:102

1.02 version, basically the first version that was ever "public".

As time went on the format changed from "sort of XML" to pretty much exactly XML. Later versions (that Quicken and the US financial institutions don't support) even have gotten different protocol for logging in like OAuth 2.0. One of Express Web Connect +/FDX claims to fame is that it "more secure" and that is based as far as I can tell on the fact that it uses OAuth 2.0 security tokens. But the only reason it is "more secure" than OFX is because of the lack of adoption of the later versions of OFX and using that option. And note that OFX/Direct Connect doesn't have either Quicken Inc's server or Intuit's server in the middle.

QuickUserPSP

@Chris_QPW - it seems like the WC QFX files syntax use is lax and not uniformly applied. This makes it difficult to troubleshoot. Wells Fargo QFX files work perfectly but their layout is "weird" which make them very difficult to read. They even have investment WC QFX files, which, I think are rarely seen. I see a lot of broken QFX files that the FI are supposedly responsible for but there doesn't seem to be any protocol to get them fixed, or even looked at. In my opinion, there should be a liaison from Quicken working with these FIs on QFX file issues.

Chris_QPW

I'm sure there is someone in Quicken Inc that deals with these kinds of problems, but Quicken Inc is far too small of a company to handle all the financial institutions. So, it is my belief/understanding that they really don't get involve unless it is a financial institution that with a lot of Quicken users complaining about it. Even saying that, almost immediately if you say "Web Connect" the answer is going to be "the financial institution has to fix it."

As for the weird format, QFX/XML files are really meant to be machine readable (no linefeed/formatting in a lot of them), but not really for humans. Intuit makes a formatter available to their "participate partners" (mostly just an XML formatter). How do I know? because at one point I was able to download it from here:

https://www.intuit.com/partners/fdp/implementation-support/ofx/support/#

But that has been closed off for many years.

You are right that not many financial institution's support Web Connect for investment account and when they do, it is usually because they don't support Direct Connect. That is the way with my wife's 401K account serviced by Merrill Lynch.

On the other hand, you might find some that put out OFX, which is easy to convert if you know what you are doing or use ImportQIF to do it for you.

One hint I can give you is that if Quicken finds a syntax error in the QFX file it logs it in the Connection Log. Their error messages tend to be pretty vague, but at least it is a starting point.

As for American Express and them not fixing their QFX files. My best recommendation there is just to use ImportQIF with a CSV file as the input and QFX as the output.

QuickUserPSP

@Chris_QPW - thank you. All of this makes sense, but I still don't understand why a large organization like American Express is unable to get, or won't get a simple file fixed? I have a sneaking suspicion that they feel it's a Quicken error, so they aren't budging? The QFX file has been in an error status for many months that I know of. Who knows, it could even be years?