nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Fidelity Price of 68389X105 ORACLE COMMON STK FD in 401k wrong

jamlevi66

The price of this 68389X105 ORACLE COMMON STK FD is being downloaded from my Fidelity 401k every day as 0.62 cents and the actual value is around $1,350. I have to update it every single day manually and it's super bothersome. Can it get fixed please? I called Fidelity and they said they have many tickets open - is anyone working on this?

Find more posts tagged with

Comments

NotACPA

68389X105 is the CUSIP for Oracle stock itself, which according to Fidelity investments closed today at $152.94.

So, how did you get $1,350 and how does this fund in a 401k have the same CUSIP as the stock itself?

jamlevi66

So, I work for Oracle. Hard to explain for me, so I asked Gemini…

the 68389X105 ORACLE COMMON STK FD entry is a Unitized Company Stock Fund (specifically the Oracle Common Stock Fund) set up internally for the Oracle 401(k) plan.

How It Works

Unitized Structure: Instead of holding individual shares of Oracle stock directly in your account, 401(k) plans pool employee contributions into a "unitized fund." This fund holds actual shares of Oracle common stock plus a small cash/money market reserve (usually 1% to 3%).
Why the Price Doesn't Match ORCL: Because you own "units" of this combined stock-plus-cash pool rather than single shares of stock, the value per unit ($1,350 or so) reflects the net asset value (NAV) of the unitized fund, not the public per-share ticker price of ORCL stock.
CUSIP Identifier ( 68389X105 ): This 9-digit code is the private CUSIP number assigned specifically to account for this commingled fund within institutional retirement plans.

So, I guess it is a unitized price. And, it's being downloaded as 62 cents every day. Weird.

Sceptic

@jamlevi66 it is very common for a 401(k) plan to hold unitized funds, especially unitized company stock funds. The reason for this is because the Oracle stock has a settlement of T+3, which doesn't work for a daily environment. The unitized company stock fund works in a daily environment because the cash pool provides the liquidity needed for daily trades.

What concerns me is that the cusip you provided in your post is the actual Oracle stock cusip, which would never be used for a unitized company stock fund. That's where I think the disconnect is. You might have set up the actual Oracle stock security in Quicken which is not the same as the unitized Oracle stock fund in your 401(k) plan. A unitized fund uses a "fake" or pseudo Ticker or Fund ID and Cusip (if needed for system purposes).

You can verify the price of this unitized fund by going into your online 401(k) account with Fidelity, and that should agree with the price being updated on Quicken. But more importantly, the price for this unitized fun does not get upated through the Quicken pricing file. The price for this unitized fund gets updated through the daily transaction file via One Step Update (OSU).

NotACPA

I concur with @Sceptic in that the CUSIP of this fund CAN NOT POSSIBLY have the save CUSIP as the stock.

Two securities, the Oracle stock and this fund, can't share a CUSIP. That's simply not how things work.

Sceptic

@jamlevi66 the other important thing about unitized company stock funds I forgot to mention. The units (shares) and price do not correspond to the actual fund. So, not only do you confirm the price from your online account, but also the units of the unitized fund. What is comes down to is the MV of the unitized fund should be the same as the Oracle stock, but the shares and price of the unitized fund are different. But mathematically their units X price should equal the actual market value of the Oracle stock.

q_lurker

What is comes down to is the MV of the unitized fund should be the same as the Oracle stock, but the shares and price of the unitized fund are different.

Well, that’s a confusing way to say it. I think what @Sceptic is trying to say is that a share of the unitized trust is equivalent to some number shares of the Oracle common stock (plus some cash). It is not a 1:1 relationship. It might be something 250:1 [meaning 250 unitized shares at $0.62 equals 1 ORCL share at $155] or it could be 1:9 [meaning 1 unitized share at $1350 equals 9 ORCL shares at $150].

Either way, the unitized trust shares are a separate security distinct from the publicly traded ORCL shares with the 68389X105 CUSIP. They should appear differently in your Quicken security list.

Sceptic

@q_lurker your explanation of a unitized fund is incorrect. The shares and price for a unitized fund are arbitrary and have nothing to do with the underlying funds. Usually when a unitized fund is created an arbitrary price of 10.00 is struck. Then, a daily NAV calculation is done which updates the daily price. For example for a unitized company stock fund -

Actual Stock price= 25.00, shares= 1000.00, MV= 25,000.00 (this is the "real world")

Unitized stock price = 10.00, Units= 2500.00, MV= 25,000.00 (this is what is shown in the 401(k))

Again, for the unitized fund, the units and price are arbitrary and really don't mean or equate, or a ratio, to anything.

jamlevi66

Thank you ALL for the insight and time you put into answering my post. I was going to post a screenshot of my Oracle 401k holdings (scrubbed of values) where the "unitized" security is listed as "68389X105 ORACLE COMMON STK FD". And a screenshot of the security in Quicken (below)... when I went to take the Quicken screenshot, it became clear to me what the issue is, and I have no idea why the security was created like this upon download from Fidelity. Quicken appears to have selected the ticker symbol of TCOR. Huh? I checked the ticker and sure enough, it's trading at .62 cents. I do not see any label of TCOR in Fidelity, I only see that in Quicken. So, how do I get my unitzed security to download properly? And, why did Quicken select TCOR for this holding? My apologies for not diagnosing the issue properly, but Quicken downloaded the account automatically, so I assumed the holdings were set up properly and I never scrutinized the holdings.

Sceptic

@jamlevi66 -

TCOR = TreeCon Resources, Inc.

Did you leave the fund ID or Ticker blank when you set up the Oracle stock? If so, there could have been a mismatch. Quicken Mac sometimes gets confused with these "pseudo" funds which don't have real fund IDs or Tickers.

The first thing to do is determine if this stock fund is the true Oracle Common Stock, or an Oracle unitized company stock fund. I would go onto your 401(k) online account and see what shares, price, and MV it shows for this fund. This will tell you what type of security you are dealing with.

You posted your issue with a Quicken Windows category. But I see that you are using Quicken Mac. From this point I would need to pass the baton to @jacobs and @Jon the Mac superusers, to provide further guidance with this issue. They can help you correct the security set up and provide steps to properly link and reconcile the security on Quicken Mac. Thanks for your understanding and good luck!

(I have also asked the moderators to move your post to the appropriate Quicken Mac category.)

q_lurker

Yes, I oversimplified. Your example clarified your prior point and better expressed what I was attempting to indicate. The aspect I omitted was that the ratio changes over time.

jamlevi66

we already established that it is unitized.

jamlevi66

I thought I would try to see if the "bug" had been fixed since the account was downloaded in Quicken, so I disconnected the account and renamed it with a prefix of ZZ… I then re-downloaded the 401k account from Fidelity. The security still was named "ORACLE COMMON STK FD (TCOR)" and mis-identified as ticker TCOR. Mystery!?!?! Then, I decided to delete the newly downloaded account & delete the TCOR security from Quicken, but I could not find the Edit Holdings button (or menu item) as indicated here: https://info.quicken.com/mac/deleting-securities

Screenshot 2026-09-17 at 10.12.38 PM.png

jamlevi66

any insight here? @jacobs and @Jon Mac superusers

Jon

If Fidelity insists on assigning the wrong symbol to that asset there’s not really anything you can do on your end to fix it. Your only real option is to take the account offline and manage it manually, unless you can get Fidelity to fix things on their side.

Jon

@jamlevi66 In order to delete a security you first have to delete all the transactions that use it. If you already deleted the newly downloaded account in Quicken then that should take care of that step.

To delete the security go to the Securities window (on the Window menu), find the TCOR security (you can sort on the Symbol column to make that easier), then right-click on the security and select the Delete Security option.