Accepting downloaded transactions

I have several hundred credit card transactions that have been downloaded into Quicken.

I am in the process of accepting them and would like to have the ones that I have already accepted move to the register.

This way, I am only looking at the transactions I have not yet accepted.

It seems that the only option is to accept them all or look and each and every one until I have accepted 100% of them.

Any suggestions will be appreciated.

Reply to
serickson32
Loading thread data ...

I think you are out of luck. Quicken was never meant to handle hundreds of downloaded transactions, so doesn't have an option to filter the download file.

Your only option is to continue on, or accept them all, then fix the transactions in the register.

Reply to
Fred Smith

And it is made worse by the fact that the viewing window is limited to

6 viewable lines.

It seems to me that in earlier versions, when I told the program that I wanted to finish later, it was smart enough to figure out that it was unnecessary to continue to show accepted transactions and did not show them the next time I went there.

Ugh.

Reply to
serickson32

I accept all of em and then review the register. It tends to do a good job if in any even if there are already matching transations.

Reply to
Todd H.

Just to clarify: the ones you have accepted have "move[d] to the register"; that is, they are in your register. But they still remain in the Accept transactions into register" window, marked "Accepted". Speaking for Q2001, Q2002, Q2004 and Q2005, I believe Quicken has always worked that way.

It's not clear to me that your desire would be an unalloyed benefit; we would lose the ability to easily review what transactions had been accepted in the current download

I find that only transactions with a status of "Match" require detailed scrutiny as I must be sure, not only that they should match any transaction, but that they match the correct transaction ... so I handle each "match" individually (*selecting* it to see which existing transaction it matches). The remaining "New" transactions can usually be quickly visually scanned just to verify that they should be new (and I can't remember one that was incorrectly so designated); once I finish the visual scan, I do an Accept All for the "New" transactions.

Reply to
John Pollard

I cannot imagine accepting all. Recently returned from brief trip -- had

2 $45 cc bills. Qkn 05p wanted to match them w/a $45 expense from July 2004. Spouse & I also have direct deposit income w/deductions. To maintain budget they are scheduled as income on the first of each month; however, if the 1st falls on a weekend the deposit is made the last business day of the prior month. Qkn treats these dl deposits as new. If I were to accept these, I would lose all the splits (it's happened) -- they must be matched manually. Until you actually click on each dl'ed transaction, you have no idea if qkn will treat it as you want it to be treated. Just another opinion. dj
Reply to
djebens

As I said, the downloaded matches should be verified individually. But, my visual scan of "new" transactions takes care of any transactions that might be unmatched; but that virtually never happens since I also endeavor to make sure that scheduled transactions are in the register before their real-world counter parts could be downloaded, if necessary by having Quicken enter them 2 days or so before their actual due date. The budget thing makes no sense to me; a budget is a guide not a rule, I can not imagine fudging real world transactions to make it appear that I am staying within those guidelines (and it is only an "appearance"). I have never had to click on "new" transactions to know if they should be a match or new (and selecting them will not help you with that decision anyway, it doesn't tell you anything about them that you do not already know): I know which transactions will be downloaded and, in any given download, which, if any, should match and which should be new.

And, if worse came to worse, and you accepted a downloaded transaction as new, then noticed that there was a scheduled transaction that it should have matched (you could not miss this if you were reconciling ... as you could miss mis-matched "matches"), it is a trivial matter to delete the downloaded transaction. (And it's even trivial to capture the downloaded flag and the date posted before deleting it).

Reply to
John Pollard

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.