Report utilizing wrong unit share value.
Eric7
Quicken Windows Subscription Member
I am using the INVESTMENT TRANSACTION report to sort out account fees. Fees are deducted by removing shares at the current unit share value the day the shares are removed. The fees are entered manually into Quicken via the REMOVE - SHARES REMOVED function.
I am using the MEMO CONTAINS function under the report SECURITY tab to sort out the applicable transactions.
The generated report is using an initial purchase share price (that can be years old) rather than the share price on the day the shares are removed to calculate the cash value. This creates a false cash value. I have looked at the other transaction options for the report, but none seem to fit my needs. Any suggestions for a fix to show the correct cash value.
I am using the MEMO CONTAINS function under the report SECURITY tab to sort out the applicable transactions.
The generated report is using an initial purchase share price (that can be years old) rather than the share price on the day the shares are removed to calculate the cash value. This creates a false cash value. I have looked at the other transaction options for the report, but none seem to fit my needs. Any suggestions for a fix to show the correct cash value.
0
Best Answer
-
Your Remove Shares process is not appropriate, IMO. I think you should be selling the shares at current cost (incurring a gain/loss as applicable, not taxable if within a retirement account). A second transaction as a MiscExp or as a Withdraw is then used to record the amount against your chosen Investment Fee type of category and take the cash out of the account..6
Answers
-
Your Remove Shares process is not appropriate, IMO. I think you should be selling the shares at current cost (incurring a gain/loss as applicable, not taxable if within a retirement account). A second transaction as a MiscExp or as a Withdraw is then used to record the amount against your chosen Investment Fee type of category and take the cash out of the account..6
This discussion has been closed.