Accounting

This release note was updated December 8, 2025.

NetSuite 2025.2 includes the following enhancements to accounting features:

Create Revenue Recognition Field Maps for Identical Custom Fields

You can now create revenue recognition field maps when the same custom field is selected in both the Source Field and Target Field. When creating a field map with the same custom fields in both the source and target, you must check the Automatically Update Target Field Value box.

This enhancement eliminates the need to manually update the target field value after the source field value changes. Previously, you had to update the target field whenever the source field changed because field maps with identical custom fields in both the source and target weren't supported. For more information about revenue recognition field mapping, see Mapping Revenue Recognition Fields.

Direct Revenue Posting for ARM Workflows

You can now configure SuiteFlow to automatically post transactions to an item revenue account using the Direct Revenue Posting option. This enhancement is particularly useful for transactions that recognize revenue at the time of the sales transaction date.

The Direct Revenue Posting option is now available under Field in the Parameters section when configuring a Set Field Value action in a workflow. You can check or clear the Checked box to control whether an item posts directly to an item revenue account:

If the Checked box is set, Advanced Revenue Management (Essentials) is disabled for that item.
If the Checked box is cleared, the item continues using ARM.

This enhancement gives you more flexibility when configuring ARM workflows in SuiteFlow.

To use this functionality, you must enable both Advanced Revenue Management (Essentials) and SuiteFlow.

For more information about enabling these features, see the following help topics:

For more information about direct revenue posting and setting field value actions, see the following help topics:

SuiteScript and REST Restrictions on Revenue Recognition and Reclassification Journal Entries

You can no longer use SuiteScript and REST Web Services to edit Debit and Credit amounts in the Lines subtab of revenue recognition and revenue reclassification journal entries. Previously, these amounts were editable through SuiteScript and REST. This restriction helps maintain data consistency in financial reporting.

This update aligns SuiteScript and REST behavior with existing UI restrictions, where these fields are already read-only. This editing restriction applies to both classic Revenue Recognition and Advanced Revenue Management (Essentials). For more information about editing restrictions, see Editing an Advanced Revenue Recognition Journal Entry and Reclassification of Deferred Revenue.

Improved Handling of Large Expense Allocation Schedules

With the NetSuite 2025.2 release, the allocation process now splits destination lines into multiple journal entries, each containing about 1,000 lines. All journal entries from the same allocation are grouped under the same allocation detail ID. This update helps prevent timeouts and allows large allocation schedules to be processed successfully without manual intervention.

Before this release, users could encounter a timeout error when running Expense Allocation Schedules that generated more than 10,000 allocation detail destination lines, primarily when using the Auto Populate option for multiple fields (such as Name, Department, Location, or Class). When this occurred, the allocation process stopped and no journal entries were posted.

Note:

This only applies to accounts updated to 2025.2. If you're using 2025.1 or earlier, the previous error rules still applies.

For more information about expense allocation schedules, see Expense Allocation Overview.

Introducing AI-Powered Exception Management (EM)

Important:

Exception Management (EM) is currently a limited release feature that’s not available to all customers. Eligibility depends on data volume and model training readiness; accounts with a large amount or insufficient historical data may be restricted. If you can’t access Exception Management, contact your NetSuite Account Manager for guidance and next steps.

Additionally, Exception Management is a production‑only feature and can't be enabled in Sandbox Accounts because those environments typically lack the required historical transaction data (approximately 18 months) needed for model training and inference.

With this update, NetSuite introduces Exception Management (EM), which helps you identify transaction outliers, unusual activity, and other changes to your normal transaction patterns. Exception Management uses machine learning to detect issues in near real time throughout the accounting period. It helps your team correct anomalies early, maintain accurate and complete books, enable real-time reporting, and reduce the end-of-period scramble. Exception Management addresses hard-to-spot gaps such as missing transactions and incorrect postings (incorrect amounts and accounts), accelerating period close and decision-making while lowering manual review effort.

To enable this feature, as an Administrator:

Go to Setup > Company > Enable Features > Accounting.
In Advanced Features, select EXCEPTION MANAGEMENT.

Note:

The ACCOUNTING PERIODS feature must be enabled first before activating Exception Management. For more information, see Accounting Period Management.

To access the Exception Management dashboard:

Go to Lists > Accounting > Exception Management.
Optional: Add the Exception Management portlet to your Home dashboard for quick access.

Note:

Access requires the Exception Management permission (View or Full). Visibility depends also on your role’s Subsidiary and Transaction Type permissions, you'll only see exceptions for subsidiaries and transaction types your role can access.

For more information, see Exception Management.

New Exception Type: Vendor Information Change in Exception Management

Starting in the December 2025 minor release, Exception Management adds Vendor Information Change exceptions to Transaction Errors tab. This capability continuously monitors high‑risk changes to vendor data, such as changes to bank accounts, tax IDs, payee names, or addresses, following recent payments, and flags them for swift investigation. Powered by configurable rules, it helps finance and compliance teams detect potential fraud in near real time without impacting core transaction processing, strengthening controls and customer trust.

For more information about exception types, see Identifying Exceptions.

General Notices