rounding on portfolio valuations
I have been using MD since March 2016, and have never had a discrepancy in valuations until I recently updated to MD2017. Is MD now using "precision as displayed" for portfolio valuations? Did I somehow miss an option or preference on this? It's kind of a pain not having MD match Quicken, Excel, and my brokerage, because it always makes me wonder if I erred during input.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Tom Freeman on 02 Dec, 2016 02:27 PM
Which version of MD 2017 are you using? Help > about MD
Can you be more specif about the discrepancies.
Tom Freeman
Infinite Kind Support
2 Posted by Geza Soos on 02 Dec, 2016 09:24 PM
I am using Version 2017 (1584)
The valuation error was for a single security. In late November I had a
reinvested dividend of 4.861 shares for $47.05. That computes as
$9.679078378 per share, and it brought my holdings of that security to
4,243.293 shares.
Per Moneydance, 4.243.293 shares times $9.679078/share = $41,071.16
Per both Excel and Quicken, the extension was $41,071.17. This was the
first time in 8 months, with multiple securities (most of which reinvest
dividends) that I had a rounding difference. Hence, my belief that MD used
"precision as displayed."
Also, and I regret that I do not remember the exact sequence of how I
found this, another security got a reinvested dividend on 12/1/16, and
after I entered the transaction in the register, I found that the security
detail had not been updated. The difference between the per/share value and
the closing value was very small (.0003203,) but I would have thought the
security detail would have been updated.
These small differences never occurred with MD2015. I hope you are not
following Quicken's lead in emasculating your product.
3 Posted by Tom Freeman on 07 Dec, 2016 06:35 PM
Please update to the latest build of MD 2017 (1293). There were some issues with security pricing that were fixed. I did the math in MD 2017 (1293) and received the correct 41071.17 figure.
You can download that from here: http://infinitekind.com/preview
If this does not resolve the issue, please send me a screen shot of your cost basis for this security. I would want to rebuild a copy of your holdings to see if the rounding error is somewhere else than the simple math.
Tom Freeman
Infinite Kind Support
4 Posted by Geza Soos on 14 Dec, 2016 02:49 PM
Thank you. I think that helped, although I am not sure because the issue
was resolved when end-of-November pricing reverted to 2 decimals.
Unfortunately, in my haste to update, I downloaded a preview [Version
2017.1 (1593)] instead of the recommended (1293.) It seems to work,
although I have gotten a few messages that (1593) did not have a digital
signature. Did I screw up? Should I (and is it possible to) go back to
(1293?)
I did not put this into the public discussion because I was unable to
find my original question.
Thanks!
5 Posted by dwg on 14 Dec, 2016 07:49 PM
Support are in error there is no such thing as Moneydance 2017 build 1293, I believe Tom meant to type in build 1593
6 Posted by Tom Freeman on 16 Dec, 2016 08:08 PM
Yes I meant 1593 but typed too fast and failed to notice.
Thanks DWG
Tom Freeman
Infinite Kind Support
7 Posted by Geza Soos on 03 Jan, 2017 09:46 PM
In 2017.1 (1593) I am still having the problem that a 6-digit history does not give a correct valuation. Formely, it was 8-digits.
I use 2 files: a file for FMV and a file that I reconcile to provider online balances. The FMV is no problem, since they never have more than 4 decimal places. However, if a dividend yields an 7-or-more decimal price, I cannot reconcile without creating some stupid reconciliation value, which I have to reverse no later than month-end.
All of this makes me think that I cannot use MD except for transitory (and unrecorded) values.
8 Posted by Tom Freeman on 12 Jan, 2017 05:21 AM
I will put in a bug ticket. The rounding to only six does through off the current value figure.
Tom Freeman
Infinite Kind Support
9 Posted by Geza Soos on 12 Jan, 2017 01:00 PM
Thank you.
System closed this discussion on 13 Apr, 2017 01:10 PM.