Accounting
NetSuite 2026.1 includes the following enhancements to accounting features:
-
Journal Line Sublists Standardized to Keyed for Reliable Line-Level Updates
-
Improved Custom GL Lines Plug-in Functionality for Secondary Accounting Books
-
Ability to Change Posting Period on Journal Entries with Pending Approval Status
-
Enhancements to Filtering for Updating Revenue Arrangements and Revenue Plans
Journal Line Sublists Standardized to Keyed for Reliable Line-Level Updates
With NetSuite 2026.1 release, journal line sublists are now standardized to a keyed configuration across all supported journal types. Each line has a unique line key and integrations (REST, CSV, and SOAP) can reference these keys to update only the intended lines. This allows you to safely modify, add, or remove specific lines without replacing the entire sublist, improving accuracy and reducing rework in financial processes and integrations.
Previously, several journal variants included a line identifier but were configured as non-keyed sublists. Therefore, integration tools could not reliably update individual lines, and attempts to do so sometimes caused issues that prevented users from loading or editing the affected journals.
No new feature to enable for this enhancement, existing permissions apply.
Integrations should work as expected for NetSuite accounts using the default configuration. However, if your integration reuses the same identifier on multiple lines, updates may fail validation after this change. Please review and test any process that updates journal lines before upgrading to NetSuite 2026.1.
For more information about sublists, see the help topics:
Improved Custom GL Lines Plug-in Functionality for Secondary Accounting Books
With the NetSuite 2026.1 release, the custom GL Lines Plug-in functionality has been improved to support transactions in secondary accounting books for all subsidiaries that have GL impact. This enhancement allows for the Custom GL Lines Plug-in to run in all accounting books active for any subsidiary participating in the transaction.
Previously, the Custom GL Line Plug-in didn't support inter-company transactions, consequently, the plug-in only run for the primary subsidiary, and the secondary subsidiaries were excluded even if the transaction had GL impact on their accounting books. This created inconsistencies between the primary and secondary accounting books.
For more information about Custom GL Lines Plug-in, see Custom GL Lines Plug-in Overview.
Ability to Change Posting Period on Journal Entries with Pending Approval Status
With the NetSuite 2026.1 release, users can now change the Posting Period field on journal entries with the Pending Approval status. This enhancement applies to Journal Entry, Intercompany Journal Entry, Advanced Intercompany Journal Entry, and Statistical Journal Entry types. This enhancement also enables better integration with SuiteApps such as Transaction Line Distribution, which creates journal entries for vendor bills that must post to the same accounting period. Consequently, both users and SuiteApps can now set the correct posting period for journals awaiting approval, ensuring consistent accounting, streamlining workflows, and reducing the likelihood of mispostings.
Previously, users could only update the posting period after a journal entry was approved. Any attempt to change the posting period on a journal entry pending approval wasn't saved, often requiring additional edits and increasing the risk of posting to the wrong period.
No additional permissions or configuration are required to use this feature.
For more information about accounting periods, see Accounting Period Management.
Enhancements to Filtering for Updating Revenue Arrangements and Revenue Plans
The Update Revenue Arrangements and Revenue Plans page now includes several new filters. These additional options let you narrow your update criteria, helping to prevent unintended revenue arrangement and plan updates and improve performance.
You can now use these filters to specify which source records to include in your update. NetSuite identifies source records that match your selected filters and updates only the revenue arrangements and revenue plans that are eligible for processing. For more information about these new filters, see Updating Revenue Arrangements.
Additionally, the Criteria column has been added to the Status section. Selecting Criteria summary opens the Criteria summary page, which displays all the filters that were applied to the corresponding submission ID when updating revenue arrangements and revenue plans.
You can update revenue arrangements and revenue plans only if the Advanced Revenue Management (Essentials) feature is enabled. For more information about enabling this feature, see Enabling the Advanced Revenue Management (Essentials) Feature.
Enhancements to Revenue Automation with Treatment Rules
You can now define additional fields in the Criteria subtab on the Recognition Treatment Rule page. Previously, rules were limited to Accounting Book, Date, Item Revenue Category, Source Type, Subsidiary, and Transaction Type.
In addition to the existing options, you can now select the following fields:
-
Class, Department, or Location.
-
Custom segments (transaction line-level only). You must have custom segments enabled to add this criteria. For more information, see Enabling the Custom Segments Feature.
-
Custom fields (transaction line-level only). For more information, see Creating a Custom Field.
These new criteria simplify revenue automation and provide greater flexibility by letting you manage recognition across broader business dimensions than individual items. While treatments could previously be grouped using attributes such as item revenue category or accounting book, you can now use new attributes, such as custom segments or custom fields.
These options let you group revenue elements and define different recognition behaviors in specific scenarios, controlling revenue scheduling, plan creation, allocation type, and allocation group for each revenue element. This gives you both simplified configuration and more granular control over revenue recognition and allocation.
For more information about this feature, see Rule-Based Recognition Treatment and Defining a Recognition Treatment Rule.
Automatic Approval for Reclassification Journal Entries
NetSuite now automatically approves all reclassification journal entries, eliminating the need for manual approval. This update prevents multiple reclassification journal entries from being approved, avoiding duplicate GL impacts.
The Approve Journal box no longer displays on the Create Reclassification Journal Entries and Schedule Reclassification Journal Entries pages. The following fields are now disabled for all pre-existing and newly-created reclassification journal entries:
-
Approval Status
-
Next Approver
-
Approved box
You can delete pre-existing reclassification journal entries that remain in Pending Approval or Rejected status, but you can't change their status.
If you have scripts, workflows, or customizations that reference approval fields on reclassification journal entries, review and update them as needed to ensure they continue to work correctly.
For more information about reclassification journals, see Reclassification of Deferred Revenue.
Exception Management Now Supported in Sandbox Accounts
NetSuites now supports using Exception Management (EM) in Sandbox accounts by running inference against models trained in the corresponding Production account. This enhancement lets teams safely evaluate EM workflows in Sandbox with production-quality results, without duplicating model training or requiring Sandbox data to meet historical volume thresholds.
How it works
A new feature flag, Exception Management Models, has been added alongside Exception Management. This new feature flag separates model training from inference on the UI, therefore, enabling Exception Management Models initiates the training of Exception Management AI models on your production data, and enabling Exception Management lets you turn on EM on the UI.
To work with EM in a Sandbox Account, in your production account, enable Exception Management Models to initiate model training on your production data, then enable Exception Management feature in your Sandbox to turn on the UI dashboard. In Sandbox, EM will run inference using the production trained models; only Sandbox transactions are sent for inference at the standard cadence (last two weeks at start, then hourly on edited or newly created transactions).
You can't enable Exception Management UI feature in both production and sandbox account if Exception Management Models is off in production. In production, if you enable the Exception Management Models alone, you'll be prompted to confirm this is intended for Sandbox testing.
You can't enable Exception Management Models feature directly in a Sandbox account.
Additionally, disabling Exception Management Models feature, will automatically disable Exception Management UI feature in production and all linked Sandboxes.
Availability and Compatibility
This change is backward compatible: any account that already had the Exception Management feature enabled will have both Exception Management Models and Exception Management enabled by default. Standard prerequisites and permissions still apply.
Exception Management (EM) remains a limited-release feature; if you don't see these options or need guidance, contact your NetSuite Account Manager.
For more information, see Working With Exception Management in Sandbox Accounts.
Class, Department, and Location (CDL) Role Restrictions on Account Records Updated to Include Unassigned Values
With this update, Class, Department, and Location (CDL) role restrictions on Account records have been updated to include unassigned values when the role restriction on the CDL segment is set to either 'Own and Subordinates Only' or 'Own, Subordinates, and Unassigned.' Both options now behave the same for Account records. This prevents empty Account datasets in Analytics and aligns Account behavior with the Chart of Accounts, improving consistency and data visibility.
Previously, Account records did not populate CDL restrictions themselves, and selecting 'Own and Subordinates Only' excluded unassigned Account records. This could result in empty Account datasets in Analytics when unassigned values existed and created inconsistency with Chart of Accounts and other record types where this change does not apply (for example, Sales Orders, Journal Entries).
This exception in behavior only applies to Account records. The standard CDL restrictions remain unchanged for other records.
For more information about CDL restrictions, see Setting Department, Class, and Location Restrictions.