Problem exchanging equity shares.
GMW2
Quicken Mac Subscription Member ✭✭
Suntrust recently became Truist. Quicken struggled with the transactions that initially resulted in both Truist and Suntrust shares in the portfolio.
I have sorted the Truist transaction but I have tried a Sell transaction on all STI shares and a separate remove shares transaction all to no avail Suntrust is still there with the original share count.
Online help recommended creating and downloading a new account - which eliminated the STI holding but now all the cost basis information for the portfolio has to be manually re-entered!
Help. Thanks!
I have sorted the Truist transaction but I have tried a Sell transaction on all STI shares and a separate remove shares transaction all to no avail Suntrust is still there with the original share count.
Online help recommended creating and downloading a new account - which eliminated the STI holding but now all the cost basis information for the portfolio has to be manually re-entered!
Help. Thanks!
0
Best Answer
-
It sounds like a placeholder is counteracting your Sell (or Remove Shares) transaction(s).
Scroll to the beginning of the register after you have added your respective STI transaction. I suspect you will see an Add Shares transaction in light gray that is doing the opposite and thusly keeping the shares in your account. Review the amount/transaction. It might be as simple as deleting the placeholder.5
Answers
-
It sounds like a placeholder is counteracting your Sell (or Remove Shares) transaction(s).
Scroll to the beginning of the register after you have added your respective STI transaction. I suspect you will see an Add Shares transaction in light gray that is doing the opposite and thusly keeping the shares in your account. Review the amount/transaction. It might be as simple as deleting the placeholder.5 -
John thanks very much for the quick and accurate reply. I worked my way through the register for that equity and poof it finally adjusted it out of the account correctly. Thanks again.0
This discussion has been closed.