Dear Kevin and Moneywell Gurus, 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? Thanks, David PS. *Love* the program!!! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
