ITR and several other SPDR ETFs were given new names and tickers and lower expense ratios on Oct. 16. It appears that the shares will be swapped 1:1. See this news article:http://www.businesswire.com/news/home/20171016005642/en/State-Street-Global-Advisors-Launches-Suite-...
Thanks for all the help. It sounds like I can probably just edit the security symbol to SPIB? Though I wonder what will happen when I sync with my financial institution - as they were the original source for this entry in my file. I.e. -- will the financial institution try to change it back?
This reply was created from a merged topic originally titled Q2017 Windows ITR ticker symbol which became SPIB in October 2017 totals wildely ....I have this problem in my IRA account, which occurred with SPIB, an ETF. All was well until it posted a dividend on 12/28 which I downloaded on 12/29/2017. At that point it showed a 30M balance, which sadly I do not have. Quicken Deluxe 2017 Windows current, no placeholder and direct connect is used for the brokerage. After searching this forum, I found something in the Mac section which matched. It is specific to ITR, which was renamed to SPIB in October, 2017. . I have a Security Detail View that I had snipped 10/26/2017. Iin the Quote section it had 50,33x.00 for a per share price (that is right $50K). It was explained in another section that the problem occurs when a dividend posts to SPIB. A dividend posted on 12/28/2017 and my Quicken download showed this wild 30M totals.I spent a lot of time trying to figure out what happened and checking with my brokerage, which did not show 30M in my account.There is good news however; my download of 1/3/2018 showed the correct total, unfortunately, not 30M! What happened? I again looked in the Security Detail View. The Quote price was 34.19 (correct). In that section, however, the Open/Close, 52-week high/low data fields were still in the erroneous in the 50K range. So Quicken fixed itself from wherever it gets the Quote Price value. I expect the rest will eventually resolve itself in the next 52 weeks, but I really don't care.I posted a similar post without realizing it to the Mac section and was politely told that this question belongs in the Windows section. I am hopeful that the problem is solved in all Quicken 2017. .
however, the Open/Close, 52-week high/low data fields were still in the erroneous in the 50K range.