(Canadian

Today I noticed that I was charged for my renewal for Quicken Mac 2020. That means I upgraded from QM 2007 one year ago today. So I thought I’d look back at the changes/progress that has been made in that year.
When I signed up (mainly because of Mac OS Catalina’s inability to run Quicken 2007), I was afraid that Quicken 2019 (at the time) was not going to be satisfactory at all. I had heard stories… As I wrote in a forum post a few months ago, the switch was fairly smooth and I was pleasantly surprised by the status of the program at the time. I was especially impressed with the “All Transactions” line that allowed me to search for a huge variety of inconsistencies and errors in the database. I spent lots of time cleaning up the file, and that has helped straighten out a lot of erroneous things I found in various reports and registers.
As I learned more about the program, I did find some shortcomings. Many of these have been addressed in the 6 releases that have happened since I signed on with 5.11. These include many conveniences such as the new Payees and Rules memorization, the new sidebar changes, the new reports lists, etc. A few added capabilities include an improving new report engine and report customization process and the improving Quick Pay/Check Pay (which I do not use yet, but hope to soon). These are appreciated and helpful, as is the seemingly more reliable update process.
So overall, I congratulate Quicken for their continued support of QM2020 and the team who respond on the forums who seem responsive and dedicated to product improvement. I would like to reiterate a few items that I’d like to see in the second half of 2020 from my wish list of December 2019.
First, in general I’d like to see a focus on improved capabilities in the investment aspects of Quicken. Such things as a wider variety and increased sophistication of Asset Classes (that should not be too hard) and the ability to determine IRR over specific (and longer) periods of time. Other improvement in investments that I’d like to see would be an “X-Ray” of holdings (aggregating mutual fund holdings by account or something similar-I think QW does this through Morningstar) so you can analyze what you really own.
Another issue in investments is that there is no way to make a dividend tax-free in a non-retirement account. For instance, Muni’s in a taxable account cannot be shown to be tax-free, except by use of tags. To see the total of tax-free income, you must tag each of them as “Tax-Free Dividend” and include them in a report through the tag portion of the customize tab in the new report generator. I’d like to see that changed.
Another thing that really should be addressed is that there is an inconsistency in how Reinvested Dividends and Reinvested Capital Gains are treated. Reinvest Capital Gains cannot easily be included in budgeting. The only way to achieve this right now is to split a Reinvested Capital Gain into two transactions, as Capital Gain Income and then a security buy (as two separate transactions). This is strange because it is not the same as how Dividends are treated, where Reinvested Dividends can be included in the budget in one transaction because the category assigned to reinvested dividends is “Dividend Income”. The category automatically assigned to Capital Gains is “Reinvested Capital Gains” which is not a budget category, and in fact does not seem to exist anywhere else in the program. Note: this might not be bad if someone is starting from scratch, but many of us updating from QM2007 or other programs have hundreds of those transactions and dividing them all into two transactions too time-consuming, so our budgets go without Capital Gains. I expect that this is problematic for those who rely on Capital Gains for their primary income.
In non-investment areas (banking), I’d still like to see a “Previously Reconciled” window/register so you could see previous month’s reconciliations when something goes wrong or changes (similar to QM2007).
But again, I appreciate the progress I have seen in the last year and look forward to 5.18 and beyond. And yes, I have put these suggestions in the Ideas section of the forum or voted for similar existing ideas, this note is just my way to consolidate and reiterate those comments.
Glenn MacCullough
QM user since 1999