Fidelity EWC+ 401(k) incorrect transaction--Bought should have been Xout

EvDob

Here's what downloaded:

The Bought of Unidentified Security should have been an Xout to a BrokerageLink account.

Now to get sidetracked, when accepting these, I got this:

Seems to me Quicken should not be trying to make a zero amount transaction into a transfer. So I said No. Here's the register:

The Transferout transactions with DC used to have a Memo such as "TRANSFER;VANG VMMR-FED MMKT OQQL;as of 07/18/2025" indicating a Roth in-plan conversion (website had more info), but now they're useless as the Memo is empty and the amount is zero, so I delete them.

This is after my manual fixes:

I filed a problem report.

Quicken Kristina

Hello @EvDob,

Thank you for letting us know you're encountering this issue. The issue with Unidentified Security downloading into Fidelity 401(k) accounts is a known issue, although a recent update was expected to correct it. For more information, please see this Community Alert:

https://community.quicken.com/discussion/7966125/ongoing-9-29-25-fidelity-investments-401-k-unidentified-security-during-cutover

You mentioned that you already manually corrected it. However, the alert has specific steps to follow to correct the issue. If you haven't already followed all the steps, I recommend doing so:

1. Edit the security for each transaction from Unidentified Security to the correct security that appears on the bank website.
2. Once all transactions been edited, delete the Unidentified Security. 
3. Go to Tools > Online Center and choose Fidelity Investments.
4. Choose the account for the 401(k) and then click the Holdings Tab
5. Click Compare to Portfolio, which will prompt for Compare to Portfolio and should bring up matching again.  Match to the correct security. 

For the transfer issue, was this a one time occurrence? Did you get the prompt when connected via DC, or is this a new behavior under the new connection?

I look forward to your reply!

EvDob

@Quicken Kristina I'll try those steps for the next paycheck in two weeks, but it seems like it's more of a hassle than what I did to correct the problem. Is there a JIRA ticket for this? It's certainly not fixed by the updates I've installed. You can probably see I'm running R64.35.

I think this is the first time I've seen the transfer issue.

Quicken Kristina

Thank you for your reply,

For this particular issue, there is an alert for the problem, and if the instructions in the alert do not correct the issue, an individual ticket is created.

Thank you!