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 9 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
241 Posted by sth on 22 Dec, 2025 02:12 AM
@dtd, The transactions were not entered previously as they had (will) occurred on 12/22. And are not listed in the register.
Here is the redacted file with almost everything except the amounts redacted. I removed the boiler plate text at the end of the file for posting.
YYYYYYYY is the account number in both MD and Fidelity
NNNNNNN is the account name in MD and the account nickname in Fidelity
ZZZZZZZZ is the security name
TTTTT is the ticker symbol
The transaction was a dividend and a subsequent buy as an automatic reinvestment.
As I said the only weird thing was the date being in the future.
If I have time I will try to decode the python code. And I will try again tomorrow morning when the dates are valid?242 Posted by dtd on 22 Dec, 2025 02:24 AM
Well there is one issue - your account numbers are in the account field and the account names are in the account number field.
243 Posted by sth on 22 Dec, 2025 02:34 AM
No, that is not the problem. The problem is getting distracted while trying to write up the posting! :-)
N was supposed to be number and I reversed it while typing.
NNNNNNN is the account number in both MD and Fidelity is the account name in MD YYYYYYYY and the account nickname in Fidelity
Will send you the full orig file by DM
244 Posted by dtd on 22 Dec, 2025 02:36 AM
I try not to assume. Assuming misses a lot of problems.
245 Posted by -Kevin N. on 22 Dec, 2025 02:48 AM
@sth,
Does the console window shed any light on the issue?
Try the import with the console window open.
-Kevin N. (not a member of Moneydance support)
246 Posted by mmd on 22 Dec, 2025 09:57 AM
@sth
I'm traveling abroad with limited Internet access mostly from my phone, but since the duplicate detection mechanism didn't change between v1 and v3, and duplicate detected means exact string of the row from the CSV file has already been processed into a transaction in your Moneydance register and is there now - did you check to make sure you are showing ALL transactions in the Moneydance Register to make sure future dated transactions are shown? In other words, I think if you use a filter like 30 days or others it might not include transactions that happen in the future although they are actually there.
Thanks!
On Mon, Dec 22, 2025 at 9:48 AM, -Kevin N. < [email blocked] > wrote:
247 Posted by mmd on 22 Dec, 2025 03:09 PM
@sth
Was bothered by your screenshot not showing the duplicated account number
Found a coffee shop with Internet and fixed truncation of last word in the dialog. Now you should be able to see which account number is duplicated in MD
Will have to wait until find better connection or back stateside for changes to the buy/sell/xfr/etc templates but did see those samples that aren't transferring correctly, thank you.
https://github.com/SnapEscalatorCarrousel/import_fidelity
248 Posted by mmd on 22 Dec, 2025 03:25 PM
Noticed pull request from yogi1967 also that, among other things, apparently fixed compatibility with toolbox zap memo and maybe displays some more verbose error messages if there is an error.
Didn't seem to break anything so merged it into main branch increase to v5.
249 Posted by Stuart Beesley ... on 22 Dec, 2025 03:49 PM
To clarify - yogi1967 is me!! 😉
250 Posted by -Kevin N. on 22 Dec, 2025 05:41 PM
@sth,
I don't know if it matters or not. The header row of your csv is different than mine.
Yours includes 'Exchange Quantity', 'Exchange Currency', 'Currency' & 'Exchange Rate'.
Yours:
Mine:-Kevin N. (not a member of Moneydance support)
251 Posted by sth on 22 Dec, 2025 06:03 PM
Don't know why that difference should be in the header, that is what Fidelity gives me. Note that your Price is explicitly in ($).
I found the duplicate account numbers in two other unrelated accounts at a different brokerage. I fixed that and all seems to be well with the download and import. Thanks for fixing the truncated error message that would have led me to the solution much quicker since I was only looking at Fidelity accounts!
252 Posted by -Kevin N. on 22 Dec, 2025 06:13 PM
@sth,
The ($) makes sense since I don't have any of that currency or exchange rate jazz. :)
-Kevin N.
253 Posted by BrianS on 23 Dec, 2025 12:34 AM
I've had one successful run of the new extension; it's very promising, and I'm so grateful.
On my second attempt, I had a small group of new securities. I get a modal telling me:
"Error: security account: '<whatever>' not found"
What's my best approach here? I take notes from the popup and start manually filling in the gaps? Is there any way to trigger the MD "accounts mapping" flow?
254 Posted by Stuart Beesley ... on 23 Dec, 2025 08:08 AM
For now you have to add the securities. The extn could certainly create them. But as we know that can cause duplicates.
255 Posted by sth on 23 Dec, 2025 05:09 PM
@Stuart, does it map by Fidelity "Symbol" with MD "Ticker"? For regular downloads Plaid sometimes lists SEDOL as the Ticker symbol and does not give you the chance to select an existing security in the account, though that is the correct response.
256 Posted by JasonS on 29 Dec, 2025 03:30 PM
So, are there any plans by InfiniteKind to support Fidelity Access? A lot of us have this problem and the workarounds are not long-term solutions. I love Moneydance, but if it can no longer support Fidelity, I likely will move to another app.
Support Staff 257 Posted by Maddy on 29 Dec, 2025 03:40 PM
@JasonS
Fidelity is currently working closely with our development team to bring automatic downloads to Moneydance+.
We’re also exploring a direct connection through Akoya as an additional option. This may take a little longer to implement, but it appears to be the most reliable long‑term solution.
We’ll continue posting updates on this public thread, where you’ll also find helpful tips for downloading your data manually in the meantime.
Thank you for your patience, and we’re sorry for any inconvenience this has caused.
--
Maddy, Infinite Kind Support
258 Posted by Ali on 30 Dec, 2025 08:05 PM
Thank you, mmd & Stuart, for this awesome script!
I have only 1 account in Fidelity and the csv I am downloading is not including any columns for account and account number. I modified this csv to add these 2 columns and it then worked for me. Is there a way to modify the script to catch this?
I am downloading the CSV by going into "Activity & Orders" > "Download as CSV".
Headers are:
Run Date,Action,Symbol,Description,Type,Exchange Quantity,Exchange Currency,Currency,Price,Quantity,Exchange Rate,Commission,Fees,Accrued Interest,Amount,Cash Balance,Settlement Date
259 Posted by David L Greene on 31 Dec, 2025 04:27 PM
This is a great tool so I am not 'looking a gift horse in the mouth' so to speak. Sometimes when volume is high, the extension may miss some buys/sells. End of year dividends and cap gains recorded nicely, but 4 buys/sells for securities were missed. It is possible that all the bought securities were not in the account but I don't think so. NOTE: I like the fact that it will not import if you don't have all securities setup, as that forces you to set them up manually, which is the most accurate way to add securities in MD. No reliable auto-setup function.
Happy New Year!!
260 Posted by jonathan on 31 Dec, 2025 08:49 PM
Long-time Moneydance user who is computer-literate but knows nothing about programming. Humbled to say I cannot figure out how to install this handy (and essential to me) Fidelity extension. Cannot even find the mkt extension file, not being too facile with Github....Thanks to all the work people have contributed to creating this extension (and educating us!). May you all enjoy a more just and joyous 2026
261 Posted by dwg on 01 Jan, 2026 01:22 AM
You can download a copy from post 248 in this thread, it is a mxt file.
In Moneydance take the menu path Extensions => Manage Extensions
At the bottom of the extension window there is an add from File button, use this and navigate to where you downloaded the extension to in order to select and install it.
It will add a new item to the Extension menu.
262 Posted by tiptonbob on 01 Jan, 2026 03:48 PM
I don't get an .mxt file. I get a .zip file that extracts to Import fidelity folder, but no .mxt.
263 Posted by -Kevin N. on 01 Jan, 2026 05:33 PM
Hi tiptonbob,
Do not unzip the file.
It has been my experience that you can leave the .zip file extension as is or just change the .zip file extension to .mxt. Then install the extension as usual.
-Kevin N. (not a member of Moneydance support)
264 Posted by zxkivyx75em8 on 02 Jan, 2026 09:49 PM
I have an anomaly transaction. This is just a cash transfer.
The action field in the csv file is:
"TRANSFERRED TO VS Xxx-xxxxxx REDEMPTION (Cash)"
So the code matches "REDEMPTION" and thinks it is a sell transaction.
Later when to code calls getSecurityAcct with no symbol and a description of "No description" it returns what looks like a random security in the the account.
I believe MD is trying its best to find a security that matches the call so latches on to one. Not sure how it decided. Luckily it does not create a new security. I am guessing if there were no securities in the account it might.
Just an FYI to be on the lookout for. Easy enough to fix manually and probably via the code I just have not looked yet.
265 Posted by NewfD90 on 03 Jan, 2026 04:02 PM
Thank you for the Extension; it worked great for my account!
Unfortunately, as my Wife's Fidelity account only has one account, the downloaded CSV has neither the 'Account' or 'Account Number' fields (yes, even with "All Accounts" selected.
So I modified your extension to detect that case and if true, pop up a dialog to prompt for the account number. I've attached a patch (diffs) file if anybody has a similar issue.
266 Posted by jonathan on 03 Jan, 2026 07:18 PM
Thanks for the extra directions dwg and Kevin N! Success!
267 Posted by biddle.rod on 03 Jan, 2026 08:03 PM
Many Thanks to all that worked on the Fidelity Access solution. It worked GREAT for all my Fidelity accounts. I selected 'Accounts & Orders' from the Summary page and used the 'Custom Date' option to D/L the .csv file. Imported into MD using the new 'Import Fidelity .....' extension. Easy/Peasy. Most of my transactions are dividend reinvestment and the extension worked very well. Probably won't pay for a 3rd party aggregator with more constraints.
268 Posted by jaraco on 04 Jan, 2026 04:37 PM
Thanks everyone for the hard work in this extension. I'm about to try it out today.
I have some ideas on how to make the GitHub project more usable by end users.
- Provide the mxt extension as a release on the project.
- Automate releases using GitHub Actions.
- In the instructions, provide detailed, step-by-step instructions on installing and using the extension.
This way, the GitHub project becomes a reliable landing page to learn about the extension and its usage and can be kept up to date with any developments (rather than following this thread and searching for the latest releases).
I plan to file issues and pull requests against the project in an attempt to help.
269 Posted by -Kevin N. on 04 Jan, 2026 05:26 PM
+1 for forum member jaraco's suggestions.
270 Posted by Tim on 05 Jan, 2026 04:05 PM
+2 for jaraco's suggestions (for many of us less-programming savy, I am afraid of breaking something. This needs to be a general Extension we can select and not have to manually manipulate to install.