Hi Dick.

I've discussed the problem relating to the category assignment error in my
other thread, but if there's a link, it's certainly far from clear.

In order to get more detail on this problem, I reverted to a backup taken
before I imported the last statement then reimported the QIF file. The
mismatch was recreated and I have copied the details from the QIF files
below:

D06-11-07
P404781 31237349 INTERNAL TRANSFER
T3000.00
^
D14-11-07
PABODE PYMT ABODE MORTGAGES LI
T3047.87
^

The first entry was from last month's statement and, after importing, the
payee details were correctly automatically changed to 'Transfer', the
category was manually assigned (as it was a transfer from a new account) and
it was 'accepted'.

The second entry was from this month's statement and, after importing, Money
offered to match the two. I know it's easy to unmatch them (which I did),
but it's worrying that Money sees some similarity between the two
transactions that are clearly different in every respect. You could argue
that the amounts are similar, but I can't see what kind of scenario would
benefit from such a coarse match. Money is a personal finance manager and
offering to match two transactions that are so dissimilar seems ludicrous.

I could understand if I'd had any input in specifying the way Money should
make matches and specifically asked it to match transactions with values
that were within a certain percentage, but I haven't and wouldn't and with
the dates being so far apart and the payee details being totally different,
it just looks like Money is making a really dumb guess. My faith in Money's
ability to match transactions accurately is further undermined by it's
failure to match transactions that I do want matching and are clearly a much
closer match (amounts are identical and the dates are within a few days of
each other).

What rules does Money use to determine the match?

How can I edit these rules so that these errors don't occur?

--

Plegron Snaith


"Dick Watson" <littlegreengecko[at]mind-enufalready-spring.com> wrote in
message news:OlWOkPbPIHA.1188[at]TK2MSFTNGP04.phx.gbl...
- quote -

See other thread. Most of the same comments apply here more or less equally.

"Plegron" <plegron[at]hotmail.com> wrote in message
news:OtXUnKbPIHA.5184[at]TK2MSFTNGP05.phx.gbl...
- quote -

I'm using Money 2006 Small Business V 15.0.150.513

I've used Money for many years, but refuse to upgrade again because MS just
keeps adding more and more 'flashy' features whilst some of the most
'useful' basic features don't work properly. Here's another one that's
caused me problems in every version I've used:

After importing my bank statement QIF file, Money tries to match any
transactions it thinks could be duplicates. Great idea and a real bonus if,
like me, you import statements for two or more accounts with transfers
between them. However Money doesn't seem to employ a very sophisticated
algorithm to achieve this and occasionally tries to match transactions with
little in common. This month it proposed a 'match' between two transactions
that had nothing in common except for being both debits.

I have no idea what criteria Money uses to decide which transactions
'match', but it clearly needs to be improved. Is there any way I can edit
this to prevent these silly inaccurate 'matches'?

--

Plegron Snaith