I'd like to confirm I understand the aspects of tracking costs when it comes to working on an instance that uses multi currency.
My understanding is that both Currency and Price field types will take a value entered by a user and convert that to the system reference currency using the current exchange rate as determined from the latest load from the European bank (So 100 GBP entered today might be stored as reference currency 122.92 USD).
Additionally, when aggregations are performed, the system will do this against the reference currency, and then convert that back for display at the current exchange rate. e.g. two records entered with 100 GBP today would be both stored as 122.92 USD, which would then be summed to 245.84 USD, and then converted back to 200 GBP at the current exchange rate.
That works fine when the currency represents a current price to be paid, however if this were being used to track the cost at the point in time, this seems to pose the issue that 100 GPB entered 3 years ago on record would have been stored as something like 135.28 USD. If we have two of these records and we want to sum them again, the calculation would be 135.28 USD + 135.28 USD = 270.56 USD, which is then converted using the current exchange rate to £220.09 GBP, despite the original sum of the entered GBP values being £200.
With this in mind and assuming this is correct; are there any recommended practices when it comes to tracking point-in-time costs?
