Navexa using wrong data to calculate trade value - Stake

Don't rely on provided Effective Price to calculate Trade Value (at least with Stake data)... this figure can be TRUNCATED to 3-4 digits when occasionally is is really 6+ digits... more complex effective price usually caused by me sometimes shifting limit price to fully fill a trade)... Importing Stake trades via Investment Activity XLXS file can result in incorrect final Trade Values (finding a fair few! a very painful audit process!!!!!) because it looks like Navexa uses the (sometimes) TRUNCATED Effective/Avg Price to calculate Trade Value rather than just taking the correct Trade Value from Stake file (and reverse engineering the true Effective Price). What were you thinking? As a banking systems person I would not have lasted long if I hadn't checked my calculations match real world results. My cash balance is out all over the place because of this... very worried your trade confirmation processor also uses this same incorrect logic as well... cannot rely on Navexa's processing as a result. But at least easily fixed! I am fixing one portfolio now... but have more portfolios to import (and audit)... how fast can you fix this? I will hold off importing more Stake portfolios if you can fix quickly... please advise... this is also a test of your support systems as a new user... an ex banking/telco/healthcare/explosives/military/food software engineer... none of those businesses allow or can afford for mistakes like this in production... either test better of fix when reported by your more dilligent users... Bug report Short summary (one sentence): Where is it happening? Platform: Web / iOS / Android Browser (if Web): Device + OS (if Mobile): App version (if Mobile): Steps to reproduce 1. 2. 3. Expected result What should happen? Actual result What happens instead? Evidence (recommended) Screenshot / screen recording: Error message (if any): Frequency Always / Sometimes / Once Extra context (optional) What were you trying to do when it happened?