nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issues Importing QFX files Quicken for Mac

siouxbarrett

I recently applied the update for Quicken for Mac Version 8.4.1 (Build 804.59810.100). Since then, I am unable to import any QFX files. Quicken does not recognize them in the directory.

When I right click in Finder and select Get Info, I see that the default application to open my qfx files is iBank 5, which I have not used in over a decade. If I try to change the default application, Quicken is not an application that can be chosen, leading me to believe there is something wrong with my most recent update of Quicken.

Any guidance you can offer will be greatly appreciated.

Find more posts tagged with

File Import

Quicken Mac

Accepted answers

Dennis@1

You can also just drag and drop the QFX file into your Quicken register.

All comments

Jon

@siouxbarrett Are you sure it isn't an OFX file rather than a QFX file? When I checked a QFX file it was assigned to Quicken, but an OFX file was assigned to Banktivity and could not be opened in Quicken. Some institutions offer both downloads so you need to be sure to pick the right one.

RickO

And if you really do have a QFX file, you can go to Quicken's menu File > Import > Bank or Brokerage File… and point the file dialog to your file and see if it will open that way.

Dennis@1

You can also just drag and drop the QFX file into your Quicken register.

siouxbarrett

Thank you. I have tried the File > Import tactic and it does not work. Quicken does not see any QFX files. The Drag and Drop method did work however.

ginger1w@aol.com

I am having the same issue. When I try to import the .QFX file, Quicken tells me the bank is at fault. The bank says it's not their fault. What's a person supposed to do? I cannot import my .QFX file.

DaveManz

The message about Quicken not being able to verify your FI is a misnomer; especially egregious since it suggests that you should "try again later". Later will never come!

Quicken and its "aggregator" Intuit is deprecating the use of QFX files/method in favor of EWC+ (OAuth2) methodology, claiming it to be more secure. My bank no longer offers transaction downloads in either QFX or QIF formats. The only viable choice left (if I chose not to use EWC+) is CSV files. This proves somewhat workable, but not without many teething tweaks. (Search support for "Importing …. CSV.." for a correct column layout needed.

Hope this helps.

jacobs

Quicken and its "integrator" Intuit is deprecating the use of QFX files/method in favor of EWC+

@DaveManz Sorry, but as I've written in reply to your posts in other threads, that is completely untrue. Quicken isn't deprecating the ability to import QFX files at all. However, some financial institutions, because of their own policies and security assessments, have told Quicken/Intuit that they will no longer support QFX downloads. Your bank is apparently one of them. They stopped providing QFX downloads because they don't want to provide them, bot because of any limitation imposed by Quicken. They feel EWC+ is more secure and the only connection method they want to provide for third-party software.

DaveManz

Whether EWC+ is the best method of user authentification is not the point being made. It is that Intuit began in my area around the start of December using a new FIDIR.txt file, which prompted Quicken Classic, when trying to import a valid QFX file downloaded recently from BofA, to tell me via a fatal error message that my FI was not valid and that I should "Try again later." Now from my perspective, since BofA continued for another two or three weeks to allow successful downloads of valid, meaningful QFX files, who do you think the average user would suspect is to blame for the failures? And how many users began the futile attempt to rectify the invalid FI by trying again and again or worse yet, by going to backups or deleting or refreshing accounts to overcome the "Try again later"….. a move that no amount of trying was going to resolve?

It may be that the general feeling at Quicken and Intuit is that Quicken Classic users are a dying breed or that few used the QFX downloads, and therefore received little attention during the transition, but it was useful and did its job. Little to no effort was put forth to inform, much less, convince, the users (formally called customers) of why EWC+ was better for them.

A query today on the Support page finds 141 inquiries about QFX failures dating from December 1 onward (if this not deprecating, by what name will thee call it?). How many others have those same concerns?