VUSA price change off

It seems the VUSA price change was way off (19% down) when it was 0.1% up yesterday. Can it be rectified? Thanks.

You mean this? => https://stocks.cafe/stock/recent/VUSA/vanguard+s%26p+500+ucits+etf?exchange=XLON

I see Yahoo have similar data => https://finance.yahoo.com/quote/VUSA.L/history?p=VUSA.L

Can you give me your data source?

Hi Evan,

I missed replying your previous message. I have an issue with the VUSA prices again. It seems that StocksCafe moved the prices 2 decimal places to the right since 9 September, e.g. GBP 49.15 became GBP 4915. As a result, my portfolio values have became way off. Could I seek your assistance to rectify this please? Thanks!

Hi Gideon,

Thank you for reporting. Sorry, my LSE provider seems to be having this issue of GBP and GBX.

I have reported it to upstream. Will update again.

Thanks,
Evan

Hi Gideon,

Apologies for the delay. Upstream have responded. It is now reverted back to GBX.

Thanks,
Evan

Hi Evan,

Thanks for following up! I noted the prices for VUSA are now in GBX. The price of each VUSA unit is 4X.XX GBP, but it is now showing these as GBX values, e.g. 4X.XX GBX. So the values are still off. Hope you can help to address it!

Hi Gideon,

I am seeing them as GBX 4000+ in StocksCafe -> https://stocks.cafe/stock/recent/VUSA/?exchange=XLON

Where are you see GBX 40+?

Hi Evan,

Apologies I took sometime to get back. I have attached a screenshot above for reference. I think the issue is with the computation of the portfolio value of my VUSA units, it is way off. I noted the unit prices are accurate in GBX.

Hi Gideon,

I believe in this case, it is likely related to your buy transactions. Can you check them?

Evan

Hi Evan,

I am facing an issue with the pricing of VUSA. If you see from the screenshot, on 23 Jun, it showed the price as 5X.XX GBX when it should be 5XXX GBX beforehand. If it is quoted in 5X.XX, it should be GBP and not GBX. It has made my portfolio value way off. Could I seek your assistance to rectify this? Thanks!

Thanks for reporting!

I have fixed it. Please verify.