On May 24, 2009, at 9:31 PM, David wrote: > I have observed a "bug" locally that appears to simply reflect the way > Smart Transactions function. > > We have "Chase" as a payee, for a credit card. The first few > transactions were processed and an auto-matching Smart Transaction was > created. > > The problem is that a lot of our bank (Wells Fargo) debits contain the > word "PURCHASE", and this fires off the Chase auto-match rule, which > then replaces the Payee name with the friendlier "Chase". This hides > the details of the transaction and assigns a bucket "Debt Repayment". > Took half an hour to figure out... > > Is there any way to prevent partial matching of payees? I realize > that adding any complexity to this process gets into creating a > programming language fairly quickly, with the attendant possibility of > bugs. > > For now, I have deleted this Smart Transaction, and also turned off > Auto-Memorize. Is there a slicker workaround?
David, You can change the aliases on memorized transactions to keep them from matching these "broad stroke" names. In the 1.5 release, I plan to give MoneyWell a list of "don't match" aliases to solve problems like this. Please know that you can see the original payee and memo for a transaction in a tool tip by hovering your cursor over the Transaction Detail title bar. Peace, Kevin Hoctor [email protected] No Thirst Software LLC http://nothirst.com http://kevinhoctor.blogspot.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "No Thirst Software User Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/no-thirst-software?hl=en -~----------~----~----~----~------~----~------~--~---
