How do I map NetSuite subsidiaries for consolidation during close?

Loopfour's NetSuite integration tags every record it creates with a subsidiaryId field. Since each OneWorld transaction posts to one subsidiary unless it's an explicit intercompany transaction, getting that field right on every record is what determines whether NetSuite's own consolidation and elimination process at close produces a correct result.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 14, 2026Last reviewed September 14, 2026Editorial policy

Part of the finance integrations guide.

What field controls this	subsidiaryId, passed on createCustomer, createInvoice, createVendorBill, and the generic createRecord action
NetSuite's own subsidiary limit	Up to 250 subsidiaries per OneWorld account; elimination subsidiaries don't count toward that limit
Default transaction behavior	A transaction posts to a single subsidiary unless it's an explicit intercompany transaction (sale, purchase, inventory transfer, cross-subsidiary fulfillment)
What consumes this downstream	NetSuite's own Intercompany Elimination process during close reads whatever subsidiary each record was tagged with

Why subsidiary tagging is a workflow's job, not NetSuite's

NetSuite OneWorld manages a hierarchical structure of separate legal entities — subsidiaries — organized as a tree that rolls up to a root, top-level parent. NetSuite doesn't infer which subsidiary a record belongs to; the subsidiary has to be set explicitly on the record at creation. For a workflow, that means every action that creates a customer, invoice, vendor bill, or generic record accepts a subsidiaryId parameter, and it's the workflow's responsibility to pass the correct one — NetSuite will accept whatever subsidiary it's given, correct or not.

Setting up the subsidiaries themselves

Subsidiary records have to be created in NetSuite before any workflow can reference them — top-down, starting with the root subsidiary and working through its children. Each subsidiary record carries a name, its parent ("Subsidiary of"), state/province and country, legal name as it appears on tax documents, base currency, and tax identification numbers. An elimination subsidiary — used only for the intercompany journal entries that reverse transactions between subsidiaries — is a separate checkbox on the same record type, not a different kind of record.

What happens with the wrong subsidiary

A record created with the wrong subsidiaryId doesn't error — it posts successfully, just to the wrong entity. That's exactly the kind of input NetSuite's Intercompany Elimination process and consolidated exchange rate handling assume is correct when they run at close; a workflow that's been silently tagging records to the wrong subsidiary for weeks is what produces the intercompany elimination and consolidated exchange rate problems covered elsewhere in this cluster — this page is about preventing that input error, not diagnosing it after the fact.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Field mapping

Where subsidiaryId is required across Loopfour's NetSuite actions

Action	subsidiaryId behavior
createCustomer	Sets the customer's primary subsidiary; a Multi-Subsidiary Customer setup can assign secondary subsidiaries afterward
createInvoice	Determines which subsidiary the transaction posts to; defaults to the customer's primary subsidiary if omitted
createVendorBill	Same pattern, on the vendor side
createRecord (generic)	Accepts subsidiaryId for any record type that supports it, including custom records

Frequently Asked Questions

No. A record with an incorrect subsidiaryId posts successfully — it just posts to the wrong entity, which surfaces later as a consolidation or elimination problem rather than an immediate error.

A subsidiary used only for the intercompany journal entries that reverse transactions between subsidiaries at consolidation. It's created the same way as any other subsidiary, with an additional checkbox, and doesn't count toward NetSuite's 250-subsidiary limit.

NetSuite's Multi-Subsidiary Customer feature lets one customer record be shared across subsidiaries, with a default subsidiary on the record and the option to select a different assigned subsidiary on individual transactions.

Sources

Topic

Month-End Close

Month-end close is the set of accounting tasks a company runs after a calendar month ends to turn raw transactions into a finished, trustworthy set of financial statements: reconciling subledgers, boo…

How-to

How do I run intercompany elimination during period close in NetSuite?

Complete currency revaluation for every subsidiary first, then run NetSuite's Intercompany Elimination process, which nets out intercompany receivables, payables, and transactions so they don't double-count in the consolidated financials. Any currency revaluation left undone before elimination runs is the most common reason a residual balance is left over afterward.

Diagnostic

Why is my consolidated exchange rate wrong in OneWorld close?

Most commonly, the Consolidated Exchange Rates table wasn't updated for the current period before consolidation ran, or the wrong rate type (Current, Average, or Historical) was applied for the account being translated. Both cause child-subsidiary amounts to roll up incorrectly into the parent's consolidated financials.

Topic

Integrations

Every finance automation vendor publishes an integrations page: a grid of logos, a claim of "seamless" connectivity, and not much else. That page answers a marketing question — does this vendor touch…