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
425 Posted by jesmail on 11 Apr, 2026 08:52 AM
@mmd
Version 13 works, thanks for the fix!!
@Sean Reilly
Thabks for the update..
426 Posted by MikeB on 11 Apr, 2026 02:38 PM
@Sean Reilly. That's all well and good but the silence out here is deafening. We're all out here swinging in the wind trying to get our downloads to work and getting zero information or help from the IK team. We have users solving problems and creating work arounds to import information. While I appreciate their efforts this is something, in my opinion, that IK should be doing as an interim solution to the issues of importing investment data in the *.csv format. I am not going to download and install some user created program to read and import my financial data. Not only is this something that I paid IK to do via my software purchase, but I also am not going to trust any software that is not integrated into the program. It's too high a security risk for something I can do manually. So, you're still pushing forward with Plaid. Great. I haven't seen significant progress on that in years which is one reason I never opted to use it. Your competitors are out there integrating Akoya, Finicity, Yodlee, Salt Edge and others while you've been working on a singular solution that Fidelity doesn't like and will probably not support for much longer. They (competitors) are also giving frequent updates with their blogs and interim patches. You should have at least been supporting alternate solutions in parallel with the work on Plaid. Instead the direct connect has slowly disappeared from almost all the financial institutions and you keep pushing Plaid as "the solution". The user fix to import and format *csv investment data from Fidelity and others should have been lead by the IK team, not users. Every year that goes by this feels more like a shareware program instead of a commercial software package. You need to decide how much you care about retaining the loyal customers who have supported you for all these years. From where I'm sitting you don't really care if we stay or go.
427 Posted by Roger Rice on 12 Apr, 2026 05:33 AM
So, my laptop died after 14 years and i had to get a new one. The import_fidelity.mxt was working like a charm before but now I can't install it. I get:
"There was an error loading the extension file for module:'import_fidelity': java.lang.Exception: Unable to load extension with iD 'import_fidelity due to missing metadata"
My old install was windows, my new one is linux if that makes any difference.
Anyone know what I'm doing wrong?
I downloaded the zip file and renamed it
428 Posted by LarryCL on 12 Apr, 2026 05:35 PM
@SeanReilly, thank you for replying here. We do appreciate it. I agree with some but not all of the prior (MikeB) poster's comments, so as a long-time (since 2009!) user of Moneydance, I wanted to add my two cents. Perhaps this would be better in the General forum rather than in the Fidelity thread, but since you posted here, I am going to reply here. And I am going to provide some blunt feedback:
As I said, while appreciate your posting, given the silence up till this point and the lack of releases in the past 14 months, just saying 'trust us, we're working on it' is not enough. I will take you at your word that the product has not been abandoned, but there is a big difference between 'abandoned' and 'actively being developed', and I have no assurance that the latter is still true. There's no denying that development has slowed to a crawl.
I am aware that TIK historically does not comment on planned features and release schedules, but I ask you to please reconsider this stance. Providing some transparency, such as a product roadmap & release schedule, would go a long way to restoring our trust & faith that the product is indeed under active development. There are those on this forum who will chastise me for asking this ("Who are you to demand that they provide their roadmap?"), and I don't disagree. I am nobody, simply a 17 year customer, so feel free to ignore my request. But do understand that loyalty cuts both ways; the lack of active development has led a number of us to look into alternatives, and I can tell you: Moneydance is not keeping up with the competition. Beyond the Fidelity issue being discussed, some key examples are:
I'm hoping this is seen as an honest critique of the current status rather than a diatribe, and I am hoping it furthers some thoughtful, respectful, discussion. Thank you for reading.
429 Posted by dtd on 12 Apr, 2026 08:21 PM
@LarryCL - I found your message to be well thought out and that asked questions and made valid statements rather than a diatribe (which often has declaratives and implied threats).
I'd like to see Sean's current thoughts on it as well as you. i.e.
+1 to the above message
430 Posted by tonyt on 13 Apr, 2026 06:22 AM
+1
431 Posted by dwg on 13 Apr, 2026 08:08 AM
I'd like to make a comment on one point.
I do not see TiK getting into the area of creating an import solution for one institution, even as an interim solution.
If they did that the argument would then be that they should create a custom solution for any & all investment institutions that only provide CSV downloads, and all around the world as well, given Moneydance has an international user base, especially as automatic downloads do not exist outside of North America.
What would make sense is an importer for investment CSV files that used configuration files to map specific institutions CSV files to what is needed, I would think it is likely the config files would need to be created by users for the institutions they use, perhaps even exchanged, or with a central repository, at best I could only see the company offering a few examples as a base reference.
There are third party programs out there that do take CSV files and create OFX or QIF files, typically they require definition files for each institution This capability is already available for Moneydance for non-investment accounts. Investment accounts are more complicated and involved.
432 Posted by LarryCL on 13 Apr, 2026 12:24 PM
hi @dwg,
I'd like to reply to your comment that "I do not see TiK getting into the area of creating an import solution for one institution, even as an interim solution. If they did that the argument would then be that they should create a custom solution for any & all investment institutions that only provide CSV downloads".
Respectfully, I don't think there is risk of a snowball, me-too requirement if TIK were to create a custom Fidelity importer. Fidelity is in the top 3 US Brokerages as measured by assets under management, and is the largest if you include corporate retirement plans. It's fair to say that it's a requirement that users be able to import their Fidelity transactions. And, the specific issue in this case is that direct downloads were working, then stopped working, and without a custom importer, raw csv imports barely worked at all. It is reasonable to expect that TIK would have fixed this specific problem
433 Posted by tiptonbob on 13 Apr, 2026 03:30 PM
It wouldn't hurt to see an estimated solution date or range from Sean. Something would be better than continual "we're working on it" notices.
434 Posted by Tim on 14 Apr, 2026 03:08 PM
+1
435 Posted by tonyt on 14 Apr, 2026 06:28 PM
+1
436 Posted by jonathan on 14 Apr, 2026 07:55 PM
As a long-time MD user, I have always longed for more communication from IK. And, there is still nothing else out there that I know of that can do what Moneydance does! Any timeline for Plaid update, given it is dependent on a large global corporation, is not really in the hands of IK. So, while there has not been a software update in over a year, there have been no blog updates either...I am not happy. But, when I look around, while other software companies are better communicators, IK does not overpromise and underdeliver like many other personal finance companies.
So, I look forward to the day when Sean hires a communications manager and we hear more regularly. I will keep hoping for some breakthroughs soon (including MD2026/7).
And while it is unusual for "paid" software to have such a robust user community, I am so grateful that I can download transactions from my numerous Fidelity accounts. Thank you to the skilled users and skilled developers. Communications is a work in progress.
437 Posted by msumick on 16 Apr, 2026 04:58 AM
I've been a customer since 2005, TIK has done exactly what I hoped since then, been a quality alternative to Quicken and MS Money. The problems with Fidelity have been less than ideal, but they are no worse than my problems with the previously stated solutions.
I would love more communication, but I have worked for a small software company, so I understand that is not always easy. I'm Looking forward to the next version, but more visibility would be my request. Thanks Sean for 2+ decades of solid, but not perfect software.
Support Staff 438 Posted by Sean Reilly on 16 Apr, 2026 02:54 PM
Hi All,
I do apologise for the FIdelity issue and I can assure you that I am working on it. It is not a matter of programming and simply a matter of meeting business requirements of which I've never had to face before. I don't think I'm allowed to relate the specific requirements of the agreement with Fidelity, but I can relate the general problem that I'm working on every day to get downloads from Fidelity working again. The Infinite Kind is a very small company, and I am basically the only developer. I have designed and built the server side and app side of all the online banking systems that we use to specifically not ever hold financial data on our servers. However in order to prove SOC 2 Type 2 compliance we need to show that we protect customer data using best practices. The problem is that we have never had private customer data and have no plans to ever have it. Because of that, it's tricky to prove that we meet "best practices" when we don't have key-cards for each employee to access secure locations, or background checks on any employee who has access to protected information. There are countless more examples of requirements that we are working on showing that we meet, despite being outside of the way that normal companies do things.
To address @LarryCL's specific points:
There's no doubt that I should've had these apps up to par with the desktop version years ago. I'm making steady but slow progress with an Android update that syncs the full data set instead of the small "mobile" version. Once that is done, Android at least can begin to get features like investment management, budgeting, graphs and reports, and online banking.
For the past 3 years I've been porting the core code in Moneydance to kotlin and trying to remove dependence on code that is specific to desktop java. The goal here is to be able to use the same kotlin core code on desktop, Android, and iOS. Desktop and Android are now using the same core code. It'll be a little while longer before that is usable on iOS, but once it is then we'll have parity across all mobile and desktop platforms.
Rule engines are fragile and difficult for the majority of people to configure. I plan to improve the automatic learning that Moneydance already does for bank and credit card transactions. If there are still requires for a rule engine after that work is done then I'll consider making one for the power users, but I hope that will only be used as a fallback.
Yes, this is an embarrassing failure for me personally. I have had the code to do this mostly completed for years but have not yet connected a new UI up to it. This is a high priority on the roadmap, and I hope to get it into a release this year, but I can't promise anything concretely.
Our customer support team is keeping up with messages, and we do focus a bit more on the private one-on-one messages since they can only be handled internally. Private messages are the majority of all support requests, and the number of resolved discussions exceeds new ones, across both public and private.
As for a roadmap, here are the most important Moneydance things (in my opinion) that I am working on:
I'm sorry I can't give you a timeline for any of these. If I did it would be a made-up guess. The best I can say is that these will all be released when they are finished.
I would be happy to help with @mmd's extension as a short term fix for the problem with Fidelity, but I would need to get up to speed on how it works.
As for a Moneydance 2026/2027 release, I have every incentive to have a major annual update every year. I should have had a major release in 2025, but I didn't feel like I had enough visible improvements to justify it. It is honestly in most customer's interest for me to skip a year of major updates because then your purchased license lasts longer. So yes, we all want a major update soon!
Thanks,
Sean
--
Sean Reilly
Developer, The Infinite Kind
https://infinitekind.com
Support Staff 439 Posted by Sean Reilly on 16 Apr, 2026 02:56 PM
I should add that the reason we don't have key-cards or background checks is because none of our employees or contractors ever have access to your private information.
--
Sean Reilly
Developer, The Infinite Kind
https://infinitekind.com
440 Posted by jonathan on 16 Apr, 2026 03:00 PM
Thanks, Sean. Very helpful to have some insights about obstacles, plans, and exciting visions for the future! Appreciate your commitment to never overpromise and underdeliver!
441 Posted by rlsantella on 17 Apr, 2026 11:45 AM
I believe the majority of us would want the Fidelity download fix prioritized above a new budgeting system.
442 Posted by pctomac on 17 Apr, 2026 12:47 PM
Would like to see the csv file download option created by mmd signed by IK and formally added as an extension to the Moneydance program. Though this sounds like a good interim solution, I won't use anything not signed and approved by the Moneydance team.
443 Posted by Tim on 17 Apr, 2026 02:52 PM
"I believe the majority of us would want the Fidelity download fix prioritized above a new budgeting system."
+1
444 Posted by Kent on 17 Apr, 2026 05:57 PM
"I believe the majority of us would want the Fidelity download fix prioritized above a new budgeting system."
+1M Votes
445 Posted by dwg on 17 Apr, 2026 11:16 PM
To play devil's advocate, only Fidelity customers want that at the top of the list :)