CURIOUSRUBIK
Let’s talk about your next move ↗View complete sitemap
Back to the blog

NetSuite Intercompany Reconciliation from Entry to Consolidation

NetSuite intercompany reconciliation should establish that both entities recorded the agreed activity, that their balances can be explained, and that consolidation removes the appropriate internal effects. Start with source documents, resolve exceptions between counterparties, and review elimination only after the underlying balances are supportable.

A single journal-entry tutorial cannot cover this process. Controllers need a repeatable handoff between local teams and group finance, with evidence for timing, currency and accounting differences. The exact treatment of loans, services, inventory profits and tax requires qualified accounting review.

Define the relationship before comparing numbers

Create a relationship register for each active entity pair. Include the nature of the activity, transaction currency, settlement terms, intercompany accounts, expected document flow and owners on both sides. Use a shared reference for recurring charges or shipments so the teams can identify the same economic event.

Separate trading activity from financing and manual allocations. A purchase-order-to-sales-order flow has different evidence from a treasury loan or a shared-service journal. Decide which transactions your native reports cover and which need an additional balance schedule. Do not assume one report contains every intercompany exposure.

For each close, agree a cutoff and a comparison basis. Counterparties should first reconcile the amount owed in the agreed transaction currency. Base-currency and consolidated differences can then be analysed without confusing missing activity with translation effects.

Enter the approved intercompany journal

In OneWorld, confirm whether the process uses regular or advanced intercompany journals. They are different record types and do not share all scripts or workflows. Finance must approve the accounting before entry.

  1. For an advanced journal, an authorized role opens Transactions > Financial > Make Advanced Intercompany Journal Entries. Select the originating subsidiary before choosing the transaction currency.
  2. Enter the approved date, period and lines with the correct subsidiary, account, debit or credit and supporting reference. The first line belongs to the originating subsidiary. Review balances, exchange rates and any configured balancing or elimination behavior.
  3. Save through the applicable approval process, then inspect each subsidiary's posting and retain the journal reference in the reconciliation. Balanced debits and credits alone do not establish that the economic treatment is correct.

Confirm the required permissions and choose the appropriate intercompany journal record type before entering the transaction.

Reconcile source transactions before elimination

Oracle's Intercompany Reconciliation report identifies unlinked or incorrectly matched trading transactions, including differences in amounts, billing and quantities. Oracle directs teams to run it before intercompany elimination. The report includes nonposting documents and uses date-range filtering, so capture its actual settings rather than assuming every result is controlled by a posting-period filter.

Review exceptions by cause. An unlinked order may need a relationship corrected; a quantity mismatch may reflect a shipment still in transit; a billing difference may indicate a missed invoice. Each requires evidence from the operating process. A blanket journal for the net difference removes that distinction and makes the following month harder to investigate.

Ask the receiving team to acknowledge the cause, expected correction and responsible person. Where timing is legitimate, retain the documents establishing it and have finance decide the accounting response. A status of “explained” should always identify the explanation and its reviewer.

Build a balance bridge for every material pair

Maintain opening balance, new activity, credits, settlements, adjustments and closing balance. Reference each component to source records. Separate disputed items from agreed amounts and keep the age of unresolved items visible.

Compare each entity's intercompany account balance with its detailed schedule. This catches manual journals, misclassified third-party balances and migration entries that may not appear in the paired-document workflow. If several intercompany accounts are used, reconcile them separately before presenting a net total.

Keep currency effects in their own bridge. Differences can come from transaction rates, settlement dates, revaluation or consolidation rates. The controller should explain which mechanism produced each amount. Currency variances are not automatically evidence of incorrect posting, and they should not be forced to zero simply because the original invoices matched.

Hypothetical reconciliation example

Assume Entity A invoices Entity B USD 24,000 for a service. B records only USD 22,000 because its team omitted one approved line. No payments have occurred. The transaction-currency difference is USD 2,000.

The teams compare the service agreement, issued invoice and B's bill. They confirm the missing line and obtain approval to correct B's source transaction in the appropriate open period. After correction, both schedules show USD 24,000 in transaction currency.

Now suppose A and B have different base currencies. Their base-currency ledger balances need not be identical numerical amounts. The teams retain their USD agreement and reconcile each local-currency carrying amount separately. Group finance then reviews the consolidated entries under its approved policy.

A second issue appears: B's correction was dated in the following month. The USD totals now agree on a current report, but the month-end comparison still differs. The reviewer checks the intended cutoff and corrects or documents the timing treatment before accepting the close. This is why a reconciled present-day balance cannot substitute for a reproducible period-end reconciliation.

Review what elimination actually did

With Automated Intercompany Management, NetSuite generates elimination journals for flagged transaction and journal lines during the close process. That makes account setup, line eligibility and posting periods important review points.

Inspect the generated journals and reconcile their totals to the approved intercompany schedule. Confirm the relevant elimination subsidiary and reporting context. Investigate unexpected remaining balances by source rather than adding an unsupported top-side entry. Some consolidation adjustments require separate analysis and will not be solved merely by marking a line for elimination.

Where balances are settled or netted, track that process separately. Settlement changes what entities owe; elimination changes how internal activity appears in consolidated reporting. Both need an audit trail, and one should not be used as evidence that the other is complete.

A practical exception register

Use one row per issue, with these fields:

  • Entity pair, transaction currency and shared source reference
  • Difference at the agreed cutoff, including its sign and units
  • Root cause and the evidence supporting it
  • Correcting action or approved timing treatment
  • Named owner on each side and escalation date
  • Approval, correction reference and retest outcome

Age the register through the month. Assign recurring causes to process owners: incomplete master data belongs with data governance, late invoices with billing, and integration omissions with the integration team. The group accountant coordinates closure but should not inherit every upstream task.

What to retain at close

Save the report parameters, pair schedules, counterparty confirmations, approved corrections and elimination review. Preserve the final report versions used for signoff, with the reviewer and date. If a period is reopened or a late entry changes a balance, identify which reconciliations and consolidated outputs must be rerun.

Why do balances still differ after trading documents match?

Check manual journals, settlement timing, rate effects, mismatched cutoff dates and account scope. A trading report and a balance-sheet reconciliation answer related but different questions.

How often should the team reconcile?

Resolve high-volume trading exceptions throughout the month, then perform a controlled cutoff review for close. The right cadence depends on transaction volume and the cost of leaving mismatches unresolved.

A useful intercompany process review starts with one difficult entity pair and follows it all the way from source documents to the consolidated statements.

Related resources

What’s on your mind?

A little context is all it takes to begin.

Please leave out passwords, payment details and confidential account data.