Accounting
NetSuite 2026.1
2026-04-20

EPM Gets AI Assistants for Reconciliation, Cost Allocation, and Narrative Reporting

NetSuite 2026.1 adds ML-driven transaction matching and reconciliation assignment assistants, a generative-AI agent for Profitability and Cost Management models, and embedded generative AI in Narrative Reporting. All features ship inside EPM integration SuiteApps — no custom SuiteScript surface is documented.

Affects:Account Reconciliation SuiteAppProfitability and Cost Management SuiteAppNarrative Reporting SuiteAppEPM Connector SuiteApps

What changed

NetSuite 2026.1 introduces three categories of AI assistants embedded in the Enterprise Performance Management (EPM) integration SuiteApps. These are SuiteApp-level features — Oracle has not documented any new SuiteScript modules, REST endpoints, or record types associated with them.

Account Reconciliation: Transaction Matching Assistance

  • An ML model analyzes your historical manual-match patterns and suggests potential transaction matches.
  • Each suggestion includes a confidence score so reviewers can accept or discard matches at a glance.
  • The model retrains on your approvals, so prediction quality should improve over time.

Account Reconciliation: Reconciliation Assignment Assistance

  • A separate ML model predicts values for specified reconciliation profile attributes based on historical assignment data.
  • Predictions also carry a confidence percentage for review before acceptance.
  • Designed to progressively automate recurring reconciliation assignments.

Profitability and Cost Management (PCM) Agent

  • A generative-AI, natural-language agent for building, executing, and analyzing cost allocation models.
  • Accepts plain-language commands — model creation, execution, and ad-hoc profitability queries.
  • Intended to reduce the setup time for complex allocation rule chains and make results more transparent to non-technical users.

Narrative Reporting: Embedded Generative AI

  • Auto-generates narrative summaries of variances, comparisons, and causal factors within financial reports.
  • Supports interactive natural-language queries and chart generation against reporting data.
  • Highlights key insights inline to accelerate variance analysis.

Technical details Oracle did not provide

The release note is light on implementation specifics. Notable gaps:

  • No SuiteScript or REST API surface is mentioned. It is unclear whether confidence scores or AI suggestions are exposed on any standard or custom record, or whether they can be read/written via N/record, N/query, or the REST Record API.
  • No governance or licensing information. Oracle does not state whether these AI features require an additional EPM license tier, a separate AI add-on, or specific role permissions.
  • No data-residency or model-training details. If your organization has data-sovereignty requirements, confirm with Oracle where inference runs and whether your transaction data is used in shared model training.
  • SuiteApp bundle IDs for the updated EPM Connector, Planning and Budgeting Sync, Account Reconciliation Sync, and Close Management and Consolidation Sync are not listed. Check SuiteApp Marketplace or your installed bundles for version bumps.

What to do

  1. Check your EPM SuiteApp versions. Navigate to Customization > SuiteBundler > Search & Install Bundles > List and verify you are on the 2026.1-compatible versions of the Account Reconciliation Sync, EPM Connector, and related bundles.
  2. Review AI feature availability. Oracle references a central Features with AI page in the Help Center. Confirm which features are enabled by default vs. opt-in for your account, especially if you are in a regulated industry.
  3. Validate downstream integrations. If you have scripts or integrations that read reconciliation status, matching results, or PCM allocation outputs, test them in Sandbox after the 2026.1 upgrade. New AI-generated fields or statuses could surface unexpected values.
  4. Assess data-privacy implications. Before enabling ML-based transaction matching, confirm with Oracle whether match-history data leaves your NetSuite tenant and whether you can opt out of model retraining on your data.
  5. Train reconciliation teams. Confidence-score-driven workflows change the review process. Ensure reconcilers understand how to interpret scores and that your approval policies account for AI-suggested matches.