This discussion was created from comments split from: One Step Update wants to treat my 401(k) contribution as a security.
I posted 10/3, 10/9 and another date I can't see on this issue. Still happening, see screenshots OSU'd yesterday.
Kinda defeats the purpose of OSU since I have to login to Fidelity NB anyway to get the details….
while trying to fix the incorrect downloaded entries above, I discovered the 1st/top transaction (10/26/26, sold, fees, .007 shares @$277.142857) belongs in my wife's 403b Roth account at Fidelity NB.
How can this be?. OSU is completely unreliable.
Hi @John Patriarca,
Thank you for bringing this to our attention. I'd like to investigate the issue with transactions appearing in the wrong accounts separately from the existing security-matching issue.
Regarding the October 26 transaction that you identified as belonging to your wife's 403(b) Roth account, could you please clarify a few things?
Separately, please know that the previously reported issue involving contributions and fees being incorrectly treated as securities is still under investigation. Our team is actively working on that issue.
Thank you for your patience and for helping us investigate these concerns.
(CTP-18776)
Thank you for your response. That's an interesting behavior!
As a next step, I would recommend saving a backup of your Quicken data file and then deactivating and reactivating the affected accounts. Please follow the steps below:
Deactivate account:
Reactivate account:
Please let me know how it goes.
Typical Q response, have the user do more work. Your telling me to deactivate/activate 4 accounts. That are already active. I've been using Q for over 35 years.
What is Q doing to fix this problem?
I understand your frustration, and I sincerely apologize that the troubleshooting steps suggested so far have been inconvenient, especially when you're dealing with four accounts that are already active.
If the suggested steps don't resolve the issue, I encourage you to contact Quicken Support so they can investigate further, walk you through more advanced troubleshooting, and escalate the matter if necessary.
You can find the Quicken Support phone number here: Support Home | Quicken. Phone support is available Monday through Friday, from 5:00 AM PT to 5:00 PM PT.
I apologize that I could not provide a more direct solution, but please don’t hesitate to reach out again if you have any other questions.
Subject: Fidelity NetBenefits 403(b) — Spouses at Same Employer, Transactions Downloading to Wrong Account — Request Engineering Escalation
I am reporting a persistent issue with Quicken Classic for Windows involving two Fidelity NetBenefits 403(b) accounts belonging to my wife and me.
We are both employed by the same employer, participate in the same employer-sponsored retirement plan, and have separate Fidelity NetBenefits login credentials. Both accounts are maintained in the same Quicken data file.
Problem:
Quicken repeatedly associates transactions from my wife's Fidelity 403(b) with my 403(b) account.
The problem is particularly deceptive because initial account activation and linking may appear successful. However, when subsequent payroll contributions post (approximately twice monthly), Quicken again downloads my wife's transactions into my account.
Previous troubleshooting:
I have repeatedly attempted to correct this through account deactivation, reactivation, and relinking. These procedures may appear to resolve the issue initially but fail when new transactions become available.
Some troubleshooting attempts have also created additional account and transaction problems, requiring substantial time to correct.
Current workaround:
I maintain online updates for my 403(b) while manually downloading and importing my wife's transactions. This avoids the incorrect account associations but defeats the convenience of automatic transaction downloads.
Request:
I believe this may be an account-identification or matching defect affecting spouses participating in the same Fidelity employer-sponsored plan.
Please:
I am not requesting another round of standard deactivation/reactivation troubleshooting, which I have already performed repeatedly without a lasting resolution.
This is more than an inconvenience. Automatically assigning one person's retirement transactions to another person's account is a financial data integrity issue that can produce inaccurate balances, contributions, and investment records.
I would appreciate confirmation that this behavior is being investigated as a potential software defect rather than treated solely as an individual account configuration problem.
I agree w/Tom. Q needs to stop asking their paid subscribers to solve Q's software problems.
Request Engineering Escalation!
[Removed-Disruptive]
Hi @John Patriarca & @Tom Hood,
Thank you both for sharing additional information and the troubleshooting steps you've already tried. @Tom Hood , I also appreciate you submitting your logs. I've forwarded them to the appropriate team for further investigation.
@John Patriarca , could you please submit your logs as well? This will help our team gather additional information to investigate the issue.
To submit your logs, please follow these steps:
To send your logs:
Once submitted, please let me know. I look forward to your response!
(CBT-1324)