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; } } }

Importing multiple payments on same day/same payee

ccc123

Windows Qucken basic - latest R60.18

Issue:

downloaded from Canadian tire master bank in qucken format

2) there are more than one transactions on the same day to same payee

3) and imported to quicken, it only shows the first transaction in preview window and other transactions to same payee/same day did not show up.

Find more posts tagged with

download transactions

Comments

Chris_QPW

Is this with Web Connect/a QFX file or Express Web Connect where you use One Step Update?

If it is the later this has been a known problem for as long as I can remember. The algorithm that Intuit uses for looking for duplicate transactions for Express Web Connect doesn't take into account that you might have the exact same transaction on the same day.

ccc123

Thanks. this is downloaded QFX file.

checked this file, those transactions has the same FITID and only first one was imported to the qucken.

tried to change the fitid for those transactions, and imorted shows up those transactions. It seems that the quicken is thinking those transcations with same payee/same fitid are duplicated even the amounts are different and it was ignored when it's being imported.

Hopefully At least quicken show show up those transactions and let user to decide if they are duplicated.

the one-step update seems not having such issue anymore. It had same issue about two years ago with previoius version.

Chris_QPW

OK, now we know who is at fault, it the financial institution that produced the QFX file, not Quicken.

The FITID is there for this very reason, to prevent duplicates. Let me give you some examples of why you might not want what you are asking for (even though it is less of a problem in a QFX file). But let me start by saying a QFX file is the "response" that Direct Connect would normally get when it requests transactions from the financial institution, just in file form. So, you have to think about it in those terms too.

So, let's say you download some transactions midday. And then come back the next day and download some more transactions. If the date used for downloading today's transactions is today you might miss some transactions from yesterday. If you use yesterday's date you would get duplicates if they were blocked. But you said, "give me the choice". Sounds fine until you consider this, you might get that every time you download transactions. But it can get much worse when you think of Direct Connect. By its nature it is designed so that they can overlap requests like this, sometimes for very long periods of time, depending on the timing of when people download transactions and when the financial institution posts transactions. So, that list of transactions you have to go through might get long. And remember there might not be anything that separates them out. Which might cause people to have to go to looking at statements from the financial institution.

I personally think that there should be an option like "ignore FITIDs" so that if one deleted transactions and needed to import them again they could do it without the difficult workarounds that are needed currently. But it certainly should be an option, and it shouldn't be on by default. It would be something you turn on when you find that you can't reconcile, and you suspect a problem like this.