Revenue split across NetSuite OneWorld subsidiaries. Available only when OneWorld is enabled.
At a glance
Revenue Booked into GL split by NetSuite Subsidiary. The OneWorld card that exposes which subsidiary is driving (or dragging) consolidated performance.
| What it counts | SUM(Transaction.Amount) for revenue accounts grouped by Subsidiary for the period. |
| Tax treatment | Net of tax across every subsidiary regardless of local tax engine. |
| Shipping | Included if mapped to revenue. |
| Refunds / Credit Memos | Deducted within each subsidiary. |
| Currency | Each subsidiary shown in its base currency on the bar chart, with reporting-currency consolidation row. |
| Intercompany | Inter-co revenue appears in each booking subsidiary; eliminations apply on the consolidated row. |
| Subsidiary scope | All subsidiaries the role can read. |
| Time window | 30D |
| Alert trigger | Variance > 20% per subsidiary vsP, surfaced as per-row warning. |
| Roles | owner, finance |
| Only-when gate | OneWorld accounts only. Single-subsidiary accounts hide this card. |
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 UK omnichannel apparel brand on NetSuite OneWorld. 30-day window 14 Mar 26 to 12 Apr 26.| Subsidiary | Local revenue | FX rate | GBP equivalent | vsP |
|---|---|---|---|---|
| UK Retail Ltd (parent) | £2,840,000 | 1.0000 | £2,840,000 | +5.2% |
| US Retail Inc | $1,920,000 | 0.7820 | £1,501,440 | +12.4% |
| EU DTC BV | €1,180,000 | 0.8540 | £1,007,720 | -8.7% |
| Less: intercompany elimination | (£162,000) | n/a | ||
| Total Consolidated | £5,187,160 | +2.1% |
- EU DTC BV is dragging. Down 8.7% vsP on a consolidated +2.1%. The card flags this as a per-row warning. The Controller drills in: is it FX (EUR weakened), seasonal (EU spring lags UK), or operational (a marketing campaign was paused)?
- US Retail Inc is the growth driver (+12.4%). New distributor onboarding in March added wholesale revenue. The card lets the Controller validate that growth is sustainable rather than a one-off.
- The £162K intercompany elimination is invisible at the per-subsidiary level. UK Retail Ltd’s local books show £3M (including £162K inter-co); the consolidated row removes it. The card surfaces both views.
- Showing local currency alongside reporting currency prevents Controller mistakes. A £1.5M GBP equivalent for US could mean either 2.1M of growth weakened by FX; the card shows both.
- The consolidated +2.1% understates the operational underlying growth. EU FX losses dragged the total down. If GBP/EUR had stayed flat YoY, the consolidated would have been +3.6%. The Currency Exposure card breaks down FX impact.
Sibling cards merchants should reference together
| Card | Why pair it with Revenue by Subsidiary |
|---|---|
| Revenue Booked into GL | The consolidated total. This card decomposes it by subsidiary. |
| Revenue by Currency | The currency-mix view. Often correlates 1:1 with subsidiary on OneWorld. |
| Revenue by Class | The Class dimension cut. Most actionable when subsidiaries are similar but business units differ. |
| Subsidiary Performance | The full health card per subsidiary (revenue + margin + AR + inventory). |
| Currency Exposure | FX risk view. |
| Intercompany Balance | Inter-co receivables/payables by subsidiary pair. |
| Top Findings Across Subsidiaries | The action list at consolidated level. |
Reconciling against the vendor’s own dashboard
Where to look in NetSuite:Reports → Financial → Income Statement with subsidiary group-by enabled Reports → Sales → Sales by SubsidiaryThe Sales by Subsidiary report is the closest native equivalent. The Income Statement with subsidiary breakdown gives the same data with full GL classification. Why our number may legitimately differ from NetSuite reports:
| Reason | Direction | Why |
|---|---|---|
| Elimination cadence | Either | NetSuite consolidates at month-end; the card runs continuously. Mid-month inter-co transactions may show differently between the two views. |
| FX rate cadence | Small | Card uses transaction-date rates; report may use period-average. |
| Reporting hierarchy | Either | If your account uses sub-of-sub structures, NetSuite’s report can roll up at any level; the card shows the leaf-level subsidiary. |
| Permissions | Card may show fewer subs | Card respects role permissions. If the user can’t see a subsidiary, it’s hidden. |
| Card | Relationship | Why |
|---|---|---|
| shopify.total_revenue (per Shopify store tagged to a subsidiary) | Should track per subsidiary | Each Shopify store typically maps to one NetSuite subsidiary. Compare per-sub. |
| bigcommerce.total_revenue | As above | Per-store mapping. |
Known limitations / merchant FAQs
OneWorld required? Yes. Single-subsidiary accounts hide this card; the data shape is meaningless. Why does my US sub show high vsP variance even though sales feel similar? FX. If GBP/USD swung 5% during the period, US revenue translated to GBP looks ~5% different. The card shows local-currency growth in tooltip; trust that for operational reading. Intercompany sales, why do they appear in the source subsidiary? Because NetSuite books them in the source’s GL. Eliminations apply only at consolidation. The card shows both views: per-sub (with inter-co) and consolidated (with elimination). Do hidden subsidiaries (inactive) appear? No. Card respects subsidiaryIsInactive = F. Reactivate the subsidiary if you need it tracked.
Permissions, what controls visibility?
NetSuite role permissions. If the connected role can’t read the subsidiary, the card hides it. Common gotcha: connector role created with subsidiary-specific permissions. Use a global role for full visibility.
Can I see a single subsidiary’s full breakdown elsewhere?
Yes. Filter the entire dashboard to a single subsidiary; every card scopes accordingly. This card collapses to a single bar.
Multi-currency consolidated rate, what’s used?
Period-average for the consolidated row by default. Configurable to period-end via field map. NetSuite’s Revenue Recognition typically uses transaction-date rates; consolidation uses period-average.
ASC 606 deferred revenue per subsidiary?
Reflected. Each subsidiary’s recognised revenue is what posts to its GL. Deferred revenue sits on each subsidiary’s Balance Sheet separately.