Identifying Exceptions
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.
Exceptions are tracked and displayed on the Exception Management page at Lists > Accounting > Exception Management.
Exceptions are organized into two subtabs: Transaction Errors (Incorrect Amount, Incorrect Account, and Vendor Information Change), grouped by transaction and business flow, and Expected Transactions (Missing Transactions) in a separate subtab. Each subtab includes KPIs for the number of exceptions pending resolution and the potential financial impact of unresolved items. Additionally, The Transaction Errors subtab has a sensitivity slider to help you control how many exceptions are shown in the list.
EM evaluates transactions created or edited in the last hour and surfaces likely issues for review. When you click View Details on an exception, EM displays:
-
An explanation why the transaction was flagged.
-
A short list of similar, error-free transactions for comparison.
-
Quick actions to Review Transaction, mark Resolved or No Action Needed, and Reopen if required.
-
For missing transactions, there is also an option to Create Transaction to fill the expected item.
EM alerts you to the following exception types:
-
Incorrect Amount: This exception type flags lines where the posted amount deviates from your organization’s learned patterns for similar transactions (for example, by item, account, entity, or period).
-
Incorrect Account: Identifies lines coded to unexpected accounts based on prior posting behavior; surfaced hourly with detected vs. expected account details and links to similar transactions.
-
Vendor Information Change: Monitors high‑risk changes to vendor data (for example, bank account, tax ID, payee name, address) following recent payments, and surfaces suspicious edits for swift investigation.
-
Missing Transactions: Learns recurring patterns and predicts expected activity. When an expected item isn’t posted by the due date, EM creates an exception with details and an option to Create Transaction for the missing activity.