Moving investment account transactions does not work properly
Hello,
So I have several Imported Investment accounts all for the same set of securities but with different dates. These are all valid transactions but when I moved from Quicken to MD, for some reason, these all came in as different accounts based on calendar year. So I thought the best thing to do would be to just move the transactions from each of these Imported accounts into the proper account using the Batch Change command. The transactions do move properly however what does not happen is that the security share numbers for the target account does not update properly regardless of the transactions showing purchases or sales.
For example, I have some Vanguard securities - Primecap and Wellington fund. In the proper Vanguard account prior to any moves, I have about 20 shares each acquired via direct purchase and dividend reinvestment. Then, when looking at one of the many Imported accounts, I have about 5 shares each due to direct purchase and dividend reinvestment. I can move these transactions over to the desired account and they show up properly but the actual number of shares in either account does not update accordingly.
Is this is a bug or desired behavior? Also, any workaround?
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 Ben Spencer on 17 Mar, 2010 03:31 PM
Hi
It is a mistake to batch change a transaction from one investment account to another. The option to do so will be removed in the next release of Moneydance. Doing so results in a transaction in the destination account referencing a security that is part of a the source account. It can be fixed by creating the security in the destination account by selecting the security detail view and adding the appropriate security. And then going to each transaction that has been batch changed and re-pointing it at the correct security. I am terribly sorry that this has affected you. We are working to prevent this from happening again.
Sincerely
Ben Spencer
2 Posted by cyberzeus on 17 Mar, 2010 05:46 PM
Ben - thanks so much for your feedback...
So first off, I was able to restore my data because I had a reliable backup but still, I think this feature offers huge benefit and has huge potential. In my particular case, I have about 8 Imported Investment accounts all for the same securities but for some reason, when I migrated from Quicken to MD, the system interpreted the different calendar years as being different accounts. So as you can imagine, this is going to be tedious no matter what I do.
Removing the batch transaction move will make things exponentially harder for me - why not just add the ability to batch move shares or better yet, make the system interpret the move of the transaction as also meaning that the shares moved. Or the nirvana might be to have this as an option when batch moving transactions.
PLEASE PLEASE PLEASE don't start removing or diminishing the batch move\change feature. This is a HUGE benefit to me and it is one of the core reasons why I use MD. I think it makes so much more sense to add functionality to this feature in order to make it stronger. Include warnings and knobs as needed to help the users out but I feel strongly that diminishing or removing this at all anywhere in the system is the wrong thing to do and I really hope others that feel similarly will add their .02.
Thanks for listening...
3 Posted by Ben Spencer on 17 Mar, 2010 06:06 PM
Hi
As the batch change function is broken for investment accounts for the reason cited above I think it is better to remove it in the short term than have a broken feature that can seriously affect the reliability of data in accounts. We will not be removing this feature from other account types.
I agree with you that the correct fix would be to automatically create the security in the destination investment account and re-point the transaction at that security. Simply moving the security is incorrect as there may still be transactions in the source account referencing that security. I have created a ticket to this effect. Here is a link to the ticket:
http://moneydance.com/trac/ticket/2729
Sincerely
Ben Spencer
Angie Rauscher closed this discussion on 24 Jul, 2011 07:41 PM.