Home → General Questions →

Fidelity Access

Showing page 6 out of 15. View the first page

1. 151 Posted by dan.tappan on 15 Dec, 2025 07:40 PM

   

   The script is not working for me. After I fixed the missing support for Short Term capital gains, that I reported above, the next problem is that I am seeing a lot of errors of the form:
   ===
   ERROR: security account: 'HallDudley:FIDELITY DIVERSIFIED INTERNATIONAL' NOT found
   ERROR: security account: 'Dan Rollover IRA:AMERICAN BOND FUND OF AMERICA CLASS F1' NOT found
   ERROR: security account: 'HallDudley:JP MORGAN MID CAP VALUE FUND CLASS A' NOT found
   ERROR: security account: 'Dan Rollover IRA:FIDELITY INT'L DISCOVERY' NOT found
   ERROR: security account: 'Dan Rollover IRA:COLUMBIA SELIGMAN TECH AND INFO CL A' NOT found
   ===

   The underlying problem is that the "Security" entry long form name does not match what's in the CSV, I suspect the cause is that at some point the fund name changed, or it was truncated when first imported, or something of the sort. I believe this has not been an issue up to this point because the Ticker Symbol is correct, and that MoneyDance has been doing security lookups based on Ticker Symbol

   The Ticker Symbols are in the CSV, and I could parse the record and extract them, but the documentation in the online MoneyDance API docs is somewhat sparse so I can't figure out how to do that lookup from the API.

   Currently the script is doing:
   securityAccountName = accountName + ":" + csvDescription
   securityAccount = root.getAccountByName(securityAccountName)
   if (not securityAccount):
       txt = "ERROR: security account: '%s' NOT found" %(securityAccountName)
       myPrint(txt)

   Is there an equivalent to the getAccountByName() call that will accept a Ticker Symbol rather than a long security name?

   Secondly, once this error happens the script doesn't seem to handle it gracefully, the "Buy" entries are recorded, but with no security names or share counds

   Thirdly, I am also seeing the problem reported by @-Kevin N. where the Buy transactions have positive transaction amounts, so they increase the cash balance in the account.

   • Edit

2. 152 Posted by mmd on 15 Dec, 2025 08:17 PM

   

   I think we lost an absolute value abs() in there when we converted to the fancier version.

   Try this.

   https://drive.google.com/file/d/1pYgdgEUYrGJtlm_-JI5PezfSphh2UzNW/v...

   For the ticket symbols, will have to look. I had a single transaction that had this error and even renaming security + security account name in MD (at least via the GUI) didn't seem to fix it.

   I don't know if you can really have a buy and sell transaction properly recorded without an associated security though.

   • fidelity.py 13.5 KB
   • Edit

3. 153 Posted by mmd on 15 Dec, 2025 08:54 PM

   

   Sorry here is the abs in the right place as it was in prior version of script

   https://drive.google.com/file/d/1pYgdgEUYrGJtlm_-JI5PezfSphh2UzNW/v...

   FWIW, for my workplace retirement accounts, the CSV doesn't list a stock symbol at all, despite the mutual funds being common public mutual funds available to all (but possibly at a different expense ratio)

   • fidelity.py 13.5 KB
   • Edit

4. 154 Posted by -Kevin N. on 15 Dec, 2025 09:14 PM

   

   @mmd,

   Thank you. The latest version of fidelity.py resolves the negative signage issue.

   I also ran into the account not found and security account not found issue. Similarly to dan.tappan's experience.
   The account name in MD was exactly as it appeared in the Fidelity CSV file.
   I did need to edit the security name in the MD GUI so that it was exactly as it appeared in the Fidelity CSV file.

   But doing so did not resolve the errors. The 'Date', 'Action' & 'Description' were imported but not the 'Security', 'Shares', 'Price' or 'Amount' values.

   To resolve this, I had to create a new instance of the security, swap it out with the current security in each txn in the register. This was the hurdles that I spoke of earlier.

   I'm thinking that I had some sort of corruption in the security which cause the script to throw the errors.

   Anyway, it's all good. Thank you again for the fix. Nice!

   -Kevin N.

   • Edit

5. 155 Posted by dan.tappan on 15 Dec, 2025 09:29 PM

   

   > For the ticket symbols, will have to look. I had a single transaction
   > that had this error and even renaming security + security account name
   > in MD (at least via the GUI) didn't seem to fix it.

   Yes, that's what I'm seeing. I've tried renaming all the failing
   securities to match what is in the CSV, and the lookups still fail.
   Maybe there's something weird in the name in the database, but I've been
   trying various Toolbox functions and nothing seems to detect/fix the issue.

   On 12/15/25 3:17 PM, mmd wrote:

   • Edit

6. 156 Posted by dan.tappan on 15 Dec, 2025 09:31 PM

   

   Yeah, it turns out the ticker symbol is in the "Action" but not in the
   "Description". I could still probably extract it from there if there
   were a way to use it to canonicalize the security name, but I don't see
   anything in the API :-(

   • Edit

7. 157 Posted by zxkivyx75em8 on 15 Dec, 2025 09:50 PM

   

   mmd

   I ran into a small issue. Some of my security names are not the same as what fidelity sends down. When this was encountered a transaction with no security was being created. It seemed like the symbol would be less likely to be off ,so I put the following in. Not neat just testing, but you see what I did.

   def GetSecurityName ( ticker):    
                               for sec in book.getCurrencies():
                                   if (ticker == sec.getTickerSymbol()):
                                       name = sec.getName()
                                       print("Security Name:", str(name))   
                               return str(name)
                               
                           securityAccountName = GetSecurityName(row['Symbol'].strip())            
                           securityAccount = root.getAccountByName(securityAccountName)
                           
                           
                           if (not securityAccount):
                               txt = "ERROR: security account: '%s' NOT found" %(securityAccountName)
                               myPrint(txt)
                           else:
                               security = book.getCurrencies().getCurrencyByName(securityAccountName)
                               if (not security):
                                   txt = "ERROR: security: '%s' NOT found" %(securityAccountName)
                                   myPrint(txt)
   

   This then created the transaction with my security name and not try to create one using fidelity's.

   I have not tested every type of transaction but It is really looking good

   Regards

   • Edit

8. 158 Posted by Stuart Beesley ... on 15 Dec, 2025 10:02 PM

   

   NOTE - the security account's name initially matches the security (currency) name. BUT if the security (currency) name later changes, then the account's name does not get updated. The script looks up the security account by name. This is actually something I identified in MD and a code fix was proposed and I understand put in to MD for the next release.

   This is probably why you are not getting luck by renaming things...

   • Edit

9. 159 Posted by Stuart Beesley ... on 15 Dec, 2025 10:02 PM

   

   If I get time, I'll help @mmd improve the account / security lookups

   • Edit

10. 160 Posted by Stuart Beesley ... on 15 Dec, 2025 10:05 PM

    

    In the mean time, you can do this... Get the security account's UUID, store this in the script, and then call lookup account by UUID AccountBook#getAccountByUUID() - just name sure that the account you get back is a security account, and linked to the investment account. OR get the investment account, iterate all its sub accounts and then look for subAcct.getCurrencyType().getName() or getTickerSymbol() == the security you want

    • Edit

11. 161 Posted by mmd on 15 Dec, 2025 10:49 PM

    

    Thanks @Stuart for the helpful code/tips

    Try this one for importing by ticker symbol also:

    https://drive.google.com/file/d/1pYgdgEUYrGJtlm_-JI5PezfSphh2UzNW/v...

    • fidelity.py 13.9 KB
    • Edit

12. 162 Posted by dan.tappan on 15 Dec, 2025 11:20 PM

    

    That seems to work! At least, it imported my history file w/o errors.
    Thank you!

    • Edit

13. 163 Posted by -Kevin N. on 15 Dec, 2025 11:33 PM

    

    @mmd, @Stuart,

    This most recent build works perfectly!
    I kept my old security names (slightly different from Fidelity's CSV)
    All txns imported without any reported errors.

    This is excellent! Thank you.

    -Kevin N.

    • Edit

14. 164 Posted by mmd on 15 Dec, 2025 11:40 PM

    

    Glad to hear!!! Stuart sent some code to help make the script into an extension so that could be the next step if there aren’t more issues.

    On Mon, Dec 15, 2025 at 5:33 PM, -Kevin N. < [email blocked] > wrote:

    • Edit

15. 165 Posted by zxkivyx75em8 on 16 Dec, 2025 12:01 AM

    

    Works for me also!! Thanks to All

    • Edit

16. 166 Posted by -Kevin N. on 16 Dec, 2025 12:17 AM

    

    @mmd,

    I'm currently using python 2.7.18.

    Q. Do you know if the script will run under python 3.12.3?

    Although, I guess that the python version is moot once it's an extension. Correct?

    -Kevin N.

    • Edit

17. 167 Posted by Stuart Beesley ... on 16 Dec, 2025 12:25 AM

    

    @kevin. Your own python version is irrelevant. MD runs Jython 2.7. That’s what this runs on. You cannot run it any other way - other than via MD’s own internal Jython version.

    Why do you think you want Python 3?

    If you are asking whether your own python 3 will interfere, then no - it’s no problem. . You cannot run run whatever you want locally.

    • Edit

18. 168 Posted by -Kevin N. on 16 Dec, 2025 12:31 AM

    

    @Stuart,

    Thank you for the clarification.

    I'm using python3 to run Pocketsense on Linux so I was just curious if I could run the script there too.

    Glad to hear that it won't be a problem.

    Thanks again, You guys rock!

    -Kevin N.

    • Edit

19. 169 Posted by dwg on 16 Dec, 2025 01:26 AM

    

    The following post talks about some python code for Linux for CSV to OFX perhaps that may be useful:

    https://infinitekind.tenderapp.com/discussions/online-banking/1251910-bank-of-america-screws-us#comment_64523132

    • Edit

20. 170 Posted by webyan on 16 Dec, 2025 05:02 AM

    

    What is the status of Moneydance adding Fidelity to Moneydance+? Can you make this script an extension so it is easy to use? If not can you post instructions on how to use the script for updating my Fidelity accounts? I really appreciate all of you with the technical skills working to solve this problem!! I just want to be able to take advantage of the work if Moneydance is unable to work with Fidelity and provide a download solution.

    • Edit

21. 171 Posted by dtd on 16 Dec, 2025 05:35 AM

    

    Fidelity and all aggregators (including Plaid) have been arguing - Fidelity wants to be paid to give out data, and insists on different access methods that aggregators don't want to use. Fidelity points to Akoya and Fidelity Access as to how aggregators are allowed to get data. Most aggregators have walked away. So when users ask, Fidelity's standard response is Akoya or Access - ask your aggregator to get that (for pay of course, which they'd pass on to you).

    So, will Plaid add Fidelity? :shrug:

    • Edit

22. 172 Posted by dwg on 16 Dec, 2025 06:00 AM

    

    Personally, I would not expect Plaid to agree to pay Akoya for access to the data, it also just puts another aggregator into the chain.

    If Fidelity are agreeable to allow Plaid direct Access by using Fidelity Access that would be a possibility.Plaid's system already accommodate using institution's systems where access is Token based, they have to allow for this as they operate in some countries where Open Banking is a feature and that uses Token based access.

    Take note that access via Moneydance+ is between Fidelity and Plaid, Moneydance i.e. TIK is not involved in this, they are a customer of Plaid.

    • Edit

23. 173 Posted by Bob on 16 Dec, 2025 10:31 AM

    

    The latest script is working great, thanks!

    My cash management transactions still aren't merging, but that's minor since I can import the same CSV transactions via the CVS Importer extension and then those transactions will merge. It's just a small extra step so not a big deal.

    • Edit

24. 174 Posted by Stuart Beesley ... on 16 Dec, 2025 11:29 AM

    

    @bob - see email.

    • Edit

25. 175 Posted by Stuart Beesley ... on 16 Dec, 2025 11:38 AM

    

    I’m wondering in general whether to make this script useful for even more people, whether it needs some sort of pop-up that allows you to select Fidelity account and securities? Or does it work just fine as it is? Can anyone who’s tried and cannot use this script, please clarify why it won’t work for you?

    • Edit

26. 176 Posted by LarryCL on 16 Dec, 2025 04:55 PM

    

    @dtd wrote:

    Fidelity and all aggregators (including Plaid) have been arguing - Fidelity wants to be paid to give out data, and insists on different access methods that aggregators don't want to use. Fidelity points to Akoya and Fidelity Access as to how aggregators are allowed to get data. Most aggregators have walked away. So when users ask, Fidelity's standard response is Akoya or Access - ask your aggregator to get that (for pay of course, which they'd pass on to you).

    So, will Plaid add Fidelity? :shrug:

    There are other aggregators out there besides Plaid, and many (well, some) of them DO support Fidelity. If Plaid can't or won't add Fidelity support, then I would like to see TIK find an additional aggregator that DOES support Fidelity. And if this cost me an additional dollar or two per month, I'd be ok with that.

    For example, as I posted earlier way back in this thread, there is a tool called lunchflow.app that has partnered with multiple aggregators (gocardless, MX, Finicity, Pluggy, Akaku, and Finverse), which allows this small-time app to support Fidelity downloads. I don't see why TIK couldn't do something similar.

    @dwg wrote:

    dwg: Personally, I would not expect Plaid to agree to pay Akoya for access to the data, it also just puts another aggregator into the chain.

    If Fidelity are agreeable to allow Plaid direct Access by using Fidelity Access that would be a possibility.Plaid's system already accommodate using institution's systems where access is Token based, they have to allow for this as they operate in some countries where Open Banking is a feature and that uses Token based access.

    Take note that access via Moneydance+ is between Fidelity and Plaid, Moneydance i.e. TIK is not involved in this, they are a customer of Plaid.

    If I understand it correctly, Fidelity Access is the API, and Akoya is the aggregator. So I have a different point of view: I indeed would hope that TIK would be talking to Akoya as a long term solution (which they in fact said they were doing via a post much earlier in this thread).

    • Edit

27. 177 Posted by -Kevin N. on 16 Dec, 2025 05:10 PM

    

    @mmd,

    I tried doing an import for a longer time period this morning.
    The script threw some errors related to some sell transactions and some purchases.

    In the script, I added , 'PURCHASE ' to line 24 buyStrings =
    and , 'SOLD ' to line 25 sellStrings =

    Doing so seems to have resolved the errors.

    -Kevin N.

    • Edit

28. 178 Posted by mmd on 16 Dec, 2025 06:30 PM

    

    Added Kevin N's strings, trim.lower() for securities name comparison, and dividend reinvestment to

    https://drive.google.com/file/d/1pYgdgEUYrGJtlm_-JI5PezfSphh2UzNW/v...

    and attached.

    Sorry haven't had time to make it extension yet even with Stuart's helpful code.

    I'll say account names from CSV are just the nicknames on the fidelity.com view so easy to change from there. Securities names of course are harder to change but not sure if matching by ticker will work for all (or most) people.

    • fidelity.py 14.2 KB
    • Edit

29. 179 Posted by ioweejun on 16 Dec, 2025 06:35 PM

    

    Please define “token based” vs “credential based”
    I would hope for a qfx by account download (I may have acronym wrong, Vanguard does this) for free; some sort of “token based” able to update multiple accounts for some nominal fee. I would have some hope cost nominal because drags some of us who couldn’t justify MoneyDance+ into the fold.

    Further, Thankyou for all the work some have done for a converter, but I need to see something from Fidelity and MD. Too worried about compromised code when dealing with financial data. Perhaps someone can explain how converter proposed secured (I am not a programmer).

    Cheers

    Get Outlook for iOS<https://aka.ms/o0ukef>
    ________________________________

    • Edit

30. 180 Posted by LarryCL on 16 Dec, 2025 07:18 PM

    

    @ioweejun wrote:

    Please define “token based” vs “credential based”

    Short answer: These are general terms, but what they mean is, with "credential based", the user's username & password are shared with a third party such as a software product (eg moneydance) or an aggregator (eg, plaid), and used directly by those services to log into the financial institution (eg, Fidelity). Whereas with "token based", during the setup process, the user would authorize the financial institution to share a "token" with the intermediary that grants the intermediary limited and specific access (eg, download of transactions only). The username & password are never shared with a third party.

    Sharing credentials directly with a third party is considered to be a security risk and thus most financial institutions have worked to reduce or even prohibit it, and now use token based systems as a secure alternative.

    Now, what's happened specifically with Fidelity is they finally disabled the API (application programing interface) that moneydance was using to pull transactions using a credential based" auth system. Fidelity's proposed alternative for finance software products is to use their aggregator Akoya. Unfortunately, Moneydance does not currently support Akoya, although much earlier in this thread someone from TIK said that they are in discussions with Fidelity/Akoya. So I am hopeful (but not holding my breath) that we will have native support sometime soon.

    • Edit