Updated 7 October 2026.
A NetSuite currency revaluation review should verify the population of open foreign-currency balances, the rate used, the calculated change and the resulting accounting entries. Complete it with an independent reconciliation, not simply a check that the process finished. Keep revaluation separate from realised exchange differences and consolidated translation.
The controller must approve the accounting policy, eligible accounts and rate source. This guide provides a review method and a hypothetical receivable example. It does not prescribe the treatment of every account or currency exposure.
Foreign-currency transactions are recorded relative to an entity's base currency. A later settlement can create a realised exchange difference, while open balances may require period-end revaluation. Group reporting can also translate subsidiary base-currency results into the parent's reporting context.
Oracle distinguishes transaction exchange rates from consolidated exchange rates used for period reporting. A successful revaluation does not establish that consolidation rates have been reviewed, and a translated group statement does not replace local-currency revaluation controls.
Name these processes separately in the close checklist. Give each an owner, source data, approved rate methodology and output evidence. This prevents an unexplained difference from being assigned to “FX” without identifying what actually produced it.
Identify the entity, accounting book, period, eligible accounts and open transactions. Review whether transactions or applications arrived after the earlier reconciliation snapshot. Capture any late corrections that could change the open balance.
Oracle recommends locking the period before generating revaluations. Its documentation also distinguishes period-end rates from runs initiated before the period has ended and notes the default exchange-rate type used when rate types are enabled. Check these conditions rather than assuming every run uses the intended month-end rate.
Verify the actual rate values, direction and effective date against the approved source. A rate expressed as base currency per foreign unit must not be confused with its reciprocal. Small formatting mistakes can produce substantial valuation errors.
Use transaction or account-level evidence rather than reviewing only the total gain or loss. Oracle's revaluation details expose foreign balances, ending rates and, for open receivables and payables, prior and net gains or losses. That information supports an independent calculation and a bridge to the posted result.
Select representative items across currencies, account types and material balances. Include a partially settled transaction, an item with prior revaluation and a transaction corrected late in the period. Test the population separately from the arithmetic: an accurately calculated sample does not prove all eligible balances were included.
Review classification completeness where the configuration carries source dimensions into revaluation. Missing departments, classes, locations or GL-impacting custom segments can affect the process. Oracle specifically calls out required source classifications for matching them during revaluation.
Assume a fictional USD-base entity has an open EUR 10,000 receivable. Its original base-currency amount is USD 11,000, and the approved period-end rate is USD 1.20 per EUR. There are no payments, credits or other changes in this simplified example.
The period-end equivalent is EUR 10,000 multiplied by 1.20, or USD 12,000. The cumulative difference from the original USD 11,000 is USD 1,000. If prior recognised unrealised gains for the same balance total USD 300, the additional change needed in this example is USD 700.
The reviewer should therefore understand both the USD 1,000 cumulative difference and the USD 700 incremental effect. Comparing only the ending value with the original transaction and expecting every run to post USD 1,000 would ignore prior revaluation.
Now introduce a EUR 2,000 payment. The open population and settlement accounting need review before applying the same calculation. Likewise, a payable or another account type may use different sign presentation and detailed processing. This example establishes the review logic, not a universal journal template.
Tie the selected revaluation records to the relevant gain/loss and balance-sheet accounts. Retain the run parameters, rate evidence, transaction population and reviewer calculations. Explain material differences from the prior period using changes in balances, rates or scope.
Review the effect of reruns. If source data or rates changed, establish which records were created or changed and whether the final ledger reflects the intended net position. Do not manually add the full independently calculated amount on top of existing revaluation entries without understanding their effect.
Where balances are marked for intercompany elimination, review exchange differences separately with group finance. Oracle notes that currency revaluation gains and losses associated with elimination-marked transactions and accounts are not themselves eliminated by that process. Accounting conclusions still require the group's policy review.
An omitted balance may reflect account eligibility, period scope, transaction status or missing classification. Trace the source record and configuration before changing the accounting. A rate difference may come from the wrong date, rate direction or selected rate type.
A residual amount after settlement may require investigation of applications, voids, credits and prior-period activity. Preserve the transaction history and ask the controller to approve the correction. Deleting history to obtain a clean balance can make the underlying issue harder to establish.
When the local ledger agrees but the consolidated statement differs, check the reporting context and translation process. Keep that investigation connected to, but distinct from, the accepted revaluation workpaper.
The reviewer should confirm:
Retain unresolved exceptions with amounts, causes, owners and due dates. Identify whether they block close under the company's materiality and control policy.
Prior revaluation and settlement history can affect the incremental amount. Inspect the detailed record and calculate the bridge instead of comparing only original and ending rates.
No. Revaluation concerns applicable foreign-currency balances within a book's base-currency accounting; consolidation translates subsidiary results for group reporting.
Use one material currency and its open-balance schedule for a currency close review. A traceable calculation is the strongest starting point for reliable revaluation controls.