2026.1 Account Setup & Maintenance: Address Subrecord Filtering, Unlimited Sandbox Refreshes, Intercompany Elimination Dataset

This release bundles a grab bag of administrative and platform changes under "Account Setup and Maintenance." The most consequential item for developers is a silent behavioral change to how address and addressbook subrecords are returned. Everything else is admin-facing or net-new UI surface area.

Address Subrecord Filtering — the one that may break integrations

NetSuite now automatically filters address-related subrecords (address, addressbook) so that only addresses linked to the parent record you are loading are returned. This applies across SuiteQL, SuiteScript 2.0, SuiteScript 2.1, and the REST Record Service (/services/rest/record/v1/...).

Oracle's note is vague on the exact mechanism — they explicitly state that no schemas, permissions, or roles changed, only the result-set filtering. In practice this means:

• Result sets for address subrecords will be smaller. Code that previously got back unrelated addresses (cross-entity bleed) will now get a precise subset.
• Any logic that relied on that bleed — for example, scripts that loaded a customer addressbook and expected to see addresses associated with related entities — will silently return fewer rows.
• Aggregations, counts, and dedupe logic over addressbook may produce different numbers without raising an error.

What to do

1. Grep your codebase for record.load/record.create calls against customer, vendor, employee, and contact that touch the addressbook sublist, and any N/query or SuiteQL referencing the addressbook, addressbookaddress, or address tables.
2. Audit REST integrations hitting /services/rest/record/v1/customer/{id}/addressbook (and the equivalent vendor/employee endpoints) and compare row counts in a sandbox before and after refresh.
3. If you have a SuiteAnalytics Workbook or saved search that drives a downstream sync (CRM, ERP, address verification), re-baseline the row counts.
4. Verify in a refreshed sandbox — Oracle has not published a flag to opt out, so the only validation path is observed behavior.

Sandbox Refresh Limits Removed

As of March 6, 2026, sandbox refreshes are unlimited. Request via Setup > Company > Company Management > Sandbox Accounts. Practical impact: you can now refresh as part of a release cadence rather than rationing refreshes per quarter. A refresh still copies all configurations, data, user passwords, and customizations from the source account.

Intercompany Elimination

Source transactions on all balance sheet eliminations

Elimination journal entries now expose source transaction links for all account types, including AP, AR, and Other Assets/Liability. Previously this drill-down was limited. Useful if you build reconciliation reports on top of journalentry records — you can now traverse from an elimination JE back to the originating intercompany transaction without joining through inferred logic.

New Intercompany Elimination dataset in SuiteAnalytics Workbook

A first-class Intercompany Elimination dataset is now available in Workbook. It exposes elimination journal lines filterable by period, plus source transaction amount, source currency, base currency amount, base currency, and consolidated exchange rate. If you've been hand-rolling SuiteQL joins to produce this view, replace it with the dataset.

Unlink Intercompany Cross Charge Journals

You can now self-serve unlink cross charge journals that have been cleared by another cross charge journal in an open period. UI path: Cross Charge Workbench > Actions > Unlink Cross Charge Self Payments. Previously this required a NetSuite Customer Support ticket. Oracle's note does not mention any SuiteScript or REST API exposure for this action — assume UI-only until proven otherwise.

Prompt Studio Updates

• GPT-OSS model support — Select GPT OSS from the Model Family list when creating custom prompts. Oracle does not specify which OpenAI GPT-OSS variant (e.g., gpt-oss-20b vs gpt-oss-120b); verify in the UI.
• Sublist variables in prompt templates — Prompts can now reference sublist data from the target record (e.g., line items on a Sales Order). A new Sublist Variables tab supports providing sample data when testing templates.
• New Text Enhance prompts for AI description fields — A set of system prompts has been added to back a unified "Optimize for AI" Text Enhance action on custom fields with AI descriptions. Pre-configured; no action required.

NetSuite 360 Redesign — Global Rollout

The redesigned NetSuite 360 interface is now available globally. Non-U.S. accounts get two dashboards: a NetSuite 360 Dashboard (cases, enhancements, issues, support contacts, SuiteIdeas, email subscriptions, Action Items and Notifications portlet) and a Financial Dashboard (NetSuite invoices, payment methods, billing/shipping address, financial documents). U.S. accounts additionally get domestic ACH and non-USD credit card payment support. This is account-management UI; no developer impact.

AI Preferences — Two New Subtabs

Intelligent Recommendations subtab

Administrator-only. Controls Intelligent Item Recommendations on sales orders, estimates, and opportunities. Settings:

• Show Intelligent Recommendations Button for Item Recommendations — toggles the in-account button. Does not affect web store recommendations.
• Show Optional Columns — toggles Display Name, Unit Price, and Quantity Available in the recommendations popup. Selected columns also propagate to the Customer Center.

Narrative Insights subtab

Generative-AI summaries on select reports and records. Administrator-only. Settings:

• Enable Narrative Insights — on by default.
• Enable Narrative Insights for External Roles — off by default. Leave this off unless you have explicitly reviewed what data Narrative Insights can summarize for Vendor Center / Shopper / other external roles. This is a data-exposure surface worth treating as a security control.
• Use OCI Credentials for Narrative Insights — off by default. When off, usage draws from a free NetSuite-provided monthly pool; when on, it bills against your Oracle Cloud account for unlimited usage. Flip this only after you understand the OCI billing implications.

User License Information

Oracle has consolidated documentation around license types, how licenses are counted, and SuiteCloud Plus / Concurrent Web Services User guidance. No behavioral change — this is a docs pointer, not a release item. Worth a re-read if you manage a Concurrent Web Services User pool.

Bottom line for engineers

1. Audit address subrecord usage in every integration before your account is upgraded. This is the only item in the release that can silently change script and integration output.
2. Replace any custom intercompany elimination Workbook joins with the new dataset.
3. Decide explicitly whether Narrative Insights should be enabled for external roles and whether to bill via OCI — both are security/cost decisions, not defaults to leave alone.
4. Take advantage of unlimited sandbox refreshes to validate the address filtering change before it hits production.