Fidelity NetBenefits (QWIN)

@DynamiteD

This is exactly what I see in the OFX data I receive from Fidelity as well. For the one mutual fund (which I believe is employer-specific in some way), the OFX data shows an empty <UNIQUEID> element in the data. Looking back thru Quicken's OFX Log, I can see that the CUSIP was present in the OFX up through 3/7, but all OFX files after that point have an empty UNIQUEID for this one fund.

More specifically, here is the <SECID> element for this mutual fund prior to March 7:

<SECID><UNIQUEID>TD8R<UNIQUEIDTYPE>CUSIP</SECID>

After March 7, the same security now comes with the following <SECID>:<SECID><UNIQUEID><UNIQUEIDTYPE>CUSIP</SECID>I also noticed that there's an <FIID> element for each security, which presumably is meant for the financial insitution's own internal unique ID. That also used to be populated with "TD8R" for this fund but is now empty. So, Fidelity has simply stopped transmitting any unique identifier for this security.This is a pretty severe, breaking change on Fidelity's part, and Quicken's choices for working around this (in absence of a fix from Fidelity) are limited and potentially brittle. Our best hope is that Quicken can convince Fidelity to revert to the prior behavior, although, as has been pointed out, Fidelity is likely slow-moving given their size and potential impact of any change.

@DynamiteD

Looking thru Quicken's OFX Log, I can see that Fidelity stopped transmitting the CUSIP for one of my mutual funds on Mar 8. Prior to that date, the <SECID> data for all securities was populated with the CUSIP (in the <UNIQUEID> element), but after that date, the <UNIQUEID> element is empty for this fund.

This is a severe, breaking change on Fidelity's part, and in absence of a fix from Fidelity, it will be challenging for Quicken to work around this in a reliable way. Our best hope is that this defect is impacting many other consumers of Fidelity's OFX data so they feel some urgency in getting it resolved.

I do share everyone else's frustration that Quicken isn't more transparent about the root cause of this issue or the progress of any communications they are having with Fidelity. Quicken would likely build a bit of goodwill if we all knew they were pushing Fidelity hard for a fix or could relay any info they get from Fidelity around an ETA for a resolution.

Why no response from quicken

The last successful download from Fidelity NetBenefits was on 3/7/2023. Since then I have been getting an OL-220-A error message. The downloads from Fidelity Investments have not been affected. It is now 3/17/2023, 10 days and still no fix. What is going on. You can't tell me it takes 10 days to fix something that was once working. Undo whatever was done to make it stop working.

Ally and Fideliity net benefit downloads still broken.

Not a good look for quicken when their loading screen advertises the tight integration with Fidelity.

Please fix asap and push update.

Ok, so right now, the users have it narrowed down to 3 things:
1) Fidelity stopped downloading CUSIPs for some securities (I think the ones that are custom to the 401ks, like their version of Fidelity ContraFund (FLCNX))
2) Some security changes that have been not communicated very well between Fidelity and Quicken

3) Quicken not paying the Fidelity to use their APIs
Here is the update from Quicken on 3/15

MikeZNC Member ✭8:44AM

Also having the same problem with connecting to Fidelity NetBenefits

Been an issue since 3/7/2023

Quicken the entity is not driving the scraping cost to Fidelity. I, as a paying Fidelity customer, am requesting that Quicken obtain my information on my behalf. Money grab by Fidelity.