Intercompany Balance, NetSuite

Card class: Card

Net intercompany A/R minus A/P across subsidiaries. Should net to zero post-elimination.

​

At a glance

Net intercompany receivable minus payable balance across the OneWorld subsidiary set. The card surfaces the unsettled trading position between the merchant’s own subsidiaries, which should net to zero at consolidation but rarely does until period-close eliminations post. A persistent or growing intercompany imbalance is the classic sign of a books-out-of-sync issue; period-close can take days longer to lock if the imbalance is not investigated proactively. Card gate: only_when: multi_subsidiary. Single-subsidiary tenants see a placeholder.

​

Calculation

Calculated automatically from your NetSuite data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​

Worked example

A US-headquartered industrial fastener distributor on NetSuite OneWorld. Three subsidiaries: US Inc, UK Ltd, AU Pty. Snapshot 04 May 26. Headline: $104k consolidated intercompany imbalance. What VP Finance reads:

1. The US-UK $100k imbalance is the dominant issue. Two possibilities: (a) timing, US Inc shipped goods late in the period and UK Ltd hasn’t yet received the inbound goods receipt, so the AP isn’t recorded yet; (b) FX, the US books at one rate, UK at another. Investigation:
   • Pull the US Inc intercompany AR list filtered to UK Ltd customer.
   • Cross-reference with UK Ltd’s intercompany AP list filtered to US Inc supplier.
   • Find the $100k of transactions that appear on US side and not on UK side. Typically 3 to 8 invoices.
2. Investigation result (this scenario): Five intercompany shipments left the US warehouse 26 to 28 Apr 26. UK goods receipt typically posts 7 to 10 days after shipment (transit time). The shipments are still in transit at snapshot date; UK has not yet recorded the inbound, so the AP entry doesn’t exist. Once UK posts goods receipt (estimated 06 to 11 May 26), the imbalance will close.
3. The pattern is normal but should not persist. A 5.5% imbalance on the US-UK pair is at the upper end of acceptable; >10% on a sustained basis is a books-quality red flag. Most multinationals operate at 1 to 3% intercompany imbalance during inter-period and net to zero at period-close.
4. The other pairs are clean. US-AU and UK-AU are within 2%, no action needed.
5. Cross-currency considerations:
   • The US-UK trade is denominated in USD on US side (USD invoice issued); UK side records the AP in GBP using the GBP-USD rate at goods receipt date. If FX moves between US shipment date and UK receipt date, the two sides record different GBP amounts, creating a small persistent imbalance.
   • The merchant uses a fortnightly intercompany reconciliation cycle to clear these residual FX-driven gaps.
6. Action playbook:
   • For period-close on 31 May 26: ensure all in-transit goods are posted to UK side before close.
   • Audit the cross-currency rate-application convention; standardise on the goods-receipt-date rate for both sides.
   • Set a monthly intercompany reconciliation review with the Controller.

Why this matters at consolidation: if the imbalance is unresolved at period-close, the consolidation engine flags an out-of-balance condition and either holds the close (delaying GL lock) or posts an Intercompany Reconciliation entry to the Suspense account. Either way, audit trail noise.

​

Sibling cards merchants should reference together

​

Reconciling against the vendor’s own dashboard

Where to look in NetSuite’s own dashboard:

Reports > Banking/Budgeting > Intercompany > Intercompany Reconciliation Report, with the period set. Shows side-by-side AR vs AP for each subsidiary pair.

For the per-transaction drill: Lists > Accounting > Intercompany Journal Entries, filtered by date and subsidiary pair. Why our number may legitimately differ: Cross-connector reconciliation: This card is a NetSuite OneWorld native. No commerce-platform analogue.

​

Known limitations / merchant FAQs

Why isn’t intercompany always zero? Because real-world books are not perfectly synchronised. Goods in transit, FX timing, partial-shipment splits, and manual journal entries all create temporary imbalances. The book-keeping convention is to clear them at period-close via Intercompany Elimination entries. Mid-period, some imbalance is normal. My imbalance is $1m on a$20m intercompany trade. How worried should I be? 5% imbalance is at the upper-end of normal. >10% sustained = audit attention. Investigation is mandatory if the imbalance has been growing month-over-month. A $100k imbalance on goods-in-transit, will it self-resolve? Yes, when the receiving subsidiary posts the goods receipt + AP. Vortex IQ does not force-resolve; the merchant’s accounting workflow does. If the imbalance is still there 14 days after expected receipt, investigate. Can I see this per-currency-pair? Yes via Ask Viq. Particularly useful for cross-currency trades where FX-timing-driven imbalances are systematic. My OneWorld account has 12 subsidiaries. How is this shown? 12 subsidiaries → 66 possible pairs. Vortex IQ shows the top 10 pairs by absolute imbalance plus a “remainder” rolled-up row. Toggle to all-pairs view via the column toolbar. Period-close is delayed because of intercompany. What’s the playbook? Three steps: (1) Identify the largest imbalance pair. (2) Pull the per-transaction list for that pair, comparing AR side to AP side. (3) Post the missing entries (goods receipts on the receiving side, FX adjustments where rates have moved). Most period-close intercompany clean-up is 30 to 90 minutes of work if the team practiced; can stretch to half a day on first attempt. The card shows $0 imbalance but I know we have intercompany activity. What’s wrong? Either (a) the activity is balanced (most healthy multinationals run near-zero between trade pairs), (b) the eliminations have already posted, or (c) the manifest filter is excluding the relevant transaction types. Open the Intercompany Reconciliation Report in NS to confirm. Should sub-customer trades count as intercompany? No. Intercompany is between subsidiaries (legal entities). Sub-customer trades within a subsidiary are intra-subsidiary and don’t appear here. My consolidation engine throws an “intercompany out of balance” error at close. How does this card help? This card surfaces the imbalance proactively, before close. Run it weekly during the month; if the imbalance is growing, address it incrementally rather than scrambling at month-end. Many controllers schedule a Friday 4pm intercompany check and clear any week-old imbalances each week. Why does the AR side and AP side differ when the same trade is on both books? Three reasons: (1) FX rate timing (each side records at its local-currency rate at its own posting date); (2) goods-receipt timing (AP doesn’t post until receipt); (3) credit-memo timing (one side issues a memo before the other side processes it). Each is normal individually; the card’s value is highlighting where the gap is large enough to warrant investigation.

---

​

Tracked live in Vortex IQ Nerve Centre

Intercompany Balance is one of hundreds of KPI pulses Vortex IQ tracks across NetSuite and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.