UPDATE [October 14, 2021]: Vanguard has confirmed to me that this issue was caused by a bug in a software update they released to their web site and then fixed a day later. See the end of this blog posting for their response.
Some time between 6:00am US/Eastern on September 14, 2021 and 24 hours later, Vanguard rolled out an update to their web site which rewrote the historical value of some customer holdings and claimed that their holdings had gone up in value dramatically overnight. In my case, that meant that the value of one of my holdings was suddenly showing up as nearly 19% higher than it had when I looked at it a day earlier, making my retirement savings suddenly seem tends of thousands of dollars larger than it was. Later the same day, Vanguard silently rolled back the change. There has been no explanation or announcement about either change, and when I spoke to a Vanguard representative on the phone about it before it was rolled back, he was unaware of it.
Discovering the problem
I run a Selenium script at 6:00am Tuesday through Saturday to pull down the value of my Vanguard retirement holdings from the web site as of the close of trading the previous day and save the data in a CSV so that I can easily perform analysis on it. This script emails me the new figures and shows the delta from the previous day’s.
On the morning of Wednesday, September 14, the email from the script claimed that the value of my holdings in one of my funds, Vanguard Target Retirement 2040 Fund (VFORX), had gone up by overnight by over 18.8%, which would obviously be a rather remarkable increase, especially given that on Tuesday both the Dow Jones Industrial Average and the S&P 500 went down.
It would be extraordinarily remarkable for the value of a diversified Vanguard mutual fund to go up by that much on a day when the markets went down, but that wasn’t the only remarkable thing. When I asked the Vanguard site to show me the value of my holdings for days prior to September 14, the values shown by the site no longer matched the values that had previously been fetched from the site by my script. For example, when I checked on September 15 for the value of my holdings as of September 13, I got a much higher value than when my script performed the same check on September 14.
A closer examination of the data made it clear that pretty much the entire jump in value could be explained by ridiculously large values for “accrued dividends” displayed on the site for VFORX. By “ridiculously large,” I mean that if those values were accurate, then the fund was looking forward to an end-of-year dividend ten times or more larger than its dividend in any previous year since its inception. While this wasn’t entirely impossible, it certainly seemed highly improbable.
Attempting to get to the root of the problem
I called Vanguard to ask them what was going on. The first time I called, it took me about ten minutes of navigating their phone system and waiting on hold before I was finally connected to a person who could help me. I started to explain the problem to him, and when I paused in my explanation and waited for him to acknowledge what I was saying, there was silence on the line — it hadn’t disconnected, it was just completely silent — I asked several times if anyone was there and received no response, so I gave up and hung up. Whee!
My second attempt to call Vanguard resulted in a 38-minute call which was a combination of navigating their phone system, waiting on hold to speak to a person, explaining the problem to him, and waiting on hold again for quite a while while he went and checked with two other departments (or so he said) about what was going on. Finally he came back on the line and claimed to me that everything was working properly and the displayed accrued dividends were correct, but he couldn’t explain why there was such a large jump overnight or why my historical account values had changed.
Working around the problem
The Vanguard representative’s explanation was not particularly satisfying, but at this point I had no choice but to assume that the data now being displayed on the site was correct and the values that had been displayed up until yesterday were wrong, which meant that I was going to have to put a bunch of effort into revamping my script for pulling data daily off of the site as well as my script for various automated analyses I do of the data every day, to account for these accrued dividends that were suddenly showing up even though they never had in the past. It was not going to be fun.
While this was unfortunate in that it meant a bunch of work for me to update my tooling, it was also rather fortunate because it meant my retirement savings were significantly more valuable than I had previously thought. Woohoo!
I set to work making the changes.
Easy come, easy go
Several hours later, I was nearly done with the changes to the data scraping script, when suddenly my new changes mysteriously stopped working. Lo and behold, the big accrued dividends had disappeared; in fact, the accrued dividends for VFORX were now showing up as “$0.00”. The Vanguard site was no longer rewriting historical holding values, and there was no longer an 18.8% jump overnight in the value of VFORX. The change disappeared as silently and without explanation as when it appeared.
It sure would be nice to know what the heck happened here, and which data was actually a correct reflection of the value of my holdings. It would also be very nice to know if there are large accrued dividends that I will lose if I sell my VFORX holdings before the end of the year!
Vanguard owes its customers an explanation of what happened.
Vanguard comes clean, at least to me
I’d been asking Vanguard for a month for an explanation of what happened, before they finally got back to me on October 14, 2021:
Dear Mr. Kamens,
I am writing with an update regarding the issue we discussed last week
regarding your “Balances by date” page.
What you picked up on was an actual software issue that happened during our
most recent elevation. The issue was as we discussed: accrued dividends for
stock funds were appearing in the “Accrued dividends” column when they
shouldn’t be. The effect is, as you noted, an inflated value of your
portfolio before the dividends were transitioned from “Accrued” to “Paid”.
Our Web Technical Support Services has “rolled back and fixed” this bit of
code that was causing the trouble. We shouldn’t see this issue going
We really appreciate you not only taking the time to contact us about the
issue you found, but your patience and support during troubleshooting was
instrumental in finding a resolution. Thanks again for your help with this.
Vanguard Retail Investor Group
I wish they had posted some sort of public acknowledgment about what happened, as opposed to just responding to me privately, but 🤷 I guess that’s probably too much to ask for.