In microsoft.public.money, Bart wrote:

- quote -

The way to deal with this is to change the transaction into a
transfer when you process the first account. Then when you process
the other end of the transfer, it will already be in the register.
Money should match to the existing transfer. If it does not, click
Change during the processing to select to match to that transfer.

When you are catching up with this, you will need to void/delete the
duplicates initially. Thereafter you should be able to keep up as
you go.

- quote -

Not sure how to sum this up. But:
I have checking account A and B at the same bank.
I download all the transactions.
MS money balances and bank balances match.
My transactions include transfers from A to B.
When I reconcile my downloaded transactions, and categorise the transfers as
actual transfers, Money will add a transaction on the other side. I.e. if
the original transaction was $100 from A to B, when I mark that as a
"transfer" when I'm reconciling A account, Money will behind the scenes go to
B and enter another $100 incoming. Since acctount B already synced, it
already has a transaction reflecting this transfer. So, now B has a double
transfer deposit, and the balance is trown off.

I transfer money between accounts often, so this is a total hassle. If I
don't categorize them as transfers, Money willl typically mistategorise them
as income, which is also a hassle.

Anyone else have this problem? I imagine many people would run into this.
Unless, I missed something in the tutorial.

Thanks,
-Bart