Incorrect Bond Price

Hiker2020

Quicken for Mac Version 7.3.2 (Build 703.50456.100)

Download from Fidelity NetBenefits 401k

From 9/29/23 to 10/22/23 Bond price dropped from $12.60 to $0.0021506.

Then 10/23/23-10/24/23 it was normal at $12.56. Then 10/25/23 it dropped to $1.00.

What's going on?

Quicken Jasmine

Hello @Hiker2020,

Let’s try a few troubleshooting steps for this issue—these steps should resolve things for you, but if not, please come back and post more about your experience so we can investigate.

First, backup your Quicken file.

I suggest deactivating the Fidelity NetBenefits 401k account(s). However, before doing so, I do recommend saving a backup of your data file first (just in case). Then, please check and make sure you do not have any hidden accounts that may be connected to this financial institution.

1. Go to the Accounts menu and choose Hide and Show Accounts
2. Uncheck any accounts with this specific financial institution that are checked as hidden in Lists

After that, please follow the troubleshooting instructions below.

1. Open the account register and navigate to the Settings gear on the bottom-right corner
2. Click on the Downloads tab
3. Click Disconnect Account (if there are more than one account associated with this financial institution, please repeat steps 1 through 3 for each account)
4. Navigate to Accounts > Add Account...
5. Use the search field at the top of the list to find and select your financial institution, making sure to choose Direct Connect, and click Continue
6. Follow the prompts to sign in using your login credentials associated with the financial institution
7. If the accounts have been found successfully; use the dropdown menus to link each account to the appropriate account in Quicken

Hiker2020

Jasmine

The bond price has been correct since the 25th. Do I need to do what you suggest?

Quicken Jasmine

Hello @Hiker2020,

No, you do not. Were there any specific steps you took to correct the issue?

Thanks!

Hiker2020

No specific steps. It was changing on its own. Apparently some glitch between Fidelity and Quicken.