Study guide

3.2 Classifications and Subsidiaries

Oracle NetSuite SuiteFoundation Specialist Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction and Exam Facts

1.1 Current Exam Facts 1.2 The 2025 Program Change and Keeping the Credential 1.3 The Five Weighted Domains and How to Study Them

2 Enable Features and Renaming Records

2.1 What Enable Features Controls 2.2 Renaming Records and Transactions

3 Support-Only Features and Classifications

3.1 Features That Need NetSuite Support 3.2 Classifications and Subsidiaries

4 SuiteBuilder and Platform Tools

4.1 Custom Forms, Fields, Records, and Subtabs 4.2 Bundles, SuiteApps, and SuiteFlow

5 Navigation, Performance, and Preferences

5.1 Roles, Centers, and Navigation Tools 5.2 Browser Experience and Performance 5.3 User Preferences That Change the Interface

6 Shortcuts, Activities, and the File Cabinet

6.1 Shortcuts Portlet versus the Shortcuts Menu 6.2 Activities, Email, and the File Cabinet

7 Sales Cycle, Quotas, and Forecasts

7.1 Setting Up Sales Force Automation 7.2 Leads, Prospects, and Customers 7.3 Quotas and Forecast Reporting

8 Cases and Marketing Campaigns

8.1 Case Management Setup and Use 8.2 Campaigns and SuitePromotions

9 Sales Orders, Fulfillment, and Payments

9.1 Sales Orders and General Ledger Impact 9.2 Fulfillment Controls 9.3 Customer Payment Methods

10 Returns, Credits, and Refunds

10.1 Return Authorization Forms and Ledger Impact 10.2 Return Controls and Refunds

11 Item Types and Inventory

11.1 Item Types and Best Uses 11.2 How Transactions Change Inventory Levels 11.3 Advanced Inventory Features

12 Pricing, Billable Costs, and Payables

12.1 Sales Pricing Options 12.2 Billable Time and Expenses 12.3 Purchase Approval Routing 12.4 Accounts Payable Steps and Ledger Impact

13 Finding Records and Saved Searches

13.1 Global Search, Lists, and Reports 13.2 Elements of a Saved Search

14 Portlets and Data Management Tools

14.1 Portlet Types 14.2 Inline Editing, Mass Update, CSV, and Duplicates

15 Support, Help Resources, and Releases

15.1 Working with NetSuite Support 15.2 Where to Look Up a Feature 15.3 Release Cycles and Release Preview

16 Custom Roles and Data Access

16.1 What a Custom Role Can See and Do 16.2 Building Roles Instead of Sharing Administrator

17 Authentication, Security Questions, and Settings

17.1 Passwords and Two-Factor Authentication 17.2 Security Questions 17.3 The Settings Portlet

18 Tracking Changes to Records

18.1 System Notes and Other Audit Tools 18.2 Ledger Impact and Field-Type Changes

3.2 Classifications and Subsidiaries

Key Takeaways Explain This Topic AI

In a NetSuite OneWorld account, Subsidiary is the primary classification used to organize records, and each subsidiary is a separate legal entity.

Department tracks an internal team such as Sales or Finance, Class tracks a segment the company defines, and Location tracks a place such as a warehouse or office.

A location on a transaction is a classification. It is not the same switch as the Multi-Location Inventory feature.

Department, class, location, and subsidiary can appear on the same transaction and drive financial reports, saved searches, budgets, role restrictions, and commission schedules.

A general ledger account records the chart-of-accounts line and does not replace class or department.

Last updated: September 2026

The March 2024 SuiteFoundation study guide asks for the general functionality of classifications and subsidiaries on transactions and reporting. The study method names five things to compare: Departments, Classes, Locations, Subsidiaries, and Accounts. It also asks how department, class, and location behave in reports, searches, budgets, roles, and commissions, and how those dimensions differ from one another. The October 2024 sample marks one sentence as the point to remember. In a NetSuite OneWorld account, Subsidiary is the primary classification used to organize records. Oracle NetSuite Help says the same thing on the Classifications Overview page.

Subsidiary is the primary classification

A Subsidiary is a legal entity in OneWorld, not a department with a different label. OneWorld organizes domestic and international subsidiaries in a hierarchy under a root parent. Each subsidiary is treated as its own legal entity for taxation and regulation. Each has a tax nexus and a base currency, which is the currency in which that subsidiary manages its financials. Help says to create a subsidiary record for each legal entity, and also to create elimination subsidiaries where consolidated financials need them. When an account is upgraded to OneWorld, preexisting data becomes the root subsidiary.

Transactions and many other records belong to a subsidiary. Help says each OneWorld transaction generally posts to a single subsidiary. The exception is a transaction between two or more subsidiaries, such as an intercompany sale or purchase. Those transactions post to more than one subsidiary, and consolidation uses elimination journal entries so the combined financials stay balanced. Subsidiary-specific results can be reported on their own, and data for several subsidiaries can roll into consolidated reports in the parent subsidiary's currency. A department cannot carry that structure. A department does not have a base currency, a country-driven tax nexus, or an elimination subsidiary.

How a subsidiary differs from a department

If a team says the UK office is only a department, so the account does not need a UK subsidiary, the legal-entity reports and the currency of the books will be wrong even when a department filter looks busy. Departments, classes, locations, and custom segments are used along with subsidiaries. Help says that if you use those classifications, you must associate each one with a subsidiary. That association is what lets a user select the department, class, location, or custom segment on a record or transaction for that subsidiary. A class that belongs only to the US subsidiary does not appear on a transaction for the Canada subsidiary.

Subsidiary restrictions on a role also narrow which departments a user can reach. Help notes that if a department is assigned only to one subsidiary, and a role is restricted to that subsidiary, users with the role can reach that department even when the role has no separate department restriction. The legal entity still comes first. Custom segments can add more classification fields that behave in a similar way, and the exam objective still expects you to know the standard four before you reach for a custom segment.

Department, class, and location

Department is a functional area, the internal team that owns the activity. Help describes departments as categories an administrator creates to identify and track financials, transactions, and employees. There is no fixed limit on how many you can create. Typical departments are Sales, Marketing, and Accounting, which is the cost-center idea the study guide expects: sales, finance, and the other functional teams. Departments are shown first on transactions. An administrator enables Departments, Classes, and Locations from the Company subtab of Enable Features, at Setup > Company > Setup Tasks > Enable Features. Department records are created at Setup > Company > Departments > New. Once they exist, you can track income and expense by department for any period, and sales forecasting can use the Forecast vs. Quota by Department report. Employees can be identified by department. None of that makes the department a legal entity.

Class is another reporting dimension, and the company chooses what it means. Help says classes organize broader segments of the business. The Help example is a sales department that uses classes for new customers and repeat customers, so a sales order shows which kind of customer produced the income. Product line and sales channel are equally common meanings, and they are the meanings a controller often needs on financial reports. NetSuite does not reserve the class list for one industry definition. Create classes at Setup > Company > Classes > New. What matters is that class is not department and not location. If the business wants both a cost center and a product line, those two facts need two dimensions. Putting both meanings in one list destroys one of the reports.

Location is a place, such as a warehouse, a sales office, or a corporate office. The Locations feature lets an administrator track employees and transactions for those places, associate transactions and employees with a location, and filter report data by location. Enable it at Setup > Company > Enable Features, on the Company subtab, by checking Locations and saving. Then create a location record for each place you want to track. You can group sales, purchases, and bank activity such as checks, deposits, and credit card charges by location, and you can search for transactions associated with a location. Parent and child locations can group offices, for example an East Coast parent with child locations for particular cities. Help still wants each location to be a real place, not a bin, shelf, or dock inside a warehouse.

Location is not Multi-Location Inventory

Location as a classification is not the Multi-Location Inventory feature from the previous section. A location on a sales order can categorize the transaction and filter a sales report when you are only answering which office was involved. Associating item quantities with a location, receiving into several locations, fulfilling from a distinct location, and transferring items between locations are Multi-Location Inventory capabilities. Help says you must enable Multi-Location Inventory to associate items with a location, and that OneWorld accounts using Inventory are required to use that feature. You can still have location records as a classification for employees and transactions. Checking Locations does not distribute on-hand quantities. A warehouse named on a transaction is not the same decision as the inventory feature that Customer Support must turn off after items have been distributed.

These values can appear together on one transaction. A single invoice can name the legal entity, the cost-center department, the product-line class, and the shipping warehouse. Financial reports, saved searches, and budgets read those fields separately. That independence is the reason the dimensions exist. If two business facts share one field, you cannot report them separately later.

Classification What it represents Required for the OneWorld legal structure? Reporting example

Subsidiary A separate legal entity, with its own nexus and base currency Yes. It is the primary classification in OneWorld A subsidiary income statement, with consolidation at a parent

Department An internal team or functional area, such as Sales or Finance No Income and expense for the Finance department over a period

Class A segment the company defines, such as a product line, a channel, or new versus repeat customers No Profit for one product line

Location A physical place, such as a warehouse or office No. The place is not the legal entity Sales or purchases filtered to one warehouse