Why not use my set fixed exchange rate 0.1282??? why is 0.1282003? Big issue for me, alway show 0.01 exchange gains…i think if that 0.1282003 become 0.1282 so the 0.01 will not show anymore.
I just test it out if the receipt is only Sales = 291.98 then 0.01 will not show anymore, why? it that manager rounding the “Sales” and “Fee” One by One? IF yes, is that accounting use the same method to rounding a sales?
How can i use Base Currency HKD and set 1USD = 7.8HKD? (now is 1usd = 0.1282 hkd, i dont want it because rounding), will that 0.01 not show anymore if i can set 1USD = 7.8HKD???
Post a screen shot of the Edit screen for your receipt. Also, do not transcribe information into your post. Post screen shots of the actual transaction. That is the only way for other forum members to understand what you have done.
Do not think of it as an error. It is a difference caused by differences between exchange rates. But we don’t know what happened without seeing the screen shots.
The answer depends on what you entered. That is why we need to see the Edit screen for the receipt.
If you are going to use multiple currencies, you are going to gain foreign exchange gains and losses at some point in time. Understand that to balance your books, the program must convert various numbers into your base currency. The results are not always exact to two decimal places. Rounding will occur.
When you reply to a post you can copy the images - on Windows I use the Windows Snipping Tool to copy the part of the screen or window, I need and then use Paste
So here is what happened, @heyjo00as. You entered a receipt for exactly 291.98 USD. But Manager must convert all balance sheet amounts to your base currency to balance the accounting equation (Assets - Liabilities = Equity). At an exchange rate of .1282, that converts to 2277.53510140456162 HKD. But the HKD is limited to 2 decimal places for transactions. So Manager rounds that to 2277.54. That is the closing balance in HKD after the transaction. Because the result was rounded up, the program rounds down to 2277.53 and calculates an effective exchange rate of .128200287153188, which it rounds to .1282003 for display purposes. (Even at 15 decimal places, these calculations are almost never exact.) That effective exchange rate would produce a converted amount of 2,277.529771771204904, rounded to 2277.53. The difference between the two converted amounts is about .00533, which rounds to .01. (See, even the differences are approximations.) That’s what goes into the Foreign exchange gains (losses) account. Sometimes the difference is positive, sometimes negative, but it is never large and tends to even out over time.
All this is really a very long-winded way of saying that, if you use multiple currencies, you cannot avoid rounding differences and forex gains/losses. If the exchange rate changes in the future, you will see even more complications.
I just thinking if the exchange rate (book rate) can be set to 1usd = 7.75usd then the 0.01 may not show anymore in any other transaction, right? i wanna prevent the 0.01.
But i search the forum seem that no method can set the exchange rate like this when base currency is hkd.
but i need report in hkd so i can not set the base currency in usd.
Anything i can do so i can prevent that 0.01? thanks
Can you add the Exchange rate for 1 ZMW = 0.0769 USD?
Manager seems to have its own ROE when converting, please update.
Alternatively why not allow the user to determine the ROE entirely at a given time eg if June was 0.075 and July is 0.0769 a forex revaluation (prof/ loss ) will be based on the 0.0019
There are built-in exchange rates. I think their function is to prevent things like dividing by zero or generating completely nonsensical results. But they should not be regarded as current in any way. And they are not updated. In other words, they just hold places in the database.
If you are using multiple currencies, you need to enter your own exchange rates based on reality.
The issue im having is that manager is comparing the ROE with its internal rate to get the realised portion. As opposed to calculating the difference between the previous and newly installed rates
You need to illustrate your problem with screen shots. And you need to recognize that unless you enter a valid exchange rate for the beginning of whatever period you are looking at, the program is going to use that placeholder rate we discussed several weeks ago. And that will, of course, give bad answers.
