NetSuite Consolidated Exchange Rates and Translation Review

Review NetSuite consolidated exchange rates by matching the period, accounting book, subsidiary pair, and account rate type to the translated financial statement. Recalculate a representative result and explain the movement. A daily exchange-rate check alone cannot establish that a consolidated report uses the intended translation basis.

This guide covers consolidated translation review in OneWorld. Transaction conversion and month-end revaluation of foreign-currency balances are adjacent processes with different purposes. It also does not choose an accounting policy for functional currency or equity translation. The responsible accountant must approve those decisions and material changes to rates or account classifications.

Identify the translation question

Start with one report line that the reviewer cannot explain. Record its source subsidiary balance, parent reporting currency, period, book, account, and expected rate type. If several subsidiaries contribute to the line, separate them before performing arithmetic.

Clarify whether the reviewer expects a current-period amount, year-to-date movement, or ending balance. An income statement and a balance sheet answer different questions. A blended ratio calculated from an entire report may not match one visible consolidated-rate row.

Save the report filters and rate snapshot together. If rates are recalculated or source transactions change during the review, preserve the earlier version so the team can explain why the output moved.

Understand the three rate types

NetSuite maintains Current, Average, and Historical consolidated rates for each period, accounting book where applicable, and subsidiary pair. Current generally supports balance-sheet accounts other than equity; Average supports income-statement translation; Historical supports equity. Account records also distinguish general and cash-flow rate types.

These descriptions are a starting point for inspecting configuration, not permission to change an account's rate type to force agreement. A classification change can alter financial presentation and requires accounting review.

Create an account-rate exception list that compares the approved account policy with actual configuration. Include newly created accounts and accounts whose type changed. A single unexpected rate classification can affect both the translated line and the balancing currency presentation.

Review the calculation population

Automatic calculation uses end-of-period currency rates for Current and transaction-amount-weighted rates for Average and Historical, based on the corresponding general rate types. Automatic calculation updates only subsidiaries the executing user can access.

That access limitation belongs in the close control. A successful calculation by a restricted role does not prove every subsidiary was refreshed. Retain the intended entity population and compare it with the actual rate rows reviewed.

For a changed weighted rate, examine transaction timing and amounts before assuming the market-rate feed is wrong. A large late-period transaction can legitimately influence the weighted result. Manual rate overrides need a documented reason, approval, and an explanation of their effect on reporting.

Hypothetical weighted-rate example

Assume the relevant population contains two positive transaction amounts in a subsidiary's base currency: 30,000 at a conversion rate of 1.10 and 70,000 at 1.20. For this simplified population, translated amounts are 33,000 and 84,000, totaling 117,000.

The weighted rate is 117,000 divided by 100,000, or 1.17. A simple average of the two rates would be 1.15 and would translate 100,000 to 115,000, producing a 2,000 difference. The arithmetic shows why equal weighting of days or rates can be an inappropriate validation shortcut.

This example is hypothetical and intentionally excludes credits, other accounts, multiple periods, and more complex reporting context. A production validation must reproduce the actual documented population and account settings rather than applying this two-line illustration indiscriminately.

Build a local-to-consolidated bridge

Use separate columns for local balance or movement, applicable translation basis, expected translated amount, actual report amount, and difference. Add the subsidiary pair, accounting book, period, and report identifier to every calculation sheet.

For an ending balance, determine whether the report line contains historical components or current-year activity that requires further decomposition. For year-to-date income, review the constituent periods instead of applying the latest month's rate to the whole year without justification.

When a report aggregates several subsidiaries, reconcile each contribution and then the total. This distinguishes an entity-specific rate issue from an omission in the report hierarchy. It also avoids interpreting a group-level effective ratio as though it were a stored direct rate.

Separate translation adjustments from transaction gains and losses

A subsidiary may have revaluation activity in its local ledger and translation effects when that ledger is consolidated. Keep those layers visible. Revaluation should be reviewed under its own process before group finance evaluates the translated result.

Using different consolidated rate types contributes to the Cumulative Translation Adjustment presentation on relevant consolidated statements. CTA is therefore not automatically an error to remove.

The review question is whether the configured rates, account classifications, source activity, and reporting context explain the result. If they do not, escalate the unexplained component with the calculation evidence. Avoid using CTA as a general balancing account for unrelated reconciliation problems.

Test changes that can affect prior comparisons

A late posting, an approved reopening, a changed account rate type, or a rate override can alter reported comparisons. Record which periods and reports need to be rerun when the change is approved.

Before changing a consolidated rate, save the old value, proposed value, reason, approver, and affected subsidiary pair. Reproduce the impact on a limited test population where a supported nonproduction environment is available. Retain the final report difference after the authorized change.

For multiple books, state whether the change concerns one book or several. Book-specific reporting requirements should not be flattened into a single global correction simply because the currencies look the same.

Make the close review repeatable

A useful monthly packet contains the subsidiary coverage checklist, reviewed rate rows, account-rate exceptions, a representative recalculation, and an explanation of material changes from the prior period. Use consistent sign and rounding conventions.

Set practical thresholds for investigation with the controller. A threshold is a prioritization rule, not permission to ignore an unexplained structural error. A small difference caused by an omitted subsidiary can signal a larger completeness problem.

Assign ownership for rate feeds, manual overrides, account classifications, and final reporting. The administrator may maintain data, but group finance should own the accounting interpretation and acceptance of translated statements.

Resolve the exact failed checkpoint

When requesting assistance, provide the local balance, report context, rate row, expected arithmetic, and actual output. This evidence can distinguish a rate-population issue, permission gap, account classification, or report design problem.

CuriousRubik's NetSuite support services can help scope that account-specific investigation. Keep the accounting decision with the finance owner and preserve evidence before any approved change to rate data or configuration.

Frequently asked questions

Are consolidated rates the same as daily transaction exchange rates?

They serve a different process. Consolidated rates translate subsidiary financial information into a parent reporting context. Daily rates also support transaction conversion and feed relevant calculations, but the tables and review questions differ.

Why does a simple average fail to reproduce the Average rate?

The calculation is transaction-amount weighted. The amounts and timing in the eligible population matter, so an equal average of two rates or calendar days may not reproduce the result.

Can a restricted role calculate every subsidiary's rates?

Automatic calculation updates only subsidiaries the user can access. Reconcile the intended coverage to the reviewed rate population rather than relying solely on a successful completion message.

Should an unexpected CTA balance be journaled away?

First explain the underlying translation. CTA can arise from the documented use of different rate types. Any correction requires an identified error and the accountant's approved treatment.

What belongs in the monthly translation evidence pack?

Keep the report context, rate snapshot, subsidiary coverage, account-rate checks, independent sample calculation, approved overrides, and explanations of material movement. Preserve affected prior-period comparisons when changes occur.