Fidelity Access
If I understand correctly Fidelity is replacing use of direct connect / OFX protocol with a new protocol referred to as "Fidelity Access". From what I can see Moneydance (and Quicken) do not (yet?) support this new protocol.
This is important in that Fidelity has indicated the continued use of MoneyDance then violates their lost funds replacement guarantee due to use of nonapproved 3rd party. Note that their use of term "3rd Party" seems different than infinitekind.
I note that Vanguard has also stopped use of OFX and does not seem to have a replacement intent. Have to use downloads by account.
Can anyone at Moneydance provide current status of this? Will Moneydance be updated to support Fidelity Access?
Showing page 15 out of 15. View the first page
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
421 Posted by rlsantella on 06 Apr, 2026 09:41 PM
mmd
Here is the CSV file with account nukmbers changed. The extension does import it as a Xfr transaction, which is fine except that it records it as a transfer from my checking acct which is strange. The issue is that it does not put the bond CUSIP and name in the security field as was the case in the past. It is difficult to tell same state munis apart without the CUSIP which is in the symbol field in the CSV file but does not get imported into MD.
422 Posted by mmd on 07 Apr, 2026 10:10 PM
I’ll take a look at both csv files thanks!
Currently a little busy with outside things and also the work 100% cpu usage bug with Moneydance which seems to be still affecting me despite turning off sync completely and trying to clean it up in toolbox too
423 Posted by mmd on 09 Apr, 2026 12:58 AM
See v13 below . Interest and muni exempt interest now recorded as dividend. Obviously security still has to be added manually. Don't rename the .mxt file from import_fidelity.mxt
https://github.com/SnapEscalatorCarrousel/import_fidelity
Support Staff 424 Posted by Sean Reilly on 10 Apr, 2026 09:10 AM
Hi Everyone,
I know it doesn't appear this way from the outside due to the lack of a release in nearly 14 months, but we are still actively developing Moneydance.
The choice to use Plaid was not due to the lack of a long term strategic view, but rather the only long term strategic view that made any sense at all. We can't support custom connections for every financial institution, and need to use a small number of protocols that can cover the largest number of financial institutions. In fact, using a aggregator such as Plaid was specifically recommended by the largest banks such as Fidelity, Citi, Chase, and Schwab.
To address the Fidelity issue specifically, we are working on restoring this connection via Plaid. Connecting to Fidelity via Plaid is not a technical issue, but rather about meeting legal requirements - the primary requirement being SOC 2 Type 2 audits which we are working on now. I am very sorry for the delay in getting this process completed.
Thanks,
Sean
--
Sean Reilly
Developer, The Infinite Kind
https://infinitekind.com