# NetSuite OneWorld: Customer or Vendor Not Available for Subsidiary > Source: https://netray.co/erp-help/netsuite-oneworld-entity-not-available-for-subsidiary-error > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind error ## System netsuite ## Erp Oracle NetSuite ## Module OneWorld / Subsidiaries and Entity Sharing ## Query NetSuite OneWorld customer or vendor not available for subsidiary on transaction ## Alternate Queries - 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 ## Applies To NetSuite OneWorld accounts with more than one subsidiary; customer, vendor, partner and employee records; sales, purchase and journal transactions ## Steps ### How to fix an entity missing for a subsidiary **Items:** - Open the customer or vendor record (Lists > Relationships > Customers or Vendors) and note the Primary Subsidiary on the Financial or Primary Information section. - Go 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. - Check 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. - Confirm 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. - On the transaction, set the Subsidiary field first, then choose the entity. The entity list filters by the subsidiary chosen at that moment. - For vendors used across many subsidiaries, consider Multi-Subsidiary Vendor if the feature is enabled in Setup > Company > Enable Features > Accounting. - For customers, use Multi-Subsidiary Customer where enabled, which lets one customer record serve several subsidiaries without duplicate records. - Retry the transaction. If the error persists, check that the item, location and department are also valid for the subsidiary. ## Sections ### How entity sharing works in OneWorld **Body:** 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 **Body:** 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### Why is a vendor missing only for some users? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms NetSuite OneWorld customer subsidiary, NetSuite vendor not showing subsidiary, NetSuite multi-subsidiary customer, NetSuite multi-subsidiary vendor, NetSuite entity subsidiaries sublist, NetSuite invalid subsidiary, NetSuite OneWorld role subsidiary restriction, NetSuite share vendor across subsidiaries --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json