Mutual shares are now rounded. Did I do that?

Don Awalt

I have several mutual funds with T Rowe Price. I noticed today that several of them show the number of shares rounded to the nearest unit in both reports and in the share balance column of the transaction detail page. Normally they report share balance in the thousands of a unit. My total value seems correct, it's like Quicken knows the true balance but just doesn't show it. Oddly, some of the mutual funds in Quicken show the share balance with thousands, some do not.

I don't know how to get this accurate as reported by T Rowe Price....did I do this? Is it a setting? Is something corrupted? What do you think I can do? Thanks!

Don Awalt

To add to the confusion, I created a new file, and added T Rowe Price, so it downloaded opening balances for my mutual funds. They all show in the thousands. 

Second point, when I bring up Quicken, I Have it default to a custom page under the Investing tab. When it first comes up, share balance is in the thousands for all fund! If I then click on one of the offending funds in the left column, which shows the share balance in units, then click back to the investing tab, the investing tab display now shows rounded to units not thousands. I also tried this with the generic unmodified "Value" report Grouped by Security, and its behavior is the same is the custom display under Investing.

So - it seems to be the transaction ledger that's the problem would you say? Does this shed any light on how to fix this?

Rocket J Squirrel

I can't explain why the numbers would change on you. But one thing to check would be

Edit > Preferences > Reports only > Decimal places for prices and shares (0-8)

Don Awalt

Thanks @Rocket J Squirrel. I checked, mine was set to 3 digits. Here is what I tried:
- set it to 5 digits - went out of the report and went back in - still some are 3 digit, some are 0 digits.
- went to the generic Value by Security report - some are 3 digit, some are 0 digits. (all the rest of my tests are with the generic Value by Security report)
- set the setting to 0 digits - some are 3 digit, some are 0 digits.
- set the setting to 2 digits - some are 3 digit, some are 0 digits.
- set it back to 3 digits - some are 3 digit, some are 0 digits.

So it seems like (a) the preference doesn't change anything unless there is some other step I should do and (b) share balance reporting, number of digits, does seem like its broken.

UKR

AFAIK, Mutual Fund transactions are typically recorded at the brokerage and downloaded with 3 decimal digits precision.

Reinvested Stock dividends' number of shares are calculated to 5 decimal places.

There's a Preference Setting about number of decimal places in reports (as mentioned above) ... and that would only affect number of shares as displayed/printed if the precision is less than what's stored in the data file.

Are the entries in the Security List using the correct Security Type, Mutual Fund? Not Market Index, not Bond!

I don't know what else to suggest, other than restoring a backup of your data file from a point in time before all this started. Restore to a different file name, so as not to overwrite your current data file. Does that file exhibit the same problems?

Did you leave the door open and allow Murphy to come in?

Don Awalt

Thanks @UKR. In reply:

Are the entries in the Security List using the correct Security Type, Mutual Fund? YES

I haven't tried a backup yet - I lose too much going back, and I don't really know how long it's done this. I did try deactivating one of the offending funds, then I added that fund NEW - then I did "Move Transactions" to move all the transactions (10 years worth) from the old fund name to the new. It had the same share balance in units.

I also tried a Validate and Super Validate - all were fine.

I do think this is a bug. I guess I'll just live with it. I have 19 mutual funds, 14 are good, 5 are bad. DOn't know what caused it.

Don Awalt

Update to this problem - I did notice in the Security Detail View/transaction history, the transactions are all in thousands/3 decimal places. So it sure seems Quicken is choosing to round these to units for some reason. I just did a "report a problem".