Quicken Community is moving to Single Sign On! Starting 1/22/21, you'll sign in to the community with your Quicken ID. For more information: http://bit.ly/CommunitySSO
The "Year-To-Date Return" function for "Investing" is not working properly for individual stocks

The "Year-To-Date" return function / calculation for use in measuring year to date investment returns is not working properly for individual stocks. For example, the stock MET closed 2020 at $46.95 and closed yesterday at $50.33. The year-to-date return using the actual data should be 7.199%. The year-to-date return shown in the quicken "year-to-date" function is (22.3857%) for that same stock. I have another individual stock which is showing a similar problem. The year-to-date quicken calculation for mutual funds appears to be working properly, so the issue seems specific to individual common stocks. Please investigate. Thanks.
0
Best Answer
-
Quicken Sarah Administrator, Moderator mod
Hello All,
We've received confirmation from our service partners that a fix has been deployed and this behavior should no longer occur.
If, however, you continue to experience an issue, please create a new post to let us know.
Thank you again,
Sarah0
Answers
I agree. The Return (%) YTD and other performance data presently being provided by the third-party provider for securities other than mutual funds appears to be incorrect.
Premier on Windows 10
It shouldn't be a surprise that Quicken relies on users to report these kinds of data issues. How could Quicken reliably know when the data provided by a third-party is not correct?
Premier on Windows 10
Do you have any idea of how many features there are in Quicken and at any given time something might go wrong. There is no way possible that there can be a Quicken employee monitoring everything. That's why there is this forum and Quicken support and Help -> Report a problem.
And frankly you talk about this as if you are reporting your house burning down, this problem isn't that important.
Thank you for taking the time to report this issue.
Our teams have been investigating this behavior and have identified a fix that is in progress.
In the meantime, this thread is being moved to our Alert & Known Product Issues category.
To automatically receive notification once an update and/or resolution is available please be sure to 'bookmark' this post by clicking the yellow star icon in the upper right.
Thank you,
Sarah
We've received confirmation from our service partners that a fix has been deployed and this behavior should no longer occur.
If, however, you continue to experience an issue, please create a new post to let us know.
Thank you again,
Sarah