[quote="Mark"]Hi Gerry,
The spreadsheet doesn't support all transactions. It was updated yesterday to add support for long term cap gain, short term cap gain, and return of capital. ...
[endquote="Mark"]
Mark,
I attempted to update my FM file with the generated spreadsheet, but it wound up creating a huge number of incorrect entries. Is there a simple way I can undo this? I thought if I close the SW and did not save, all would be back the way it was; but no, all the errors are saved. Now what?
Gerry
|
|
Fidelity Download problem
Hi Gerry,
If you go "Back" or "Cancel" when looking at the "Preview Importing Transaction" dialog, that would be fine. If you do "Finish" the import, you can still exit without saving. To do that, make sure the "Save Investments/Portfolio on Exit" commands are un-checked from the top level "Options" menu. If you finish the bad import, and save, you'd have to either restore from a backup or manually delete the imported transactions.
While it would be a perfect solution to go back to the system as it was, I have (grudgingly) learned to accommodate to the Vanguard workaround. I have trading authority already in the family and friends Vanguard accounts that I manage in my retirement so I have them aggregated on one statement, therefore one download and a single batch input into Fund Manager.
I don't understand why Fidelity doesn't offer the ability to download into .QIF format as opposed to only .CSV As I said, it wouldn't be perfect but I for one could make a .QIF download from Fidelity work. Schwab works perfectly for me, although just one account so I haven't had to aggregate. I'm not in a position to move the Fidelity accounts that I manage to Schwab, however, for reasons that I won't go into. Come what may, they must stay at Fidelity.
I use a quick python script to use the csv file and convert it to a qif file. It's pretty basic and will get me through this, hopefully interim, situation. I can always add additional script classifications as new transaction codes show up in my csv. Results in cludgy programming code, but if it works, I'm good - not publishing anything!! I'll see how far I can take the tack-ons in the script to continue converting unknown transactions in the csv. But I agree - at a minimum it would be very beneficial if Fidelity offered up QIF downloads which are a bit more standardized than the csv format.
Mark,
I have not had much luck with CSV downloads. When I get some time, I will try again. However, I use a product called TradeStops from TradeSmith. One of their features is the ability to monitor portfolios at Fidelity. I went in, and it is still working. I did have an error, and when I went to fix it, A screen popped up explaining how they connect to Fidelity. I have attached a file with the info on it. Jim
A little off topic of the Fidelity download issue we face, but is still relevant. I am weary of "data aggregators", not because they pose any security risks (but always a possibility, it's just the burden has been more pointedly and visibly placed on you, the consumer), but because I don't know why any ONE fin-serv needs to aggregate ALL of my data. It's my data, I will aggregate it. But it seems all the brokers are saying "That's fine". I don't need the fin-serv's 'opinion' on what my data is telling me. If I did, I'd pay them for it. But not wanting them to provide it, shouldn't preclude me from aggregating it with the simplest, easiest mechanism possible. CSV files are FAR from that low bar. To suggest it's all about 'security' is a smoke screen at best. There are too many examples where the brokerage firm has allowed FDX, cookie access. If FDX is secure (I trust it is), then using it should be no more less secure using cookie exchange with expiring auth levels. Trust me, if Schwab can allow it, so can every other brokerage. They just choose not to do so. Although it may not be an overnight AUM shift, there are enough individual investors that will most certainly shift over time.
<Rant over>
Today, December 16th, the Fidelity tech rep, "Grady" mentions that the ball is in your court to accept their terms. To quote:
------------------- Thanks for reaching back out, but the changes are up to the Software developers and agreeing to the security protocols and terms that Fidelity has put in place to allow third-party access to clients account data. If you are wanting updates, you will need to stay in contact with your software’s support team as Fidelity has already done their part. ------------------- In a gleeful joyous state, the Tech Rep closes with: ------------------- Thank you for the opportunity to assist you and have yourself a wonderful day! Sincerely, Grady ------------------- Indeed, I'm having a wonderful day!
If it were so, we would gladly accept the terms, but that hasn't been our experience. We are in the process of applying for access to their new FDX server now. We have provided all the requested information and are awaiting for their review and hopefully an approval.
Hi Gerry,
At this point I think we just need to wait for the approval process to complete. Fidelity knows about Fund Manager and has a process we're currently going through. We've provided all the requested data, but are just waiting on possible approval and next steps.
Hi Jeff,
Unfortunately, there is no update. We're still waiting to hear back on the status of our application. The holidays have probably contributed to the delay. We'll reach back out to them after the holidays for a status update if we haven't heard by then. I'm sorry for the delay, and wish I had better news...
Who is onlineUsers browsing this forum: No registered users and 2 guests |
| FundManagerSoftware.com | Search | Site Map | About Us | Privacy Policy |
| Copyright © 1993-2026 Beiley Software, Inc. All rights reserved. |