Stock Spin-off - generates transactions in other investment accounts
David.Klein
Quicken Windows Subscription Member
Hi, has anyone else experienced this problem, and is there any way to avoid it?
- I have two investment accounts, each of which has some of the same stock.
- One account was up-to-date,but I was playing catch-up (a few months behind) on one of the accounts.
- The company spun off shares. This worked fine in the up-to-date account. Everything reconciled in this account.
- Entered the investment transactions in the other account, and performed the same spinoff (including using the temporary stock name).
- Found that, in addition to performing the split in this account, Quicken then added a new set of transactions for the split in the account I had already reconciled, throwing the holdings for the stock (original and new stock) out of whack.
Is this a bug? Why is Quicken creating transactions in other investment accounts other than the one I'm working on?
Thx,
DK.
- I have two investment accounts, each of which has some of the same stock.
- One account was up-to-date,but I was playing catch-up (a few months behind) on one of the accounts.
- The company spun off shares. This worked fine in the up-to-date account. Everything reconciled in this account.
- Entered the investment transactions in the other account, and performed the same spinoff (including using the temporary stock name).
- Found that, in addition to performing the split in this account, Quicken then added a new set of transactions for the split in the account I had already reconciled, throwing the holdings for the stock (original and new stock) out of whack.
Is this a bug? Why is Quicken creating transactions in other investment accounts other than the one I'm working on?
Thx,
DK.
0
Best Answers
-
A spin-off, like a stock split, is a per-security event, not a per-account event.
Quicken user since version 2 for DOS, now using QWin Premier (US) on Win10 Pro.
1 -
The Corporate Securities Spin-Off wizard has no way of knowing you only want to record the spin-off in one account. Normally, a spin-off should be applied to all holdings of a security. It should be a simple matter of deleting the additional transactions and correcting the spun-off security. If you want to avoid the issue in the future, you may enter the RtrnCap, MiscInc, and Added transactions directly yourself.
1 -
If you want to avoid the issue in the future, you may enter the RtrnCap, MiscInc, and Added transactions directly yourself.
Or you should make sure all accounts are up-to-date with respect to that security when you first enter the Spinoff wizard. Yes, it is by design that a spinoff in one account gets applied to all accounts holding that security at that time.
1
Answers
-
A spin-off, like a stock split, is a per-security event, not a per-account event.
Quicken user since version 2 for DOS, now using QWin Premier (US) on Win10 Pro.
1 -
The Corporate Securities Spin-Off wizard has no way of knowing you only want to record the spin-off in one account. Normally, a spin-off should be applied to all holdings of a security. It should be a simple matter of deleting the additional transactions and correcting the spun-off security. If you want to avoid the issue in the future, you may enter the RtrnCap, MiscInc, and Added transactions directly yourself.
1 -
If you want to avoid the issue in the future, you may enter the RtrnCap, MiscInc, and Added transactions directly yourself.
Or you should make sure all accounts are up-to-date with respect to that security when you first enter the Spinoff wizard. Yes, it is by design that a spinoff in one account gets applied to all accounts holding that security at that time.
1 -
Thanks, everyone, for the answering. Yes, I can see that the wizard is applying to all holdings, but I would much rather retain the control of the spin-off process and limit the wizard to applying the changes only to the account on which I'm working. To me, though, it seems like a flaw in the wizard itself in that it would simply dump transactions into an already reconciled account. That completely threw off the other account, along with the 'temporary' security name. At least, I was able to simply manually delete the unwanted transactions.0