Redenomination event – Belarus where 10,000 old rubles became 1 new ruble -How Oracle Financials Handles This

Fusion doesn’t treat this like a normal FX fluctuation. Historical AP invoices remain exactly as originally entered, and we don’t reopen or edit them because they form the audit trail. The transition is driven by currency setup, rates, and standard accounting processes, not by changing old documents.​

At a high level, the setup and steps look like this:

1. Enable both currencies (old and new) in the ledger if not already available.

2. Load the official redenomination rate on the effective date using Manage Conversion Rates → Daily Rates (for Belarus, 10,000:1 old-to-new).Create a Custom Rate Type

3. Continue operational activity after the redenomination using the new currency.

4. For any open AP invoice, Fusion keeps the invoice in the old currency, but the payment after the effective date is done in the new currency. Fusion automatically converts the liability using the redenomination rate and records any rounding or realized gain/loss.

5. Run Revalue Balances with revaluation as a new custom Rate Type Defined earlier along with the transition date for accounts that need restatement . This ensures the ledger reflects the new currency values correctly while keeping all historical transactions untouched.

6. This way, past data stays intact and auditable, while the business continues smoothly under the new currency using Fusion’s standard multi‑currency and revaluation capabilities.