3.2 Classifications and Subsidiaries

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.

Reports, searches, budgets, roles, and commissions

Financial reports are the most visible use. Department reports show income and expense for each internal team across a period you choose. Class on the transaction shows which segment produced the income or the expense, using the meaning the company assigned, whether that meaning is product line, channel, or new versus repeat customers. Location reports and transaction searches filter activity to an office or warehouse. Help's location topic says you can search for transactions associated with a location and filter reports to show data for each location. Subsidiary reporting shows one legal entity, and a parent can roll several subsidiaries into consolidated reports in the parent's currency.

Because the fields are independent, a saved search can require the US subsidiary, the Wholesale department, the Outdoor class, and the Reno location, and return only that slice. A search that could filter on only one of those fields would force the company to pick a single story for every report. The study guide points you at searches for this reason. The classification is useful only if a report or a search can isolate it without destroying the other three.

Budgets use the same dimensions. When you build a budget, Help tells you to select Department, Class, and Location values that are associated with the selected subsidiary. A budget for the US subsidiary can state what Finance may spend, what the Outdoor product line may earn, or what the Reno warehouse is expected to handle, without stuffing those facts into the account name. When the Multiple Budgets feature is enabled, at Setup > Company > Setup Tasks > Enable Features on the Accounting subtab under Advanced Features, each budget needs a category. The category separates budgets that would otherwise share the same class, department, or location. In OneWorld, with Multiple Budgets and Multiple Currencies, a budget category is local or global, which determines the currency used for a subsidiary's budget and actual amounts. The exam point is simpler than the whole budgeting setup. Department, class, location, and subsidiary are real budget dimensions, and they are not synonyms for one another.

Roles and the department restriction the study guide names

Roles decide which slice of those dimensions a person can see. The study guide points candidates to restricting access to records by department. With Departments enabled, go to Setup > Users/Roles > Manage Roles and click Customize, Edit, or New. Department restrictions on the role can limit transaction, employee, partner, and, if you check Apply to Items, item records. They can also limit which departments the user is allowed to assign. The same Restrictions subtab can restrict the role by class or by location. Help documents three useful settings. None, default to own, does not limit which records the user can open. It defaults the field to the user's own department, class, or location. Own, subordinate, and unassigned lets the user reach their own value, child values, and records where the field is empty. Own and subordinates only drops the unassigned records. Allow Viewing lets the user see, but not edit, records outside the restriction, and Help says that setting does not open employee payroll or commission data.

In OneWorld, subsidiary restrictions sit on top of these segment restrictions. A user locked to the Canada subsidiary does not gain the US books because the department restriction was left open. The reverse is also true. A careful department restriction does not create a second legal entity. It only narrows the teams inside the subsidiaries the role may already see. Class and location restrictions follow the same pattern on the Restrictions subtab, so a product-line manager or a warehouse supervisor can be limited without redefining the chart of accounts.

Commissions read the same segments, which is why choosing the wrong dimension changes pay, not just a column heading. On an employee commission schedule, created at Lists > Commissions > Employee Schedules > New, the Categorized by field can be class, item, department, or location. In OneWorld the schedule also asks for a subsidiary. If you categorize by class, NetSuite builds a matrix row for each class, so the rate for one product line can differ from the rate for another. Categorizing by department would instead follow the internal team on the sale. Help uses the example of a class such as a first-time customer: when the sale carries that class, the rep earns the commission defined for it. If the implementer stored customer type in Department and product line in Class, a commission plan written against class would pay on product line, and a plan written against department would pay on customer type. The labels on the schedule would still say department and class. The business meaning would be whatever was loaded into those lists.

A controller who wants four answers from one invoice

A controller at a two-entity distributor wants four views of the same sale. Which legal entity earned it. Which cost center owns the margin. Which product line produced it. Which warehouse shipped it. Assign the fields the way the dimensions are defined. Class holds the product line, because that is the segment the company defines. Location holds the warehouse. Department holds the cost center, such as Wholesale Sales or Finance. Subsidiary holds the legal entity that owns the transaction. One invoice can carry all four, and each report, search, budget, role, and commission schedule can pick up the field it actually means.

Why the product line does not belong in Department

Now suppose an implementer puts the product line in Department instead, with departments named Outdoor Gear and Kitchen. Several reports break at once, even though every transaction still has a department value and the financial statements still balance. The cost-center report no longer has Wholesale Sales and Finance, so management cannot see functional profit. A role that was supposed to restrict the finance team now has nothing named Finance to restrict, or it restricts a product line by accident. Department budgets follow Outdoor Gear and Kitchen rather than the teams that spend money. A commission schedule categorized by department pays on product line, while the sales manager still thinks department means the team. Warehouse profit still needs Location, and the legal books still need Subsidiary, so those two fields are not free to absorb the product line either. Class sits unused, or it gets a second copy of the product line, which does not restore the missing cost center.

The transaction stores one department for that reporting purpose. Spending it on product line means the other department reports have nothing correct to group by. The same collision happens if the warehouse is stored in Class and the product line is stored in Location. Location searches would return product lines, and class commission rates would follow buildings. The names on the form would look filled in. The reports would answer the wrong question. Help's own examples keep the meanings apart: departments for teams such as Sales or Accounting, classes for a broader segment such as new versus repeat customers, locations for offices and warehouses, and subsidiaries for the legal entities in OneWorld.

The account is a different dimension

An account is the chart-of-accounts dimension, and it is not a substitute for class or department. Every posting line still needs an account such as Sales or Cost of Goods Sold. The account answers which general-ledger line received the amount. It does not answer which team, which product line, or which warehouse was involved, unless someone wrongly encodes those facts into the account name.

Help does let you limit an account to a single department, class, or location, and in OneWorld to a subset of subsidiaries. After that limit is saved, the account can be selected only on transactions where those same segments are selected. That is a control. It keeps a payroll account from being used on a sales-department line, or keeps a subsidiary-specific bank account inside the right legal entity. It does not turn the account into a product line, a warehouse, or a cost center. Creating a separate income account for every product line bloats the chart of accounts, makes the consolidated income statement harder to read, and still gives the controller no warehouse column and no cost-center column. Keep the account for the general-ledger line. Keep class, department, location, and subsidiary for the four questions the controller asked.

When you practice, listen for which question the transaction is supposed to answer. Legal entity means subsidiary. Functional team means department. A meaning the company invented, such as product line or channel, means class. A place means location. Item quantity by place means Multi-Location Inventory, which is a feature decision, not a fourth copy of the location name. Role limits follow the same map, starting with the department restriction the study guide highlights at Setup > Users/Roles > Manage Roles.

Use the SuiteFoundation practice questions to test whether you can keep those four dimensions apart on a single transaction.