Enhancements to Filtering for Revenue Arrangements in NetSuite

TL;DR

The latest enhancements to the Update Revenue Arrangements and Revenue Plans page in NetSuite 2026.1 introduce new filtering options. These allow users to narrow down selection criteria, mitigating the risk of accidental updates and boosting system performance.

What Are the New Enhancements?

Starting with these enhancements, you can now utilize additional filters to refine which source records you wish to include in your updates. This means NetSuite will only update revenue arrangements and plans that match your specified filters, streamlining the process considerably.

Benefits of the New Filters

• Prevent Accidental Updates: By refining your selection with filters, you reduce the risk of unintentionally modifying records that should remain unchanged.
• Improved Performance: Narrowing down the update criteria not only makes the update process faster but also minimizes the load on the system, enhancing overall efficiency.

Status Column Update

A new Criteria column has been introduced in the Status section. By selecting Criteria summary, you can access the Criteria summary page where you will find a detailed list of all filters applied to the submission ID during the revenue arrangements and plans update.

System Requirements

To take advantage of these new filtering options, ensure that the Advanced Revenue Management (Essentials) feature is activated. If you are unsure how to enable this feature, you can refer to the documentation on Enabling the Advanced Revenue Management (Essentials) Feature.

Manual and Automatic Updates

NetSuite allows revenue arrangements and elements to be updated based on the setting for Revenue Arrangement Update Frequency. If set to automatic, updates occur every three hours following source changes that are relevant to revenue management. Manual updates can be performed based on subsidiary permissions, which automatically dictate which arrangements are subject to change.

Filter Conditions

You have the capability to implement filters based on:

• Date range
• Record type
• Accounting book (for Multi-Book Accounting)

While this makes it easier to manage updates, it’s important to note that you cannot select individual revenue arrangements for manual updates.

Conclusion

With these enhancements, users can expect a decreased likelihood of mishaps when updating revenue arrangements and plans, along with a noticeable uptick in system performance and responsiveness.

Who This Affects

• Administrators: Responsibilities include managing the settings and permissions for revenue arrangement updates.
• Finance Teams: They need to understand how to utilize the new filters to streamline their workflows.
• Users with Update Permissions: Any role involved in updating revenue arrangements and plans will benefit from these enhancements.

Key Takeaways

• New filters enhance the filtering capabilities on the Update Revenue Arrangements and Revenue Plans page.
• A new Criteria column provides transparency on which filters were applied.
• The feature requires the Advanced Revenue Management (Essentials) to be enabled for successful updates.

Additional Enhancements in 2026.1

Journal Line Sublists Standardized to Keyed for Reliable Line-Level Updates

With the 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, allowing integrations (REST, CSV, and SOAP) to reference these keys for reliable updates. 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.

Important: 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:

• Working with Sublists
• Sublist Data Import
• Sublists in SOAP Web Services

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 ran 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 users to wait for an approval before making necessary changes.