Security is a big deal for Banks and Brokers (and everyone else whether they know it or not). They develop their own systems and guard them scrupiously. They understandably do not want to share their security protocols or access with anyone else. The more hands there are sharing, the more chance of a security breech. Every time a comapny tightens their security, Quicken has to adjust and either negotiate, or cirumnavigate the security obstacles with a company that does not want to share. So far it was happened with Schwab, and now Fidelity NetBenefits, and others. The pattern will repeat. I thik the days of data consolidators are numbered. There is nothing it for the financial companies themselves.
At this point, given the info here and in the r/fidelityinvestments sub-reddit, I think we can be fairly positive about the root cause of this issue: on or about 3/8, Fidelity made a change to their OFX export API which broke Quicken's ability to import data for certain types of securities. More specifically, Fidelity is omitting the unique CUSIP that identifies some 401k-specific mutual funds, which is a field required by Quicken to match these funds against the holdings in your Quicken file. (Note: the CUSIP is a required field based on the OFX specification, so Fidelity's OFX export is now non-compliant with OFX standards.)
It appears that Quicken and Fildeity are both aware of the problem, although no ETA for a fix has been provided. In terms of a fix, there are really just a few possible options:
Hopefully, Fidelity fixes this soon as this change clearly makes their OFX export out-of-spec with OFX standards. Again, it may depend on how many partners are consuming their OFX API and how much impact those integrations have on Fidelity customers like us.
Fidelity NetBenefits - Valuateion/Updates Not Working. I have found no way to resolve this. What is Quicken's team doing to resolve this with Fidelity and when will this be fixed? (Windows 10 O/S). I am a very long-time Quicken Premier (online) user, however it is unacceptable to have to manually login to my Fidelity account for balance informatio then manually update either a postive/negative cash balance in order for Quicken to reflect correct valuation.
What are you seeing that makes you believe there is a TLS issue? For me, the Quicken OFX Log shows that the HTTPS connection to Fidelity appears to be working as expected, but the OFX data that's returned from Fidelity is non-compliant (which results in a "Parse error. Current object: SECID Missing Tag: TAG UNKNOWN" in the Connection Log).
As for OFX vs FDX vs scaping, the industry is certainly moving to more secure, reliable, API-based approaches such as FDX. These types of approaches no longer require the aggregator (e.g. Quicken) to store your credentials for the FIs you do business with. We've seen Quicken making this transition as they've converted different FIs to EWC+, which relies on FDX (or other FDX-like protocols) to exchange info without storing your username/password.
Such changes were inevitable as aggregation moved off of the desktop (i.e. locally-installed software like Quicken) and into the cloud (e.g. Mint, Personal Capital, …). When passwords were stored locally on your computer, there was little risk of (wide-spread) exposure. But storing millions of users' credentials in the cloud is high-risk.
As for scraping, certainly this is used for many smaller FIs, but for large FIs like Chase, BofA, Fidelity, Schwab, etc., scraping is a largely thing of the past. Now, as FIs deprecate their OFX integrations, they are being replaced with more secure, FDX-based (or FDX-like) APIs. None of these large FIs will expect aggregators/integrators to revet back to scraping; in fact, their licensing agreements likely disallow it.
I am having same problem as others are reporting, all of my other non-Fidelity NetBenefits account are updating just fine. I even have another separate Fidelity account that is updating just fine. Problem appears to be limited to the Fidelity NetBenefits account. The last sucessful update was 2/19/23. In the One Step Update Settings window, it shows up as "Fidelity NetBenefits: error recovery". I have reset the two accounts contained within Fidelity NetBenefits, with no improvement. I have Quicken Deluxe, Version R48.9, Build 22.214.171.124.
Please get this fixed.
and being a long time user - it would help to know….
- what version ?
- what error code or message - or just nothing downloading ?
QWin Deluxe Subscription - sticking with R47.15 - Win10
Quicken Premier, version R48.9, build 126.96.36.199, windows 10 enterprise.
Error: OL-220-A | 2 accounts
Quicken is unable to complete your request
Shows last successful download March 2, 2023
I regularly update quicken software whenever prompted. I do not recall which version /build this issue started with, but updates had been working fine until about March
guess you missed this ongoing thread and Alert -
From my CONNLOG.TXT, I am getting the following error:
20230319 13:31:27: Parse error. Current object: SECID Missing Tag: TAG UNKNOWN
Ditto, same problem. I am about to delete my auto-renewal of quicken if this doesn't get fixed ASAP. My Fidelity NetBenefits account has not updated since 2/19/23.
Having the same issue. Its been happening for around a few weeks.
Fidelity investments is doing a major overhaul of thier systems trying to tie them together between fidelity investments UI and netbenefits UI especially around brokerage link transactions. I am sure it is interface related and is no longer parsing like it should be with the new system changes. This will probably need to be rearchitected with a new interface on quickens end.
Add me as another with the same issue starting around the beginning of March. Also having problems with USAA trying to force me to reauthorize for no apparent reason.
adding to the long chorus of same problem. my spouse's Netbenfits account connects and downloads fine. but my account you can see some of the 401k accounts but the Brokerage Link account doesn't show up anywhere.
Please fix!!! We're paying $60/y for Deluxe!
If I understood your response correctly, you are using separate applications for banking and for investment tracking, neither of which is Quicken. By comparing those applications' logs, you've inferred that a TLS-related issue is preventing the investment tracking app from downloading NetBenefits data. Is that right?
I can say unequivocally that the Quicken issue is not TLS-related. If TLS were the problem, Quicken's OFX log would not be showing any data as the TLS error would prevent Quicken from establishing an HTTPS connection to Fidelity. The presence of OFX data in the log indicates that the connection must have been succesful.
Of course, I can't comment on your other software applications; however, the fact that another application is also failing for NetBenefits does imply the problem is on the Fidelity side.
It sounds like you're suggesting that Quicken is scraping data from the Fidelity UI and that this failure is tied to recent Fidelity UI changes. I can assure you that is not the case; Quicken uses a Fidelity-provided API to pull data. That said, if Fidelity is attempting to unify Retirement and Investment Services, it's certainly plausible that some back-end change related to that effort has had this unintended side effect.
I would agree that Quicken is responsible for working with Fidelity on our behalf to get this fixed, and I certainly wish Quicken would be more forthcoming with what they've found, what interactions they've had with Fidelity, etc. But, I don't believe Quicken can fix this unilaterally. It's unfortunate, but as advocates for their users, Quicken is completely tone-deaf: their lack of transparency is left for most of us to interpret as indifference.
I just started using quicken today! Loved it until I downloaded my fidelity net benefits accounts. No error message, but for some reason it looks like there is a big. My account values are exactly doubled, mistakenly
I am continuing to get Fidelity NetBenefits OL-220-A errors, "Quicken is unable to complete your request". Last update of my Fidelity NetBenefits account was March 7, 2023. Attempting to add an account from Fidelity NetBenefits to a 'New Quicken File' results in: "Sorry. We encountered an error. (It's not your fault.)" Updating Quicken to 'Version R48.9 Build 188.8.131.52' on Windows 10 Home did not resolve the issue. It looks like Quicken may already be aware of this issue which has been going on for quite a while now. It would be nice if they would provide us with an update when they have identified the problem and provide us with an "official" explanation of the cause of this issue.
It doesn't matter what version or anything else. As far as the error code, if you look at the thread you're on, all 15 pages is OL-220-A for Fidelity Net Benefits accounts only.
Good Morning everyone,
OL-220-A Error at 2 weeks now with no solution.
We do not have an ETA at this time for a resolution for this issue, though our teams continue to work towards a solution. We apologize for any inconvenience and thank you for your patience.
Same problem no official response from Quicken.
I cant Believe I'm paying for this Abuse
I continue to have issues updating the value of my Fidelity Net Benefit account in Quicken. I have not changed my Net Benefit "securities" except quaterly when some are sold to pay management fees. The last sale was 1-3-23 and those sales posted properly to Quicken. While troubleshooting my account I went to Fidelity and forced them to download transactions from the beginning of the year. I knew it would duplicate the 1-3-23 sales but that I could delete them. Interestingly it duplicated them with slightly different security names. For instance my "Total US Stock Index" became "Total US Stock Index(OJJ4)". When I look on Quicken for my holdings in the account these newly named stocks show up as new stocks with a negative value. Usually Quicken will ask if new stocks are being added so you can link them to the old stock names but this did not happen. I was wondering if this could be part of the update problem?