Mobile App-Option to NOT memorize memo entries made in Transactions

BigTex

PLEASE provide an option to NOT memorize memo's made in transactions.

PLEASE stop creating a new transaction every time a different memo is entered in a transaction to the same vendor.

PLEASE stop auto populating the Desktop app with the above two auto memorized details.

EXAMPLE:

I go to Target and buy my wife a present, and enter New Watch in the memo field. The next time I go to Target I buy a Household item, and enter Frying Pan in the memo field. The mobile app memorizes both of these as separate instances and then synchronizes and auto populates the Memorized Payee list in the Desktop app. This is HIGHLY UNDESIRABLE behavior. Personally, I think this functionality should be removed, but at the very least give us an option to turn it off.

Thanks!

splasher

I don't use QMobile, but are your Memorized Payees LOCKED in desktop Quicken?

Chris_QPW

This is a problem that has been going on for years.

https://community.quicken.com/discussion/7900267/stop-mobile-app-from-memorizing-transactions-edited

CyborgOne

Yes, this has been an issue for FAR too long!

I should not have to find EVERY SINGLE PRIOR PAYEE and explicitly "lock" it in the Classic (desktop) app's Payees & Rules list … but because I've suffered so many problems, I have done so. I want the Category to be saved (e.g. transactions at "Safeway" will always be "Goceries"), but do NOT want the other details (the amount, and the memo) saved as a part of the memorized details, as they will change every time.

HOWEVER, even though I do this: The next time my wife creates a transaction in the Mobile app, it syncs back to the desktop with whatever amount and memo she added in. Yes, this action OVERRIDES the already-"locked" QuickFill rule in the desktop app.

This is absolutely maddening.

Please, please, please, Quicken team: FIX this, and make the interaction between Mobile and Desktop actually functional and useful.

CyborgOne

Update: I just spoke with Quicken support on the phone, who indicated that this is how it is designed (!).

The agent said that QuickFill rules are setup to help with downloaded transactions - so that when you obtain a new transaction from your financial institution, you can have it automatically apply a category, a helpful memo, etc. Very beneficial when updating your Desktop app, easily entering similar new transactions, etc.

But, when entering a transaction from Mobile, this behavior is different: Effectively, any transactions entered on Mobile becomes "the downloaded transaction" for Desktop, and therefore the details become the Memorized transaction … and result in a modified QuickFill Rule being defined (!!). This means that even if you have LOCKED your QuickFill transaction on Desktop, you will wind up with the specific payee getting that most-recently-entered Mobile transaction's category, amount, and memo saved off as the (inexplicably-updated) QuickFill Rule.

This seems completely unfathomable to me: Why would I ever want a specific transaction entered on Mobile, to be the desired default for ALL future transactions with that Payee? Would anyone, ever, want such a behavior? Because it certainly seems to be problematic to everyone I've spoken with, regarding the current functionality.

This seems to be an easy fix for the Quicken development team: Please provide a preference setting on Mobile to indicate "NEVER memorize transactions entered on Mobile". OR, even better, just simply never do this by default. This is not something which it seems any (at least, "most") users would want to take place, and is maddeningly frustrating for users who have specifically tried to work around it (by locking the QuickFill Rule), only to have this desired setting be completely overridden.

Quicken team: Please respond to this post, with information on why this is the current behavior - and, ideally, that you will log a bug/enhancement request to resolve this issue for your users in the near future.

CyborgOne

I knew this had come up before….

Turns out that we've been discussing this same topic for several years at this point. See:

https://community.quicken.com/discussion/7900267/stop-mobile-app-from-memorizing-transactions-edited