Skip to main content

Why is my consolidated exchange rate wrong in OneWorld close?

Most commonly, the Consolidated Exchange Rates table wasn't updated for the current period before consolidation ran, or the wrong rate type (Current, Average, or Historical) was applied for the account being translated. Both cause child-subsidiary amounts to roll up incorrectly into the parent's consolidated financials.

Zuny FesterBy Zuny Fester, Head of Operations and Marketing
Reviewed by Zuny Fester
Published Last reviewed Editorial policy

Part of the month-end close guide.

Most common causeConsolidated Exchange Rates table not updated for the current period
Second causeWrong rate type applied (Current, Average, or Historical)
Where the table livesLists > Accounting > Consolidated Exchange Rates
When it should be updatedAs part of period close tasks, every period

The three rate types, and why using the wrong one matters

NetSuite's Consolidated Exchange Rates table maintains three rate types per period and subsidiary pair: Current (the balance-sheet rate at period end), Average (typically used for income statement accounts, reflecting the average rate across the period), and Historical (fixed at the rate when a specific transaction, like equity, occurred). Applying the Current rate to an income statement account, or vice versa, produces a translated number that's technically calculated but conceptually wrong for that account type.

Why it's most often just a stale table

The Consolidated Exchange Rates table doesn't update itself automatically — it needs to be maintained as part of period close tasks, each period, for every subsidiary-to-parent currency pair in use. When this maintenance step is skipped or delayed, consolidation runs against a stale rate from a prior period, producing a translated balance that doesn't reflect actual currency movement for the current period.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Checklist

Diagnosing a wrong consolidated exchange rate

  • Check whether the Consolidated Exchange Rates table was updated for the current period
  • Confirm the correct rate type (Current, Average, Historical) is applied per account type
  • Verify the elimination subsidiary's consolidated exchange rate is set to 1 relative to its parent
  • Re-run consolidation only after the rate table is corrected, not before

Frequently Asked Questions

Usually the controller or a member of the close team responsible for multi-entity consolidation, as a scheduled part of the period close checklist.

No — consolidated exchange rates only matter when subsidiaries have different base currencies from their parent.

Yes, but consolidation needs to be re-run after correcting the rate table — simply fixing the table doesn't retroactively correct financials already generated from it.

Sources

Related