Quicken 2017 For Mac Entries Default To Expense Rating: 6,7/10 3763 reviews

May 10, 2018 - You can either apply your changes to all similar registers, or reset all similar registers to their default column set. Click Done to save your.

I have recently had a problem with Quicken 2017 for MAC. I have downloaded all updates and am running Version 4.6.6 (Build 46.19138.100). I have created an Accounts Receivable account (asset) to use as a 'Transfer' when I have purchased something that I will ultimately be reimbursed from others for.

Sometimes if I realize that I will not be reimbursed I will change the category (or a portion thereof) of the original transaction from an a transfer (e.g.[Accounts Receivable]) to an expense category (e.g. Historically, this has always resulted in the amount being newly categorized as an expense and no longer appearing in the Accounts Receivable Account. Recently (never happened in Quicken 2007 for Mac and not in my initial months of using Quicken 2017 for Mac) the behavior has changed. For example, assume that I purchased an item for $10 on my American Express Card from Target. I expect to be reimbursed by others for the $10.

Initially I recorded the category on my Amex Account as [Accounts Receivable]. A few days later I realize I am going to keep the item, so I change the category on my Amex from [Accounts Receivable] to 'Groceries'. Ik multimedia modo bass v1.0.2 incl keygen win/mac-r2r. Old Behavior As recently as a few weeks ago, when I did the above, Quicken would have: (a) Kept the Amex balance at $10 (b) No longer showed any activity for the transaction the Accounts Receivable Account.

(c) Would show a Groceries Expense of $10. New Behaviour Recently, Quicken has started to behave as follows: (a) Keep the Amex balance at $10, with an offsetting Groceries Expense of $10.

(b) Keep the Accounts Receivable balance at $10, with an offsetting contra (i.e. Negative) Groceries Expense of $10. (c) Show a Groceries Expense of $10, offset by a negative Groceries Expense of $10, resulting in a net Groceries Expense of $0 showing up in my expense reports. Effectively, it is overstating my assets and understanding my expenses. I have not experienced this before.

I actually restored an old version of my quicken file from August to see if it behaves the same way I described above (i.e. Behaves erroneously) and it does.

2017

This tells me that this is a bug that popped up with all the recent updates to the tool. Can anyone else replicate this issue? Experience with Tech Support I spent a fair amount of time with Chat Support today who told me that this is the way that the engineers designed the system to work, and that if I want it to do otherwise, I should delete the original transaction and enter an entirely new transaction with my new expense category. When I politely (3 times) told the individual that this is not the way the tool behaved before, that I thought it was a bug, and that I would like to make sure it is reported as such, he assured me it is not a bug and said that it would not be reported as a bug because the tool is operating as designed. As both a CPA and an individual that has designed client software for my employer, I find it hard to believe that (a) this is the way that Quicken intended the product to work (i.e. Ignore the double entry bookkeeping standard that is what Quicken is built upon) and (b) that they would not be interested in understanding that the tool is not operating in the manner in which users expect (and by past experience have been conditioned to expect) it to operate.

Yes, this is not a bug per se but a poor UI design when they introduced the ability to enter transfers via the category field in QM2017 v4.3, like you can in QM2007. First understand that this anomaly exists of this new feature combined with the feature where you can categorize transfers in QM2017, which you cannot do in QM2007. This is a design oversight that I pointed out long ago as soon as this feature was first available in Beta in QM2017 v4.3. And is documented to address this. Until they implement a solution, the only work-around is to do as @RickO mentions above. (If you find this reply helpful, please be sure to click 'Like', so others will know, thanks.).