Quicken Discussion: My Quicken updated to R45.13, and now when my transactions download with automatic entry turned off (2023 Update)

It sounds like you are experiencing an issue with Quicken where the downloaded transactions are not showing up in the downloaded transactions list after updating to R45.13. You have also confirmed that this is not limited to R45.13 but also happening in R43.26 for all financial institutions that have dropped Direct Connect downloads such as BofA, Chase, Discover and Schwab.

The solution you have found is to turn on automatic entry and then do a validate and repair the file every time. However, you have also found that it is not necessary to do a validate to get the transactions entered in their respective registers/transaction lists.

One potential solution is to turn on the appropriate "Automatically add to banking registers" and/or "Automatically add to investment transaction lists" (found at Edit > Preferences > Downloaded transactions). This should cause the downloaded transactions to appear in their designated registers/transaction lists. Once the downloaded transactions have been successfully added, turning off the "Automatically add ..." preferences causes the "Downloaded Transactions" and "Bill and Income Reminders" tabs to become visible again

I just read your response; it seems to me you have merely repeated the workaround I already suggested. [I am not the originator of the Community Discussion - I just provided a workaround in the Quicken Newsgroup, in case anyone there was having the problem]

If I missed something from your post, perhaps you can enlighten me. I

I am not the one who reported the problem originally; I'm the one who was offering a workaround for the problem originally reported in the Quicken Community (not in this newsgroup).

That is the "solution" posted by the originator of the discussion in the Quicken Community - it was not me who made that statement, I just quoted the originator.

Yes I was the originator of that idea - here in the Quicken newsgroup, not in the Quicken Community where this discussion originated.

Your previous two sentences are in direct conflict with one another: because the first notion in the first sentence was posted by someone else, while the notion in the second sentence was posted by me. My offering pointed out that the original poster did not need to Validate.

That is the workaround that I posted; just curious why you felt the need to repeat it. I think your "potential solution" is duplicative of mine - but framed in a series of comments that are more confusing than helpful.

Am I missing something?

This is the post I referred to earlier in this discussion where I said my attempt to post at BeanSmart was rejected due to some server error. Apparently, that "server error" was just a built-in delay at the BeanSmart web site, to allow time for my post to be "approved". My post was eventually "approved" and posted there, then copied here.

It seems there is a circular process involved; where what is posted in this newsgroup is automatically posted at BeanSmart, and what is posted at BeanSmart is automatically posted here.

This problem seems to have been fixed in release R46.12.

"Broken link to

The original link is not broken; whatever software copied that link to BeanSmart truncated the link.

Here's a tinyurl link to the original Quicken Community discussion:

Thank you John! Yeah, that makes more sense now