nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Incorrect Share Balances For TD Ameritrade and Fidelity (R45.7 Day 1)

FrankZ

For TD Ameritrade: Downloaded some investment transactions, and the "number of shares" field was not populated. All other fields were accurate.

For Fidelity: Quicken told me that my share balance didn't match my account on a holding when it did in fact match.

Also noticed that "Day Gain/ Loss" and "Day Gain / Loss %" did not populate as they always had when downloading end-of-day quotes.

Find more posts tagged with

Comments

Frankx

Hi @FrankZ

Sorry to see that you haven't gotten a reply to your post of the other day.

Are you still seeing the problems you have described? I just saw another post that had similar issues with TDA downloads. Are you still seeing those issues?

Frankx

FrankZ

Thank you for asking.

Yes, when I downloaded trades from Friday on Saturday morning, the number of shares field was blank and had to be manually entered.

These are options contracts if that helps troubleshoot (shares are usually reported "100" per contract traded). I haven't traded common shares in that account to see if the issue extends to common shares.

Frankx

Hi @FrankZ

I know that some folks have reported problems regarding downloads of option transactions from time to time. But I haven't seen anything recently involving TDA. If the behavior has changed recently for this account, you could try deactivating and then reactivating the account in Quicken (but before you do that - make sure you have a good recent backup file, just in case.

Frankx

FrankZ

Thank you @Frankx. I appreciate the time you took to look at this.

I've gone ahead and rolled back to R44.28 using the instructions I found here.

https://www.quicken.com/support/reinstalling-and-patching-your-quicken-subscription-version-after-your-membership-has -

This has corrected the problem. I'll try updating again if the next update mentions that this has been addressed.