Compare to Register QIF import

rich

I am using Windows 10 Pro (version 22H2 Build 19045.5247 64 bit) and Quicken Classic Premier ver 27.1.60.20.

I think all transactions imported from a QIF file should appear in the Compare to Register. That would make it so much easier to keep my data accurate.

heisescott

I don't understand - could you supply some screen shots and more explanaction?

NotACPA

@heisescott The OP of this thread was last active in March 2025 … so I doubt you're going to get a reply from him.

Chris_QPW

Just to put this in context, before Quicken Subscription (Quicken 2017 and below), when you would import QIF files they would go into the Downloaded Transactions tab, just like current transactions that are downloaded using Web Connect, Express Web Connect, Express Web Connect + and Direct Connect when you aren't using the Edit → Preferences → Downloaded transactions → "Automatically add to banking registers" preference.

As in here (at the bottom of a register):

And it would also use the memorized payees to fill in the categories and it would match existing transactions.

Starting with Quicken Subscription QIF imports go directly into the register with no processing. It doesn't set any status, so there isn't any "review" of the transactions, and it won't apply categories or match existing transactions.

There is zero chance that Quicken Inc will reverse this decision. They did it on purpose to discourage the use QIF importing.

heisescott

thanks for the explanation!

rich

sorry for the late reply - way too many emails and forums ! as Chris_QPW said above on 7 Sep, this (importing QIF files - the transactions would go into the Downloaded Transactions tab) used to work. this was and still is my point. again, like Chris_OPW said "Just like current transactions that are downloaded using Web Connect, Express Web Connect, Express Web Connect + and Direct Connect". That is my reasoning for why that functionality should work for importing QIF Files: if it works for one process, why not for all ? The main reason i want this is that I have several non USA accounts so quicken does not download the transactions. instead, i have other processes that create the QIF, which i then import into quicken. As it is now, those transactions go directly into the register and i have to manually review them all to delete duplicates, etc. Sometimes the QIF file contains more than 100 transactions.

Chris_QPW

@rich I certainly understand the need, and I'm sure Quicken Inc does too, but they have their criteria of what they want to support and their ideas of trying to restrict features that might take away from their ability to sell more subscriptions.

The QIF format has very "winding history". The first thing is that it was created by Intuit as a tool for their support people. It was never intended to be a universal import/export format. It was never standardized. That is why you will find different variations especially in different countries. Even Intuit kept varying it even after there was a published format. And the fact that their competitors picked it up and started using it to get people to go to their product…

In Quicken Windows 2004, was the first time Intuit tried to restrict this. They changed the GUI so that it would only allow selecting asset and liability accounts. But people found that if the account name and type were in the QIF file it would still import into the right account, so the importing continued.

In 2007 Intuit started working on a total replacement for Quicken Mac, and they totally dropped QIF. It wasn't till a few years ago that Quicken Inc put some support for it back into Quicken Mac, but the restriction there is that it can only be used to create new accounts. It is pretty easy to see the intent there. "Allow importing QIF files from competitors, but not just general use of it." Side note. Intuit and Quicken Inc after them have always resisted supporting CSV format. They are now supporting importing transactions in Quicken Windows and Quicken Mac in CSV format (with restrictions, as of now, no splits). Why now? Because they wanted to grab the Mint customers. The required format for the CSV format is basically the Mint CSV format.

And then we get to Quicken Subscription, and Quicken Inc decides they will drop the GUI restriction for selecting accounts to import into but take away the processing. Why? The motivation is the same. If you are importing a QIF file from a competitor, you don't need matching and such.