SuiteCloud Platform
NetSuite 2026.2
2026-10-19

2026.2 October Monthly: Event Subscriber Scripts, Expanded MCP Tools, and Banking Record Exposures

The October 2026.2 monthly release introduces the Event Subscriber async script type, expands the MCP Standard Tools SuiteApp with record-action and file-cabinet endpoints, exposes banking reconciliation records via SuiteScript and REST, and adds document-relevance ranking to the N/llm module.

Affects:SuiteScript 2.1N/llm ModuleN/documentCapture ModuleN/machineTranslation ModuleSuiteCloud Development Framework (SDF)REST Web ServicesMCP Standard Tools SuiteAppSuiteAnalytics ConnectSuiteCloud Extension for VS CodeCompliance 360 SuiteAppProject Resource Management SuiteApp

The October monthly update for NetSuite 2026.2 is one of the more developer-heavy drops this cycle. It spans a new script type, a significant expansion of the MCP tool surface, banking-record exposure across both SuiteScript and REST, and several SDF object additions. Below is a breakdown of every code-impactful change.

Event Subscriber Script Type (SuiteScript 2.1)

A new script type — Event Subscriber — runs asynchronously after supported record events. Think of it as a fire-and-forget post-submit hook that decouples downstream logic from the user's save transaction.

  • Has its own JSDoc declaration tag (check the updated SuiteScript 2.1 JSDoc Validation topic for the exact annotation).
  • Subject to its own governance-unit allocation and execution-time limits (listed under the updated Script Type Usage Unit Limits and Script Execution Time Limits topics).
  • Deployable via SDF as XML definitions — a new eventsubscriber SDF custom object type has been added, with documented fields, attributes, and subscription criteria.

This is a genuinely new execution model. If you currently chain user-event afterSubmit scripts or scheduled scripts to handle post-save side effects, Event Subscribers may be a cleaner replacement. Oracle's documentation does not yet clarify exactly which record events are "supported" or whether governance is pooled or per-subscriber — verify in the help center before migrating production logic.

MCP Standard Tools SuiteApp — Major Expansion

The NetSuite AI Connector Service (MCP) surface area roughly doubled this month. New tool functions:

Record Action Tools

  • ns_getRecordActionMetadata — retrieve metadata about available record actions.
  • ns_executeRecordAction — execute a record action programmatically.

File Cabinet Tools

  • ns_attachFile / ns_detachFile
  • ns_getFolderByPath
  • ns_getIdFromPath / ns_getPathFromId
  • ns_searchFiles

File Cabinet MCP Apps

  • File Cabinet Browser — browse folders.
  • Get File — retrieve file content.
  • Upload File — push files into the cabinet.

Record Tools (Updated)

  • ns_getRecordTransformMetadata — introspect available record transforms.
  • ns_transformRecord — execute a transform (e.g., Sales Order → Invoice).

Runtime Tools

  • ns_getSessionInfo — return current session context.

If you are building external AI clients that interact with NetSuite via MCP, these tools mean you can now manipulate file-cabinet assets, trigger record actions (approve, reject, fulfill, etc.), and run record transforms without writing intermediary SuiteScript. You can also configure File Cabinet folder access for custom tools — see the updated Managing Custom Tools in NetSuite topic for the permission setup.

Banking Records Exposed via SuiteScript & REST

Four banking-related records are now scriptable and available through REST web services:

  • Bank Reconciliation Suggestion (includes record actions for accept/reject)
  • Banking Statement
  • Banking Transaction
  • Transaction Match

The SuiteScript exposure includes record-action support, meaning external AI clients can accept or reject bank reconciliation suggestions through MCP. The REST exposure follows the standard /services/rest/record/v1/ pattern — check the updated REST Browser for exact endpoint paths and supported fields once your account is on 2026.2 October.

N/llm Module Updates

  • Document relevance ranking: You can now rank documents by relevance to a prompt. This is useful for RAG-style workflows where you need to prioritize which documents to feed into a generation call.
  • Code samples across N/llm, N/documentCapture, and N/machineTranslation modules have been rewritten to SuiteScript 2.1 syntax.
  • A bug in the Clean Up Content for Text Area Fields After Saving a Record sample was fixed — the correct pattern is results[0].text and results[1].text to access LLM response objects.

SDF: Skills and Agent Definitions

The Skills as XML Definitions topic was updated with new requirements for defining and deploying custom skills. SDF agent definitions can now reference both core and custom skills — see the updated agentskill folder requirements and skill-availability rules if you are building or deploying AI agent configurations through SDF projects.

OAuth 2.0 for SuiteAnalytics Connect

Accounts using SuiteAnalytics Connect now support OAuth 2.0 authentication. If you are still using token-based auth for ODBC/JDBC connections, begin planning a migration — Oracle has historically deprecated older auth mechanisms within a few releases of adding OAuth support.

SuiteCloud Developer Assistant — VS Code Panel

A new dedicated panel replaces the previous Cline-integrated approach. Cline version 4.1.0 or later is now required. The feedback process has also changed — check the updated FAQ if you participate in the feedback program.

Other Notable Changes

  • Compliance 360: New audit approval workflow with submit/approve/reject/resubmit lifecycle and bulk audit-control assignment. New roles and permissions required.
  • Project Resource Management: End of support is October 27, 2026. Uninstall guidance and alternatives are documented — if you depend on this SuiteApp, migrate now.
  • AI Preferences renamed to Agent Preferences: The menu location has moved to Setup > Agent management. Any documentation or training materials referencing the old path need updating.
  • NetSuite CPQ: Create template-based assemblies with independent BOMs; clear single-row QTables. CPQ AI Assistant is now available in all supported regions.
  • Field Service Management: New 2026.07.3 version released.
  • NetSuite Connector: Custom data syncs between NetSuite and Salesforce now supported.
  • Localization: UAE electronic invoicing SuiteApp; Banxico currency exchange rate integration; Japan Bank Feeds SuiteApp (v3.0.0 with Manage Import Schedule); Brazil bank-slip reconciliation with Banco do Brasil.
  • Non-Profit Financial Management: Automatic release from use restrictions.
  • EPM Connector: 26.2.1 release notes; new Profitability and Cost Management Sync SuiteApp (initial 26.1 release).

What to Do

  1. Evaluate Event Subscriber scripts for any afterSubmit or scheduled-script logic that would benefit from async, decoupled execution. Review governance limits before adopting.
  2. Update SDF projects that define agent skills or will adopt Event Subscriber deployments — the eventsubscriber custom object and updated agentskill folder rules may require manifest and project-structure changes.
  3. Test MCP integrations against the expanded tool set. If you have external AI clients, the new record-action and file-cabinet tools may eliminate custom SuiteScript middleware.
  4. Review banking-record access if you are building reconciliation workflows — the new SuiteScript and REST exposures plus MCP record actions provide three distinct integration paths.
  5. Audit N/llm usage: If you use the document-cleanup sample, update to the corrected results[0].text / results[1].text pattern. Explore the new relevance-ranking capability for any RAG implementations.
  6. Migrate off Project Resource Management before October 27, 2026. Follow the documented uninstall guidance and evaluate alternatives.
  7. Plan OAuth 2.0 migration for SuiteAnalytics Connect ODBC/JDBC connections.
  8. Update VS Code extension and ensure Cline ≥ 4.1.0 if you use SuiteCloud Developer Assistant.
  9. Update internal references from AI Preferences to Agent Preferences under Setup > Agent management.