When I accepting a match on my downloaded bank transactions, Quicken creates a duplicate. Anyone have success in correcting this? I am using Quicken Classic and Personal on OC
This issue was first reported on April 2nd and I reported this on April 12th. I am still having this problem.
This is a very long time to resolve.
Is this still being worked on by development?
What is the ticket number?
Your post is at the top of the 3rd page of replies. If you look back through the previous pages, you will see number CTP-16752 .
There are at least 2 other discussions on this same issue, and one of them mentions another tracking number, CTP-16297. Perhaps the Moderators could merge these discussions.
Despite all the users who are affected by this issue, I do not see any Alert about it.
When is someone going to address the fact that if you have a scheduled transaction, it gets duplicated in Quicken when it gets downloaded via One Step Update? This is not like it is a small issue, the transactions literally duplicate and do not even update the register, if they are a transfer between accounts in Quicken, they do not even show up in the other account, they are ghost transactions. This has been going on for months and months, and has been brought up multiple times. [Removed - Rant/Edited - Readability]
I've had the same issue for well over a month with Bank of America, Citicards, and couple others. For what we pay annually I'd expect things to be FIXED and FIXED QUICKLY. What is the estimated time for this fix(es)? Frustrating that issues keep coming up…obviously they don't test their upgrades before throwing them out to us hoping they will work.
Hello @CiwJKkan,
Thank you for sharing your feedback. I understand how frustrating it is that this issue has been going on for so long. To help our teams investigate the issue, please provide additional information:
Thank you!
(CTP-16752)
Can someone at Quicken confirm if this is the same issue as (or at least related to) the following (and maybe merge the two threads)?
[Edited - Enabled Link]
Someone at Quicken should merge this thread with the following two, which seem to cover the same (or at least a very similar) issue:
[Edited - Enabled Links]
Same issue here, since at least early April
GM Carlos…just checking in. It's been two weeks since we've heard anything on this thread. Any progress? Please give us an update. Thank you!
@Quicken Carlos and @Quicken Laura
I've been following the thread for some time now because this issue is truly a time-consuming horror. However, I wanted to relate my experience yesterday with my update.
As usual, the One Step Update produced easily 10 or more duplicate transactions. Unfortunately, I ignored my own advice about transfers and voided the wrong transaction resulting in one-sided voids. My registers were so screwed up that I decided to restore my previous backup and start over.
Once the data was restored, I ran One Step Update again. This time (to my amazement!) there were no duplicate transactions created. Go figure…
Is there any resolution is sight? Unfortunately, I've had to start researching alternatives.
Hi @DennisDe, Thank you for sharing your experience, and I completely understand how frustrating this situation has been.
I checked ticket CTP-16752, and our escalations team is requesting a few additional details.
To help the team properly investigate whether this behavior is related to a bug or expected transaction matching limitations, we need some more information about the specific duplicate transactions you encountered. Unfortunately, the logs alone are not enough for the team to determine the root cause.
When you have a moment, could you please provide the following details for a few of the affected transactions, as @Quicken Kristina requested in the previous comment?
For reference, Quicken for Windows currently looks back 7 days from the last download for transaction matching purposes, with a maximum lookback window of 30 days. The additional transaction details will help determine whether the duplicates should have matched automatically or if the transactions fell outside the expected matching window.
We appreciate your patience while this issue continues to be investigated, and I look forward to your reply! [CTP-16752]
This problem has gotten worse. Since April I have received duplicate downloads everyday for all my banking transactions since April. Today I received the duplicate banking transaction AND all my credit card card transactions since April!! This is a nightmare and taking hours to resolve.
We need a fix!!
I have sent information via Report a Problem twice.
Hi @rsb515, I understand that this issue has become increasingly frustrating.
I can confirm that the Escalations Team has reviewed the reports that were submitted. However, they have not yet been able to determine the root cause based on the logs alone and require the additional information previously requested in order to continue their investigation.
Specifically, they need:
These details are critical because they allow the team to compare the downloaded transaction data with the existing register entries and determine why the transactions are not being matched correctly.
Once you provide the requested information, I will ensure it is forwarded to the Escalations Team for further review.
Thank you for your cooperation and patience as we investigate this issue. [CTP-16752]
Hello Carlos,
I submitted a report with the "Report a problem" function and used the ticket number above in the subject line. I will post some of the provided information here as well.
Hello @dbex,
Thank you for letting us know you're also seeing an issue with duplicate reminders. Based on your description, it sounds like you're encountering a similar but slightly different issue. There's a separate ticket for duplicates with a blank category column or [Unspecified Category] as the category.
(CTP-16297)
I'm seeing this happen too but only in my Bank of America checking account where most of my bill reminder entries are entered. Specifically, I have recurring transactions like HOA dues, house cleaner, medical insurance premium payments, etc that are usually monthly but some are bi-weekly. I enter them into my checking account register through Bill & Income tab. They are entered into my BofA checking account register as future dates until the actual download of the transaction occurs at BofA. In the download, it states that there is a MATCH for the transaction so I accept for all of them. Upon reviewing by checking account register, it actually repeated the transactions and made duplicate ones when the original was already present. This started back in April as everyone stated and continues to get worse. I CAN'T manually match to the correct transaction either. I need to enter the incorrect match, delete it, and reconcile the correct one. Seems like Quicken did something in their Matching algorithm that is INCORRECT.
Its almost as if the download sees the transaction but instead of matching to it, enters an identical one.
Are you guys at Quicken using AI to beta test your new code?
I have the same symptoms in my checking account (FWIW it's also Bank of America).
However, I am able to manually rematch the downloaded transaction to the original correct transaction before accepting it. After accepting the correctly matched transaction, I then delete the bogus duplicate transaction that gets created as a result of the OSU. The bogus duplicate transactions invariably do not include the Category.
This happened again this morning with 1 payment transaction. I submitted a report with log files and an extensive description, as well as a screenshot showing the checking account register and the Downloaded Transaction window taken right after the OSU completed AND BEFORE I took any corrective actions.
For transactions where I see this problem, my answer would always be Yes to the first question.
For the 2nd question, it depends on exactly what you mean. For example, the transaction that I had a problem with this morning (monthly rent payment) is always entered into the register dated for the 1st of the month - which is when that bill gets paid. However, I typically enter it into the register (from the Bills & Income screen) a few weeks before that.
Which is the date that actually matters; the date in the register, or the date I put it there?
@tompfr The date in the register is what matters for matching. Unless something has changed recently, for banking transactions Quicken uses the amount of the transaction for matching (not the Payee) and will match to a transaction that is between 15 days before and 1 day after the date in the download (not today's date). For investing transactions, the dates must match exactly.
I generally set Reminder dates to a few days before the expected download date. I review and accept downloaded transactions one at a time, not using automatic accepting or Accept All. Quicken will select what it thinks is the matching transaction in the register and I accept the match by clicking on the green Save button to the right of the transaction. If there is no match because amount in the register is wrong or the date is too far off, I change the transaction so it matches and click the Save button.
Please try this process and let us know if you still see duplicates.
I sometimes see phantom duplicate transactions if I click on the Accept button below the transaction in the downloaded transaction (C2R) area. The phantom disappears if I select a different transaction. It is important not to accept these phantoms because that will create duplicates.
@Jim_Harman
I also do not have Quicken set to automatically accept downloaded transactions. I review them manually before accepting.
I would like to stress that the duplicate transactions that I am seeing ALWAYS appear in the register immediately after OSU completes, and BEFORE I do anything at all. IOW, they appear in the register on their own, even though I do NOT automatically accept downloaded transactions.
When this happens, the original transaction that I had previously entered into the register via the Bills & Income screen is still there, unchanged from before. However, there is also now this uninvited bogus copy of that same transaction in the register that is the same, except that it does not have a category assigned. In the Downloaded Transactions window, the downloaded transaction is ALWAYS MATCHED to this bogus copy (without category) created during the OSU process.
What I have been doing to correct this is to manually rematch the downloaded transaction to my originally entered transaction and then accept it. That still leaves me with the bogus duplicate in the register, which I then delete afterwards.
My most recent case of this was yesterday (6/2). The downloaded transaction was dated for 6/1, the same date as the previously entered transaction that was already in the register. For that transaction, I had entered it into the register probably about 3 weeks before the transaction date, which is what I typically do with any transaction where I already know the amount. I do this mostly to be able to see my future balance in the register, which I find helpful. In any case, I have been doing it this same way for years and years, but only recently (the past 3 or 4 months) have these bogus duplicates started happening.
From what I can tell from reading posts from others on this subject, most of them are reporting symptoms that are the same or similar to mine. But it can be a confusing problem to describe, so sometimes it's hard to tell.
@tompfr Do you use Quicken on the Web, the mobile apps, or have Mobile & Web sync enabled? The setting for that is at Edit > Preferences > Mobile & Web. If you don't use the web or mobile apps, there is no harm in turning that off.
An Alert was posted yesterday saying that some duplicates have been created by the sync process but it has been fixed. See this post
Are you seeing any new duplicates today?
Please reply using the Leave a Comment section at the bottom of the page rather than by clicking on Reply, because nested replies are hard to find if there have been more comments since your reply.
"Do you use Quicken on the Web, the mobile apps, or have Mobile & Web sync enabled?"
No, I don't. None of the above. I did have Mobile & Web sync enabled in the past to try it out, but it's been disabled in Settings for years now.
No duplicates today (no checking account transactions today)
I am experiencing the same issues as everyone else. I have posted logs and a screen shot.
Also, I have pulled out a sample transaction that was duplicated and compared the first one (downloaded yesterday) to the second one (downloaded today) and will attach that below as a screen shot. I have blanked out the sensitive information, but it was largely identical both days except things you would expect to be different (such as the date it was downloaded). The one thing that is different is the txn_type on row 21—the first day, it was "CASH_FLOW", while the second day, it was "DEBIT". The rest—including the transaction id—are the same. Hopefully, this will help.
I have been following this with interest as I'm experiencing similar issues. It doesn't seem as though sending log files through "report an error" is useful, as there is commentary above that the technical teams have not been able to resolve it using log files alone. There are two things I observed that may be helpful, and I'd appreciate it if this could be passed along to the technical teams. 1. I have a recurring bi-weekly transfer of a specific amount from my checking account to a vacation savings account. This has a scheduled transaction set up manually using Manage Manual Bills and Income. I typically enter it a few days prior to the date the transfer occurs. When this issue first started, I thought there was a problem with how these transfers were set up in Bills and Income, so I deleted them all and recreated them. Previously, this transfer used the Payee "Transfer to Vacation Savings". When I recreated it, I named the Payee "Vacation Savings". After One Step Update runs and the transfer is downloaded, the phantom/incorrect duplicate transaction is created using "Transfer to Vacations Savings". In this case, it's very easy to tell which is the incorrect, duplicated transaction. 2. Perhaps this was mentioned before, but for other transfers that are duplicated - both appear to be correct. But right-clicking on one of them and selecting "Go to matching transfer" will give an error indicating that the transfer to account no longer exists in Quicken. Even though the account (category) is correct. Even attempting to update the transfer to account (category) does not fix this. As with others, I'm quite frustrated at the amount of work this is causing; and the amount of cleanup it requires. What puzzles me is that things worked perfectly for years, then suddenly broke. Surely there's the ability to revert back to an earlier version of the code to fix this?
@FlyGuyTx I'll ask you the same question I asked @tompfr earlier this morning:
Do you use Quicken on the Web, the mobile apps, or have Mobile & Web sync enabled? The setting for that is at Edit > Preferences > Mobile & Web. If you don't use the web or mobile apps, there is no harm in turning that off.
Are you seeing any new duplicates today? From your description, it seems that issue may apply.
Hi Jim, I do not use Quicken on the Web or the mobile apps and have not for several years. (too many issues…but that's not the topic here!). Mobile and Web Sync is and has been disabled for some time. No duplicates today - but - based on the timing of scheduled account transfers, I may not see them again for about a week.
I had another duplicate transaction during OSU today, once again in my BOA checking account. The transaction date in the register is 6/5, and the downloaded posting date is 6/8. I submitted another report with screenshot (showing the duplicate before I corrected it) and the log files.
The problem transaction today is a fixed monthly bill payment amount. It is one of those that I enter into the register from the Bills & Income screen 3 to 4 weeks before the transaction happens. I have some others that I handle the same way, and based on what I've been seeing, these seem to be the ones that are subject to the duplicate transaction issue.
I also had 2 other transactions that downloaded today, but no duplicate was created for either of them. These 2 payments were also entered from the Bills & Income screen, but they are variable amounts (the electric bill and a credit card), so I entered them a few days ago when the amount became known.
If you accepted this Reminder 3 or 4 weeks ago, that may have been before Quicken's potential fix for this problem.
Please keep checking for any duplicates of Reminder transactions that you accepted recently.
June 9/26, still having the same problem as others in this thread with Quicken matching / duplicating transactions downloaded via OSU. As a result, account balances reported by Quicken are wrong. The problem was reported by others early April. When will Quicken have this problem with the program fixed?
Yes, I'll be keeping an eye on that.
It will be a while. I have just entered next month's instance of the one that occurred today. That's the first of the troublesome ones that I have entered since the potential fix was announced.
I've never had any trouble with the ones that I enter in the register within a few days of when they happen. So not having problems with them will not prove the fix is working - in my case anyway.
