Payroll/Paycheck Splits Disappeared
I have lost all detail dating back to 5/12/2017. Deposits that had detail splits now just show as 'Salary Spouse' or some other random category that was in the split list originally. This has caused all of the 401k contributions (set as a split to deposit into another account in Quicken) to disappear and my 401k accounts to now show huge negative cash balances.
Restoring a backup isn't the right answer if a recent software update caused the issue as I'll be back in the same boat shortly. Please determine root cause and solve it! I work in Quicken Classic daily and just discovered the issue this morning when I opened a related 401k account so a recent software update may be the culprit.
I have restored from a backup I made yesterday (12/29 2:57pm CT) and the split details are present in that file. I will move forward on the restored file.
I am currently on Quicken Classic Premier, Version R53.32 Build 27.1.53.32 - Win 11 Home.
Comments
-
The One Step Update is causing this problem. After a scheduled update early this morning (6:53AM CT) the issue has returned. I have lost prior transaction split details. There are also significant issues with budgets - actual historical transactions in Category A, for example, are showing up in Category X transaction history when comparing to Category A budget even though the transaction itself is properly associated with Category A. There appear to be tremendous data integrity issues now following One Step Updates.
0 -
Do you have sync to Mobile/Web on?
If you do, I suggest you try it with it off.
Signature:
This is my website: http://www.quicknperlwiz.com/0 -
Yes, I sync to Mobile/Web. Appreciate your response. Yes, turning it off should bypass the issue for the time being given what I experienced this morning. I rely on this sync extensively to enter new transactions on the go and certainly need this bug smashed. Root cause must be found and irreversible correct action implemented. Since discovering the issue, I have downgraded to v53.26, restored a backup from a few days ago and am now syncing with cloud (resetting cloud file). I'll run on this prior version to see if the 53.32 upgrade may have caused the issue.
Just when I had thought to myself that Quicken Classic had finally stabilized a bit and that I hadn't seen any major issues in the past several upgrades … BOOM!
0 -
All I can say on the matter is the Sync Mobile/Web has caused data file corruption from the day it was released in Quicken 2015. How many reports on it doing so have gone up and down over time, but it has never been zero.
Signature:
This is my website: http://www.quicknperlwiz.com/0 -
Agree though I seem to have had pretty good luck with it. I just think they've got too much built into the sync process. Seems like too much logic in there … just 'sync'! 😕
0 -
From what I understand Quicken Mac is much better. Most likely because of the newer code base. But yeah, from what I have seen "sync" has way too much "authority" to change almost anything in the Quicken data file without any kind of user input. It has changed, pay checks, memorized payee, budgets, transactions (even old ones), … All with no feedback to the user, let alone prompting to OK it.
Signature:
This is my website: http://www.quicknperlwiz.com/1 -
After a lot of trial and error, I still cannot determine what specifically causes the unexpected sync behavior. To bypass the issue, I have disabled one step update on the 401k investment account and disabled mobile/web sync on all accounts except the credit card account I use to regularly enter transactions via the Quicken mobile app. So far, after multiple syncs/OSUs over the past few days, the paycheck split detail in the checking account (which includes a transfer to 401k account) is not changing … consequently the 401k is still getting the transfer deposits and not showing the negative cash balance. The 401k was never sent to mobile/web, only included in OSU. The checking account, however, was sent to both mobile/web and included in OSU.
Issue apparently bypassed by giving up some of the functionality I've used successfully for a very long time. Issue not resolved, however.
2