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 13 out of 13. 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
361 Posted by cjl27 on 18 Feb, 2026 03:36 PM
Has anyone tried either uploading transaction csv files or pdf monthly statements showing transactions into Claude (or other AI service) and asked for an OFX file output?
I had asked Claude and it says it can do it, but have not tried it yet... curious if others may have attempted this or something similar and what their thoughts are.
362 Posted by dtd on 18 Feb, 2026 04:32 PM
Sounds like an interesting thing to try - I'd guess it might get the securities correct, but might have trouble with some action step choices.
363 Posted by wuhl756 on 20 Feb, 2026 02:26 PM
When one of my credit card banks stopped providing QIF or QFX files for download, only CSV, I asked Claude about importing the CSV into Ace Money Lite (which I use in addition to MD for separate monitoring of expenses). AML will import CSVs but my efforts to reformat them were unsuccessful. Claude offered and then created a python script to convert the CSV files to importable QIFs. After a couple of tweaks and step-by-step instructions for this amateur, it works great.
364 Posted by ExplodingSidewa... on 21 Feb, 2026 05:51 PM
I'd like to thank mmd for all his work on the Moneydance Extension import_fidelity.mxt. I have been using Version 8 but, it's not importing the correct price ($) and for some reason it doesn't recognize (no match) for investment fund FID FDM IDX 2035 IPR even though it matches my Moneydance Investment Fund exactly. I will investigate further. I also see that a new Version 11 is out there so I'll download that and test. Thanks again for all your help.
365 Posted by ExplodingSidewa... on 21 Feb, 2026 06:11 PM
I don't know why Fidelity does this in their csv file download. If you download a csv for All Accounts the fields are messed up for example. Let's say I have HSA and 401(k) transactions in the csv file. The HSA Transactions will have a dollar amount the the Price ($) column and shares in the Quantity column. The 401(k) Investment Transactions will have the number of shares in the Price ($) column and nothing in the Quantity column. I guess the solution is to have separate csv downloads, one for HSA and one for 401(k), ESOP, IRA, ROTH, etc.
366 Posted by tkr on 23 Feb, 2026 04:09 PM
I created some scripts for importing Fidelity data and put them on Github along with explanations of the gotchas I ran into for anyone who is interested in tinkering a bit. They are here.
https://github.com/tkralphs/MoneydanceScripts
I started out using Claude, as someone suggested above, to produce a script to parse the CSV and produce an OFX file. Claude gave me about a 90% solution, but the last 10% required a lot of painful trial and error. The script Claude produced at first did not generate valid XML and it required some human intervention to get something that actually worked in Moneydance. You can find the result in the Github repo, but I don't recommend going this route if you are trading any individual stocks.
For me, the OFX solution was painful on multiple fronts. When the transactions involve new securities being added or things like company mergers that necessitated changing the CUSIP of an underlying security, there is just no way that I could see to handle this gracefully with a single OFX produced in a completely automated fashion. It's sometimes really necessary to look up information for a security and do some manual intervention updating security information before importing transaction if you don't want a mess.
Fidelity does some really wonky stuff in the CSV files, such as listing the CUSIP instead of the ticker in cases where the CUSIP changed as a result of the transaction. Actually, this kind of weirdness was already there in the QFX files Fidelity pushed out and I was already spending hours fixing things up each time I downloaded transactions. Duplicate securities were often being created without associated ticker symbols and other annoying things. The OFX file route also introduces an additional layer of translation for transaction types, among other things.
I ended up with a workflow that parses the CSV and generates a script that can be run through the Developer Console that directly adds the transactions. It allows for checking ahead of time to make sure the securities exist already in the account. The workflow is a bit manual (not a plugin), but if you are willing to tinker, this allows for a bit more fine-grained control.
367 Posted by Stuart Beesley ... on 23 Feb, 2026 05:01 PM
I think at this time whilst changes are still being made to the extension, it would be wise to wait to get this extension signed…
368 Posted by Billy Goat on 26 Feb, 2026 05:50 PM
My standing position is that MD needs to figure this out quickly, else it risks losing a massive volume of customers. Also, the inability of MD to provide ANY directional feedback on timing of the resolution is unacceptable.
BUT if the extension approach is secure I will consider it. Can someone point me towards a resource that defends the security of the extension approach described by the folks in this discussion?
I appreciate the creative volunteer work by this community, but MD should NEVER rely on the volunteer work here. If so, MD will just be a boutique platform with zero mass adoption and it will die.
Thanks.
Support Staff 369 Posted by Maddy on 26 Feb, 2026 09:30 PM
@Billy Goat
Connecting Moneydance+ with Fidelity is a key priority, and the team is actively working through the technical and regulatory requirements needed to make it happen.
These steps take time, but progress is ongoing.
We truly appreciate your patience as we continue toward full support.
--
Maddy, Infinite Kind Support
370 Posted by dabrjn on 01 Mar, 2026 09:06 PM
So Maddy,
I'm glad you are working on it, but what does that mean? Is there any timeline? Could we see something in a month? three months, six months? a year?
371 Posted by dwg on 01 Mar, 2026 09:14 PM
If it is via Moneydance+ that means it is up to Plaid to do the implementation and is out of TIK's (Moneydance) control.
372 Posted by Billy Goat on 02 Mar, 2026 08:53 PM
@DWG
I don't understand your persistent apologies on behalf of MD. I bought a product from Infinite Kind. I didn't hire a broker between myself and Plaid. I have spent a lot of time as a leader in companies reliant on premier product development. The second you start explaining away your product deficiencies due to 3rd parties and sub-contractors, you are no longer a product company. If the IK product offering is no longer relevant then I will seek out another fully formed product elsewhere, as many other have done. These customer never come back, and the overall platform suffers from less users. The downward spiral kills companies.
I've been a MD customer for well over a decade, and there are reasons I've stuck with it despite its obvious challenges. It should have grown to a more formidable platform by now, but the inability to even state and own a forecast timeline approaches a critical mass of problems that looks more like a garage frankenproduct than a real product you would trust sensitive financial information with. Yes, what Fidelity and others have done is likely predatory and it sucks, but MD needs to compete and perform. I am the customer, and I want performance and specific and measurable accountability, not adverbs and "trying" verbs.
Billy Goat
373 Posted by bpdonovan on 02 Mar, 2026 09:02 PM
I am interested in trying this out. Is there any documentation concerning installation and running the extension V10 - how to use it so to speak.
374 Posted by smith.chrisg on 02 Mar, 2026 10:39 PM
Bump to Billy Goat's comments re "MD needs to compete and perform". I am almost 10 years in with MD (4/29/16) and don't WANT to go elsewhere but Fidelity is a large part of my portfolio - sorry but no excuses accepted. I am loyal to MD and can appreciate the user community temp solutions efforts, but going on without at least weekly updates/status from IK team may end up pushing me out to seeking other product/s within a couple of months. At this point i am manually keying in my info which is totally lame.
375 Posted by Tim on 03 Mar, 2026 03:20 PM
What "other" products are there that don't require a Subscription - and WORK -, ala QUICKEN? That's the only reason I'm sticking it out for now with MD.
376 Posted by James K on 03 Mar, 2026 10:53 PM
Re: Billy Goat's comments.
I must agree. As a long time user, I don't quite get it anymore. Is there anyone at IK?
All I see are replies from Maddy from the support staff, and 2 or 3 developers who are not working for IK. The last blog entry was over a year ago. All the problems customers are complaining about are never resolved or blamed on Plaid, or Fidelity, or the Tooth Fairy. I paid for a product and I expect it to work, and when problems arise, have them fixed. If there is actually anyone left at IK, how about a few blog posts about what is being done to fix these issues?
377 Posted by dwg on 03 Mar, 2026 11:31 PM
I placed a pointer and a note on the Developer's slack site that users were unhappy with the lack of response on the fidelity issue.
Trying to bring the issue to the managements attention is all that users can do. The developer is one of the Company's owners.
378 Posted by Steve on 04 Mar, 2026 01:45 AM
@ Billy Goat
I agree completely. These manual workarounds are no solution. I'm sure most of us do NOT want to spend needless hours parsing and collating data. Plus, we do not want to hear about hurt feelings and other perceived offenses. As you stated, we want a fully formed product that works. Period.
379 Posted by cjl27 on 05 Mar, 2026 02:31 PM
I also agree with Billy Goat... at a bare minimum, Moneydance itself should be internally implementing the patch and extension workaround that some of the users have worked on and been discussing on this forum and be implementing it into their product even as a stopgap measure. I find it remarkable that we sit here listening to the great work users are doing to try to solve the problem and Moneydance is not making this a top priority. Its sitting back and letting others solve the problem (at least on an interim basis) that I am finding equally as frustrating. Maybe I have this wrong... I am just a simple user (for 20 years +/-) and a layman on the technical stuff.
380 Posted by MikeB on 05 Mar, 2026 05:12 PM
Has anyone actually been able to sign up and use Fidelity Access? I can find information about it but it tells you to manage what apps have access on your Dashboard. My dashboard is empty and there is no obvious way to add any. I've searched the Fidelity site and don't find anything really telling you how to add them. If not I can try to chat with their customer service and see what they say.
381 Posted by dtd on 05 Mar, 2026 07:17 PM
Fidelity Access is not for individuals. It's for aggregators to sign up to to gain access to Fidelity data. And to pay Fidelity for the privilege before they can pass it on to you.... i.e double dipping - Fidelity wants money and the aggregator wants even more money to provide you your own data via automatic download.
382 Posted by LarryCL on 05 Mar, 2026 11:10 PM
@dtd, regarding Fidelity charging for access, there are two sides to every story. Chase announced something similar; see this article from last summer: https://www.cnbc.com/2025/07/28/jpmorgan-fintech-middlemen-plaid-da...
Quote: "Morgan Chase said the fintech companies that help financial apps connect with traditional checking accounts are flooding the bank’s systems with unnecessary data requests.
Of 1.89 billion data requests from middlemen hitting its systems in June, only 13% were initiated by a customer for transactions, according to an internal JPMorgan memo seen by CNBC.
The majority of data pulls, known as API calls, were for purposes ranging from helping fintech companies improve their products or prevent fraud to other efforts including harvesting data for sale, said a person with knowledge of the memo."
Regardless, whether or not Fidelity is charging for aggregator access, it is something many many many Moneydance customers want, or more precisely NEED.
I am anxiously awaiting for Sean to respond publicly to @dwg's Slack alert mentioned upthread.
383 Posted by dtd on 06 Mar, 2026 12:57 AM
@LarryCL - I was providing an answer to mbrown305's question. Charging mechanisms are one of the reasons banks have abandoned direct connect, another is that they say they are moving to better security (by adding middlemen into the process).
My answer had nothing to do with moneydance. You didn't need to turn my answer into yet another diatribe as if it were.
384 Posted by dtd on 06 Mar, 2026 01:36 AM
@bpdonovan - I don't think there is any formal documentation to the fidelity download extension yet. Mostly it has been help in this thread when asked for.
I have three fidelity accounts and am quite satisfied with being up to date with my accounts. the only real issues for me are rare transactions that haven't been addressed yet, because, well, they're rare, and addressed when they appear.
Given this thread has been hijacked by naysayers about this concept, and that users can't (and shouldn't) be adding capabilities through extensions, and that only IK/MD should do this, this is probably no longer the place to insert comments about the extension, sadly.
I'll try to work up a write up with some instructions and such and create a new thread with the info.
385 Posted by LarryCL on 06 Mar, 2026 02:37 PM
@dtd, I was responding to your response where you wrote "...And to pay Fidelity for the privilege before they can pass it on to you.... i.e double dipping". Eg your response came off as a implied "Fidelity are the bad guys in this", and I responded to show that there are business reasons for charging for access. Not a diatribe.
As a consumer obviously I don't like paying fees, but as I wrote, sometimes there are legitimate business reasons for fees (eg, the $2/mo fee we pay for Moneydance+).
386 Posted by Ambassador Dave on 11 Mar, 2026 01:30 AM
mmd, thank you kindly for creating and sharing your script/extension. Stuart, thank you as well for all the help you've given on it along the way.
I just caught up on 3 months of Fidelity account reconciliation that I'd put off after their OFX server stopped responding and this forum post started up. Your extension definitely helps a lot. There is one major hiccup that I've run into and I wonder if you'd consider yet another update to your extension to handle it?
For a 401k account, for some reason, Fidelity is putting the shares quantity into the "Price" column, the "Quantity" column blank, and the "Amount ($)" column properly filled. Here's a couple lines as an example (also attached as a png file screenshot):
Run Date,Account,Account Number,Action,Symbol,Description,Type,Price ($),Quantity,Commission ($),Fees ($),Accrued Interest ($),Amount ($),Settlement Date 02/27/2026," 401(k)","123456789","Contributions",,"FID 500 INDEX",,1.942,,,,,464.85,, 02/27/2026," 401(k)","123456789","Contributions",,"FID TOTAL MKT IDX",,2.463,,,,,464.85,,Again, thanks so much for sharing your extension!
387 Posted by ppinocci on 11 Mar, 2026 01:19 PM
For 401k accounts, Fidelity has a QIF download option, in addition to the CSV download option. With the QIF download you can use the built-in import function in Moneydance.
388 Posted by Ambassador Dave on 11 Mar, 2026 02:29 PM
@ppinocci Thanks for the suggestion, it's a good one. I tried it, yet for some reason, Moneydance imported every single buy transaction into the 401k as a new security. I ended up with over a dozen listings for each security with a single history date & price each. In looking at each copy of the security, they all appeared the same only with the different history. This forum's search is currently broken, yet when I used Google to search I didn't find any posts discussing the same issue. I reloaded a backup and am back where I was. I feel there is less 'work' manually adding the 401k share amounts while importing all my Fidelity accounts vs. two downloads and then recombining copies of securities.
389 Posted by ppinocci on 12 Mar, 2026 02:43 PM
@Ambassador Dave, Sorry about that. I should have mentioned that, I did have to update the security name in the QIF before importing so that it matched the security name in Moneydance, so it wouldn't add new securities. I lose track of the manual stuff now needed for Fidelity, I only get new transactions monthly or less. Fidelity stores some weird names for the securities in its system somewhere. Even the security names in the CSV don't match the security names in Moneydance. Again, sorry for omitting that detail.
390 Posted by mmd on 12 Mar, 2026 08:38 PM
Fidelity CSV import extension with workaround for Fidelity 401(k) bug as detailed by @Ambassador Dave
https://github.com/SnapEscalatorCarrousel/import_fidelity
Remember the file has to be called import_fidelity.mxt (or maybe .zip is fine) but nothing else in the name like (1) or (2) that may be added by your browser.