Securities in wrong account
I have several retirement accounts with Fidelity. One is a 403b and another is a 457. I have different securities in each account. However when I download the transactions online securities from the 403b are also put into the 457 (duplicate entries). How can I keep this from happening. In MS Money, I provide one login for Fidelity and it puts the securities into the correct account. In MD I have to duplicate my login to Fidelity several times which also is a pain, especially since it doesn't remember passwords between runs of MD. I'm using MD 2010 (build 738, although I saw this with build 735, too)
Comments are currently closed for this discussion. You can start a new one.
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
1 Posted by forslund on 02 Feb, 2010 03:24 PM
It also seems to have trouble matching a transaction to the proper security. The description of the transaction in an online download has the name and number of the security involved, but MD puts in an different security in the name of the security purchased or sold. This is a slightly different problem than described above, but may be the same underlying problem since it doesn't seem to know which security is in which account all with the same institution (Fidelity). This is a real pain. It is fixable but I have to do a lot of repair of deleting wrong transactions and changing others after an online update. I can't simply do an update and expect to have things right.
2 Posted by forslund on 03 Feb, 2010 03:27 PM
And I have to correct the transactions each time I do an update as it keeps putting the wrong securities in the wrong account every time. What can I do about this?
3 Posted by forslund on 04 Feb, 2010 05:23 PM
I upgraded to build 739 and the problem seems to have been resolved. I no longer get the updates in the wrong account! I hope that is because something was fixed.
4 Posted by forslund on 05 Feb, 2010 12:36 AM
The problem wasn't resolved. When I restarted MoneyDance it downloaded the transaction to the wrong account again. It adds the security to the account even though it isn't in the account. When I delete the security that has been erroneously added, it asks if I'm sure I want to delete account: "Fidelity NetBenefits UNIV OF CALIF 457(B):CUSIP-broken-0054". This is confusing, at least, as I want it to delete the security not the account. I get the same error warning when deleting the second security that was downloaded at the same time. If it gets it into the wrong account, who knows what errors it makes that I don't discover?
5 Posted by Angie Rauscher on 02 Mar, 2010 07:58 PM
I apologize for the long delay in our response, I am embarrassed to say that we have been snowed under with questions about Moneydance 2010. If you are not using the most recent version (2010r2 build 743), please update to that version. You can download the update here. This update has resolved a few key issues our users have been experiencing, including a number of download issues. Please let me know if your issue persists and we will look into other solutions, including your OS and the version of Java you are using.
Please let me know if I can be of further assistance, and I apologize again for any inconvenience this may have caused you.
Angie Rauscher
Moneydance Support
6 Posted by forslund on 31 May, 2010 07:29 PM
This error still persists with build 751. I mentioned it in another thread. It is annoying.
7 Posted by Brian Adler on 14 Jul, 2010 08:38 PM
Forslund,
This issue has been fixed as of build 751. But it is necessary to disable and reconnect your connection with your bank.
Sincerely,
Brian Adler
Moneydance Support
Brian Adler closed this discussion on 14 Jul, 2010 08:38 PM.