This discussion was created from comments split from: New VOYA and Quicken Issues.
Well there looks to be another issue with VOYA. For about 2 weeks I have a holding that does not update share price. I have disconnected account and reconnected. Deleted account and then added it back. Those actions did not fix problem. All other accounts/holdings are fine. I am guessing it is another VOYA issue. The holding that does not update is: Any suggestions would be greatly appreciated. Thanks
Hello @dmurad53,
Thank you for letting us know you're seeing this issue! To help troubleshoot, please provide more information:
I look forward to your response!
T. Rowe Price Capital Appreciation Portfolio - Service Class
Ticker Symbol ITCSx
It is a balanced mutual Fund
Other accounts have this fund but there is no issue with share price updates.
This is really an odd situation. I will post any other information I can find out.
Hi @dmurad53,
Thanks for providing those additional details, @dmurad53 . Since ITCSX is updating correctly in your other accounts, that is helpful information.
If the same security is held in multiple accounts, the market price should generally be the same for all of those holdings. This makes me wonder whether the issue is specific to how ITCSX is set up or linked in the affected account rather than a general pricing issue with VOYA.
Could you please check the following?
If ITCSX is updating normally elsewhere but not in this particular VOYA account, the additional information above should help us determine whether we're dealing with a security-matching issue or something specific to the VOYA download.
I look forward to your response.
Thanks
here is what I found. VFL 226 is in a 457 account symbol NGWIN:VFL226:4S
VT 3243 is in a 403B account symbol INGWIN:VT3243:5G
There is no Security Name in the 0788 labeled "other"
The error occurs in the 403B account
Thank you for confirming that the affected holding is ITCSX and for providing the Voya identifier. Yes, ITCSX is the ticker for this fund.
At this point, I think a test file would be a useful diagnostic. It will help us determine whether the issue is specific to your existing Quicken data file or whether the same behavior occurs when the 403(b) account is downloaded into a completely new Quicken file.
Please test the account in a new file as follows:
Note: Creating a test file will not affect your existing data file. However, you may want to create a backup before proceeding.
Please let me know the results once you’ve had a chance to test this.
The new file containing just the VOYA accounts look ok
Thank you for your reply,
Since it works in a new file but not in the existing file, that indicates a file-specific issue. Go back to your main file if you haven't done so already (if you need instructions on switching between the new file and your main file, click here). Make a backup of your file, deactivate the problem account, and add it back into your file as a new account. To do that, navigate to Accounts>Add Account and follow the prompts. When you get to the Add/Link screen, instead of linking to the existing account, select the Add as a new account option.
Once the account is added, confirm whether the issue happens in that newly added account.
Thank you!
Thanks I will give it a try
Thank you for the follow-up,
Let me know how it goes!
Unfortunately the issue still exists in the newly added account
Since that account won't work properly in your main file but it works in the test file, I recommend exporting your data from your main file and importing it into the new test file.
To export your data, navigate to File>Export>Quicken Transfer File.
Follow the prompts. Then, navigate to the test file, go to File>Import>Quicken Windows File (QDF, QXF).
It may take several minutes to complete the import. Once it completes, review your accounts to ensure everything is correct. Reconnect your accounts and confirm whether everything is working correctly.