Investment module overall and refresh

fciani
fciani Quicken Windows Subscription Member ✭✭✭

This module was clearly written totally separate from the main Quicken operational protocols. Functionality and operations don't behave the same. Tagging transactions is cumbersome. Investment categories are stored in one location with both income and expense combined. New investment categories cannot be created within that container and they cannot be rearranged for reporting purposes.

Additionally, there are two bugs that I have to deal with.

  1. When using a saved transaction for a deposit or a withdrawal, Quicken will NOT override the transaction amount. Quicken uses the previous value. I have to save the transaction with the incorrect amount and then edit it to the correct amount.
  2. The second bug is something that i just discovered today. When recording income to 'misc', Quicken has a field for the category to use. However, the category defaults to 'misc'. I have to override the category a second time to record the correct category.

I think it's time that that investment module gets a complete overhaul. First and foremost, Quicken should ask its users how we use the investment module. How we invested 20 years ago is not how we invest today. There are new investment products (ETFs, Futures trading and now 0 DTE options) that didn't exist then and we are forced to make Quicken work as it doesn't recognize them.

Comments

  • Jim_Harman
    Jim_Harman Quicken Windows Subscription SuperUser ✭✭✭✭✭
    edited January 27

    I think I am also seeing your issue #1. To clarify, this is when you click on Enter Transactions for an Investment Deposit or Withdrawal and the Payee is on the Memorized Payee List. Quicken uses the amount from the MPL rather than the amount you enter. Is this what you are seeing? See this discussion

    As far as I know no one has officially reported this, and Quicken has not acknowledged it.

    QWin Premier subscription
  • fciani
    fciani Quicken Windows Subscription Member ✭✭✭

    Correct. This seems like a simple issue to correct.