Investigate a NetSuite elimination difference by freezing the report context, identifying the residual transaction population, and tracing eligibility, timing, currency effects, and elimination placement. Start with the amount that remains after the run. Posting a balancing journal before understanding that residual can conceal the original problem and distort the next close.
This article is a diagnostic guide for post-elimination differences in OneWorld. It assumes the company has a broader intercompany reconciliation process. It does not repeat that full workflow or determine transfer pricing, ownership accounting, or the correct treatment of an intercompany transaction. Material adjustments require the responsible accountant's approval.
Record the report name, subsidiary context, accounting book, period, currency basis, account, and residual amount. Save the elimination run time and the report extraction time. A report rerun after late transactions can legitimately differ from the snapshot reviewed immediately after elimination.
Ask whether the residual is in intercompany receivables and payables, internal income and expense, an elimination subsidiary, or CTA-E. These are different investigation paths. A currency-related elimination amount should not be silently treated as a missing invoice.
Use a single signed residual statement: expected group balance, actual group balance, and the difference. Specify whether debit balances are positive or negative so paired investigations do not reverse the sign halfway through the analysis.
Identify which transaction lines should participate in elimination and which actually did. Confirm the intercompany account, counterparty or representing entity, subsidiary, and elimination marking appropriate to the transaction type.
Elimination creates journals for lines marked for elimination. Intercompany orders themselves are nonposting; invoice and bill activity supplies the posting lines. The process also depends on prerequisite close tasks and considers linked currency-revaluation effects.
A sales order matching a purchase order therefore does not prove that the corresponding posting transactions exist in the same period. Trace the invoice, bill, credit, or journal that actually affected the ledger. Retain document relationships but reconcile the posting population.
Compare the source population at the elimination run time with the population at final reporting. Search for postings, approvals, reversals, and edits after the original run. A late credit memo can create a new difference even when the original pair was correct.
Elimination can be run more than once for a period. That capability should support a controlled rerun after approved changes, with before-and-after evidence. It is not a reason to rerun repeatedly without identifying the changed population.
Before rerunning, confirm that dependent currency processes and relevant books are current. Then inspect the resulting elimination journals and reconcile the change in the residual. The expected improvement should be explainable by the transactions that changed.
In a multilevel hierarchy, check the reporting node and the elimination subsidiary. Elimination journals are posted to the elimination subsidiary under the least common parent of the two subsidiaries. A regional report and a group report may therefore include different elimination populations.
Draw a small hierarchy showing the two trading entities, their common parent, and the relevant elimination subsidiary. Mark which nodes the report includes. This often resolves a presentation question before any accounting change is considered.
Do not assume that selecting one subsidiary in a report defines the scope of the elimination process. The process is organization-wide rather than a per-subsidiary elimination run. Report scope and processing scope need separate explanations.
Reconcile the original transaction-currency amount first. Then explain each entity's base-currency amount and the relevant revaluation or translation effects. Finally compare the consolidated result and elimination output.
Maintain separate columns for principal, linked currency adjustment, elimination amount, and residual. This prevents an exchange-rate difference from being hidden inside an alleged commercial dispute. It also makes it easier for the accountant to assess whether the difference belongs in the configured currency-related account.
Check whether the investigation compares the same accounting book. Different approved accounting treatments or book-specific rates can produce different results. A primary-book extract and a secondary-book elimination report are not interchangeable evidence.
Assume two entities trade in the same base currency for this simplified example. Entity A posts intercompany income and a receivable of 50,000 currency units. Entity B posts the matching expense and payable of 50,000. The initial eligible population is matched and eliminated.
After the run, Entity A posts a 2,000 credit relating to the same service, while Entity B has not yet recorded the corresponding adjustment. A final report shows a 2,000 residual. The correct investigation identifies the late credit, confirms the commercial agreement, and determines the approved counterpart and period treatment.
Blindly posting a 2,000 balancing entry would make the report look cleaner while leaving the missing counterpart unresolved. If that counterpart posts later, the balancing entry may create a new difference. The example is hypothetical and deliberately excludes currency effects to isolate timing and completeness.
For each residual, record the source IDs, entity pair, book, currency, account, amount, expected elimination location, and cause. Useful cause categories include missing counterpart, inconsistent period, incorrect marking, wrong account, late change, currency effect, and report-scope mismatch.
Assign the next action to the person who can resolve the cause. AP can investigate a missing bill; the subsidiary controller can approve a period correction; the administrator can inspect configuration; group finance can review consolidation treatment.
Do not close the exception merely because someone has promised a correction. Record the posted transaction or verified configuration change, the rerun evidence where required, and the final residual. Preserve the original amount so the audit trail explains what changed.
Manual entries to intercompany or elimination accounts deserve targeted review. Determine why the standard process was insufficient and whether the entry will interact with a later automated run or reversal.
Check the journal's entity pair, period, account, marking, and supporting calculation. A balanced journal can still contain an unbalanced elimination subset. Test the actual transaction type and validation behavior in the account instead of assuming every journal entry receives the same intercompany checks.
Where a recurring correction appears each month, investigate the source mapping or process ownership. The long-term solution may be better counterpart creation or cutoff discipline rather than another recurring elimination adjustment.
The final evidence should let another reviewer reproduce the starting difference, follow its cause, and verify the outcome. If a residual remains intentionally, retain the accountant's approved explanation and next review date.
For help with an unresolved process or configuration difference, bring one complete entity pair and its elimination evidence to CuriousRubik's NetSuite support services. Keep the question specific to the failed checkpoint rather than changing the entire intercompany design prematurely.
Possible causes include late transactions, missing counterparts, eligibility or account errors, currency effects, and report scope. Completion of the run does not prove that the source population was complete or commercially matched.
NetSuite supports multiple elimination runs for a period. First identify approved changes, refresh dependent processes as needed, and retain before-and-after evidence so the rerun has a defined purpose.
The process uses the elimination subsidiary under the least common parent of the trading subsidiaries. Verify the hierarchy and reporting context before treating an apparently missing journal as a processing failure.
No. Orders are nonposting. Trace the invoices, bills, credits, and journals that affected the ledger and compare their periods, amounts, and elimination eligibility.
No. Establish the cause and obtain the accountant's approved treatment. A balancing entry can duplicate a later counterpart or hide a configuration problem that will recur.