Hello. After using quicken for a couple of years without any major issues, using 2010R5, beginning to have some manually matching problems. It doesn't happen often, but sometimes a downloaded item will be marked as new and I have to manually match it. What is happening to me now is the matching item in the register is not showing in the window you scroll through to select the entry to match to. It's not marked as clear, so shouldn't it appear? I have to accept the new item and then manually clear the original entry and delete the entry I accepted.
Additionally, not sure if it's new or if I am just noticing it now, there are items on the list that I can match to that are already cleared and reconciled. Why would those entries be on the list to match to? Appreciate any thoughts, thanks.
I had hoped this problem would be fixed in 2010, as I'm still using 2009 and having the same problem. In fact, one of my checking accounts is no longer reconciling for that same reason. I saw a fix somewhere that said you have to unreconcile all the entries in the register and go back and do them all over. I'll get rid of Quicken before I do that with thousands of entries.
I'll be looking forward to what the answer to this issue is.
Me too. I usually accept the new tranaction and delete the original when there is a dupe. Frequently on bills the bank has paid the category is changed - like from utilities... to housing. I change it to what it should be. I too do not want to go back and reconcile thousands of tranactions! Hopefully there's a better fix.
We went through this a little while back, it's a new behavior that began with Q2009 although people here will insist it's always been that way. I'm glad someone else has noticed it's a new behavior but I'm not glad to report there seems to be no fix for the problem.
My resolution is to accept the duplicates and then delete them when reconciling, they're easy to spot then and it's easy to delete them. Since there aren't very many (so far!) it's not too difficult to do it that way.
The "match" process could care less whether a transaction has been reconciled (so I don't see how unreconciling transactions could have any beneficial effect).
The "match" process is interested in determining whether an existing register transaction, that has NEVER been downloaded, matches a transaction currently waiting to be "Accepted". [And actually, the "manual match" process allows the user to match a single downloaded transaction to multiple existing register transaction. So things like payee name and amount are not critical to the manual match process.]
Any existing register transaction that has never been downloaded is a potential candidate to be matched (usually oldest first). No transaction that has already been downloaded should be a candidate to be matched.
Quicken marks "Accepted" transactions as having been downloaded, so it won't allow them to be "matched" to future downloaded transactions.
To see whether an existing register transaction has already been downloaded, right-click the transaction, then hold CTRL while left-clicking "Copy transaction(s)". If the "Downloaded" box is checked, and the "Posting date" is a valid, non-space, date; the transaction has been downloaded.
If you want the "downloaded status" changed, you can can change it in that same dialog.
The situation being discussed in this thread sounds like it could have one of two causes: the financial institution has re-used a "Financial Institution Transaction ID" (FITID), which should never happen (but has); or the stored Quicken FITID's are being lost, or corrupted, making the downloaded FITID appear to be "new".
Normally, if a transaction with the exact same FITID as a transaction that has ever been downloaded before (even if it was not Accepted, but Deleted), appears in the OFX data being downloaded, Quicken will never present that transaction to the user. Quicken compares the FITID's in the downloaded OFX data, to the FITID's it saves for every downloaded transaction it has ever seen; and excludes downloaded transactions with FITID's that have been downloaded to that account before. This is what (normally) allows you to tell Quicken to import the same QFX file multiple times, but only see its transactions during its first import (even if you delete all the QFX file transactions during the first import).
Thanks John and all. In the morning when I have new downloads, I figure all the ones not marked properly and mark them as instructed through the register. The main issue with not having them on the list to match is frustrating and hopefully it'll resolve itself. It's not common I have to manually match and still don't understand why something I put in the register would not show up, doesn't seem like the bank would have gotten to it top impact it yet.
I was able to clean up all the entries in the match to window for manually matching items. Thank very much for showing us the tip to correct. Everything matched automatically this morning, so we'll see going forward. Thanks again.
My experience with this quirk is that QD2010 is much better than QD2008. I've always had issues with some d/l transactions that had no match in the manual window. Q2010 seems to have corrected this for me.
But now that I think about it, what may be the kicker in this is that I can't remember if the problems I saw were where I: d/l a transaction, tried to manually match it, found I had forgotten to enter it, minimized the clearing window, entered the transaction, then tried to match again with no luck.
Sorry, this is no help at all. Bottom line for me, I've seen this problem, but am not sure but what I may have been the cause of it. I just know my impression of QD2010 is much better in this area than QD2008
XS11E wrote in news:Xns9D1C62AA56357xs11eyahoocom@
You can do as you suggest, but before you try matching, close the account and then reopen it. You will be able to match. Some sort of cache is not being refreshed until you do that.
-----Original Message----- From: speedlever [mailto: snipped-for-privacy@NOSPAMyahoo.com] Posted At: Saturday, February 13, 2010 5:50 AM Posted To: alt.comp.software.financial.quicken Conversation: Manually Matching Errors Subject: Re: Manually Matching Errors
My experience with this quirk is that QD2010 is much better than QD2008.
I've always had issues with some d/l transactions that had no match in the manual window. Q2010 seems to have corrected this for me.
But now that I think about it, what may be the kicker in this is that I can't remember if the problems I saw were where I: d/l a transaction, tried to manually match it, found I had forgotten to enter it, minimized the clearing window, entered the transaction, then tried to match again with no luck.
Sorry, this is no help at all. Bottom line for me, I've seen this problem, but am not sure but what I may have been the cause of it. I just know my
impression of QD2010 is much better in this area than QD2008
XS11E wrote in news:Xns9D1C62AA56357xs11eyahoocom@
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.