2026.2 August Minor Release: Event Subscriber Script Type, AI Units Consolidation, and Banking Auto-Match

SuiteScript

New Event Subscriber Script Type

A new Event Subscriber script type enables asynchronous follow-up processing after record create, update, and delete events. Unlike User Event afterSubmit, these scripts execute after the originating record operation has already completed and returned to the user, so they cannot block the transaction.

• Entry point: handle(options) in a SuiteScript 2.1 module.
• Subscription criteria are defined in an eventsubscriber SDF custom object (XML).
• Governance limit: 1,000 usage units per execution.
• Time limit: 3,600 seconds (1 hour).

This is a significant addition for teams that currently chain Map/Reduce or Scheduled scripts off afterSubmit to avoid blocking. The new script type gives you a first-class, event-driven pattern for that workflow.

N/runtime.isNextActive()

New method runtime.isNextActive() returns a boolean indicating whether NetSuite Next is active for the current user session. Available in both client and server script contexts. Use this to branch logic for UI-layer scripts that behave differently under the new Next shell.

N/llm Module Changes

• Cohere Command A Vision model is now available via llm.generateText(options) and llm.generateTextStreamed(options). You can pass an image and receive captions, descriptions, or chart analysis in the response. Check llm.ModelFamily for the new enum value.
• ociConfig object deprecated. Passing OCI credentials to N/llm, N/documentCapture, or N/task API calls no longer has any effect. No error is thrown, but values are silently ignored. All LLM usage now consumes NetSuite AI Units exclusively.
• New methods: llm.getRemainingUsage() and llm.getRemainingUsage.promise() return remaining AI Units for LLM and embed requests.
• Deprecated methods (still functional, but delegate to the new method internally):
  • llm.getRemainingFreeUsage() / .promise()
  • llm.getRemainingFreeEmbedUsage() / .promise()
  • documentCapture.getRemainingFreeUsage() / .promise()

SuiteCloud Development Framework (SDF)

Custom Tool Validation on Deploy

SDF now validates toolset objects at deployment time. Validation covers the JSON-RPC schema, referenced files, and the mapping between tool definitions and their SuiteScript methods. A failed validation halts deployment with a descriptive error. This applies to both SuiteApp and Account Customization Projects (ACPs).

New agentskill Custom Object

SDF supports a new agentskill object type for deploying custom skills. Each object references a File Cabinet folder containing a SKILL.md file (name, description, instructions). Key constraint: the name and description in the XML definition must match the corresponding values in SKILL.md.

• SuiteApp projects: skill folder lives inside the SuiteApp folder.
• ACPs: skill folder lives in /SuiteScripts/Skills/ at the File Cabinet root.

Banking

Automatic Exact-Match Reconciliation (On by Default)

A new account-level preference, Automatically Accept Exact Matches, is enabled by default as of this release. When set, NetSuite auto-submits unambiguous single-match reconciliation suggestions immediately after generation—triggered by manual imports, Automated Bank Statement Import, bank feeds, or manually run reconciliation rules.

Auto-submission does not apply to: entity-enriched suggestions, multi-option matches, or AP/AR payment application suggestions. If the importing user lacks the Reconcile permission at Create/Edit/Full level, suggestions remain pending.

Administrators can disable this at Setup > Accounting > Accounting Preferences > Bank Matching and Reconciliation.

On the Reconcile Account Statement page, the Review subtab shows System in the Submitted By column for auto-submitted matches.

Create Payments from Bank Matching

You can now create customer payments (inbound) and bill payments (outbound) directly from the Transactions to Match subtab at Transactions > Bank > Bank Matching and Reconciliation > Match Bank Data. Supports invoices, credit notes, bills, bill credits, installments, partial applications, and payment discounts. Bill payments requiring approval must still be created outside this workflow.

Inventory Management & Supply Planning

Automatic Work Order Creation

Supply Planning can now create work orders automatically after a planning run or when releasing planned work orders from the Planning Workbench, eliminating the separate Mass Create Work Orders step. Two new preferences at Setup > Manufacturing > Manufacturing Preferences > Production Planning, Scheduling and Allocation:

• Create Work Orders for MPS Items
• Create Work Orders for MRP Items

Requires Assembly Items, Work Orders, and Material Requirements Planning features enabled.

New Inventory Optimization Results Workbook & Dataset

A new SuiteAnalytics workbook and dataset display stored item-location planning results in a single table: service levels, demand, lead-time metrics, Safety Stock, Reorder Point, and Preferred Stock Level. Results are stored snapshots—SuiteAnalytics does not recalculate. Requires Advanced Inventory Management and Inventory Optimization features, plus View permission on Inventory Optimization and Edit on SuiteAnalytics Workbook.

Accounting

IFRS 18 Income Statement Layout

A new IFRS 18 Standard Income Statement Layout is available in the Financial Report Builder. It organizes income statement data into the five IFRS 18 categories: Operating, Investing, Financing, Income taxes, and Discontinued operations. IFRS 18 replaces IAS 1 for annual reporting periods beginning on or after January 1, 2027. You can add filters (e.g., Account Name) per section. Works with Income Statement and Comparative Income Statement reports.

Intelligent Close Manager Enhancements

• User-defined custom close tasks (Custom tab in the portlet).
• Narrative insights generation from the portlet.
• New Run Intercompany Eliminations task on the Accounting tab.

SuiteTax Hub

New centralized page at Setup > Accounting > Taxes > SuiteTax Hub for Legacy Tax accounts preparing for SuiteTax migration. No additional setup required.

Account Setup & Administration

Auto-Generated Numbers History (as of Aug 17, 2026)

The Auto-Generated Numbers page now includes a History column for supported document types. The History window shows latest changes to numbering fields: date, user, context, previous value, and new value. Navigate to Setup > Company > Auto-Generated Numbers > Document Numbers subtab. Note: this is not a complete audit log—it only shows the most recent change per field, excludes Update Initial Number / Update boxes, and does not support custom transactions.

Very Strong Password Policy (as of Aug 17, 2026)

New password policy option requiring all four character groups (uppercase, lowercase, digits, special characters). Set at General Preferences.

Inactive Subsidiaries Hidden from Subsidiary Context

Inactive subsidiaries without posted transactions are now hidden from the Subsidiary Context dropdown in reports. Those with posted transactions remain visible for historical reporting.

NetSuite Next Access Management

Administrators can control NetSuite Next access per role at Setup > Company > AI > NetSuite Next Access (options: NetSuite Next only, Optional, Blocked). Partner Center, Customer Center, Employee Center, and Vendor Center roles are not eligible.

AI & Ask Oracle

AI Preferences Cleanup

• Usage tables removed from AI Preferences subtabs—all usage now consolidated under AI Units.
• OCI configuration settings removed from AI Preferences (Settings subtab, Text Enhance, Narrative Insights).
• Prompt Studio and SuiteScript subtabs removed from AI Preferences.

New Ask Oracle Core Skills

Six new ready-to-use core skills:

• ns-fulfillment-performance-insights – fulfillment lifecycle timing analysis
• ns-inventory-balance-viewer – real-time inventory levels
• ns-inventory-impact-review – transaction inventory impact
• ns-item-creation-assistant – item extraction from uploaded catalogues
• ns-pricing-configuration-review – read-only pricing config review
• ns-workflow-manipulation – creates basic SuiteFlow workflow drafts from natural language

Ask Oracle can also now use saved searches as a data source—reference a saved search by title or script ID in your prompt.

Vendors & Purchasing

Document Highlighting Removed from Bill Capture

The highlight tool has been removed from the document preview for scanned vendor bills. Uploading, emailing, reviewing, and creating vendor bills via Bill Capture still works. If your process depends on document highlighting during review, update it to remove that dependency.

What to Do

1. Audit ociConfig usage. Search your SuiteScript codebase for any references to ociConfig in calls to N/llm, N/documentCapture, or N/task. The parameter is silently ignored now—remove it and ensure your AI Units allocation is sufficient.
2. Replace deprecated remaining-usage methods. Replace calls to llm.getRemainingFreeUsage(), llm.getRemainingFreeEmbedUsage(), and documentCapture.getRemainingFreeUsage() with llm.getRemainingUsage(). The old methods still work but delegate to the new one internally.
3. Evaluate Event Subscriber scripts. If you have Map/Reduce or Scheduled scripts triggered from afterSubmit for async post-processing, consider migrating to the new Event Subscriber script type for cleaner architecture and a dedicated 1,000-unit governance budget.
4. Review the auto-match reconciliation preference. The Automatically Accept Exact Matches preference is on by default. If your reconciliation workflow requires manual review of all matches, disable it immediately at Setup > Accounting > Accounting Preferences.
5. Update SDF toolset objects. If you deploy toolset custom objects via SDF, be aware that deployment now validates JSON-RPC schemas and script method mappings. Fix any mismatches before your next deploy or it will fail.
6. Prepare for IFRS 18. If your organization reports under IFRS, the new layout is available now for testing. IFRS 18 is mandatory for annual periods starting January 1, 2027.
7. Remove Bill Capture highlight dependencies. If your vendor bill review process depends on the document highlighting tool, update your procedures—the tool is gone.
8. Test runtime.isNextActive(). If you maintain client scripts or Suitelets with UI logic that may behave differently under NetSuite Next, use this new method to branch behavior.