What’s Going On Between Fidelity and Quicken?

After 6 weeks of missing transactiosn with Fidelity, Quicken support helped me resolve the Fidelity missing transaction issues last week (week of September 16). After that, no missing transactions through 9/24. This morning (9/25) the app updated to R64.30. Now Fidelity transactions won't download again. All other instituitons (banks and credit cards) download transactions without a problem. Now I get error code CC-501 for Fidelity Investments, and no downloads

When I launch the Quicken app, the Quicken logo briely appears and that logo includes the Fidelioty logo with words like "Powered by Fidelity". That implies some sort of special relationship with Fidelity. When can we expect the Fidelity issues to be fixed for good? - Frustrating

Does anyone know where we submit invoices to Quicken to bill them for our time?🙄 This is beyond rediculous, even with the bar set extremely low from countless past fumbles.

For over a week, I was having issues downloading transactions from one Fidelity account. I had no issues on the other 5+ Fidelity accounts. After wasting a lot of time resetting the account, deactivating and re-activating, opening old files before the issue, etc. the account uploaded everything last night.

Today (09/25/25), Quicken launches the R64.30 "fix" for Fidelity accounts and now the account, which was finally working after more than a week, is no longer updating. Did anyone test the update before implementing?

I found it OK at 11:39 AM MST ( 2:39 PM Eastern)

I have experienced the same thing over the last couple of days. If this is going to be the norm, I will wait until the middle of the afternoon to update Fidelity.

Summary: Still Not Working Properly

Yesterday, Thursday 25 Sept 2025, after updating Quicken Deluxe to R64.30, I successfully performed another reauthorization with Fidelity. This morning after downloading Fidelity updates, the same issue identified above still exists; the DC connection works properly, but the EWC+ connection did not include the sale of FZDXX in the investment portion of the split account to cover the check withdrawal.

I'm very glad the Sept 25 switchover passed without disabling the legacy DC connection.

Quicken Classic Deluxe; Ver R64.30, Build 27.1.64.30; Windows 11 Home – Quicken user since Windows 3

I received an update (Quicken Classic version R64.30 build 27.1.64.30) that allegedly fixes the Fidelity issues, but did absolutely nothing for my Fidelity HSA account. The previous "new method of connecting" made a disaster of the account, adding multiple money-market transactions & short-cover transactions (?), changing previously reconciled transactions, etc. The net result was a unfathomable balance mismatch. Additionally, no new REAL transactions have been downloaded in several weeks, even though they show up on the Fidelity website as activity.

Again, the "update" appears to do nothing. Meanwhile, I deleted all the extraneous transactions and am about to disconnect the account from online access altogether unless this can be resolved quickly

Like another recent post, I've been using Quicken for decades and have never encountered such situation

Another difference between DC and EWC+ connection methods. I did a Roth conversion Friday, the DC method properly recorded the transaction as Remove shares in the Traditional IRA account and the Roth IRA as Add shares. However the EWC+ method recorded the same transaction incorrectly as a Sell shares in the Traditional IRA and the Roth IRA as Buy shares.

Plenty of issues remain to be resolved.

Quicken Classic Deluxe; Ver R64.30, Build 27.1.64.30; Windows 11 Home – Quicken user since Windows 3

I'm getting the "reauthorize" prompt after having successfully migrated from zzz-Fidelity DC to Fidelity EWC+. After some tweaks and upgrading to R64.30, it was working well, including treating MMFs as cash. Now it seems like it's going backwards.

I'll wait a couple of days until I hear more reports from those who go through the reauthorize process I'm being prompted to do.

Is rolling back to DC with an older backup still an option?

Upgraded to R64.30. At first was not getting any transactions. Now seems to be working OK for 2 accounts. Will wait and see how the end of month downloads (mainly Interest) work out tomorrow before re-activating my others.

Hello @Quicken Kristina,

I am managing 2 identical Quicken files except one has been reauthorized and therefore uses EWC+ and the other is still using the old DC connection method. When I detected this difference with handling a Roth conversion I manually fixed the EWC+ file. However, I'm maintaining a backup of the DC file so I can check if this issue is fixed in the future (I probably will not perform another Roth conversion this year). This issue occurred on a routine update a few days after the transition from DC to EWC+. I've checked and if I do another reauthorization using my backup, the same issue occurs on this one Roth conversion. Roth conversions performed prior to the transition were not impacted.

I'm working to debug a couple other issues I've noticed and question if this is the proper way to inform Quicken and/or Fidelity as I discover differences between the DC and EWC+. Please let me know if there is a better way to provide details.

BTW, I'm a retired SW/FPGA/ASIC Engineer who has extensive debugging experience, thus I use a very methodical approach so issues are repeatable.

I run both a Fidelity DC and EWC+connected version of the datafile. I used the DC datafile to create a template copy and then reconnected all the accounts in the template copy including connecting Fidelity with EWC+. It's kind a doublecheck of accuracy between the working DC version and EWC+ version during the cutover period. It also showed me corrections I needed to make (or report as errors) in the EWC+ version to make it match the DC version balances while knowing the DC version was still around to get accurate results. I had to make some corrections to some 20 core Money Market Fund transactions in the EWC+ version. Now both the DC and EWC+ version match every day and I feel less stressed about cutting over.

For me, many dividends are being downloaded incorrectly as deposits.