NetSuite 2026.2 Release Readiness Checklist

What changed

In 2026.2, SuiteQL queries and Analytics datasets based on generic transactions use Transaction.tranDate as the default sort when no explicit sort order is specified. Previously, Transaction.tranDisplayName was used.

Why it matters

A query may continue to return correct rows while returning them in a different order. Any script, report, integration, or downstream process that relies on implicit result ordering will be affected.

What to check

• Identify all SuiteQL queries that have no explicit ORDER BY clause.
• Identify Analytics datasets with no explicit sort configured.
• Review every script that consumes SuiteQL results and depends on ordering.
• Review every integration that consumes SuiteQL results.
• Add explicit ORDER BY to queries wherever business logic depends on sequence.

What changed

2026.2 adds the ability to start order fulfillment directly from Sales Order record lists without opening each individual record.

Why it matters

This changes the fulfillment workflow for operations teams and may affect training, role permissions, and documented processes.

What to check

• Review the current fulfillment workflow.
• Determine whether users should adopt the new list-level fulfillment process.
• Validate permissions for relevant fulfillment roles.
• Test representative Sales Orders in Sandbox.

What changed

NetSuite users can set up passwordless authentication using passkeys for account login as of 2026.2.

Why it matters

This is an optional authentication change. IT and security policy must be reviewed before enabling passkeys across the organization.

What to check

• Review your security policy to determine whether passkeys should be enabled.
• Test user enrollment in Sandbox.
• Test login recovery procedures with passkeys.
• Test passkey login with representative user roles.

What changed

FIDO2-compliant passkeys can now be used as a second authentication factor. Administrators can disable this option to keep users on authenticator apps.

Why it matters

Existing two-factor authentication workflows may change. The administrator policy must be explicitly set to match the organization's security requirements.

What to check

• Review your current two-factor authentication policy.
• Test FIDO2 passkey enrollment in Sandbox.
• Confirm fallback authentication procedures remain documented.
• Set and document the administrator policy on passkey 2FA.

What changed

Starting with NetSuite 2027.1, integrations using NLAuth will stop working. The only exception is the existing IssueToken endpoint use case explicitly excluded by Oracle. Oracle recommends migrating to OAuth 2.0 as soon as possible.

Why it matters

Any integration still using NLAuth will break when 2027.1 releases. This is a hard cutoff, not a deprecation warning. Accounts with custom integrations, RESTlets, or external applications using NLAuth need a migration plan now.

What to check

• Inventory every NetSuite integration in your account.
• Identify all NLAuth usage across integrations and RESTlets.
• Identify external applications authenticating via NLAuth.
• Create OAuth 2.0 migration plans for each affected integration.
• Prioritize business-critical integrations for migration first.

What changed

Starting in 2027.1, new integrations using Token-Based Authentication cannot be created. Oracle is preparing for broader TBA end of support, tentatively targeted for 2028.1. Existing TBA integrations continue until the final end-of-support date.

Why it matters

Any integration being designed or built now should not use TBA. Existing TBA integrations need a migration roadmap before 2028.1.

What to check

• Inventory all existing TBA integrations.
• Stop designing any new integrations that use TBA.
• Identify which existing TBA integrations should migrate to OAuth 2.0 first.
• Create a migration roadmap aligned to the 2028.1 deadline.

What changed

New OAuth 2.0 Authorization Code Grant integrations will require PKCE (Proof Key for Code Exchange) starting in NetSuite 2027.1.

Why it matters

Integrations currently under development using OAuth 2.0 Authorization Code Grant need to be built with PKCE from the start. This affects architecture decisions being made now.

What to check

• Review current OAuth 2.0 Authorization Code Grant integration architecture.
• Review integrations currently under development.
• Confirm that all future OAuth 2.0 Authorization Code Grant implementations include PKCE support.
• Update internal integration standards and documentation to require PKCE.

What changed

2026.2 adds system-note visibility for matching and reconciliation activity, so the audit trail now captures who performed matching.

Why it matters

This improves audit trail completeness for bank reconciliation. Finance teams should confirm that reconciliation audit requirements are met and that existing audit reports reflect the new note structure.

What to check

• Review reconciliation audit requirements against the new system notes.
• Confirm finance users can identify who performed matching activity.
• Validate any existing audit reports that cover reconciliation activity.

What changed

The reconciliation experience includes new matching and submission information, additional filtering options, transaction details, and UI enhancements.

Why it matters

Finance users will encounter a changed reconciliation interface. Existing processes should be tested to confirm expected behavior is preserved.

What to check

• Test existing reconciliation processes in Sandbox after 2026.2.
• Validate matching behavior.
• Validate transaction submission.
• Test finance-user permissions within the new UI.
• Confirm existing reconciliation reports remain readable and correct.

What changed

NetSuite introduces suggested transaction matches within bank reconciliation, proposing potential matches for finance users to review and accept.

Why it matters

Finance users will see match suggestions alongside their existing workflow. The acceptance process and reconciliation impact should be understood before going live.

What to check

• Test suggested matches in Sandbox.
• Review the acceptance process for suggestions.
• Determine whether finance users need training on the new workflow.

What changed

NetSuite can suggest payments to apply against open invoices and open payables.

Why it matters

Suggested application changes the AR and AP workflow. The approval process and accounting treatment should be validated before relying on suggestions in production.

What to check

• Test payment application suggestions in Sandbox.
• Validate the accounting treatment for accepted suggestions.
• Review the user approval process for applying suggested payments.

What changed

Manual matches and cleared transactions can now be automatically submitted based on the new reconciliation functionality.

Why it matters

Automatic submission changes existing reconciliation controls. Finance teams should understand what submits automatically, what still requires manual approval, and whether reconciliation SOPs need updating.

What to check

• Review current reconciliation controls and approval steps.
• Test automatic submission behavior in Sandbox.
• Ensure finance users understand what the new automatic submission means for their process.

What changed

NetSuite now warns that imported bank transaction memo fields may contain sensitive information such as bank account numbers, credit card numbers, and addresses.

Why it matters

If memo fields contain sensitive data, this has implications for data retention, access controls, and reporting. Finance and IT teams should audit what data enters these fields via bank imports.

What to check

• Review bank import files to determine whether sensitive data appears in memo fields.
• Confirm whether sensitive data is entering NetSuite via bank imports.
• Review data-retention and access policies for bank transaction records.
• Review any reports or dashboards that expose bank transaction memo data.

What changed

For Multi-Location Inventory accounts, 2026.2 allows initial average cost to be set for new inventory and assembly items at each individual location.

Why it matters

Costing may now differ by location. Item creation workflows and location-level cost reporting should be tested to confirm expected behavior.

What to check

• Review the item creation process for inventory and assembly items.
• Test new item creation with location-level costing in Sandbox.
• Validate costing results at the location level.
• Confirm estimated assembly costing where applicable.

What changed

New Demand View and Supply View pegging analysis workbooks are available for Supply Planning.

Why it matters

Planning teams may benefit from the new views. Existing supply-planning processes should be validated in Sandbox to confirm no behavioral changes.

What to check

• Determine whether supply planners need the Demand View and Supply View workbooks.
• Validate existing supply-planning processes in Sandbox.
• Identify reporting opportunities from the new views.

What changed

NetSuite adds Rough-Cut Capacity Planning capabilities associated with Supply Plan Definitions and work-center capacity.

Why it matters

Manufacturing and supply chain teams should evaluate whether this feature should be adopted and whether it affects existing supply plan assumptions.

What to check

• Review current capacity planning processes.
• Identify relevant Supply Plan Definitions.
• Test capacity assumptions in Sandbox.
• Determine whether Rough-Cut Capacity Planning should be enabled and adopted.

What changed

NetSuite 2026.2 adds support for bin transfers involving vendor-consigned inventory.

Why it matters

Accounts using vendor-consigned inventory should test bin transfers to confirm inventory balances and reporting are correct after 2026.2.

What to check

• Test representative consigned inventory bin transfers in Sandbox.
• Validate inventory balance calculations after transfers.
• Validate inventory reporting after transfers.

What changed

NetSuite introduces Inventory Optimization functionality for reorder-point planning, incorporating lead times, safety stock, and projected exceptions.

Why it matters

Accounts managing inventory replenishment should evaluate this feature and test whether it affects existing reorder-point logic or planning outputs.

What to check

• Review current reorder-point planning processes.
• Identify items applicable to Inventory Optimization.
• Review lead-time and safety-stock settings for applicable items.
• Review reorder-point assumptions and projected exceptions in Sandbox.
• Evaluate whether the feature should be adopted.

What changed

Price Rules can now use Item Collections and Customer Groups, including dynamic collections and groups that update automatically as membership changes.

Why it matters

Dynamic collections mean a Price Rule's scope can change without a manual update. Existing pricing configurations should be reviewed to ensure dynamic membership does not create unintended pricing behavior.

What to check

• Review existing Price Rules for any that reference Item Collections or Customer Groups.
• Identify rules where dynamic membership could affect pricing outcomes.
• Test customer-specific and item-specific pricing scenarios in Sandbox.

What changed

Sales Order lines now provide additional context for how the price on each line was determined.

Why it matters

Sales users and pricing administrators will see more detail on how prices were set. Training may be needed to explain the new fields and their source.

What to check

• Test representative pricing scenarios in Sandbox.
• Train sales users on the new pricing context fields.
• Validate customer-specific pricing outcomes.

What changed

Pricing records can now be managed through the CSV Import Assistant.

Why it matters

This opens a new pathway for bulk pricing maintenance. Accounts with large pricing structures maintained manually should evaluate whether CSV import improves the process and establish governance around CSV uploads.

What to check

• Identify current manual pricing maintenance processes.
• Determine whether bulk CSV import would improve the process.
• Establish CSV governance and validation procedures before using in production.

What changed

NetSuite introduces a preference to exclude zero-quantity components from manufacturing transactions.

Why it matters

If scripts, Saved Searches, SuiteQL queries, integrations, or reports currently process or expect zero-quantity component lines on manufacturing transactions, enabling this preference could break that logic. This is a structural change to manufacturing transaction data.

What to check

• Review whether any scripts process zero-quantity component lines on manufacturing transactions.
• Review Saved Searches filtering on manufacturing transaction components.
• Review SuiteQL queries selecting manufacturing component data.
• Review integrations that receive manufacturing transaction data.
• Review reports based on manufacturing component quantities.
• Test manufacturing transactions in Sandbox before enabling this preference.

What changed

NetSuite changes how assembly components associated with Advanced Bill of Materials are stored for affected manufacturing transactions.

Why it matters

This is a data storage change, not a UI change. Any script, SuiteQL query, integration, or report that reads assembly component data from manufacturing transactions may return different results after 2026.2.

What to check

• Review transaction-line Saved Searches for manufacturing transactions.
• Review SuiteQL queries that read assembly component data.
• Review SuiteScript accessing manufacturing transaction sublist lines.
• Review integrations that receive manufacturing transaction component data.
• Compare pre-release and post-release transaction data in Sandbox.

What changed

Manufacturing charge costs can now be updated in bulk.

Why it matters

This is primarily an efficiency improvement, but costing changes have financial reporting implications. Finance and manufacturing teams should validate costing outcomes after bulk updates.

What to check

• Review current manufacturing charge costing maintenance.
• Validate purchase-price and custom-cost behavior in Sandbox.
• Test costing results after bulk updates.

What changed

NetSuite CPQ introduces an AI Assistant designed to guide users through product configuration.

Why it matters

CPQ users may encounter the AI Assistant during configuration. Sales and CPQ teams should evaluate whether AI-assisted configuration fits the sales process before it is visible in production.

What to check

• Review CPQ product configuration in Sandbox.
• Evaluate whether AI-assisted configuration fits the sales process.
• Test representative product configurations.

What changed

NetSuite introduces an improved CPQ Configurator migration process.

Why it matters

CPQ migrations carry risk to configuration and transaction data. The migration sequence and bundle requirements must be documented and understood before migration is attempted.

What to check

• Document the full migration sequence before starting.
• Validate migration bundle requirements in Sandbox.
• Protect existing configuration and transaction data before migrating.
• Do not uninstall migration components without understanding the data implications.

What changed

CPQ configuration can support adding attachments to transactions.

Why it matters

This extends what CPQ can attach to resulting transactions. Accounts using CPQ should test to confirm attachments and permissions work as expected.

What to check

• Test attachment creation from CPQ configuration in Sandbox.
• Validate attachment permissions.
• Validate the resulting transactions.

What changed

NetSuite introduces automated payment adjustments.

Why it matters

Automated adjustments change existing manual payment processes. Finance teams should understand what triggers an automated adjustment and how it affects accounting and reconciliation.

What to check

• Identify current manual payment adjustment processes.
• Test automated adjustment behavior in Sandbox.
• Validate accounting treatment for automated adjustments.
• Validate reconciliation behavior after automated adjustments.
• Review approval controls.

What changed

SuiteBilling can now support usage billing where usage amounts are calculated externally and provided to NetSuite, rather than being calculated within NetSuite.

Why it matters

Accounts using SuiteBilling for usage-based revenue need to validate that external usage data flows correctly, billing calculations are accurate, and downstream accounting and revenue recognition are correct.

What to check

• Test external usage data ingestion in Sandbox.
• Validate billing calculations against external usage data.
• Validate downstream accounting transactions.
• Test revenue recognition behavior where applicable.
• Review integration error handling for failed usage data submissions.

What changed

Subscription Metrics functionality has been expanded in 2026.2.

Why it matters

Finance and revenue operations teams relying on subscription metrics for reporting should validate that existing metrics remain correct and explore whether expanded functionality affects reporting.

What to check

• Review recurring revenue metrics in Sandbox.
• Review subscription renewal processes.
• Validate existing subscription reporting.

What changed

The Payment Token Type field can now differentiate between different token types.

Why it matters

Accounts using payment tokens in integrations or reporting should review whether token type differentiation affects downstream logic or processing.

What to check

• Review payment integrations that use token data.
• Review payment reporting for token-related fields.
• Determine whether token type should affect downstream processing or routing.

What changed

NetSuite adds five Project Health Indicators: Planned vs. Actual Time Overrun, Overdue Tasks, Resource Coverage, Project Margin, and Unbilled Approved Charges.

Why it matters

Project managers and finance teams gain new visibility into project health. Existing project data should be validated against the new indicators to confirm they reflect accurate project state.

What to check

• Determine which health indicators are relevant to project managers.
• Validate project data in Sandbox against the new indicators.
• Review margin calculations for accuracy.
• Review unbilled approved charges for completeness.
• Establish ownership for projects showing exceptions in the new indicators.

What changed

Exports of lists, Saved Searches, and reports to Microsoft Excel now default to .xlsx rather than .xls.

Why it matters

Any downstream process that relies on .xls output, including macros, external imports, and reporting pipelines, may break. This is a broad change affecting all users who export to Excel.

What to check

• Identify all downstream processes that consume NetSuite Excel exports.
• Test macros that open .xls exports for compatibility with .xlsx.
• Test external imports that ingest NetSuite Excel output.
• Test external reporting processes.
• Validate formatting and data structure in the new .xlsx output.

What changed

Saved Searches can now be transferred to NetSuite Analytics Warehouse, allowing account-specific search data to be analyzed alongside standard Warehouse data.

Why it matters

This is a new data pathway. Accounts using Analytics Warehouse can bring custom Saved Search data into their analytics environment, but data governance should be considered before transferring searches.

What to check

• Identify high-value Saved Searches that could benefit from Analytics Warehouse analysis.
• Determine whether any searches should become Analytics Warehouse data sources.
• Review data governance policies for Analytics Warehouse before enabling.

What changed

NetSuite Analytics Warehouse can now distinguish NetSuite and Salesforce as separate data sources, including functional areas that share the same name in both systems.

Why it matters

Accounts with both NetSuite and Salesforce data in Analytics Warehouse should validate functional-area mappings and check dashboards after 2026.2.

What to check

• Review existing NetSuite and Salesforce data models in Analytics Warehouse.
• Validate functional-area mappings after 2026.2.
• Check existing dashboards and reports for any data-source changes.

What changed

Advanced Record Customization provides a centralized layer where administrators can review, manage, and override supported record definitions. The first attribute available for override is the AI Description.

Why it matters

This is a new administration capability. Accounts should inventory supported record types and establish governance around who can configure overrides, before overrides are applied in production.

What to check

• Review supported record types in Sandbox.
• Identify any existing AI descriptions on records.
• Establish governance and access controls around override configuration.
• Document any account-level overrides applied.

What changed

Currency custom fields can now have a currency context configured. Oracle notes this is optional and that existing reporting is unchanged unless currency context is configured.

Why it matters

Finance and technical teams should inventory currency custom fields and evaluate where currency context would improve data clarity. Changes to existing fields should be tested carefully to avoid reporting regressions.

What to check

• Inventory currency custom fields across applicable record types.
• Identify fields where currency context is ambiguous.
• Review reporting implications before configuring currency context.
• Configure only where there is a clear business need.

What changed

AI Description fields have been added to custom records, custom fields, and custom transactions. Administrators can provide concise descriptions that NetSuite AI features use to understand custom objects.

Why it matters

This improves how NetSuite AI features interpret custom objects in your account. Adding descriptions is optional but recommended for accounts that use or plan to use NetSuite AI features.

What to check

• Identify critical custom objects that AI features interact with.
• Add meaningful, accurate AI descriptions in Sandbox.
• Review AI-facing terminology for consistency.
• Establish ownership for maintaining AI descriptions over time.

What changed

The July 13 preview notes state that the 2026.2 versions of the SuiteCloud Extension for VS Code, SuiteCloud CLI for Node.js, WebStorm plug-in, and SuiteCloud CLI for Java were not yet available at the time of the preview draft.

Why it matters

Development teams that upgrade SuiteCloud tooling before 2026.2 versions are released may face CI/CD pipeline or SDF deployment issues. Tooling availability should be confirmed before upgrading development environments.

What to check

• Check SuiteCloud tool availability before upgrading any development environments.
• Review CI/CD pipelines for SuiteCloud tooling version dependencies.
• Review SDF deployment processes.
• Verify development team tooling compatibility before 2026.2 reaches Production.
• Do not assume tooling availability based solely on the release notes.

What changed

REST SuiteQL now supports anonymous bound parameters, allowing query values to be supplied separately from the query string itself.

Why it matters

Integrations that build SuiteQL queries dynamically with user-supplied values should evaluate whether bound parameters can replace string-built queries. Bound parameters reduce injection risk and improve query reuse.

What to check

• Review dynamic SuiteQL integrations that incorporate user-supplied or runtime values.
• Identify queries where string-building creates maintenance or security concerns.
• Evaluate whether bound parameters should replace string-built queries.
• Test affected integrations in Sandbox.

What changed

REST Web Services now supports sequential processing of batch operations, allowing dependent operations to be chained within a single batch.

Why it matters

Integrations with dependent operations, such as parent/child record creation or order-dependent transactions, may benefit from sequential batch processing. Existing integrations using workarounds for operation ordering should be evaluated.

What to check

• Identify integrations with parent/child record creation dependencies.
• Review order-dependent transaction creation in integrations.
• Determine whether sequential processing can simplify existing integration logic.
• Test sequential batch operations in Sandbox.

What changed

SuiteTax introduces tax handling for term discounts on purchase transactions. Tax calculation on vendor term discounts has changed in 2026.2.

Why it matters

Accounts using SuiteTax and vendor term discounts need to validate tax calculations, resulting accounting transactions, and reconciliation in Sandbox before production. This has direct financial reporting implications.

What to check

• Test vendor bills with term discounts in Sandbox after 2026.2.
• Validate tax calculations on discounted purchase transactions.
• Validate resulting accounting transactions.
• Review reconciliation for affected transactions.
• Test credit and adjustment behavior.

What changed

NetSuite introduces Payment Runs, a new capability for preparing, reviewing, approving, and processing multiple payables in a single workflow.

Why it matters

Payment Runs is a new AP workflow. Existing Bill Payment processes should be reviewed to determine whether Payment Runs should be adopted, and the approval workflow should be validated in Sandbox.

What to check

• Review the existing Bill Payment process.
• Test Payment Runs in Sandbox.
• Review the approval workflow for Payment Runs.
• Review payment selection logic.
• Validate accounting entries generated by Payment Runs.

What changed

Bill Capture preferences have been enhanced around item and expense amounts and gross/net handling.

Why it matters

Changes to Bill Capture preferences can affect how vendor bills are captured and the amounts that appear on captured bills. AP teams should test representative vendor bill captures in Sandbox after 2026.2.

What to check

• Review current Bill Capture preference settings.
• Test vendor bill capture in Sandbox after 2026.2.
• Validate captured amounts for items and expenses.
• Test approval workflow behavior for captured bills.