Skip to main content

Why Does My Portfolio Value Look Different in Navexa?

Learn how to troubleshoot portfolio value differences between Navexa and your broker by checking quantity, price, trade history, DRP, transfers and corporate actions.

If your Navexa portfolio value looks different to your broker or registry, the first step is to work out what is actually different so you can check the right thing.

Start Here

A portfolio value difference usually comes from one of these areas:

  • the holding quantity (units) is different

  • the current price is different

  • part of the trade history is missing

  • a setting or event has changed the holding, such as DRP, a transfer, or a corporate action

Before troubleshooting, compare Navexa and your broker and confirm whether the difference is in:

  • the total portfolio value

  • one specific holding

  • the holding quantity (units)

  • the current price

If the difference is only in a return percentage or performance figure, that is a different issue to portfolio value.

Check Quantity First

If the quantity (units) in Navexa does not match your broker, the most common cause is missing or incomplete trade or investment history.

Check that you have:

  • imported your full history, not just recent trades

  • added trades from every broker or platform you have used

  • entered any share registry transfers or IPO allocations that were not imported automatically

  • recorded any transferred holdings with the original buy history where needed

If the quantity is wrong, the portfolio value will also be wrong.

Check DRP Settings

A Dividend Reinvestment Plan (DRP) automatically uses dividends to buy more units.

If DRP was enabled with your broker but not enabled in Navexa, your quantity and value can differ.

For any holding with DRP:

  • open the holding and check whether DRP is enabled in Navexa

  • confirm the dividend reinvestment has been applied to the correct holding

  • review recent dividends if the quantity changed unexpectedly

When DRP is enabled correctly, Navexa recalculates the dividend, updates the quantity, and adjusts the cost base.

Check Corporate Actions

Corporate actions can change your quantity and portfolio value. This includes splits, consolidations, mergers and demergers.

If a company has gone through a corporate action, make sure it has been recorded in Navexa.

You can review these options under Trades > Add.

Examples:

  • A split increases the number of units.

  • A consolidation reduces the number of units.

  • A demerger can create a new holding or change the cost base.

If the corporate action is missing, the holding will not match your broker.

Check Transfers And Crypto Fees

Transfers can also create valuation differences if the original history or fees are incomplete.

For shares:

  • make sure transferred holdings include the original buy history where required

For crypto:

  • check whether wallet transfer fees were captured correctly

  • confirm the net amount received matches what actually arrived in the destination wallet

A missing fee or incorrect transfer amount can change both the holding balance and the portfolio value.

Check Price Timing

If the quantity matches and the difference is only a small amount, the cause is often price timing rather than missing data.

A small value difference can happen because:

  • brokers may show live or intraday prices

  • Navexa may use a different pricing source or official close price

  • values may be rounded differently between platforms

This type of difference is usually small. If the gap is large, go back and check quantity, history, DRP, transfers and corporate actions first.

What To Send Support

If you have worked through the checks above and the value still looks wrong, send support:

  • the holding name or names that do not match

  • the quantity and value shown in Navexa

  • the quantity and value shown in your broker

  • screenshots from both platforms for the same date

This helps us work out whether the difference is caused by missing data, a setting, or a pricing mismatch.

Did this answer your question?