I'm upgrading from Quicken 7 for MAC to 2019.

wbcpoint

Is Quickfill available in Quicken 2019

jacobs

Yes. No. Not now, but in the future.

Currently, if you enter a transaction, Quicken 2019 will auto-match as you type letters in the Payee field, and it will auto-fill ("quickfill") the values (category, tags, memo, splits) from the most recent transaction for that Payee. This is basically the same as Quicken 2007.

But there is currently not a way to "memorize" a transaction in a certain state to re-use later, as there is in Quicken 2007. Let's say you shop at a supermarket that also sells gas, and your transactions are mostly groceries but sometimes gas. In Quicken 2007, you could memorize the transaction the way you wanted it to default each time. In Quicken 2019, it will always use the most recent transaction for that payee. (Of course, if you're entering transactions manually, you could have two Payees, one for Supermarket-Groceries and another for Supermarket-Gas.) In Quicken 2007, you could also memorize a transaction with some data filled in and other data empty; for instance, some of my memorize transactions have no amount if it's a Payee where I know the amount always varies. Again, in Quicken 2019, it will always quickfill the most recent transaction for that Payee.

That's today. But the product manager for Quicken Mac has stated that they are working on some equivalent to quickfill/memorize transactions for a future release. He's described a method where Quicken would be able to suggest multiple categories you've used for a Payee in the past so you can easily pick the one you want to apply this time. Exactly how this will work, and when it will be released, is unknown; we just know it is under development and coming sometime in the future.

jacobs

Yes. No. Not now, but in the future.

Currently, if you enter a transaction, Quicken 2019 will auto-match as you type letters in the Payee field, and it will auto-fill ("quickfill") the values (category, tags, memo, splits) from the most recent transaction for that Payee. This is basically the same as Quicken 2007.

But there is currently not a way to "memorize" a transaction in a certain state to re-use later, as there is in Quicken 2007. Let's say you shop at a supermarket that also sells gas, and your transactions are mostly groceries but sometimes gas. In Quicken 2007, you could memorize the transaction the way you wanted it to default each time. In Quicken 2019, it will always use the most recent transaction for that payee. (Of course, if you're entering transactions manually, you could have two Payees, one for Supermarket-Groceries and another for Supermarket-Gas.) In Quicken 2007, you could also memorize a transaction with some data filled in and other data empty; for instance, some of my memorize transactions have no amount if it's a Payee where I know the amount always varies. Again, in Quicken 2019, it will always quickfill the most recent transaction for that Payee.

That's today. But the product manager for Quicken Mac has stated that they are working on some equivalent to quickfill/memorize transactions for a future release. He's described a method where Quicken would be able to suggest multiple categories you've used for a Payee in the past so you can easily pick the one you want to apply this time. Exactly how this will work, and when it will be released, is unknown; we just know it is under development and coming sometime in the future.

wbcpoint

I hope sooner than latter!

wbcpoint

Misspelled later

jacobs

They never say when something will come out, unless it's very imminent, because they don't want to frustrate users if there are complications during development and the timeline changes. The Payee renaming rules feature that was release last month was in development since late last year, and took a lot longer than they originally thought it would. As users, we want every feature NOW -- but more importantly, we want it when it (a) works well, and (b) doesn't have bugs. Development of some features is anticipated to take a long time because of the complexity involved, but development can prove more complicated than expected; in testing, troublesome bugs can sometimes take awhile to track down and fix, and beta testers may send the developers back to the drawing board if there's feedback that an update doesn't work well or is confusing.

And, of course, there are several hundred feature requests we users have asked the developers to work on, so just prioritizing those requests and optimizing who on the development team can work on different aspects of the program can have a major impact on what comes sooner and what comes later.

Since the product manager has talked about them working on memorized transactions, I'd guess it might be coming late this year or early next year, but that's a guess without inside knowledge of their development roadmap. We just know it's coming…sometime.