Investment Account Syncs Shares with the Decimal Point in the Wrong Place

bob4321

Quicken Classic for Mac is incorrectly reporting the Shares field for one of the component funds in my 401k Investment account. It is putting the decimal point in the wrong place, two places to the left — thereby reporting 1% of the correct number of shares owned (555.5555 becomes 5.555555).

This is happening with only one among several funds in my 401k portfolio. The rest sync correctly, as do all funds in another investment account, and do all other accounts.

If I manually correct the value the error returns the next time I sync.

The 401k account is managed by Voya.
The fund is Vanguard Inst Total Bond Mkt Index Trust 80.
This behavior began between November 19 and November 25, 2025, and is ongoing.
It began when I was using a previous version of Quicken Classic for Mac and has continued through the most recent release - Version 8.4.2 (Build 804.59835.100).

I tried clicking "change connection" to reestablish the connection to sync the account, and it didn't help.

Asking the Quicken Support AI chatbot was 🤡 (unsurprising).
I'll try a human when one becomes available.

In the meantime, does anyone have any insight how to fix this? Maybe this will also help someone else.

Jon

The only thing I can suggest is to double check that security in the Securities window and make sure the Type field is set to Mutual Fund (it sounds like this is VBTIX or something very much like it) and not Bond. If I'm not mistaken actual bonds are priced kind of weird in exactly the way you describe, but that shouldn't be the case for a bond mutual fund.

bob4321

https://community.quicken.com/discussion/comment/20532533#Comment_20532533

That's interesting. The fund is very much like the one you mentioned. It is VBITX.

Quicken has classified this particular fund as Type "Bond" with Asset Class "Domestic Bond". I restored a backup from a time before the error began and at that time Quicken was classifying the same fund as Type "Other" and Asset Class "Unclassified".

I've never touched any of that — it's whatever came down when I synced the account.

Jon

What happens if you change it to Mutual Fund? That's what it should be IMO.

bob4321

https://community.quicken.com/discussion/comment/20532535#Comment_20532535

Thanks for your help on this!

I just realized I identified the wrong symbol for the fund that's having issues. The fund I'm having trouble with is the one you mentioned: VBTIX. For some reason Voya doesn't include it's symbol in the prospectus, but it identifies the fund with exactly the name you used.

VBITX is also in my portfolio, and it's properly updating. Quicken classifies it as Type "Mutual Fund".

I tried changing the Type of the problematic fund to Mutual Fund, as you suggested, and re-synced.
It did not automatically download the correct number of shares (they stayed at 1%, where they were).
I manually edited that to the correct number, and tried re-syncing again, to see if the correct number would stick.
Unfortunately, even with the Type set to Mutual Fund, the number of shares synced to 1% the correct number, with the decimal point in the wrong place.

jacobs

@bob4321 Your Vanguard fund is a mutual fund, not a bond. It's a fund that invests in bonds, not an actual bond. So it should be Type=Mutual Fund in the security setup. Changing that will fix your problem. (You may have to fix the existing transactions, but anything going forward should come in correctly.) Setting the security to Type=Bond results in the exact behavior you described, because that's the way bond shares are tracked in Quicken.*

*If you're interested, you can read a little more about bond prices and how they are tracked in Quicken in this thread:

https://community.quicken.com/discussion/comment/18477560#Comment_18477560

bob4321

@jacobs Thanks for the suggestion! I agree with you and Jon, who both told me the same advice. And as I mentioned earlier, I confirmed from a backup that before the problem began, Quicken was classifying it as Type "Other" and Asset Class "Unclassified". These classifications are now and have always been whatever came down with the sync. Until I followed the advice to correct the asset Type, I never intervened.

But as I also mentioned earlier, changing the asset to mutual fund didn't change the behavior, not even after manually correcting the share balance (it was overwritten with the wrong number next time I synced), nor after disconnecting and reconnecting the account (the problem remained). So there seems to either be an error in the data coming from Voya, a misinterpretation by Quicken, or some other bad communication.