I've researched this topic in this group and this topic seems to come
up frequently. Most solutions talk about matching the wrong
transaction. My problem is subtly different. When I click "change" on
the suspect transaction, MS claims that this transaction is unmatched.
The funny thing is, the payee listed in the register ("Billy") is
different than the payee shown on the "change" screen (the screen you
go to when you select "change.") On the "change" screen, MS claims
that this transaction (payee is "Bob") is not matched!! I then click
cancel and the payee on the register is back to "Billy" Why is MS
changing the payee on a transaction that is unmatched? Please advise.
Thanks,
Dave

Can't "change" downloaded transaction match by fulltimeshopper

fulltimeshopper
Wed Oct 06 23:40:06 CDT 2004

I am having a similar problem. When I enter a payment
recieved for an invoice, the downloaded entry will not
match up with the transaction in my "register". When I
click change, that particular entry is not even visible
to choose from. Right now I am manually deleting the
downloaded transaction. Any idea how to fix this?

>-----Original Message-----
>I've researched this topic in this group and this topic
seems to come
>up frequently. Most solutions talk about matching the
wrong
>transaction. My problem is subtly different. When I
click "change" on
>the suspect transaction, MS claims that this transaction
is unmatched.
>The funny thing is, the payee listed in the register
("Billy") is
>different than the payee shown on the "change" screen
(the screen you
>go to when you select "change.") On the "change"
screen, MS claims
>that this transaction (payee is "Bob") is not matched!!
I then click
>cancel and the payee on the register is back
to "Billy" Why is MS
>changing the payee on a transaction that is unmatched?
Please advise.
>Thanks,
>Dave
>
>.
>

Re: Wrong Payee on downloaded statement by Scott

Scott
Fri Oct 08 17:14:55 CDT 2004

When I had the same problem, I figured out that the matching "logic" was
wrong. It defaults to match the same amount--and overwrites the info from
the download...

So, if you have a record for $25.50 made payable to al's gas Station, any
download for $25.50 may "correct" itself to show payee as al's.

solution - change the date range for matched to something reasonable ~1-3
days. That way, any manual entry you might have for Als will match with the
same day transaction but not one 2 months ago for another payee.

God luck...
"Cool G." <dave.boylan@gmail.com> wrote in message
news:1097064551.000533.238440@k26g2000oda.googlegroups.com...
> I've researched this topic in this group and this topic seems to come
> up frequently. Most solutions talk about matching the wrong
> transaction. My problem is subtly different. When I click "change" on
> the suspect transaction, MS claims that this transaction is unmatched.
> The funny thing is, the payee listed in the register ("Billy") is
> different than the payee shown on the "change" screen (the screen you
> go to when you select "change.") On the "change" screen, MS claims
> that this transaction (payee is "Bob") is not matched!! I then click
> cancel and the payee on the register is back to "Billy" Why is MS
> changing the payee on a transaction that is unmatched? Please advise.
> Thanks,
> Dave
>



Re: Wrong Payee on downloaded statement by Chris

Chris
Fri Oct 08 20:53:51 CDT 2004

Easier yet, click the change button, then whatever click is required to tell
Money it's not a match and to create a new transaction. At that point the
original downloaded description reappears. You could also link it to a
different existing transaction if you wanted to.
--
Chris Cowles,
Gainesville, FL

"Scott" <mcgratscspam-x@comcast.net> wrote in message
news:zjE9d.206002$MQ5.181347@attbi_s52...
> When I had the same problem, I figured out that the matching "logic" was
> wrong. It defaults to match the same amount--and overwrites the info from
> the download...
>
> So, if you have a record for $25.50 made payable to al's gas Station, any
> download for $25.50 may "correct" itself to show payee as al's.
>
> solution - change the date range for matched to something reasonable ~1-3
> days. That way, any manual entry you might have for Als will match with
> the same day transaction but not one 2 months ago for another payee.