How do I prevent Quicken from matching downloaded transactions to already reconciled entries?
More info needed in order to help you.
When you do TOOLS, Account List … what shows in the "Transaction Download" column next to the account(s)?
Have you recently changed the download method, say from Direct Connect to Express Web Connect(+). OR, have you "reset" the account download?
About how long has this been happening? From a single financial institution? Or many? If many, please answer the above questions for each of them.
I have been having the same problem for about a month with Wells Fargo, I have deleted the downloaded duplicate from the download, I have tried accepting and then duplicating from the reconciliation page, but they recur every day, essentially every transaction for the past month.
I changed from Direct Connect to Express Web Connect and the problem seems to be resolved.
It's back and now it occurs in multiple accounts including brokerage accounts.
Hello @Harold-Jr,
I apologize that you never received a response.
Do you still need assistance?
Thank you!
Hello again,
Checking in once more before this thread is closed.
Let us know if you still need assistance.
Still having same problem with Wells Fargo as well as USAA and my brokerage account. Since yesterday, I cannor connect to Wells Fargo. It seems to be their problem since when I try resetting the account Quicken cannot connect.
For what it is worth, there seems to be a misconception on how Quicken's matching works.
First off, Quicken doesn't look at the Clr status to decide to match at all. I think the main reason for that is because if one switched over from manual entry only to downloading, they would need to have the existing reconciled transactions to match.
The way Quicken decides if an existing transaction in the register is a candidate for matching is if an internal flag has been set.
If you hold down Shift+Ctrl and right click on a transaction and then select copy transaction this dialog will come up.
It the Downloaded Transaction and the posting date being set that take a transaction off of the list of transaction of possible matches. Note that this hidden command only works on non-investment accounts (the way the matching works is probably the same but there isn't a way to show the internal settings)
And on the switching between Direct Connect and Express Web Connect + will change the Download ID which might cause duplicates because what Quicken does is store the Downloaded ID for ever transaction it download (per account) and if a downloaded transaction has the same ID it ignores it. If the ID changes for the same transaction Quicken normally thinks it is a new transaction. I say "normally" because when Express Web Connect + was introduced and people changed from Direct Connect to Express Web Connect + the expected behavior would have been people getting a lot of duplicate transactions but that didn't happen. So, it is clear that they are doing something on the Quicken server that is filtering out duplicates in some other way.
At any rate these two operations are q
