tag:infinitekind.tenderapp.com,2009-01-14:/discussions/general-questions/110509-confiurm-and-categorize-multiple-transactions-from-the-same-payee-at-the-same-timeInfinite Kind: Discussion 2021-07-06T13:00:24Ztag:infinitekind.tenderapp.com,2009-01-14:Comment/491247262021-04-05T15:46:37Z2021-04-05T15:46:37ZConfiurm and categorize multiple transactions from the same payee at the same time<div><p>just a user,</p>
<p>You can use the search field to find the targets, select the transactions found, right click the selected group, then Right Click and "Mark as cleared".</p></div>mhoggietag:infinitekind.tenderapp.com,2009-01-14:Comment/491247262021-04-05T16:16:41Z2021-04-05T16:16:41ZConfiurm and categorize multiple transactions from the same payee at the same time<div><p>"Mark as cleared" is not the same as "mark as confirmed"</p></div>jimrhtag:infinitekind.tenderapp.com,2009-01-14:Comment/491247262021-04-05T16:37:29Z2021-04-05T16:37:29ZConfiurm and categorize multiple transactions from the same payee at the same time<div><p>just a user,</p>
<p>In MD, the "mark as confirmed" is a function of the transaction download feature where you match, merge, or add downloaded transactions to your register. It puts a Blue Circle on the right side of the description field to mark the transaction that it was confirmed by a downloaded transaction. Is that what you are looking for? A way to mark transactions as confirmed outside of the download function?</p></div>mhoggietag:infinitekind.tenderapp.com,2009-01-14:Comment/491247262021-04-05T17:11:29Z2021-04-05T17:11:29ZConfiurm and categorize multiple transactions from the same payee at the same time<div><p>At risk of dissing an awesome program:</p>
<p>In "quicken", "confirming" a transaction created an association between the line of gibberish that comes over the wire from the bank, with a human-readable description and category.</p>
<p>Using the example from the original posting, "VZWRLSS*PRPAY AUTOPAY" is always, <em>always</em>, <strong><em>always</em></strong> "Verizon Wireless" with a category of "Utilities: Cell Phone".</p>
<p>Quicken would then offer the opportunity to take <strong><em>every</em></strong> transaction that had "VZWRLSS*PRPAY AUTOPAY" and convert it to "Verizon Wireless" with a category of "Utilities: Cell Phone".</p>
<p>Absent that feature, (which only is possible from within find-and-replace and does not change the "confirmed" status), I question the utility of having transactions "confirmed" or not. As it is, I simply end up using it as a marker for transactions I have to re-visit with better information later.</p>
<p>As it currently is, I do the following:<br>
1. Go to a transaction.<br>
2. If the transaction is a common one, (like Verizon, or the local gas station, etc.), I go to find-and-replace, find all the transactions, change the description and category and clear the gibberish out of the memo field.<br>
3. Rinse and repeat.</p>
<p>After that, to tidy up, I have to go back to <strong><em>every stinking transaction</em></strong> and manually confirm it. This replaces the gibberish in the memo field so I then have to go process these transactions <strong><em>AGAIN</em></strong> to re-re-remove the gibberish.</p>
<p>Additional pain point that has already been extensively discussed:<br>
Confirming a transaction automagically assumes you want to <strong><em>MERGE</em></strong> that transaction with something else, not simple confirm-in-place. If you're not careful what you click on, (especially with my shaky hands and failing eyesight), you end up deleting transactions.</p>
<p>It shouldn't be this difficult. Being able to clear the "(un)confirmed" status in find and replace would be a start to solving this problem.<br>
(/rant)</p></div>jimrhtag:infinitekind.tenderapp.com,2009-01-14:Comment/491247262021-04-05T21:02:33Z2021-04-05T21:02:33ZConfiurm and categorize multiple transactions from the same payee at the same time<div><p>just a user,</p>
<p>No problem complaining about MD. We all do at times, But it's the most versatile personal finance software I've found with out the server storage and subscription fees.</p>
<p>Every time you download transactions, MD notices the category you assigned in the past with a similar description and will recommend a transaction to Merge with or s Merges, or a similar Payee to use along with the category you used in the past. Or you can just ignore both, change the category as needed and accept the transactions as is. Then in future transactions with similar names you will be offered those that you used in the past with the categories you selected. It takes a period of time before MD will offer the similar transactions, but it will start happening more with time. So if your cell phone bill has the same or similar description each time, it will start showing up with the Cell Phone category under the similar payee listing so you can accept.</p>
<p>So when you begin with MD, be sure to set the category correctly each time and you will start seeing the correct category appearing when you see those transactions again. Just give it some time. For instance, when I download credit card transactions with Walmart activity, it will not give me the Grocery category by default since that is my most common category for Walmart, but it will also list similar transactions where I used other categories. But if none of the categories are appropriate, I just select the needed category. You can also set the history window that MD uses to find the similar transactions. That setting is under File Preferences, Network. "Only match downloaded transactions when they are at most (XX) days apart" I have that option set to 21 days to prevent me accidentally merging with a previous months activity.</p></div>mhoggietag:infinitekind.tenderapp.com,2009-01-14:Comment/491247262021-04-05T21:04:52Z2021-04-05T21:04:52ZConfiurm and categorize multiple transactions from the same payee at the same time<div><p>just a user,</p>
<p>You can also use MD basic search to find the transactions, select as needed, then right click, and change the status of multiple transactions.</p></div>mhoggietag:infinitekind.tenderapp.com,2009-01-14:Comment/491247262021-04-06T09:50:22Z2021-04-06T10:03:37ZConfiurm and categorize multiple transactions from the same payee at the same time<div><p>I really hate complaining, especially since they seem to work so hard on this - as opposed to other companies that shall remain forever nameless, (whose name starts with a "Q")</p>
<p>If the folks at Infinite Kind, (especially program and development management), are reading this, please let me place an important issue at your feet:</p>
<p>It is my humble opinion that the root cause of virtually every complaint can be reduced to one simple thing: The user interface gets in the way and confuses them.</p>
<p>Before I retired, I used to work as a software QA analyst for some pretty big firms, (think Fortune 500+), and my emphasis was on UI design and clarity, so perhaps I'm a bit more sensitive to this than others. Especially since doing the UI "right" is often no more difficult than doing it "wrong". It's just another discipline, like remembering to commit frequently to the CVS tree, or taking regular backups.</p>
<p>Much of my frustration with MoneyDance, (and admittedly a lot of other software), is because <strong><em>the developers write the interface for other developers</em></strong> and not the user. This is the fast boat to UI disaster and a dedicated UI design and test team will pay huge dividends in increased reputation and sales.</p>
<ol>
<li>
<p>I personally believe that every developer should have a copy of <em>The Tau of Programming</em> on the side of their cube, and management should enforce this rigidly.</p>
</li>
<li>
<p>Remember that the people using your software <strong><em>are not professional developers</em></strong>, or (in many cases), <strong><em>neither are they professional accountants</em></strong>. The extremely strict rules of double entry accounting may not make sense to mere users.</p>
<ul>
<li>Idea: Perhaps there can be a preference to "relax" some of the strict, (and potentially annoying), rules to make them more in line with user expectations?</li>
<li>For example: Transactions cannot cross day boundaries. They have to be on the same day and you cannot have an entry in one register on a different day than the corresponding entry in a different one. (an entirely different discussion)</li>
</ul>
</li>
<li>
<p>It is crucially important to remember certain fundamental rules of interface design:<br>
(a) "Closure" - that is, designing the interface to "guide the user along the path of righteousness" and help him avoid mistakes. In fact, "mistaken" choices should be disabled as much as possible. Perhaps with an option to turn this on and off.<br>
(b) The Rule of Least Astonishment: This "rule" means to try to do things in the way the <strong><em>USER</em></strong> expects, even if it is more difficult or inconvenient for the developers.</p>
<ul>
<li>For example, in Windows people expect to be able to highlight something, right-click, and copy and/or paste. In MoneyDance, the user needs to use CTL-C and CTL-V to copy and paste. Most users are not Linux command-line gurus, so this is really a pain.</li>
<li>In the same vein, Mac users have expectations on how their user interface is expected to behave and on Mac releases that should be rigidly adhered to as much as is possible.</li>
<li>Whenever possible, <strong><em>use the standard system UI interfaces, API's, commands, and keyboard shortcuts</em></strong>. Even if they make life more difficult for you. Your users will thank you.</li>
</ul>
</li>
<li>
<p>Remember the KISS rule, (Keep It Simple, Sir).</p>
<ul>
<li>Don't make things more difficult for the user than absolutely necessary.</li>
<li>Don't make the process flow more difficult than absolutely necessary.</li>
<li>Make sure the user can do all of, (or at least 99% of), their tasks <strong><em>without removing their hands from the keyboard</em></strong>.</li>
<li>Likewise, keyboard commands should have a UI variant that uses the mouse.</li>
<li>The basic rule here is that the user should not have to continually move back and forth between the keyboard and the mouse.</li>
</ul>
</li>
<li>
<p>Often the difference between an expensive, super-duper professional piece of software and a lower priced variant, is the care and detail taken to ensure the user interface is as polished as possible and the workflow is smooth and simple.</p>
<ul>
<li>Users give better reviews, and are more likely to recommend, a piece of software that does not frustrate them at every turn.</li>
</ul>
</li>
<li>
<p>UI design and UI management should be an integral part of all software design meetings and project management meetings - with the authority to make themselves heard and their opinions respected.</p>
</li>
<li>
<p>Rule: Just because Quicken did things one way, doesn't mean you have to copy them. They are notorious for having a crappy interface that generated hordes of complaints.</p>
</li>
</ol>
<p>What say ye?</p>
<p>Maybe I should open another ticket about this?</p></div>jimrhtag:infinitekind.tenderapp.com,2009-01-14:Comment/491247262021-04-06T12:53:00Z2021-04-06T12:53:00ZConfiurm and categorize multiple transactions from the same payee at the same time<div><p>just a user,</p>
<p>There is always a learning curve with any software. MD for sure is not perfect, but what I see a lot is X-Quicken users who are confused about features on MD that don't work like features on Quicken. Sometimes they expect MD to be a Quicken like program, but it's not. It's organized differently and the programmer has a different approach to the function. If they want to make MD look like Quicken, then they need to add the online chat support, server storage, and monthly subscription. Many of us don't want those Quicken features. That's one reason I left Quicken many years ago.</p></div>mhoggie