Adding another voice to this issue. As with all, stuck since March 5th or so. It seems pretty clear now that NetBenefits changed their access to "Fidelity Access", away from user id / password and Quicken has not implemented this change.
Just wanting to report that I am having the same issue in that the "Update Accounts" fails for Fidelity Netbenefits accounts with error OL-220-A since March 7th 2023. I have Quicken Premier Version R48.15 Build 220.127.116.11 on a Win10 PC.
I am reviewing this alert page and hoping for a status or some sort of update, thank you:
Any progress on downloading transactions from Fidelity NetBenefits? I've had two software updates and still cannot download transactions from Fidelity NetBenefits.
Apparently, Fidelity implemented a new multi-factor authentication (MFA) Is Quicken taking action to support this new MFA? Does Quicken have the ability to adopt or is Fidelity completely blocking access? I'm confused whether this new MFA is causing a "temporary interruption" or if this is a termination of third party downloads from Fidelity (Fidelity's MFA will not support third party access.)
Hello @Tammy Van Buren,
I have sent you a direct message, please navigate to the inbox in the top right-hand corner of the Community page and check your inbox.
I too DM'd @Fidelity this morning and got back a reply in minutes. In my case the NetBenefit funds are a 403(b).
Thanks for messaging us about this! We understand some clients are receiving an error related to importing 403(b) data with Quicken. The case has been escalated internally at Quicken and Fidelity, and teams are actively working on a solution. We do not have an ETA on the fix yet, so please continue monitoring your 403(b) on http://Netbenefits.com for now. Please let us know if there's anything else we can help with.
I have three Fidelity 401K accounts set up for online download with Quicken (Quicken Windows subscription version). These accounts have downloaded without issue, for the most part, for several years. Beginning around March 11, 2023, all three accounts stopped downloading, generating the error code OL-220-A. The issue continues through today, March 21st. Quicken says it is a Fidelity issue, that is known and being worked on. I believe that Fidelity is the issue since all of my other accounts (at least seven others) download with no problems.
I totally agree that Quicken needs to be pressuring Fidelity — they are our advocates in this matter. Moreover, they should be sharing any progress/feedback with us (even if it's bad news). My comment was purely in response to the notion that Quicken could "roll back" a software change to resolve this issue as you had suggested.
Fidelity Access is Fidelity's newest, OAuth-based integration method, and I would expect Quicken is aware of this and has adoption of this new API on their roadmap. We'll know it's happening when they convert the Fidelity integration to EWC+, just as they've done with a bunch of other FIs recently.
That said, I don't see any evidence that Fidelity has, at this point, "shut down" the OFX-based integration API that Quicken currently uses. The endpoint is still up and running, but it's returning invalid data for some 401k accounts. (Note that the OFX API for non-401k Fidelity accounts is still working as expected).
It is a valid question though of whether, given OFX is deprecated, Fidelity feels any urgency in fixing the error they've introduced, especially if there are only a few integrators that leverage it. Instead, they could tell Quicken (and others) to switch to their new APIs, but that will take some time.
To rightfully assign blame in this case, we would need to know what, if any, end-of-life expectations Fidelity set with integrators for the OFX API. If Quicken knew such a thing was coming and missed the date, then clearly this would be Quicken's fault. But if Fidelity broke a deprecated but still-active API, then Fidelity should be blamed.
Another update from quicken for me today; still the same issue on the Fidelity/Netbenefits sync. I appreciate everyone keeping this going. Misery loves company :)
The problem with your links to the MFA and 3rd party info is that the regular Fidelity accounts are still operating and updating. The error is only on the Net Benefits side. If you look right now you won't see Quicken listed as 3rd party acess. Quicken isn't a financial aggregator. I believe the problem is solely in the connection method, either the Direct Connect, Web Connect, or Express Web Connect/Quicken Connect methods or a combination of these methods.
But again, it really doesn't make sense that Fidelity accounts are OK, but the Fidelity Net Benefits accounts are at issue since they both are Fidelity.
I sent Fidelity another email basically stating if the 2 kids can't play nice and talk to each other, I can easily cancel the Quicken subscription and move my accounts to another investment firm. It's BS that this has gone on over 2 weeks and niether side really wants to say anything except for Anja.
Same thing here. Add this to the Citi Bank and AMEX issues ongoing, and it really makes me cringe given the $78 renewal I just paid Quicken for. Common folks …. what the heck is going on.
One of my Net Benefits accounts is a brokerage account, regular stocks and funds with CUSIP's, so it's not the lack of CUSIP's. I have another Net Benefts account with a fund in it, no CUSIP, no update since 3/6, but somehow they reported it as be 2x the value that it is.
I'm not even going to fool with it anymore until they send an update that the problem is fixed.
My Fidelity account updates, but when you used to get the window that said x # Fidelity accounts updated, x # Net Benefits accounts updated, now it only shows the error for Net Benefits, doesn't say anything about Fidelity or that Fidelity updated even though it did.
> @Brian14 said:
> @Tony Luers
> Correct, connection issue only occuring with Fidelity Netbenefits accounts. However, Fidelity customer service agent said it may be a matter of time before the Fidelity Investment accounts experience the same issue. He suggested customers may experience a temporary interruption and then went on to say MFA will not support third party access. Seems like contradictory statements from Fidelity.
I desperately hope it is not Fidelity's intent to eliminate third party access if what they characterize as such are financial software such as Quicken, [Removed-3rd Party Software] or any other software listed as "The Best Personal Finance Software for 2023" - PC Magazine (referenced earlier in this loooooong thread).
So if Fidelity NetBenefits is the canary in the coalmine and issues are on the horizon for Fidelity Investments, here's hoping Q is paying attention and working on potential solutions quickly. Hmmmmmm.
Since it is my investment tracking software (not Q) that is not working correctly, I'll figure out how to manually download and import there. I was planning on being out of my NetBenefits accounts by end of this year already, so that headache is not to worry. Although this will be a much bigger issue for all of my Fidelity Investment accounts, if and when it comes to that.
I am very happy that my banking software (not Q) is downloading both Fidelity Investments and NetBenefits accurately via OFX Direct Connect. Inspection of the OFX logs shows that they have implemented some additional security measures involving Trusted Certificates, TLS requests, and cipher suites. Looking back through the Software changelogs for the past two years, this is something they put in place in April 2019 ("OFX connections now default to using system certificates, with the ability to opt-in to OFX-specific certificates for individual connections") and Jan 2021 ("Restored custom TLS layer settings for connections requiring custom tweaks (including Fidelity")).