transactions not registering in portfolio view (Q Mac)
Reinvestment transaction from 12/28/2017 onward are posting as Transactions but do NOT show in Portfolio view as additions to total share count and don't show as line items under the security in Portfolio view.
Quicken Deluxe 2019 Version 5.9.2 (Build 59.25153.100) on macOS 10.13.6
Quicken Deluxe 2019 Version 5.9.2 (Build 59.25153.100) on macOS 10.13.6
0
This discussion has been closed.

Comments
https://getsatisfaction.com/quickencommunity/topics/faq-what-are-placeholder-transactions-in-quicken...
If you go to the portfolio value view and Group By Security, then click the triangle next to the security, it will show all the share-changing transactions for the security. Which of the following are you seeing when you do this:
1) The reinvest div transaction is missing from this view, or
2) The reinvest div transaction is there, but the total shares for the security are wrong.
If it's the latter, I suspect a placeholder is "adjusting" the share total.
I had a Remove Shares entry from 2004 for .026 shares of the affected security with a remark to “add cost” in the Description/Category column.
I deleted that entry and now the transactions from Dec 2018 and Jan 2019 for this security are properly reflected in the Portfolio view and continue to be properly displayed in Transaction view.
Thank you...
I have a brokerage account where recent downloaded reinvestment and buy/sell transactions appear in the register but are not reflected at all in the portfolio view. In the past, I found I could edit the lots on a sale, but not only would that not help the other transactions, it isn't working this time.
The bottom line is that NO downloaded transactions are reflected in the portfolio of at least two of my accounts at all, even though they appear in the register. I can fix Sell transactions (I misspoke above) by using the Specify Lots work around, but none of the others.
Meanwhile, just to cover the bases, have you checked each of your accounts to make sure there is no placeholder transaction (typically at the beginning of the account)? Placeholder transactions are the most frequent cause of transactions that are visible but having mo impact on an account balance.
FAQ: What Are Placeholder Transactions in Quicken for Mac?
Thank you for taking the time to report this issue, although I'm sorry to hear of the negative experience you had with one of our Support Agents.
I would like to look into this matter a little further, but unfortunately was not able to locate the case details for the chat. Please send me a PM with the chat transcript PDF or if you happen to have it, the case number from Support.
Thank you,
Sarah
You didn't respond to the part about your interaction with Quicken Support. If what you wrote above truly occurred, I strongly encourage you to respond to Quicken Sarah with the transcript you said you have of your interaction so she can check it out and make sure the support agent who gave you incredibly bad, wrong instructions gets some remedial education. Please help this from happening to some other Quicken user in the future. Thanks.
I have have sent a message to Quicken Sarah, so she may get back to me to confirm.
I mentioned this to Quicken Saah, and I hope the Quicken Web team will see if there could be a better way to print and print/save support chats to PDF in Safari on a Mac.
In the meantime, other folks might find this procedure helpful.
First - STOP pointing EVERY discussion towards these placeholder transactions. The bug is not about them.
I have NO placeholder transactions. I don't even download online transactions, as Quicken refuse to recognize that brokers and exchanges exist outside the US and Canada. I download a qfx file from Interactive Brokers and import it. On a given day I have 3 transactions on LSEX - for CSPX, IWDA, and TIP5. The one for TIP5 is reflected in the portfolio, the other two are not. Therefore the portfolio is off.
If I delete the imported (and not visible in the portfolio) transaction from the list and recreate it manually, the portfolio gets even more messed up - some of the existing transactions disappear and the portfolio gets even worse.
Now - get this. If I create and delete a manual (duplicate of the downloaded) transaction and leave the imported one (which was missing from the portfolio) - voila! - the transactions magically get correct in the portfolio for that security.
Therefore - the portfolio view has bugs, being generated from the transaction list.(Rant Redacted)
- Where to find a Help Guide for Quicken for Mac?
- Quicken Mac FAQ list
- Quicken Windows FAQ list
- Help Guide and FAQs for Quicken Mobile
COMPLETE list of Product Ideas - Quicken for Mac to VOTE onObject to Quicken's business model, using up 25% of your screen? Add your vote here:
Quicken should eliminate the LARGE Ad space when a subscription expires
(Canadian Q user since '92, STILL using QM2007)
BKG
So herein lies the problem: if Quicken Support doesn't document a problem and pass it upstream to the developers, it's likely it's just not on anyone's radar. We don't know that for sure; it's certainly possible there is a bug they're aware of and haven't fixed yet -- but the odds are otherwise.
If a user can figure out what circumstances cause this to happen, ideally simplifying it down to someone one could do creating a blank new files and entering a couple transactions -- then it can be reported as a bug (via Report a Problem), a Quicken team member would reproduce the steps and verify the problem, and it woulds be coded into their bug tracking system for investigation and repair. Alternatively, you could use Report a Problem and upload a sanitized version of your data file, and point out specific transactions not reflected in the portfolio, or how to reliably make this occur, and that could also be enough to get them to verify and document the issue as a bug.
Should it be the job of us end-users to troubleshoot and diagnose issues like this? No, of course not. But unfortunately, there's really no other way to get the developers to look into it. I'd guess that 95+% of the posts on this forum which complain "there's a bug!" turn out not to be bugs, and that's why Quicken doesn't have their developers spending considerable time sifting through all the posts on this forum... and that's why your report here is likely not to gain traction unless we can find a way to inject it into the developers' bug database. I know it's frustrating, and I don't know if you have the time or inclination to try to pursue it further. If so, what I'd suggest is creating a new test file, create one account and one or two securities, and try to see if you can replicate the problem in such a simple setting; if you can, post what you did here and let someone else verify that you're found a reproducible bug -- and then there's ammo for reporting it to Quicken.
And note that at 10:11 AM today (May 13) jschaffe just commented that he also has called Quicken Support to report the same problem. It's not just me.........
Please advise............
BKG
A video screen capture can be helpful, but from things I've seen, what they value most is step-by-step instructions how to replicate a bug. (A couple times I sent videos as a beta tester and was told they couldn't open the file, which was annoying.) Here's the trick with bug reporting: once you can make the bug appear, keep trying again with a new file to cut it to the simplest sequence you can that shows the bug.
(As for jschaffe, it could be the same thing or it could be something different, since he's downloading transactions and you're entering them manually. Your approach is, fortunately, easier to write directions to reproduce if you can find what causes it; it's often hard for people who are downloading transactions to come up with reproducible methods for developers to test.)