Item added without my input

JamesE

I recently opened Quicken on my PC and saw that the balance was way off. I had reconciled the account at the end of last month, so knew what the beginning balance should be, but the reconciliation screen also showed the beginning balance to be off. I finally found the problem as a deposit that was a duplicate from one that was entered almost a year ago. It showed that it had been entered the same time as the original, and was reconciled. I deleted the item and everything was back to normal. I've been using Quicken for many years and have never seen anything like this. Would appreciate any insight as to what might have happened. I really don't want to have to deal with this again.

Jim

Quicken Kristina

Hello @JamesE,

To assist with this issue, please provide more information. Is the account this happened in connected to the financial institution to download transactions into your Quicken file, or is this an offline account that you update manually? You mentioned this happened recently, do you recall when? Was only one account impacted, or have you observed the issue in multiple accounts? Have you recently had to cut/paste transactions into the problem account (for instance, if an account wasn't working right, and you had to re-add it as a new account, then cut/paste the history into the new account)?

If it is a connected account, which financial institution is it connected to? Did you recently deactivate/reconnect the account? Do you have your account set to automatically do a reconcile after downloading?

I look forward to your response!

JamesE

Kristina,

Thank you for your response. In answer to your questions: This account is not connected to a financial institution. I manually input all data. The event happened about two weeks ago, and I was able to find the affected entry yesterday. I have multiple accounts on the system, but this is the only one that I've ever had such an issue. This is the most used account though. If the issue was only that an additional entry showed up, I probably would think I just made a mistake and duplicated that entry, but the fact that, not only was there a duplicate entry, but that it was reconciled tells me something very different was happening. Also, as I mentioned, the bogus entry showed up as being reconciled, and added to the prior(correct) balance on the reconciliation screen. One other fact. When I did find the bogus entry, it was immediately after, or maybe before, the correct one, and was identical in date, payee, amount and category.

Thanks again for your help.

Quicken Kristina

Thank you for your reply,

Since this is a manual account, the most likely cause would be a file-specific issue. Do you keep your Quicken file directly on your local hard drive? Is it synced with any cloud service, such as OneDrive, iCloud, or Dropbox? Did anything happen just before you noticed this issue, such as a program or computer update, program or computer crash, etc.?

Have you noticed any other issues in your Quicken file? You mentioned that you noticed this while reconciling and you manually corrected it. Has the issue happened since? Does reconciling the account trigger further misbehavior?

Thank you!

JamesE

Kristina,

I've not had any other issues with Quicken. The files are on my hard drive, and the only thing it's synced with is my on line backup. There's been no issues or crashes. Everything on the program worked fine, except for the additional, reconciled, entry showing up from a year ago. The reason I went through the reconciliation process was that I was trying to see if I could find where the bogus entry was located. As it turned out that didn't work as that entry was reconciled, so it didn't show up. What I was able to do was to subtract the beginning number that showed up on the new reconciliation screen with the real number I had from before. I then did a search for that number, and that's how I found the duplicate entry from a year ago. Knock on wood, but there have been no additional issues.

Jim

Quicken Kristina

Thank you for the follow-up,

There is troubleshooting for file-specific issues, but if this behavior was a one-off that you've already corrected, it may be better just to leave it be. There wouldn't be any way to tell if the troubleshooting fixed it, since the problem hasn't repeated.

Thank you!