NetSuite company preferences define many of the defaults that shape how an account records transactions, displays information, sends communications, and behaves for users. They are different from personal preferences, which only adjust an individual user’s experience. For administrators, reviewing these settings before go-live is essential because a single account-level default can affect transaction entry, document numbering, reporting, email delivery, and day-to-day controls across the organization.
What are NetSuite company preferences?
NetSuite company preferences are administrator-controlled settings that establish account-wide defaults for business processes and system behavior. They include general display and communication settings, accounting rules, numbering conventions, printing options, email behavior, search settings, and other configuration choices available under the company preference areas.
To answer the core question directly, administrators manage NetSuite company preferences by opening the relevant preference page under the Setup menu, reviewing each setting against documented business requirements, testing changes in a controlled environment where possible, and saving only settings with a clearly understood impact. Company Information is reviewed separately because it stores core organizational identity and account details, while company preferences control how NetSuite applies operational defaults. Personal preferences should not be used as a substitute for either one.
This distinction matters. A user changing a time zone or dashboard portlet does not change the account’s accounting behavior. An administrator changing an accounting preference, transaction numbering option, or email setting may affect many users and future transactions.
For the broader individual setup process, see our guide to NetSuite personalized preferences for faster, cleaner daily work. That article focuses on user-level personalization, while this guide addresses account-wide administration and control.
NetSuite Company Information vs. company preferences
NetSuite Company Information and company preferences serve related but different purposes. Company Information identifies the organization in NetSuite, while preferences tell the system how to apply certain defaults and processes.
The Company Information page generally contains foundational details such as the organization’s name, address, contact information, fiscal information, and other account-level identity fields. The exact fields available depend on account configuration, enabled features, and whether the account uses OneWorld. A OneWorld account also relies heavily on subsidiary records, so administrators should not assume that one company-level address or name controls every transaction document.
Company preferences influence behavior. Examples include:
Whether transaction numbers are generated automatically
How dates, numbers, and percentages are displayed
How emails are sent from NetSuite
Which defaults appear on transactions
How certain accounting and inventory processes operate
Whether users receive specific system messages or reminders
How records and searches behave in the account
The practical test is simple: if the setting describes who the organization is, review Company Information. If it describes how NetSuite should behave, review company preferences. If it describes how one person wants to work, review personal preferences.
This classification prevents a common configuration error: attempting to solve an account-wide requirement through an individual user’s settings. A user’s preferred date format does not establish the company’s accounting date rules, and a dashboard customization does not replace role or form configuration.
Where do you find company preferences in NetSuite?
Company preference pages are typically available through the Setup menu under company-related configuration areas. Navigation labels vary based on role permissions, account features, and NetSuite’s interface configuration, so administrators should rely on the menu available in their account rather than a fixed click path copied from another environment.
Common areas include:
General Preferences, which covers broad account behavior, formats, communication defaults, and other shared settings
Accounting Preferences, which controls important financial and transaction behavior
Other Preferences, which contains additional account-wide options that do not fit into the general or accounting categories
Company Information, which stores organizational identity and foundational account details
Access is role-dependent. A full administrator sees more configuration options than a role with limited setup permissions. In addition, enabling features such as OneWorld, Advanced Inventory, SuiteTax, or electronic payments changes which settings appear and how they interact.
Before changing a preference, record the current value, identify the responsible owner, and note the expected effect. This creates a configuration baseline that helps with testing, audit review, and troubleshooting. NetSuite’s System Notes also provide a useful history for many record and configuration changes, but documentation should not depend on system history alone.
Which NetSuite company preferences require the most attention?
Not every preference carries the same level of risk. Settings that affect financial posting, transaction numbering, tax treatment, period control, or external communications deserve formal review before lower-impact display options.
1. Accounting preferences
Accounting preferences influence how NetSuite handles core financial activity. Depending on the account, administrators may encounter settings related to accounting periods, posting behavior, rounding, revenue recognition, approval processes, inventory costing, payment processing, and transaction defaults.
These settings should be evaluated against the organization’s chart of accounts, close process, internal controls, and reporting requirements. A preference that appears convenient for transaction entry may create reconciliation problems if it bypasses an approval step or changes how users enter dates and amounts.
Accounting preferences also interact with other NetSuite features. For example, SuiteTax configuration, tax registrations, nexus records, subsidiaries, and transaction forms all influence how tax information appears and is calculated. Administrators should review the complete configuration rather than treating one preference as an isolated switch.
2. Transaction numbering and document control
Transaction numbering is a small configuration area with a large operational impact. Administrators need to decide whether numbers are generated automatically, whether users can override them, and how numbering behaves across transaction types, subsidiaries, or legal entities.
The goal is not simply to produce sequential numbers. The numbering approach should support auditability, duplicate prevention, document retrieval, and any legal or internal control requirements. Administrators should test numbering for sales orders, invoices, vendor bills, purchase orders, journal entries, and credit transactions separately because different transaction types may follow different numbering rules.
If numbering is changed after transactions exist, the effect on reporting, integrations, saved searches, and downstream processes requires careful evaluation. External systems may store NetSuite transaction numbers as references, so changing the way those values are generated can affect data matching.
3. Date, time, and number formats
Date and number formats appear administrative, but inconsistent settings create real processing errors. Review the account’s date format, number format, negative number display, decimal precision, and time zone requirements.
NetSuite distinguishes between a user’s preferred display settings and the underlying value stored on a record. That distinction matters when users work across countries or subsidiaries. A date displayed as day-month-year to one user may appear as month-day-year to another, while the transaction still represents one underlying date.
Time zone settings require special attention for scheduled scripts, workflows, saved searches, system notes, and email timestamps. A scheduled process that runs near midnight in one time zone may appear to execute on a different calendar date for another user. Administrators should test time-sensitive workflows with representative roles rather than relying only on the administrator’s display.
4. Email and communication preferences
Email preferences determine how NetSuite communicates with customers, vendors, employees, and internal users. Review the account’s default email behavior, sender identity, copy and blind-copy rules, reply-to settings, and restrictions on sending messages to external recipients.
Email delivery also depends on transaction forms, workflows, saved searches, user permissions, and NetSuite’s email authentication and delivery controls. A company preference alone does not guarantee that every transaction email will reach its destination.
Administrators should establish a clear policy for testing. Test emails should use controlled recipients, and production communication should not begin until the organization has confirmed sender addresses, reply handling, templates, attachments, and approval requirements. Where the account sends significant transaction volume, review SPF, DKIM, and DMARC alignment with the organization’s email administrator. These are external email standards, but they directly affect trust and delivery.
5. Forms, defaults, and transaction behavior
Company preferences work alongside custom forms, role preferences, workflows, and scripts. A default subsidiary, department, location, class, payment term, shipping method, or tax setting may appear to come from one place when several configuration layers are involved.
When a user reports that NetSuite is selecting the “wrong” value, administrators should trace the source instead of changing a global preference immediately. The value may come from the customer record, vendor record, employee record, subsidiary, custom form, role, workflow, or script.
This is where SuiteScript and workflow governance becomes important. A global preference should establish a reliable default, not conceal a process problem. If a value must be enforced under specific conditions, a workflow or validation rule is more appropriate than a broad setting that changes every transaction.
How should administrators review NetSuite company preferences?
A safe review starts with business requirements, not with clicking through every checkbox. Create a configuration inventory that connects each preference to an owner, affected process, test case, and approval status.
A practical review sequence looks like this:
Document the current state. Capture existing values, account features, subsidiaries, roles, custom forms, workflows, integrations, and scripts that may depend on the setting.
Classify the preference. Mark it as financial, operational, communication-related, display-related, security-sensitive, or integration-sensitive.
Identify the impact radius. Determine whether the change affects one user, one role, one subsidiary, one transaction type, or the entire account.
Define a test case. Use a representative transaction or user scenario, including an exception case where the preference should not apply.
Review dependencies. Check saved searches, SuiteAnalytics workbooks, workflows, SuiteScript, integrations, templates, and external reporting processes.
Approve and document the change. Record the reason, owner, date, previous value, new value, test evidence, and rollback plan.
This process is especially important for settings that appear harmless in a sandbox but interact with live integrations or external email. A test environment is valuable, but it does not reproduce every production condition automatically. Confirm that the sandbox contains representative roles, forms, subsidiaries, workflows, scripts, and integration credentials before treating test results as conclusive.
What should be tested after changing a company preference?
Testing should reflect the preference’s actual impact. A display setting needs user validation, while an accounting preference needs transaction and reporting validation.
For a financial setting, test the complete transaction lifecycle. Enter the transaction, approve it if approval applies, post it, review the resulting journal impact, include it in a report, and confirm how it behaves during period close. For a numbering setting, create multiple transactions of the affected type and check duplicate prevention, gaps, subsidiary behavior, and integration references.
For an email setting, test internal and external recipients separately. Confirm the sender address, reply-to address, template, attachments, merge fields, delivery timing, and record communication history. Do not assume that a successful appearance in the Outbox proves external delivery.
For a role or subsidiary setting, log in with the relevant role and test the process as an ordinary user. Administrators frequently see broader access and more configuration options than the people who execute the process every day.
SuiteAnalytics provides another useful validation layer. A saved search or workbook can confirm whether the new setting affects transaction fields, statuses, dates, amounts, or subsidiary reporting as expected. This is more reliable than checking only the data-entry screen.
How do company preferences interact with OneWorld and subsidiaries?
In NetSuite OneWorld, company preferences do not replace subsidiary configuration. The account contains global settings, but subsidiaries carry important legal, financial, tax, currency, address, and reporting attributes.
Administrators must determine whether a requirement is global or subsidiary-specific before changing an account-level preference. A single default may work for one legal entity but create incorrect documents, tax treatment, or reporting behavior for another.
Review these related layers together:
Company Information and global account identity
Subsidiary records and legal entity details
Accounting books and accounting preferences
Tax nexus, registrations, and SuiteTax settings
Currency and exchange-rate configuration
Transaction forms and subsidiary restrictions
Role permissions and employee access
Intercompany and consolidation processes
A global change deserves additional scrutiny when subsidiaries operate under different statutory, tax, language, currency, or document requirements. The right answer may involve subsidiary-specific forms, workflows, or records rather than one broad company preference.
Common mistakes with NetSuite company preferences
The most common mistake is treating a company preference as harmless because it appears on a short setup page. Many settings affect data created after the change, and the resulting behavior might not be obvious until month-end, an audit, or an integration reconciliation.
Another mistake is changing several preferences at once. When multiple values change together, administrators lose the ability to identify which setting caused an unexpected result. Make controlled changes, test them, and document each one.
A third mistake is relying on the administrator role for all testing. Administrator access hides the restrictions and defaults that shape ordinary user behavior. Test with representative roles, subsidiaries, forms, and approval paths.
Finally, avoid using custom scripts to compensate for an undocumented preference decision. Before adding SuiteScript, confirm that the requirement is not already supported by a standard preference, form, workflow, or permission. If configuration is insufficient, document the gap before selecting customization.
If your account needs a broader review of setup, integrations, customization, or ongoing administration, our NetSuite services and implementation support can help establish a controlled configuration process.
Conclusion
NetSuite company preferences form part of the account’s operational foundation. They influence accounting behavior, transaction numbering, communication, formatting, reporting, and the defaults users encounter every day.
The safest approach is to separate Company Information, company preferences, personal preferences, roles, forms, workflows, and scripts before making changes. Review each setting against a documented business requirement, test it with representative transactions and roles, and record the decision for future administrators.
A disciplined review reduces avoidable errors and makes the NetSuite environment easier to govern as the organization adds subsidiaries, integrations, users, and processes. If you need help assessing your configuration or planning a controlled improvement, contact Versich to discuss your NetSuite requirements.
