Thank you all for your great information and suggestions!

I appreciate the quick response. I'm probably going to change to Quicken to
avoid this and some of the other issues I've been having. This products
seems to try to do too much for me, which is not a good accounting practice.

-Scott


"Mark" <abcd[at]abcd.com> wrote in message
news:41d499d7$1[at]news.microsoft.com...
- quote -

Reference: http://support.microsoft.com/default...b;en-us;890440

"Cal Learner-- MVP" <via_newsgroup[at]please.tnx> wrote in message
news:f239t0huodqlkpvehf62b5blvktgmbqnko[at]4ax.com...
- quote -

In microsoft.public.money, ScottK wrote:

- quote -

It is some kind of Yodlee-related thing that is reportedly a
function of which FI is involved. By entering a support case with
Microsoft, they will be sure to identify that as a FI that has that
symptom.

This has happened to me and as far as I can tell at least one other person in
this forum. All of us that have experienced this problem have Washington
Mutual accounts. I found this happened to me as soon as I migrated my file
from Money 2004 to Money 2005. I also found that if you delete the
transactions instead of accepting them as they are matched, the error goes
away. It also "remembers" what you had called the payee before if you were
doing the merge game and sometimes even remembers what category you put it
under. I haven't been able to determine if the problem pops up again with
new transactions but it definetely doesn't occur with transactions that are
downloaded rather than matched to existing transactions. So, the work around
is:

1. Update and match your transactions like normal (to remember the payee
and/or category)

2. Update again, this time deleting the matched transactions instead of
accepting

3. Update again and the transactions will be downloaded and merged using
your previous payee and category info. The transaction matching madness is
stopped for these transactions.

Whether it does it for future transaction matching...we'll have to see when
some checks clear the bank.

"ScottK" wrote:

- quote -

I've been using Money 2005 Home and Business for a month or so now getting
everything manually migrated from 7 years of Quickbooks. I've gotten
everything connected online with my bank and most everything seems to be
working ok. However, every time I download from my bank (Washington Mutual)
the same sets of transactions show in the "Transaction to read: X". I
accept the transactions, matched to an earlier entry, the register shows
fine and the next time I start M2K5 and try to do a download they show up
again as needing to be read. What gives? Is this a feature?

Thanks
ScottK