NetBenefits
This comment was split from the discussion: Fidelity Net Benefits and Investments not working with OFX or Plaid
Since NetBenefits handles accounts differently than Fidelity Investments, can we turn this into a NetBenefits discussion? I feel like the main Fidelity thread is so large that NetBenefits-specific posts might get lost. I'll copy this over to the main thread if the consensus is that it would be better over there. Here goes:
I was initially excited to discover that NetBenefits allows downloading QIF since the CSV doesn't work with the importer discussed on the main thread. However, it still requires a lot of manual work because the transactions all come in with the correct dollar amount but shares divided by 10. That requires me to go into every share price, add *10, then go to the dollar total and add /10 at the end (I'd forgotten these functions have been built into MD for years--maybe since the beginning). Afterwards even though the transactions have been corrected, the price history is still 10 times greater than it should be. If I want an accurate history I have to edit each one and add /10 to the end of the price. I remember reading on another thread (perhaps a response to me about Schwab?) that the "off by a factor of 10" error might be due to different place settings between the Fidelity QIF and MD. To that end here's a snippet from the QIF:
!Type:Invst
D04/06/2026
NBuy
YVANG US LG CP EQ IDX(OHRN)
I360.31000
Q3.830
U1380.24
T1380.24
MContribution
This was imported as .383 shares at 3603.75979112272 for a correct total of 1380.24. When I edit security, I see Max Decimal Places is set to 5 and is greyed out. I'll go check Toolbox because I think that can be changed there. Which number should I change it to? The price shows 5 places, but they've apparently rounded it to 2 places, and the shares show 3 places.
Related to Toolbox, all of the securities come in like "VANG US LG CP EQ IDX(OHRN)" and do not match with the existing security "VANG US LG CP EQ IDX." I think this is another Toolbox task where I can find the "hidden" identifiers assigned to each security and then add whatever is missing to my version of the security. I did that for all my main Fidelity securities last month and am about to import this month's transactions there to see if I did it correctly.
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 dwg on 29 Apr, 2026 01:05 PM
QIF files do not contain scheme information. The match is based on the name, i.e. the value of the Line starting with "Y", it must match exactly with the security name in Moneydance otherwise it deems it a new security.
It seems strange that the position of the decimal point is not being honoured.
2 Posted by dwg on 29 Apr, 2026 01:10 PM
I have created a test QIF file containing your transaction and imported it to a new Investment account and it imported as expected.
3 Posted by Ted on 29 Apr, 2026 08:08 PM
Thanks, I didn't mean to post the same thing in two places, but when I posted here I hadn't worked through Toolbox to see that I couldn't edit the hidden security details to make them match. Do you have any ideas what I can try to see if I can get the transactions to import with the correct number of decimal places? Unlike your new account, these securities were initially downloaded from Fidelity before they turned off OFX. That seems to have set the decimal places at 5. Since the QIF has only 3 places for the number of shares, I wonder if that is somehow messing it up. I suppose I can try to change one of the hidden decimal places in Toolbox and see if it imports correctly.
4 Posted by Ted on 30 Apr, 2026 03:21 PM
I tried changing the hidden decimal place to 4 on one of the four securities in the portfolio. I also ran the regex I mentioned in the other post (replace "^Y(.+?)([A-Z0-9]{1,6})" with "Y\1") to rename all of the securities.
This time when I imported, ALL of the transactions had the correct decimal point position. This leads me to conclude that the hidden decimal place setting didn't affect the import because all four securities worked even though I didn't change 3 of them. I guess I'll go see if I have any new transactions and try to import them with the name change to see if they import correctly.