In microsoft.public.uk.money, martin_pentreath[at]hotmail.com wrote:

- quote -

You would want to match the downloaded transaction to the transfer
before accepting the transaction. You may be saying that is not an
option.

Try Voiding (right-click) the "rogue transactions" rather than
deleting.

Hi all,

I have an annoying recurring problem. I bank with Nationwide. I have a
current account and several deposit accounts ("E-savings"). I've set
up monthly standing orders so that fixed amounts get transferred from
the current account to the various deposit accounts after payday. I've
replicated this within Money by entering the transcations within the
"bills" section as monthly "transfers".

When I synchronise Money with my bank immediately after these payments
it links the standing orders with the transfers in my register.
However, periodically afterwards, whenever I synchronise it wants to
add a separate deposit (not transfer) into one or other of the deposit
accounts duplicating the original transfer and throwing the balance
out. This is currently happening much more with one of the deposit
accounts than th others for some reason. If I delete these rogue
deposits then sometimes (but not always) Money will just regenerate
them next time I synchonise. It doesn't attempt to put a matching
withdrawal into the current account. The original correct transfer
transactions all have an "E" in the column headed "C" in the register.

The only work-around I have at the moment is to keep a careful watch
out for these rogue transactions and delete them when I see them,
although Money is being pretty insistent and putting them back when I
synchronise.

Any solutions?

Cheers!

Martin