NetSuite Subsidiary Setup for Asset Acquisitions
Learn how to set up NetSuite subsidiaries for asset acquisitions without legal entity changes.
Sarah Jenkins, CPAPrincipal Finance Automation Specialist
On this page
When Company A acquires Company B through an asset deal, the legal entity disappears but the reporting need doesn't. You still need to track revenue, expenses, and customer activity by the original business unit, for management reporting, earn-out calculations, or simply understanding which acquisition is performing. NetSuite handles this through its subsidiary architecture, even when no legal subsidiary exists. The key is configuring a reporting subsidiary that mirrors the acquired operation without creating compliance risk.
Why a Reporting Subsidiary Works Here
NetSuite subsidiaries are management constructs first, legal entities second. A subsidiary record in OneWorld carries a Legal Name field and an Is Inactive checkbox, but nothing forces you to file tax returns for it. For an asset acquisition, you create a subsidiary under Company A's hierarchy, mark it as non-elimination (unless you're booking intercompany transactions), and use it as a reporting container. This gives you:
- Separate P&L and balance sheet views via the Subsidiary filter on financial reports
- Distinct posting periods and lock dates if the acquired business closes on a different calendar
- Isolated audit trails for earn-out or purchase-price allocation work
The alternative, using only classes or departments, breaks down when you need subsidiary-level features: separate charts of accounts, nexus configurations, or consolidation eliminations. Classes can't own bank accounts or run their own AP/AR aging.
The Elimination Subsidiary checkbox is the most common misstep. Leave it unchecked unless you're actually booking intercompany journals between Company A and the acquisition entity. Most asset deals don't need this.
Creating the Acquisition Subsidiary
Navigate to Setup > Company > Subsidiaries > New. Complete these fields with intention:
| Field | Recommendation for Asset Acquisition |
|---|---|
| Legal Name | "Company B (Acquisition)", signals purpose to auditors |
| Subsidiary of | Company A (parent) |
| Currency | Match Company A unless the acquired ops used a different functional currency |
| Fiscal Calendar | Align with Company A unless earn-out requires separate period ends |
| Elimination Subsidiary | Unchecked, no intercompany eliminations needed for pure asset deals |
| Always Display Subsidiary Name | Checked, forces the name onto transactions for clarity |
After saving, edit the subsidiary record to configure Nexus. Open the subsidiary record and select the Nexus subtab. Even if the acquired entity has no legal nexus, assign the same nexus as Company A so tax calculations work on transactions posted to this subsidiary. If the acquisition operates in states where Company A didn't previously have nexus, add those now, this is where the acquisition creates new filing obligations.
Handling Shared Customers
The discussion notes "many of the same customers already." This is the operational friction point. You have three options:
Option 1: Single customer record, multi-subsidiary access Keep one customer record in Company A. On the customer record's Access subtab, grant access to both subsidiaries. Transactions post to the subsidiary selected on the transaction form. Risk: users accidentally post to the wrong subsidiary. Mitigation: use SuiteFlow to default the subsidiary based on the user's role or a custom "Acquisition Source" field.
Option 2: Duplicate customer records per subsidiary Create "Customer X - Company A" and "Customer X - Company B" as separate records. Clean for reporting, painful for AR aging and collections. You'll need a saved search to consolidate aging across both records.
Option 3: Multi-Subsidiary Customer feature Enable Multi Subsidiary Customer at Setup > Company > Enable Features (Transactions tab). This lets you assign a primary subsidiary and additional subsidiaries on a single customer record. The primary subsidiary drives default currency and tax treatment; additional subsidiaries allow posting transactions to the acquisition entity without duplicating the customer master. This is the cleanest for shared customers, but requires the feature enabled and disciplined subsidiary assignment on each transaction.
For most asset acquisitions, Option 3 balances reporting clarity with AR manageability. Set it up at Lists > Relationships > Customers > [customer] > Classification subtab > Primary Subsidiary and Additional Subsidiaries.
Posting Transactions to the Acquisition Subsidiary
Users must consciously select the subsidiary on every transaction. The Subsidiary field appears on:
- Sales Orders, Invoices, Cash Sales
- Purchase Orders, Vendor Bills
- Journal Entries
- Bank Deposits, Payments
Train the team: "If the work relates to the acquired business, pick 'Company B (Acquisition)'." For journals, consider a Saved Search that flags entries posted to the acquisition subsidiary without a memo referencing the acquisition, catches misposts early.
If volume is high, use CSV Import (Setup > Import/Export > Import CSV Records) with the subsidiary column mapped to the acquisition subsidiary's internal ID. Find the ID at Setup > Company > Subsidiaries > [subsidiary] > URL (the id= parameter).
Reporting: Separate Views, Consolidated Reality
The payoff comes at month-end. Run these reports filtered to the acquisition subsidiary:
- Income Statement (Reports > Financial > Income Statement), subsidiary filter isolates acquired revenue/expense
- Balance Sheet (Reports > Financial > Balance Sheet), tracks goodwill, fixed assets, and working capital from the purchase
- AR Aging (Reports > Customers/Receivables > A/R Aging), subsidiary filter shows only acquisition receivables
- Trial Balance (Reports > Financial > Trial Balance), the auditor's starting point for purchase-price allocation testing
For consolidated views, run the same reports without a subsidiary filter. NetSuite OneWorld consolidates automatically up the hierarchy, no elimination entries needed since you unchecked "Elimination Subsidiary." The Subsidiary Context list in the report footer lets you toggle between individual and consolidated views instantly.
What to Validate Before Go-Live
- Posting periods: Confirm the acquisition subsidiary's open periods match Company A at Setup > Accounting > Manage Accounting Periods. A mismatch blocks transaction entry.
- Account mapping: If the acquired business used a different chart of accounts, map those accounts to Company A's structure via Setup > Accounting > Chart of Accounts > [account] > Subsidiary Overrides. This keeps consolidated reporting clean while preserving subsidiary-level detail.
- Role permissions: At Setup > Users/Roles > Roles, ensure finance users have Subsidiary Access set to "All" or explicitly include the new subsidiary. Restrict AP/AR clerks to their operating subsidiary unless they genuinely process both.
- Bank accounts: If the acquisition brought bank accounts, add them at Setup > Accounting > Bank Accounts > New with the acquisition subsidiary selected. This enables proper reconciliation by entity.
The Control That Matters
From an audit perspective, the control is subsidiary assignment discipline. Every transaction carries a subsidiary tag. If that tag is wrong, your acquisition P&L is wrong, and no elimination entry fixes it because you're not eliminating. Build a monthly validation: a saved search showing transaction count and amount by subsidiary, reviewed by the controller. Flag any month where the acquisition subsidiary drops below a materiality threshold (e.g., $0 revenue for an operating business).
This isn't just configuration, it's the difference between a clean earn-out calculation and a spreadsheet reconciliation that takes two weeks. Your auditors will thank you for the subsidiary-level trial balance. The acquisition team will thank you for the separate P&L. And you'll close the books in days, not weeks, because the structure does the segregation automatically.
