For the month of June, an incorrect exchange rate was entered in GP dynamics. Is there some way to fix the subledgers?
Also, how can this problem be fixed using the revaluation report?
Any help would be greatly appreciated.
I strongly suggest that you configure the 'rate variance' for each exchange rate that is used in GP. By default this value is set to zero which means that any exchange rate value that is typed in by a user is accepted by GP. If a non-zero 'rate variance' is specified for a currency, then an invalid exchange can still be entered by a user but at the time of processing a transaction, GP will reject the exchange rate value outside of the valid 'rate variance' range.
This suggestion will not fix your existing sub-ledger problem but it will prevent similar problem occurring in the future.
Another suggestion is to use an automated exchange rate tool for inserting the latest exchange rates to stop operator typing errors. ( Envisage Software Solutions has such a tool :-) )
Envisage Software Solutions