Downloaded transactions matching wrong entry in register

[HomerJ]

Every two weeks my scheduled 'paycheck' gets entered into quicken as
defined. Then the next day, the deposited transactions get downloaded
from my bank(s). However, Quicken tried to match the deposit to the
PREVIOUS paycheck deposit (even though it is already reconsiled).

I do edit->unmatch, and then it automatically matches the correct
transaction. How can I get it to match the first time without having
to tell it to unmatch the previous entry?

Chris

[HomerJ]

Oh, I'm running Quicken 2005 R2 on XP. I have had the same problem on
Q2004. The files super validate just fine and it has even happened on
brand new files.

garbage123@softhome.net wrote: Oh, I'm running Quicken 2005 R2 on XP. I have had the same problem on Q2004. The files super validate just fine and
it has even happened on brand new files.

I am trying to picture this: it might be a good avenue of
investigation, but I can't quite see how a brand new file could
have any transactions in it to match.

Can you tell me how you setup the new file to test with, what
transactions you entered, by what means, and when the
download/wrong-match came into play?

Also, is your paycheck for the same amount every paycheck? And
was your paycheck setup in the Paycheck Wizard?

--
John Pollard
First Last at Bellsouth dot net
Please reply to newsgroup

[Andrew DeFaria]

John Pollard wrote:
garbage123@softhome.net wrote: Oh, I'm running Quicken 2005 R2 on XP. I have had the same problem on Q2004. The files super validate just fine and it has even happened on brand new files. I am trying to picture this: it might be a good avenue of investigation, but I can't quite see how a brand new file could have any transactions in it to match. Can you tell me how you setup the new file to test with, what transactions you entered, by what means, and when the download/wrong-match came into play? Also, is your paycheck for the same amount every paycheck? And was your paycheck setup in the Paycheck Wizard?

Well back in the good old days you could right click on the transaction
entry and select properties and you'd be able to set the Downloaded
transaction toggle and the date. But properties are not available on the
special transaction called Paycheck. I wonder why they did that?
Normally when something like this happens I check the toggle and date
and see that they are not set so I set them.
--
Learn from your parents' mistakes - use birth control!

[David Steigerwald]

garbage123@softhome.net wrote: Every two weeks my scheduled 'paycheck' gets entered into quicken as defined. Then the next day, the deposited transactions get downloaded from my bank(s). However, Quicken tried to match the deposit to the PREVIOUS paycheck deposit (even though it is already reconsiled). I do edit->unmatch, and then it automatically matches the correct transaction. How can I get it to match the first time without having to tell it to unmatch the previous entry? Chris
I have this problem all the time, on all sorts of transactions that
repeat every month. Maybe nobody else has repetitive transactions? It
is making me crazy - this never happened with Q99!

Andrew DeFaria wrote:
John Pollard wrote:
garbage123@softhome.net wrote: Oh, I'm running Quicken 2005 R2 on XP. I have had the same problem on Q2004. The files super validate just fine and it has even happened on brand new files.
I am trying to picture this: it might be a good avenue of investigation, but I can't quite see how a brand new file could have any transactions in it to match. Can you tell me how you setup the new file to test with, what transactions you entered, by what means, and when the download/wrong-match came into play? Also, is your paycheck for the same amount every paycheck? And was your paycheck setup in the Paycheck Wizard?
Well back in the good old days you could right click on the transaction entry and select properties and you'd be able to set the Downloaded transaction toggle and the date. But properties are not available on the special transaction called Paycheck. I wonder why they did that? Normally when something like this happens I check the toggle and date and see that they are not set so I set them.

If I am understanding you correctly, you can still do that, you
just don't use "properties", and I was heading in that
direction. But I can not square that solution with the problem
.... at least not yet.

I have tested doing what I believe is precisely what the op is
doing, and I do not have the problem.

The method for setting the downloaded flag and the posting date
have changed, but you can still do it, even on paycheck
transactions [right-click the transaction, hold down CTRL and
left-click Copy Transaction]. And since Intuit says that
previously matched transactions will not be eligible to be
matched again, that might sound like the route to go. But the
problem is, that if the op is manually matching to the correct
transaction each time, then Quicken should not be finding a
previous paycheck transaction available for matching, presumably
the only unmatched paycheck transaction should be the most
current one. That was why I wanted a better explanation of what
was actually happening.

--
John Pollard
First Last at Bellsouth dot net
Please reply to newsgroup

[Homer J Simpson (Chris A)]

>>>I am trying to picture this: it might be a good avenue ofinvestigation, but I can't quite see how a brand new filecould have any transactions in it to match.


When you create a new file, Q downloads the previous 30-90 days worth of
transactions (1 year in case of Discover). Those downloaded
transactions are already cleared of course. The problem then acts up
after the next two paychecks have been entered. True, it would then not
be considered a 'new' file, but it's more 'new' than than my other file
that has years worth of data.

With the new file I do make a change that I'm sure is affecting the
matching, but with the old file I don't.

It's described in more detail here (#3)
http://groups-beta.google.com/group/alt.comp.software.financial.quicken/browse_frm/thread/2fd498f289eb1809/568ed2551ee0cf1b?q=garbage123&_done=%2Fgroups%3Fq%3Dgarbage123%26start%3D0%26scoring%3Dd%26&_doneTitle=Back+to+Search&&d#568ed2551ee0cf1b

The gist of it is, I have to delete one of the deposits in one bank
account to accomadate a split transaction in another account that has a
later ending statement date. Here is a shortened version:

Bank 1 closing date 10/31. Transactions are downloaded up through 11-31
(when I created the file).
Bank 2 is manual and the closing date is 11/18.

My paycheck (created with the wizadr) occured on the 11/19. It goes
into Bank 2 with a split that goes into Bank 1. So I enter the paycheck
into Bank 2. At this point Bank 1 has the downloaed transaction for the
deposit AND the split deposit for the same deposit (from entering it
into Bank2). Ok. So now I go into Bank 1 and delete the downloaded one
and marke it 'R'.

Now, the next paycheck comes 12/3. In enter in the Paycheck that goes
to Bank 2 and a split into Bank 1. Then Q downloads the deposit
transaction for Bank 1 and matches it to 11/19.

I assume it was because the downloaded 111/19 was deleted and replaced
by the split 11/19. I have to select 'unmatch' and then it will match 12/3.

This occured with my other data file (of many years). Don't know how,
and for some reason it went away, and then it came back.

Also, is your paycheck for the same amount every paycheck?And was your paycheck setup in the Paycheck Wizard?

Yes and yes
Well back in the good old days you could right click on thetransaction entry and select properties and you'd be able toset the Downloaded transaction toggle and the date. Butproperties are not available on the special transaction calledPaycheck. I wonder why they did that? Normally when somethinglike this happens I check the toggle and date and see thattheyare not set so I set them. If I am understanding you correctly, you can still do that, you just don't use "properties", and I was heading in that direction. But I can not square that solution with the problem ... at least not yet. I have tested doing what I believe is precisely what the op is doing, and I do not have the problem. The method for setting the downloaded flag and the posting date have changed, but you can still do it, even on paycheck

How? I think that is what I need to do with the original dl'ed
transaction that I have to replace.
transactions [right-click the transaction, hold down CTRL and left-click Copy Transaction]. And since Intuit says that

Oh-- guess I should have read before I typed above. I'll try this.
previously matched transactions will not be eligible to be matched again, that might sound like the route to go. But the problem is, that if the op is manually matching to the correct transaction each time, then Quicken should not be finding a previous paycheck transaction available for matching, presumably the only unmatched paycheck transaction should be the most current one. That was why I wanted a better explanation of what was actually happening.

I am not manually matching it. I am manually 'unmatching' the wrong
transaction and then Q auto matches to the next (right) one.

[Homer J Simpson (Chris A)]

> transactions [right-click the transaction, hold down CTRL and left-click Copy Transaction]. And since Intuit says that Oh-- guess I should have read before I typed above. I'll try this.

Worked like a charm! Thanks!

Homer J Simpson (Chris A) wrote: > I am trying to picture this: it might be a good avenue > of > investigation, but I can't quite see how a brand new > file > could have any transactions in it to match. When you create a new file, Q downloads the previous 30-90 days worth of transactions (1 year in case of Discover). Those downloaded transactions are already cleared of course. The problem then acts up after the next two paychecks have been entered. True, it would then not be considered a 'new' file, but it's more 'new' than than my other file that has years worth of data. With the new file I do make a change that I'm sure is affecting the matching, but with the old file I don't. It's described in more detail here (#3) http://groups-beta.google.com/group/alt.comp.software.financial.quicken/browse_frm/thread/2fd498f289eb1809/568ed2551ee0cf1b?q=garbage123&_done=%2Fgroups%3Fq%3Dgarbage123%26start%3D0%26scoring%3Dd%26&_doneTitle=Back+to+Search&&d#568ed2551ee0cf1b
The gist of it is, I have to delete one of the deposits in one bank account to accomadate a split transaction in another account that has a later ending statement date. Here is a shortened version: Bank 1 closing date 10/31. Transactions are downloaded up through 11-31 (when I created the file). Bank 2 is manual and the closing date is 11/18. My paycheck (created with the wizadr) occured on the 11/19. It goes into Bank 2 with a split that goes into Bank 1. So I enter the paycheck into Bank 2. At this point Bank 1 has the downloaed transaction for the deposit AND the split deposit for the same deposit (from entering it into Bank2). Ok. So now I go into Bank 1 and delete the downloaded one and marke it 'R'.


This seems like a timing issue to me and one that Quicken could
never handle automatically; though I believe that you can
control the timing in such a way the the problem disappears.

I don't see how the actual depost in Bank 1 from your paycheck
can occur until the paycheck has been issued. If you have
Quicken enter the paycheck in the Bank 2 register on the date of
the paycheck, the Quicken transfer from the Bank 2 paycheck
transaction to the Bank 1 account should be in the Quicken Bank
1 account when you download the real-world transaction from Bank
1. If the deposit is already in the Quicken Bank 1 account, the
downloaded transaction should match it.

In other words, have Quicken enter the paycheck in your Bank 2
register before you accept the downloaded transactions
(containing the transfer deposit from Bank 2) from Bank 1; that
is, on or before the paycheck is issued.

And if you are able, get your employer to do "direct deposit"
for your paycheck; you will have the money sooner, with less
hassle, and the time between the deposits in the two bank
accounts will shrink to nearly negligible.
Now, the next paycheck comes 12/3. In enter in the Paycheck that goes to Bank 2 and a split into Bank 1. Then Q downloads the deposit transaction for Bank 1 and matches it to 11/19. I assume it was because the downloaded 11/19 was deleted and replaced by the split 11/19. I have to select 'unmatch' and then it will match 12/3.

Yes, I think that is what happens.
This occured with my other data file (of many years). Don't know how, and for some reason it went away, and then it came back.
> Also, is your paycheck for the same amount every > paycheck? > And was your paycheck setup in the Paycheck Wizard?
Yes and yes

So, if you get paid at regular intervals, you can have Quicken
"automatically" enter your paycheck transaction in the Bank 2
register on or before you download the Bank 1 paycheck transfer
deposit ... then the downloaded deposit should match the correct
transaction.
Well back in the good old days you could right click on the transaction entry and select properties and you'd be able to set the Downloaded transaction toggle and the date. But properties are not available on the special transaction called Paycheck. I wonder why they did that? Normally when something like this happens I check the toggle and date and see that they are not set so I set them.
If I am understanding you correctly, you can still do that, you just don't use "properties", and I was heading in that direction. But I can not square that solution with the problem ... at least not yet. I have tested doing what I believe is precisely what the op is doing, and I do not have the problem. The method for setting the downloaded flag and the posting date have changed, but you can still do it, even on paycheck
How? I think that is what I need to do with the original dl'ed transaction that I have to replace.
transactions [right-click the transaction, hold down CTRL and left-click Copy Transaction]. And since Intuit says that
Oh-- guess I should have read before I typed above. I'll try this.
previously matched transactions will not be eligible to be matched again, that might sound like the route to go. But the problem is, that if the op is manually matching to the correct transaction each time, then Quicken should not be finding a previous paycheck transaction available for matching, presumably the only unmatched paycheck transaction should be the most current one. That was why I wanted a better explanation of what was actually happening.
I am not manually matching it. I am manually 'unmatching' the wrong transaction and then Q auto matches to the next (right) one.

It is a good thing that you posted all the details; from your
original post it was not at all clear that your problem was in a
different account from the one your paycheck was deposited in
and only had to do with a transfer generated from your paycheck
rather than the paycheck itself.

--
John Pollard
First Last at Bellsouth dot net
Please reply to newsgroup