Home Quicken for Windows File Conversion and Backup (Windows)
Quicken Community is moving to Single Sign On! Starting 1/22/21, you'll sign in to the community with your Quicken ID. For more information: http://bit.ly/CommunitySSO

Quicken will not import .QFX files. Finally a solution!

TL;DR Quicken can't load two transactions with the same id, if you deleted the transaction and tried to import it again or it just won't import you should open the QFX file with notepad look at all the IDs find them as <FITID>YYYYMMDD (for chase at least) and replace them with a date you would never use, this doesn't change the date of the transaction.

The Full Story
As I do on a monthly basis I logged in to chase and downloaded my transaction file AKA .QFX file and loaded it to my quicken 2016. for some reason it imported all of my transaction twice (but that's chase's fault) so I deleted all of the transactions and tried again, but oh no! it wouldn't import for some strange reason, I tried everything that you are supposed to that's written on the quicken support page and surprise.. it didn't work.. classic.. now I got very frustrated but my 30 year career as an IT consultant came in handy. I read on this forum: http://help.infinitekind.com/discussions/problems/2758-qfx-import-unreliability that quicken can't import the same transaction id twice which supposed to prevent duplicates, so my quick solution to this problem was to change the ID number of all the transaction to a different one using the basic text editor built in to windows just right click and "open with" any text editor of your choice instead of <FITID>20170422 I changed to year that I would never use- <FITID>20150422. hurry, it worked I saw many people with the same problem and no solution, hopefully this solution helps you understand the problem better and how to solve it. another forum post to help you: http://help.infinitekind.com/discussions/problems/2245-duplicate-entries-when-importing-ofx-difqfx-f...

another option is to backup your QIF file before you do any kind of imports so you can go back to the time quicken didn't "remember" the IDs of your transaction.
if there is an option to reset transaction ID memory that I didn't know about that might be a better option I there isn't I think quicken should implement this.

This should help you in the journey of the mysterious quicken. Thanks.

Forums:
image
image

Comments

  • UnknownUnknown Member
    edited October 2018
    "another option is to backup your QIF file"

    I think you meant QDF file.

    "but oh no! it wouldn't import for some strange reason"

    Nothing strange at all.  That is exactly what the FITID is for, preventing duplicate transactions when importing the same data.  Quicken records the FITIDs imported into a given account and ignores a transaction that has a FITID that it has already seen.  Yes at times it might be nice to "clear" this list so that you can do an import again, but there are workarounds.  Yours of changing the FITID is one (I tend to just add "a" to the end of the FITID as long as it doesn't exceed the 32 character max).  There is also deactivating the account for downloading, import the QFX file into a new account, and copy the transactions from that account to the old one, and switching back to which one is active (or just do the copy/merge in the new account).

    People might wonder, why have this feature in, if I'm controlling the dates that will ensure that there isn't any overlap.  But they would be wrong.

    First off just imagine if you downloading some transactions with today's date as the ending date, but you did it in the morning.  And more transactions came in later that day.  There is no date that you can pick that will at the same time avoid duplicates, but also make sure the transactions at the end of the day get picked up.

    But there is even more to it.  The QFX file is in fact just the response part of the OFX protocol.  When using One Step Update Quicken actually request transactions with a date about 1 week sooner than the last date you downloaded.  The reason it does that is because not only do you have that one day problem I described above you have a problem with pending transactions.  Imagine you have a pending transaction on 4/20/2017.  It will not be downloaded on 4/20/2017's download.  Now it clears on 4/22/2017.  Some financial institutions will set its date to 4/20/2017.  And clearly if the "requested start date" requested by a client that is just using the last date downloading was strictly adhered to it will fail to download this transaction.  The OFX protocol actually says that if a client requests a date of say 4/22/2017, and the server has this situation where that transaction on 4/20/2017 was never sent, that it should be included.

    But needless to say several financial institutions don't get that part right.
    Simple fix, download a week back so that cleared pending transactions are on or after the requested start date.  And then just rely on the FITID processing to take care of the overlapping transactions.

    BTW it is import to look at the connection type to at least have a guess at where the FITID is actually coming from.  If you are using Web Connect (QFX file) or Direct Connect the FITID is guaranteed to be coming from the financial institution.

    If the connection type is Express Web Connect it gets much fuzzier.  This is Intuit's "aggregator" service, which basically tries to do what Web Connect does, automatically.  But there is no standard for this. Some financial institutions will provide the QFX file, but others won't.  If they get the data in another format, then it most likely will not have any unique id in it.  So Intuit's "scripts" make up one.
    And their algorithm has proved to have a couple of flaws in it.
    For instance if you have more than one transaction that has the same payee, memo, and amount on the same day, it will give these all the same FITID, and only one will be imported into Quicken.
    The second known flaw is that they are using some kind of "seed" tied to the account.  If you reset the account or deactivate/reactivate the account, it starts producing different ids for the same transactions.  And this is why people report getting duplicates after this kind of action.
  • UnknownUnknown Member
    edited October 2018
    I just resolved a similar situation after hours of trying. Close Quicken. Copied all files from my previous computer's drive in: ProgramData/Intuit/Quicken/Config and placed them in the same folder of the new computer. Overwrote all files. Open Quicken and presto! You will see your entries!!image
  • UnknownUnknown Member
    edited April 2017

    I just resolved a similar situation after hours of trying. Close Quicken. Copied all files from my previous computer's drive in: ProgramData/Intuit/Quicken/Config and placed them in the same folder of the new computer. Overwrote all files. Open Quicken and presto! You will see your entries!!image

    Gary McRobb I'm not sure what your problem was, that moving the config files fixed, but it really has nothing to do with the someone trying to import the same transactions twice into the same account.

    The FITIDs are stored inside of QDF file.
  • UnknownUnknown Member
    edited April 2017

    I just resolved a similar situation after hours of trying. Close Quicken. Copied all files from my previous computer's drive in: ProgramData/Intuit/Quicken/Config and placed them in the same folder of the new computer. Overwrote all files. Open Quicken and presto! You will see your entries!!image

    Perhaps so ... i don't get paid to do this and am just trying to help out those who encounter the same problem i did. And i'm surprised you don't know about it. Here's the situation: my computer crashed, dead. Got a new one. Installed Qkn and imported the qdf retrieved from the dead computer's drive. But Qkn would not allow me to sign-in despite trying several times (see image). I tried the recommended options but they didn't work either. I rebooted twice. Nothing worked. Qkn would not allow me to access the previous file. Copying the config files fixed that. Surely this will help others who find themselves in the same frustrating situation.image
  • UnknownUnknown Member
    edited April 2017

    I just resolved a similar situation after hours of trying. Close Quicken. Copied all files from my previous computer's drive in: ProgramData/Intuit/Quicken/Config and placed them in the same folder of the new computer. Overwrote all files. Open Quicken and presto! You will see your entries!!image

    Gary McRobb sounds like some very good information, it just didn't make any sense in context of this thread.

    What I suggest that you do is select NEW POST from the top of the page and post your information with a good subject, so that is is visible to people looking for information on that kind of problem.
This discussion has been closed.