NetSuite Platform Administration and Configuration
This domain tests how you configure and maintain a NetSuite account: feature enablement, company and accounting preferences, subsidiary and currency structure, sandbox and release management, and core administrative tools. Exam questions tend to focus on dependencies and on settings that are difficult or impossible to reverse.
Account structure and feature enablement
- OneWorld accounts use a subsidiary hierarchy; transactions post to a subsidiary and roll up to the parent. The subsidiary record controls currency, tax nexus, and many defaults.
- Enable Features is grouped by category (Accounting, CRM, Transactions, SuiteCloud, Analytics). Enabling a feature can add records, fields, permissions, and preferences.
- Company preferences and accounting preferences apply account-wide, while some defaults can be overridden by subsidiary, role, or user.
Environments and change control
- A sandbox is a copy of production used for testing. Refreshing a sandbox overwrites its data; the copy direction is production to sandbox, not the reverse.
- Release Preview lets you test the next upgrade. SuiteCloud Development Framework (SDF) can package custom objects for deployment between accounts.
Worked example
An administrator must add a German subsidiary that invoices in EUR. The reasoning: enable Multi-Currency before creating EUR transactions, create the subsidiary under the correct parent, set EUR as its currency, configure tax codes and nexus, then confirm that administrators and local users have subsidiary access. Test in sandbox first because currency and tax-model choices affect the ledger and are hard to unwind.
Traps
- Enabling a feature does not grant users permission to use it.
- A subsidiary-level preference may be ignored if an account-level preference or role restriction overrides it.
- Do not use a sandbox refresh as a backup; it replaces sandbox data.