You already ranTranslation, but a last-minuteadjusting journal entryin yourledger currencywas entered after you consolidated your results. What does Oracle considerbest practicewhen this occurs?

When a new journal entry is posted in the source ledger after translation and consolidation have already run, the translated balances for that period become outdated. The best practice is to rerun the translation process for the affected period. This updates the translated balances in the target currency to include the impact of the late adjustment. Following the translation, the consolidation process must be run again to reflect the updated, accurate figures in the parent ledger.

A. Revaluation is only necessary for foreign currency-denominated balances. The adjusting journal was in the ledger currency, so revaluation is not required.
B. Translation is run for a period and ledger, not for individual journal entries. The entire period's balance must be re-translated.
D. Entering a manual journal in the target currency is a workaround that breaks the audit trail and can lead to reconciliation issues.

1. Oracle Fusion Cloud Financials, Using General Ledger, Release 24B, Chapter: Period Close, Section: Translate Balances. "If you post a journal entry to a period after you've already run translation for that period, you must retranslate."

2. Oracle Fusion Cloud Financials, Implementing Enterprise Structures and General Ledger, Release 24B, Chapter: Ledgers, Section: Translation: Explained. "If you post additional journal entries or change your ledger currency balances after a translation, you must rerun translation for the same period."