NetSuite Review for Multi-Entity Organizations (2026)

Q: How long does it take to implement NetSuite for a holding company?

A standard multi-entity deployment takes between 4 to 6 months, accounting for the structural design of the dimensional chart of accounts, data migration, API integrations, and comprehensive user acceptance testing.

Disclosure: This structural analysis is strictly independent and designed for CFOs and Controllers evaluating enterprise resource planning (ERP) architecture. We may receive partner commissions from software vendors mentioned should you request a consultation through our referral links. This does not influence our technical evaluation or architectural scoring of Oracle NetSuite.

Executive Summary: The Apex Predator of Mid-Market ERP

When conducting a rigorous NetSuite review multi-entity analysis, Corporate Controllers must separate Oracle’s aggressive marketing engine from the actual structural capabilities of the database.

Is NetSuite the right ERP for your holding company in 2026? If your organization generates between $20M and $250M in revenue, operates five or more distinct legal entities, executes transactions in multiple fiat currencies, and requires a single, unified database to run inventory, CRM, and accounting concurrently, NetSuite OneWorld is the undisputed apex predator of the mid-market ecosystem.

Our Structural Verdict: NetSuite solves complex global consolidations and FASB ASC 830 currency translation adjustments natively. It forces strict, auditable governance across decentralized subsidiaries. However, it is not a lightweight tool. It is an expensive, highly rigid enterprise platform that will permanently break a small, under-resourced finance team. If you operate a simple, domestic US structure with three entities, NetSuite is severe architectural overkill.

The Architectural Philosophy: The “Unified Suite”

To properly evaluate this software, you must first understand the fundamental philosophy that drives its design. Most entry-level accounting systems—and even some mid-market competitors—are “best-of-breed” point solutions. They handle the General Ledger (GL) and rely on third-party APIs to handle the rest of your operations.

NetSuite operates on the “Unified Suite” philosophy. It is designed around a single, massive Oracle relational database.

When you configure NetSuite, the goal is to execute your entire quote-to-cash process without the data ever leaving the system. A salesperson closes an opportunity in the NetSuite CRM, which instantly generates a Sales Order, which instantly pings the NetSuite Warehouse Management module to pick the inventory, which automatically triggers the NetSuite billing engine to email the invoice, which finally hits the GL for revenue recognition.

The Multi-Entity Difference: NetSuite vs. NetSuite OneWorld

The most common trap in a NetSuite review multi-entity evaluation is misunderstanding the licensing tiers. “Standard” NetSuite cannot consolidate multiple subsidiaries with different base currencies. If you are a holding company, you are structurally required to purchase the OneWorld module.

We break down the exact technical differences in our guide on NetSuite OneWorld vs Standard NetSuite (2026).

OneWorld is the specific engine that transforms NetSuite from a single-company ledger into a global enterprise architecture. It introduces the “Subsidiary Hierarchy.”

The Root Parent: The ultimate holding company sits at the top of the tree.
Child Subsidiaries: Operating entities sit underneath the parent.
Elimination Subsidiaries: NetSuite automatically provisions “invisible” elimination subsidiaries at every node where branches converge. This is where intercompany cross-charges are systematically neutralized to prevent double-counting revenue on the consolidated P&L.

This hierarchy is immutable once transactions are posted against it. It forces your entire organization to adhere to a single, unified Chart of Accounts (COA) while allowing local subsidiaries to map those accounts to their specific statutory reporting requirements (e.g., local GAAP in Germany vs. U.S. GAAP at the parent level).

Core Capability Teardown: Global Consolidations

The primary reason CFOs endure the heavy NetSuite pricing premiums and implementation friction is the consolidation engine.

In a legacy environment running multiple instances of desktop accounting software, a global consolidation takes an experienced Controller two weeks of manual Excel manipulation. In NetSuite OneWorld, a global consolidation takes approximately 45 seconds.

1. Real-Time Roll-Ups

NetSuite does not rely on batch processing at month-end to generate consolidated reports. Because every child subsidiary operates inside the exact same database as the parent company, the consolidation is instantaneous and continuous.

If a clerk in your London subsidiary posts a £5,000 vendor bill, the CFO in New York can immediately refresh the consolidated Parent Income Statement and see that expense reflected in USD, translated at the precise daily spot rate. This delivers the ultimate structural advantage: real-time capital visibility.

2. Automated Intercompany Management

Managing intercompany loans, management fee cross-charges, and inventory transfers between subsidiaries is historically the highest-risk area for audit failures.

As explored in our primer on What Is Multi-Entity Accounting?, standard systems require you to post a “Due To” entry in Entity A, log out, log into Entity B, and post the corresponding “Due From” entry.

NetSuite OneWorld eliminates this asymmetrical risk.

Automated Cross-Charges: When Subsidiary A purchases a software license on behalf of Subsidiary B, the accountant enters a single transaction.
The Balancing Act: NetSuite instantly reads the subsidiary tags and automatically posts the balancing intercompany journal entries to both ledgers simultaneously.
Automated Eliminations: At month-end, the Controller runs the “Generate Intercompany Eliminations” script. NetSuite automatically identifies all intercompany balances and posts the neutralizing entries into the designated Elimination Subsidiary, instantly clearing the consolidated balance sheet.

3. Multi-Currency and FASB ASC 830 Compliance

If your holding company operates internationally, this is where a NetSuite review multi-entity analysis heavily outscores lightweight competitors.

Foreign exchange (FX) management is mathematically complex. You cannot simply use an average monthly rate for everything. U.S. GAAP (ASC 830) requires specific translation rules:

Income Statement accounts must be translated using the weighted average exchange rate for the period.
Balance Sheet accounts (Assets/Liabilities) must be translated using the exact spot rate at the end of the month.
Historical Equity must be retained at the historical rate from the date of the transaction.

NetSuite OneWorld handles this natively. It automatically pulls daily exchange rates from providers like Xignite or Reuters. At the push of a button during the month-end close, the system calculates the Cumulative Translation Adjustment (CTA) and posts it directly to the consolidated equity section, ensuring flawless audit compliance without touching a single spreadsheet.

The Dimensional Chart of Accounts (Segments)

A major structural shift for organizations migrating from entry-level ledgers to NetSuite is the adoption of a dimensional Chart of Accounts.

In legacy systems, to track travel expenses for the marketing department in the UK subsidiary, you would have to create a hard-coded “string” account: 6000-Travel-Marketing-UK. This leads to bloated ledgers with 10,000+ accounts that are impossible to manage.

NetSuite utilizes a highly optimized dimensional structure. You establish a lean, base Chart of Accounts (e.g., just 6000-Travel). You then use “Segments” (Dimensions) to tag the transaction.

NetSuite provides three native core segments:

Subsidiary: (Which legal entity incurred the cost?)
Department: (Which functional team is responsible?)
Class: (Which revenue stream or product line does this relate to?)
Location: (Which physical warehouse or office?)

If you need more tracking (e.g., tracking profitability by a specific “Sales Channel” or “Vendor Group”), you can create Custom Segments. This dimensional tagging is what allows a CFO to run a P&L, pivot the columns by Subsidiary, and filter the rows by Department instantly.

For a direct comparison of how NetSuite’s dimensional tagging stacks up against its primary rival, review our technical breakdown: NetSuite vs Sage Intacct: Which Is Better for Multi-Entity Accounting?.

Advanced Modules: The Enterprise Compliance Engine

A rigorous NetSuite review multi-entity analysis must acknowledge that you are not paying a premium merely for a ledger; you are paying for an impenetrable compliance engine. For pre-IPO organizations or heavily audited private equity portfolios, NetSuite’s advanced modules are the primary defense against material weaknesses.

While the base OneWorld module handles the consolidation mechanics, organizations dealing with complex contracts or international tax jurisdictions must evaluate two critical architectural add-ons.

1. Advanced Revenue Management (ARM) & ASC 606

If your holding company generates revenue through SaaS subscriptions, long-term construction contracts, or complex hardware/software bundles, standard accounting systems fail immediately. They force accountants to manage deferred revenue schedules in massive, error-prone Excel workbooks.

NetSuite’s Advanced Revenue Management (ARM) module systematically decouples the billing event from the revenue recognition event, strictly enforcing FASB ASC 606 and IFRS 15 compliance.

The Structural Workflow: When a salesperson closes a $120,000 annual SaaS contract, NetSuite instantly generates the invoice (debiting Accounts Receivable and crediting Deferred Revenue).
The Revenue Arrangement: ARM simultaneously creates a “Revenue Arrangement” operating completely independently of the invoice. It automatically calculates the standalone selling price (SSP) allocations and builds a multi-period amortization schedule.
The Month-End Automation: During the close, the Controller executes a single script. NetSuite systematically sweeps the Deferred Revenue accounts and recognizes the precise monthly earned revenue ($10,000) into the P&L. There is zero manual intervention, eliminating the risk of premature revenue recognition that routinely delays IPO filings.

2. Multi-Book Accounting (Multi-GAAP)

For holding companies scaling aggressively overseas, statutory reporting is a massive hidden cost. A subsidiary in Germany must report its local taxes in Euros using German HGB standards, while the US parent requires the exact same subsidiary’s data reported in USD under US GAAP.

Entry-level systems force you to maintain two separate, disconnected ledgers. NetSuite’s Multi-Book Accounting module solves this by allowing a single transaction to post to multiple parallel ledgers simultaneously, utilizing different accounting rules.

The Execution: An asset depreciates over 5 years under US GAAP, but 3 years under local statutory rules. The accountant enters the asset purchase once. NetSuite’s engine automatically calculates and posts the divergent depreciation schedules to the respective “books.”
The ROI: This automated dual-reporting capability is precisely why NetSuite consistently ranks as the apex architecture when evaluating the best accounting software for international subsidiaries. It removes the necessity of hiring expensive local accounting firms merely to translate US GAAP financials into local statutory compliance formats.

The UI/UX Reality Check (The Oracle Aesthetic)

When evaluating the daily operator experience, Corporate Controllers must temper their expectations. NetSuite is not a sleek, consumer-grade application. It is a dense, Oracle-backed relational database prioritizing data integrity over modern aesthetic minimalism.

The Executive Dashboard Advantage

For the CFO, the user experience is highly optimized. The NetSuite “Portlet” dashboard system is structurally brilliant. You can configure a multi-entity dashboard that displays real-time consolidated cash balances, intercompany AR aging, and budget-to-actual variances.

Because the data is unified, the drill-down capability is absolute. A CFO can click on a consolidated “Travel Expense” line item on the parent P&L and drill down five layers deep—through the European elimination subsidiary, into the London operating entity, and directly to the underlying PDF receipt attached to the specific vendor bill—all within three clicks.

The Operator’s Steep Learning Curve

However, for the AP clerk or the operational department manager, the UI can be overwhelmingly complex.

The navigation menus are deeply nested and text-heavy.
Creating a custom report requires understanding the underlying database schema and table joins, a skillset that frustrates standard accountants who are used to simple drag-and-drop report builders.
If your organization requires hundreds of non-finance operational users to interact with the system daily (e.g., project managers or warehouse staff), the interface friction is a common point of failure. This specific usability challenge is often the deciding factor when organizations pivot their evaluation toward more intuitive, consumption-based models, a dynamic we explore thoroughly in our NetSuite vs Acumatica (2026) architectural breakdown.

The Structural Limitations of the Platform

No enterprise software is flawless. A vendor-agnostic NetSuite review multi-entity evaluation requires identifying the exact breaking points of the architecture before you sign the Master Services Agreement. If your holding company cannot tolerate the following three structural limitations, NetSuite will become a highly expensive liability.

1. The Immutable Subsidiary Hierarchy

NetSuite OneWorld’s greatest strength—its rigid, auditable subsidiary hierarchy—is also its most unforgiving limitation.

When you configure your entity tree (Parent > Child > Elimination), it is etched in stone the moment you post the first live transaction against it.

The Trap: If your holding company executes a complex internal reorganization—for example, moving a UK subsidiary from underneath the US Parent directly to a new European Holding Company—NetSuite cannot simply “drag and drop” the entity to a new node on the tree.
The Consequence: To alter the base hierarchy post-go-live, you are often forced to provision an entirely new legal entity record, manually migrate the historical open balances via journal entry, and abandon the historical transactional data in the “old” inactive entity. For highly dynamic private equity portfolios that constantly spin off and merge entities, this structural rigidity is a severe operational bottleneck.

2. The “SuiteScript” Maintenance Burden

NetSuite markets itself as infinitely customizable. If the native workflow does not match your business process, you can build custom automations. However, these customizations are executed using “SuiteScript” (NetSuite’s proprietary JavaScript API).

The Trap: Heavy reliance on custom SuiteScripts shifts your accounting department’s dependency directly onto expensive external developers.
The System Upgrade Risk: NetSuite pushes two mandatory system upgrades per year to all customers simultaneously. If your implementation partner built a fragile, poorly coded SuiteScript to handle a custom billing workflow, the bi-annual Oracle update will break that script, halting your invoice generation until a developer patches the code. CFOs must ruthlessly enforce a “native-first” configuration policy to minimize this technical debt.

3. Enterprise Implementation Friction

NetSuite cannot be deployed quickly. Due to the interconnected nature of the Unified Suite, deploying the core financials requires configuring the underlying CRM and inventory master records simultaneously.

If your organization requires a rapid, 30-day deployment strictly to handle top-side consolidations and multi-currency translations, NetSuite is the wrong tool. It demands a grueling 4-to-6 month implementation timeline, consuming hundreds of hours of internal finance leadership capacity. For organizations exploring the absolute top tier of enterprise complexity where deployments can take a year, understanding how NetSuite scales against titans is critical. We map this specific ceiling in our NetSuite vs Workday Financial Management (2026) comparison.

Integrations & API Architecture: The Middleware Dependency

A thorough NetSuite review multi-entity analysis must look beyond the native modules and examine how the database interacts with your existing operational tech stack. NetSuite is designed to be the central nervous system of your holding company, but it requires highly specific neural pathways to communicate with external systems.

Oracle markets the “Unified Suite,” suggesting you can run everything natively. The structural reality is that best-in-class mid-market organizations still rely on specialized external software for specific workflows, such as Salesforce for enterprise CRM or specialized global payables platforms (see our guide on the Best AP Automation Software for Multi-Entity Companies).

To connect these systems to NetSuite, you must understand the API architecture and the hidden costs of middleware.

1. SuiteTalk and the REST API

NetSuite communicates with the outside world via “SuiteTalk,” which supports both legacy SOAP web services and modern REST APIs.

The Structural Advantage: The API is incredibly robust. Nearly every standard and custom record within NetSuite (e.g., a Sales Order, an Intercompany Journal Entry, a Customer Record) can be queried, created, or updated via API. This allows for massive transaction volumes to flow into the ledger automatically.
The Trap: NetSuite’s API is highly governed. To protect the performance of the shared cloud environment, Oracle enforces strict “concurrency limits” (how many API calls can happen simultaneously). If your eCommerce platform attempts to push 10,000 orders into NetSuite at the exact same second, the API will hit its concurrency limit and throttle or reject the data, requiring error-handling scripts to retry the push.

2. The Celigo and Boomi Tax (Middleware)

Because point-to-point custom API integrations are brittle and expensive to maintain, Corporate Controllers should never allow their internal IT teams to hard-code a connection between Salesforce and NetSuite.

Instead, enterprise architecture dictates the use of an Integration Platform as a Service (iPaaS) like Celigo or Dell Boomi.

The Execution: Celigo provides pre-built, managed connector apps. When a deal closes in Salesforce, Celigo automatically maps the data fields, navigates NetSuite’s concurrency limits, and generates the Sales Order in the ERP.
The Financial Impact: This middleware is not optional for a stable enterprise deployment, and it is not free. CFOs must model an additional $15,000 to $30,000 in annual OpEx specifically for the iPaaS licensing, plus the consulting hours required to configure the data flows.

3. Operational Overlays vs. Native Modules

Before customizing NetSuite to handle highly specific industry requirements, you must evaluate if a native integration with a specialized overlay is more capital efficient.

For example, while NetSuite has native project management capabilities, complex services firms often find it lacks the granular resource-planning depth they require. Instead of writing custom SuiteScripts to force NetSuite to behave like a dedicated PSA (Professional Services Automation) tool, they deploy an overlay. We break down this exact architectural decision in our comparison of Certinia vs NetSuite for Services Organizations (2026). The integration allows the operational team to live in Certinia, while the financial data syncs seamlessly into the NetSuite OneWorld GL for consolidation.

The Truth About NetSuite Pricing & Contract Negotiation

The most opaque element of a NetSuite review multi-entity evaluation is the procurement process. Oracle NetSuite possesses one of the most sophisticated, aggressive software sales engines on the planet. If a CFO enters the negotiation without understanding the underlying math of the Master Services Agreement (MSA), they will fundamentally compromise their 5-year Total Cost of Ownership (TCO).

NetSuite does not publish standard pricing tiers. Every contract is custom-built based on user counts, module scope, and negotiation leverage. To establish a baseline for your CapEx modeling, you must study the exact mechanics detailed in our comprehensive NetSuite Pricing guide.

Here is the operator’s playbook for surviving Oracle procurement.

1. The “SuiteSuccess” Methodology

NetSuite sells its mid-market deployments through a model called “SuiteSuccess.” Instead of starting with a blank database, SuiteSuccess provides pre-configured industry editions (e.g., Software, Manufacturing, Wholesale Distribution) loaded with standard dashboards, KPIs, and workflows.

The Pitch: SuiteSuccess is marketed to drastically reduce implementation time and consulting fees by utilizing “leading practices.”
The Reality: It is a powerful accelerator, provided your organization is willing to conform exactly to NetSuite’s predefined workflows. If your Corporate Controller insists on rebuilding your legacy, highly customized approval matrices inside the new system, the SuiteSuccess model breaks, and your implementation fees will immediately skyrocket.

2. The User Tier Trap

NetSuite charges a premium monthly fee for every individual who requires login access (typically around $99/user/month for a full license).

The Trap: Account Executives will pressure you to buy 50 user licenses on Day 1 to secure a “volume discount.” However, your implementation will take six months. Buying licenses for operational staff before the system is live creates immediate “shelfware”—you are burning cash on software you literally cannot use.
The Play: Negotiate a ramped licensing schedule. Purchase only the 5 to 10 core financial licenses required for the implementation team on Day 1. Pre-negotiate a fixed price for the remaining 40 licenses to be activated strictly upon the go-live date.

3. The Renewal Spike and the Hard Cap

Oracle values NetSuite Account Executives based on Annual Contract Value (ACV) growth. Their compensation is tied to increasing your bill at every renewal.

The Trap: The vendor will offer a massive discount (often 40% to 50% off list price) to win the initial Year 1 contract. However, standard Oracle MSAs include clauses that allow them to remove those discounts and apply standard inflationary increases upon renewal. In Year 4, your software bill could mathematically double without you adding a single new entity.
The Play: Before signing the initial MSA, you must redline the renewal terms. Demand a strict, contractual hard cap on annual price increases (e.g., no more than 3% to 5% uplift upon renewal). If the Account Executive refuses, threaten to pivot your evaluation to a competitor. They will concede.

4. Timing the Oracle Fiscal Year

Enterprise software sales operate on strict, quota-driven deadlines. You must leverage the vendor’s internal financial pressures against them.

Oracle’s fiscal year ends on May 31st.

If you attempt to negotiate a NetSuite contract in July, you have zero leverage. If you push the final signature to the final week of May, the Account Executive and their Regional VP will be desperate to close the revenue to hit their year-end accelerators. Executing the contract in late May consistently yields 20% to 30% deeper structural discounts than a mid-quarter negotiation.

If your organization is scaling beyond the standard mid-market constraints and evaluating true enterprise titans where millions of dollars are at stake, understanding this procurement leverage is even more critical. We map these high-stakes dynamics in our Workday vs NetSuite for Multi-Entity Finance architectural review.

The Build vs. Buy Decision: When NetSuite is Severe Overkill

A definitive NetSuite review multi-entity evaluation is incomplete without identifying the exact operational threshold where buying this software is a catastrophic misallocation of capital.

NetSuite is an apex predator, but it requires a massive caloric intake to survive. That intake comes in the form of your finance team’s time, dedicated system administrators, and constant consulting retainers. If your holding company does not have the structural complexity to justify this overhead, NetSuite will crush your margins.

The Profile of a Failed Deployment

You should strictly avoid NetSuite OneWorld if your organization matches the following profile:

Revenue Under $15M: The proportional cost of the software and implementation will destroy your Year 1 EBITDA.
Lean Finance Teams: If your accounting department consists of one Controller and one AP clerk, they do not have the bandwidth to manage a Tier 3 enterprise database. They will spend all their time feeding the system rather than analyzing the output.
Simple Domestic Structures: If you operate three LLCs entirely within the United States, execute zero foreign currency transactions, and have no complex inventory routing, the OneWorld consolidation engine is structurally unnecessary.

The Overlay Strategy (The Capital-Efficient Alternative)

Before committing to a $150,000+ NetSuite implementation, Corporate Controllers must evaluate if their legacy ledger is actually broken, or if their manual workflows simply lack modern automation.

If you are running fragmented entry-level ledgers, you can often delay an enterprise ERP migration by deploying targeted architectural overlays:

The Consolidation Fix: Instead of replacing your entire GL, deploy a dedicated reporting tool via API to pull trial balances from your existing systems and map them into a consolidated view automatically.
The Month-End Fix: If your close is taking 20 days because of manual intercompany reconciliations in Excel, leave the ledger intact and implement a strict close-management overlay. We analyze the exact tools for this in our breakdown of the Best Financial Close Software for Multi-Entity Orgs (2026).
The Structural Upgrade: If you have outgrown entry-level software but are not ready for the IT burden of Oracle, you must look at modular, finance-first alternatives. We detail the exact timing and metrics for this transition in our guide: QuickBooks vs Sage Intacct: When to Upgrade.

Understanding when to hold your ground on a Tier 2 system is the hallmark of a disciplined capital allocator. For a broader view of how NetSuite scales against leaner alternatives, review our ranking of the Best Accounting Software for Holding Companies.

Regulatory References & Evaluation Methodology

To ensure this NetSuite review multi-entity analysis remains grounded in compliance-grade structural reality, we benchmarked the OneWorld architecture against the following foundational accounting standards:

FASB ASC 810 (Consolidation): The U.S. GAAP standard dictating the requirement for rigorous intercompany transaction matching and elimination. NetSuite’s automated elimination subsidiaries natively enforce this standard without manual top-side journal entries.
FASB ASC 830 (Foreign Currency Matters): The standard governing the treatment of foreign currency translations. NetSuite’s automated calculation of the Cumulative Translation Adjustment (CTA) and period-end revaluation routines perfectly align with these complex multi-currency requirements.
FASB ASC 606 (Revenue from Contracts with Customers): The core framework for decoupling billing from revenue recognition. NetSuite’s Advanced Revenue Management (ARM) module is structurally built to automate the five-step model mandated by this standard.

Frequently Asked Questions: NetSuite Multi-Entity Architecture

Is NetSuite good for multiple entities? Yes, NetSuite is widely considered the industry standard for complex multi-entity organizations. However, to consolidate multiple subsidiaries—especially those with different base currencies or international tax jurisdictions—you must purchase the NetSuite OneWorld module. Standard NetSuite cannot execute global consolidations natively.

How does NetSuite handle intercompany transactions? NetSuite handles intercompany accounting by linking transactions across subsidiaries in real-time. When a cross-charge is entered, the system automatically posts the balancing “Due To / Due From” journal entries to both respective ledgers. At month-end, the automated elimination script neutralizes these balances within a designated elimination subsidiary to clear the consolidated balance sheet.

How much does NetSuite OneWorld cost? NetSuite pricing is highly variable. A mid-market holding company should expect a base platform fee starting around $999 to $1,499 per month, plus a significant premium for the OneWorld module (often $1,999+ per month). Additionally, organizations must pay a flat monthly fee for every user license and a provisioning fee for each legal entity added to the hierarchy.

How long does it take to implement NetSuite for a holding company? Due to the complexity of the Unified Suite, a standard multi-entity deployment takes between 4 to 6 months. This timeline accounts for the structural design of the dimensional chart of accounts, historical data migration, API integrations via middleware, and comprehensive user acceptance testing (UAT).

Conclusion & Final Structural Verdict

NetSuite OneWorld is not merely accounting software; it is a rigid, unforgiving corporate governance engine. When fully deployed, it forces absolute operational discipline across disparate, decentralized subsidiaries.

If your holding company requires real-time global consolidations, automated ASC 830 currency translations, and the ability to run inventory, CRM, and revenue recognition within a single unified database, NetSuite is the undisputed market leader. It will systematically eliminate the spreadsheet risk that plagues rapid-growth enterprises.

However, Corporate Controllers must enter the procurement cycle with their eyes wide open. You are absorbing a massive CapEx burden, steep learning curves for operational staff, and a permanent reliance on expensive third-party implementation partners. Buy NetSuite when your structural complexity demands it; never buy it simply because it is the default industry name.