NetSuite OneWorld: Customer or Vendor Not Available for Subsidiary
NetSuite OneWorld customer or vendor not available for subsidiary on transaction
Also searched as
- NetSuite vendor not showing in subsidiary dropdown
- NetSuite customer cannot be selected on transaction different subsidiary
- NetSuite OneWorld add subsidiary to customer record
- NetSuite invalid subsidiary reference on transaction
Short answer
In NetSuite OneWorld a customer, vendor, partner or contact can be used only on transactions in subsidiaries it is assigned to. If it does not appear in the dropdown or the save fails on subsidiary validation, add the subsidiary on the entity's Subsidiaries sublist and make sure a transaction currency is available for that relationship.
Applies to: NetSuite OneWorld accounts with more than one subsidiary; customer, vendor, partner and employee records; sales, purchase and journal transactions
How to fix an entity missing for a subsidiary
- 1Open the customer or vendor record (Lists > Relationships > Customers or Vendors) and note the Primary Subsidiary on the Financial or Primary Information section.
- 2Go to the Subsidiaries subtab or sublist on the entity and check which subsidiaries are listed. Add the transaction's subsidiary with the plus sign and save.
- 3Check the Currencies sublist. A transaction in a subsidiary uses a currency that the entity must allow; add the currency if the transaction currency is missing.
- 4Confirm the user has access to that subsidiary. Check the role's Subsidiary restrictions under Setup > Users/Roles > Manage Roles, and the user's own subsidiary restriction setting.
- 5On the transaction, set the Subsidiary field first, then choose the entity. The entity list filters by the subsidiary chosen at that moment.
- 6For vendors used across many subsidiaries, consider Multi-Subsidiary Vendor if the feature is enabled in Setup > Company > Enable Features > Accounting.
- 7For customers, use Multi-Subsidiary Customer where enabled, which lets one customer record serve several subsidiaries without duplicate records.
- 8Retry the transaction. If the error persists, check that the item, location and department are also valid for the subsidiary.
How entity sharing works in OneWorld
Each entity has a Primary Subsidiary that owns it. By default an entity can only be used on transactions for its own subsidiary and that subsidiary's children, depending on how the entity is shared. This keeps books, tax and access separate across legal entities.
With the Multi-Subsidiary Customer and Multi-Subsidiary Vendor features, an entity can be shared with additional subsidiaries through its Subsidiaries sublist. Each subsidiary row is a separate relationship. NetSuite also holds currency per relationship, so a vendor shared with two subsidiaries may trade in different currencies in each.
Without the multi-subsidiary features, the only way to use a customer in a different subsidiary is to create another customer record. Many accounts end up with duplicate customers for this reason, which complicates consolidated reporting and credit control.
Subsidiary on the transaction versus entity
A transaction takes its subsidiary from one of two places. On sales transactions it typically comes from the customer's primary subsidiary, or from the user's default subsidiary if the form allows editing. On purchase transactions it follows the vendor. If you change the Subsidiary field after picking the entity, the entity may become invalid and the save fails.
Users often hit this on intercompany or shared service scenarios: a shared service centre in one subsidiary raises a bill for a vendor owned by another. For those cases, create the transaction in the subsidiary that owns the vendor or share the vendor, then use intercompany transactions to allocate cost across subsidiaries.
The error can also come from a scripted or imported record where the subsidiary column is wrong. A CSV import that sets the entity but not the subsidiary will use defaults, and the combination fails validation.
Currency and role restrictions that cause the same symptom
A customer or vendor may be shared with the subsidiary but still missing from the dropdown because the entity currency list excludes the subsidiary's base currency or the transaction's currency. Add the currency under the Currencies sublist of the entity.
Role restrictions are a common hidden cause. A role limited to certain subsidiaries only sees entities shared with those subsidiaries. A user with Sales Rep restrictions may see only customers assigned to them. Compare with an administrator view before changing data.
Inactive entities, entities with Hold status and entities on a different custom form can also vanish from lists. Check the Inactive box and the Search filters on the field's Customer Lookup.
Bulk fixes
To share many entities with a new subsidiary, use a CSV import for Customers or Vendors with the Subsidiary sublist mapped, or a saved search plus mass update where supported. Test on a small batch in a sandbox before production.
When creating a new subsidiary, plan entity sharing first. Decide which customers and vendors are global and share them at creation, rather than asking users to ask for access after the fact.
Common pitfalls
- !Picking the entity before the subsidiary, then changing the subsidiary and invalidating the entity.
- !Creating duplicate customer records per subsidiary instead of enabling Multi-Subsidiary Customer.
- !Forgetting the Currencies sublist so the transaction currency is not allowed for the entity.
- !Debugging as administrator when the real limit is the user's role subsidiary restriction.
- !Importing transactions with an entity but without the subsidiary column.
- !Sharing a vendor to a subsidiary without checking tax registration and payment terms for that relationship.
How an ERP-grounded AI assistant handles this
An assistant grounded in your NetSuite account can compare the entity's Subsidiaries and Currencies sublists with the transaction's subsidiary and the user's role restrictions, then say which of the three blocks the save. ERPray is read-only by default and respects NetSuite roles, so it tells you what to add and where, and your admin makes the change.
Frequently asked questions
Why is a vendor missing only for some users?
Role subsidiary restrictions and entity sharing combine. A user can only select entities shared with subsidiaries their role can access. Compare what an administrator sees to what the user sees and check the role's subsidiary list.
Do I need Multi-Subsidiary Customer to fix this?
Not for a one-off. You can add the subsidiary on the Subsidiaries sublist only when the feature allows sharing. If it is disabled, the alternative is a separate customer record. Weigh the cleaner data model of enabling the feature against the change effort.
Can I change a customer's primary subsidiary?
Yes in many cases, but existing transactions stay in their original subsidiaries and some restrictions apply when the customer has activity. Test in sandbox, and review open transactions, credit limits and tax setup before changing a primary subsidiary.
Does this affect intercompany transactions?
Intercompany transactions use internal vendor and customer records that represent the other subsidiary. Those are created by NetSuite for each subsidiary pair. If they are missing from a dropdown, check the subsidiary's intercompany setup rather than the normal sharing list.
Related
How to run intercompany transactions in NetSuite (OneWorld)
Enable the Intercompany Framework and Automated Intercompany Management features (Setup > Company > Enable Features > Company), then create an Intercompany Sales Order or Purchase Order between two subsidiaries in the same NetSuite account; NetSuite auto-generates the matching intercompany transaction on the counterparty subsidiary and posts the elimination journal entries during period close if Advanced Intercompany Journal Entries is also enabled.
Error fixFix NetSuite INSUFFICIENT_PERMISSION Error
INSUFFICIENT_PERMISSION means the role executing the request, whether a logged-in user or the role behind a script deployment, lacks a specific permission needed for the record type, transaction type, or subsidiary being accessed. Fix it by checking the role's permission list under Setup > Users/Roles > Manage Roles against the exact record and level (View, Create, Edit, or Full) the operation requires.
Error fixFix NetSuite INVALID_KEY_OR_REF Error
INVALID_KEY_OR_REF fires when NetSuite cannot resolve a key used to reference another record, most commonly a parent record id on record.create's initial defaultValues, a joined internal id in a saved search filter, or a foreign key style reference in a CSV import mapping, because that id does not exist, is inactive, or is not visible in the current role or subsidiary context. Fix it by confirming the referenced internal id actually exists and is accessible before the reference is used, rather than assuming a previously valid id is still good.
How-toHow to Import CSV Data Into NetSuite Reliably
NetSuite's CSV Import Assistant, under Setup > Import/Export > Import CSV Records, maps spreadsheet columns to record fields, matches existing records by internal ID or a chosen field, and can create, update, or upsert in a single run. The most reliable imports use a saved import map, reference records by internal ID where possible, and stage the file with a header row that exactly matches expected column types.
Error fixFix NetSuite SSS_USAGE_LIMIT_EXCEEDED Error
SSS_USAGE_LIMIT_EXCEEDED fires when a SuiteScript execution consumes all the governance units (usage points) allotted to its script type before it finishes. Fix it by checking runtime.getCurrentScript().getRemainingUsage() before expensive calls, yielding or rescheduling in Scheduled scripts, and moving heavy record-count work into Map/Reduce, which yields automatically across stages.
Error fixFix NetSuite INVALID_FLD_VALUE Error
INVALID_FLD_VALUE means NetSuite rejected a value you tried to set on a field because it does not match the field's expected type, list option, or reference record. Fix it by confirming the internal ID or text value actually exists on that field's source list and matches the field's value type (text versus list versus record reference) before setting it.
AI for ERPAI for NetSuite OneWorld Multi-Subsidiary Consolidation
Grounded AI for NetSuite OneWorld consolidation: intercompany, elimination, and multi-subsidiary questions answered through SuiteQL, without sending financial data to a public model.
Stuck on Oracle NetSuite?
Talk to engineers who work inside Oracle NetSuite every week, and who build private AI that answers these questions from your own ERP data.