[moneydance] Transaction matching rules

[Sean Reilly]

Hi John,

Please keep in mind that Moneydance matches downloaded transactions to  
local transactions based on the original payee/memo fields in the  
local transactions, not the current payee field.  To see the original  
payee/memo fields in build 614 or newer hold the 'alt' key and move  
the mouse over the transactions in your register.  You should see some  
similarity between the local and online payee/memo fields in the  
extended information shown in the popup.

I'm not saying there isn't a bug to be fixed, but this should provide  
a better view into how the transaction matching works until I get time  
to write a complete rules-based matching system for matching payees.

Thanks,
Sean


On Aug 1, 2008, at 12:25 , John Muccigrosso wrote:

> A related problem:
>
> MD seems to insist on certain old transactions being similar to new
> ones, despite (1) the old transaction not looking at all like the new
> one, and (2) there being perfectly good, nearly identical old
> transaction that do look like the new one.
>
> For example, for a new transaction for "Café Meow", MD will suggest
> "Joe's Auto repair" as a repeat payee even though there are several
> old transactions for "Café Meow". It will similarly suggest "Joe's
> Auto repair" for "Wooden You Know" toys and "Knit Knack" yarn shop,
> again despite the presence of previous transactions for the latter two
> stores.
>
> Actual matches go fine, so if I've already entered the "Café Meow"
> transaction, MD will match it perfectly.
>
> I filed a bug on this already, described somewhat differently:
>
> http://moneydance.com/trac/ticket/1209
>
> John