Services · Streamline & Outsource

NetSuite subsidiary access configuration

Set which subsidiaries each role can view and work with across your OneWorld account. Configure access deliberately for every role, from group finance’s full view to a branch operator’s access to one entity, so permissions match the way your group is governed.

Entity reach per roleGroup and local, both served
The problem

In OneWorld, access has a second question: which subsidiary?

A role may have permission to view invoices, but subsidiary access determines whose invoices it can see. Poorly configured entity access can expose a German payroll vendor to the UK team, allow a group analyst to post to the wrong books or undermine local autonomy. We configure subsidiary access deliberately, matching each role’s reach to the way your group is governed.

What we run

How we configure subsidiary access in NetSuite

The work is run by our consultants inside your account, with every change visible to you as it happens. Approvals and authority stay with your team.

  • Entity-access mappingWe map each role’s legitimate reach – whether that is one entity, a regional group or the whole organisation – based on how responsibilities are managed in practice.
  • Role subsidiary configurationAccess is built to the map, with the platform’s subsidiary restrictions applied through the role architecture to the same standards as our custom role creation work.
  • Cross-entity role designGroup finance, shared services and consolidation roles receive deliberate access across multiple entities. That broader reach is documented and reflects their responsibilities.
  • Posting-boundary protectionWe align transaction access with viewing access, so roles cannot post to subsidiaries outside their approved remit. This protects against both unauthorised viewing and posting to the wrong books.
  • Acquisition onboarding patternNew entities are added to the access model using agreed rules, so acquisitions inherit the group’s governance instead of being configured ad hoc.
  • Entity-access reportingA standing report shows which roles and users can access each entity, so the group can answer audit questions about who can view or change what.

Someone posting into the wrong entity?

We configure NetSuite subsidiary access to match how your group is governed. Talk it through with a senior consultant. It’s free, it takes 30 minutes and there’s no sales pitch.

The payoff

What handing it over buys you

Local users see local data

Entity-scoped roles keep the German vendor invisible to the UK clerk, correctly.

Group roles reach on purpose

Wide access is documented, so the consolidation team is served without sprawl.

Wrong-entity postings stop

Boundary-aligned reach designs out the misposted journal.

Acquisitions inherit the model

Rule-based onboarding governs entity forty-three like entity one.

How handover works

From reach mapping to a governed entity model

  1. Map the reach – responsibility is compared with access, per role, across entities.

  2. Configure the model – subsidiary restrictions are applied through the role architecture.

  3. Protect the boundaries – posting reach is aligned and tested.

  4. Govern & report – changes go through the controlled change process and the reach report stands.

Good to know

What to know before you hand it over

  • !Entity access reflects your group governance. Deciding who can work across entities is an organisational decision. We map it with your owners and configure the system to match.
  • !Intercompany work needs designed reach. Intercompany processes legitimately cross entities, so those roles receive deliberate multi-entity access rather than exceptions. The process side is covered by our intercompany services.
  • !This service assumes your OneWorld structure is already in place. If the entity architecture still needs to be designed, that comes first. Access configuration follows the hierarchy; it does not define it.
Straight answers

Subsidiary Access Configuration FAQs

Can one user work across several entities?
Yes. A user can be given access to multiple subsidiaries through their role where their responsibilities require it. That access is documented, deliberate and reviewed regularly.
Where are NetSuite subsidiary permissions actually set?
On the role, with the employee record alongside it. NetSuite subsidiary permissions work by stating which subsidiaries a role may reach, while the employee’s own subsidiary decides where they sit in the group. Both matter: a correctly built role still gives the wrong reach if the employee record places someone in the wrong entity, so the two are checked together rather than separately.
Do we need OneWorld for this?
Yes, for subsidiary access specifically. Entity reach only exists where the account runs OneWorld, so a single-instance account scopes visibility by department, class and location instead, through the restricted view work. If you are weighing up whether a group structure needs OneWorld at all, that is a wider question than access configuration and the multi-subsidiary pages cover it.
What happens to someone’s access when they move between entities?
It changes with the move, and that is worth planning rather than discovering. A transfer usually means a new home subsidiary on the employee record and often a different role, so reach is reset as part of the change rather than added to what they already had. Leaving the old reach in place is how group-wide access accumulates quietly, which the standing entity-access report is there to catch, and a mover is the moment it is cheapest to put right.
What prevents posting to the wrong entity?
We align transaction access with viewing access, so users can only post within their approved subsidiaries. We test those boundaries in the same way we test restricted views for data leaks.
How do new acquisitions get access set up?
They follow the onboarding pattern. The new entity is added to the access model, and roles are extended according to agreed rules. This keeps access consistent as your OneWorld structure grows.

Last reviewed: 9 November 2026 · Written by the Suite Generation team

Ready to hand this one over?

Tell us what you need and the problems you’re seeing, and we’ll scope the work.

Scoping Call — Sitewide

We reply within 24 hours.

or email hello@suitegeneration.net

Suite Generation is an independent, senior-led NetSuite consultancy. Every project is designed and delivered by consultants at or close to solution-architect level. We don’t resell licences or carry partner targets. Our advice is ours, whether you’re implementing NetSuite, rescuing a stalled project or fixing a system that never delivered.

Independent – no licence resellingSenior-led – solution-architect levelTrusted to fix failed implementations
Talk to a solution architect