NetSuite Help Updates for AI, Banking and SuiteCloud

Review NetSuite help changes for AI, SFTP limits, custom tools, inventory optimization, regional tax guidance, and FSM documentation.

·8 min read·View Oracle Docs

NetSuite’s help updates cover AI agent plug-ins, banking, SuiteCloud development, inventory optimization, regional tax guidance, and Field Service Management. Priorities include the documented 5,000-file SFTP directory limit, custom-tool deprecation guidance, and Cline version requirement. The changes also include renamed and reorganized topics, which should not be mistaken for new product behavior.

What Changed in AI and Account Administration?

The SuiteCloud Agent Skills guide is now named AI Agent Plug-ins and SuiteCloud Agent Skills, with added information about AI Agent Plug-ins. The update does not identify specific plug-ins, supported platforms, or installation procedures. For related preparation, see SuiteCloud Agent Skills for AI development.

Core Skills documentation now includes five additional skills:

  • Inventory exceptions review.
  • Inventory movement insights.
  • Narrative insights records.
  • Narrative insights reports.
  • Supply chain persona based responses.

Generative AI Feature Availability in NetSuite now states that Text Enhance, Text Enhance Translations, Prompt Studio, and the SuiteScript N/llm module are available in all supported NetSuite regions. It also removes the HIPAA disclaimer for task prioritization because that disclaimer is no longer applicable. This is a specific documentation change, not a broader compliance statement.

Managing Agent Preferences now points readers to the NetSuite AI Units usage dashboard for instructions on viewing usage. A new topic covers viewing system notes for changes made by AI features, and a new NetSuite Next section has been added. Ask Oracle content was also restructured. The related NetSuite Next readiness and Ask Oracle guide provides additional preparation context.

Searching Bulk Processing Jobs now clarifies how NetSuite defines bulk processing jobs and how to view the process types available for an account. Administrators reviewing job-monitoring procedures should consult that topic; the update does not supply a navigation path, column list, or filter instructions.

Which Banking Changes Need Operational Review?

Auto Bank Statement Import documentation now identifies a 5,000-file limit for SFTP directories. Both the limitations topic and SFTP connection configuration guidance include this information. Directory file counts therefore belong on the review checklist for teams using this import method, but the update does not describe failure behavior or prescribe a cleanup procedure.

Preinstalled Bank Feeds Records adds connectivity plug-in and transaction parser columns, along with a note about requirements and restrictions for preinstalled bank feeds format profiles and related components. Review those references together when checking a feed configuration rather than treating the format profile as the only relevant component.

Payment application guidance now addresses suggestions that are no longer valid or available in three areas:

  • Creating, applying, and matching payments for open invoices.
  • Creating, applying, and matching payments for open payables.
  • Manually running reconciliation rules.

Automatic Submission of High-Confidence Matches adds guidance on identifying automatically submitted matches and clarifies that cash-in-transit suggestions require manual review. Reconciliation procedures should preserve that distinction rather than assuming all suggestions can follow the same automated path.

Two topic titles have also changed:

Current titlePrevious titleDocumented scope
Reconciling Bank DataReconciling Bank and Credit Card StatementsOverall bank reconciliation workflow
Reconciling Bank and Credit Card StatementsReconciling TransactionsStatement reconciliation

Teams maintaining internal procedures should check that references still lead readers to the intended workflow.

What Changed in Regional Tax and Localization Guidance?

Brazil deferred revenue and localization

Brazil Deferred Revenue Recognition adds dedicated topics for setting up the GL Lines plug-in deployment and adding the deferred revenue account to tax types. The setup overview now references those topics, while roles and permissions guidance adds default and required permissions for defining deferred revenue accounts.

Creating Deferred Revenue Settings for Brazil adds a step involving Enable Deferred Revenue Posting for Taxes. Review deployment, account assignment, permissions, and this field together before revising setup instructions. The update does not provide the field’s default or the permission names.

Other Brazil documentation changes include:

  • CNAB 240 Delivery Files: Removes the limitation about Pix payments in Banco do Brasil delivery files.
  • Brazil Localization best practices: Adds guidance about audience and context filters in script deployments.
  • Brazil predefined-record import status: Removes references to the FTEBR SDF Installer script because it no longer creates predefined records.
  • Brazilian Hub SuiteApp: Adds a known limitation, without describing its substance in these notes.

Norway, Japan, and other regional guidance

Norway Tax Reports now separates guidance for accounts with SuiteTax from guidance for accounts without it and adds information for version 1.16.0. Teams updating reporting procedures should select the section matching their account’s tax configuration.

SuiteTax Latam Engine documentation clarifies the introduction to tax determination rules and adds an example. Its best-practices and known-limitations topic also adds a recommendation about creating those rules; the recommendation itself is not reproduced in the update.

Japan’s deductible purchase tax guidance adds the following field options:

FieldAdded options
Tax Deductible70%, 30%, and 0%

Understanding E-invoicing Errors adds error codes observed during e-invoicing. Inclusions in the Payment Times Report 2025 also incorporates PTR 2025 updates. The notes do not identify the individual codes or reporting changes, so they are not sufficient on their own to revise troubleshooting or reporting instructions.

How Was Field Service Management Documentation Reorganized?

Four areas replace the former Field Service Management Administration grouping: Setting Up FSM, Managing FSM Operations Data, FSM Configuration, and FSM Features. The main FSM topic now organizes capabilities by user role and describes work from service creation through completion and billing review.

Setting Up FSM expands guidance on required features and preferences, locations and inventory setup, item records, customers and assets, and user access. It also consolidates Schedule Board and FSM Mobile setup guidance. Implementation checklists should use this area as their reference rather than the former administration grouping.

Managing FSM Operations Data covers customer, asset, and employee maintenance; inventory and service work records; and notifications. Service Provider guidance moves under Field Service Asset Records, while Sales Order Templates moves under Sales Orders and Item Fulfillments.

Field Service Operations is reorganized into operations and operational tracking, real-time monitoring, reporting and analytics, and notifications. These changes give teams a reason to review onboarding references, particularly where setup instructions and ongoing record maintenance were previously grouped together.

How Did Inventory Optimization Guidance Expand?

Inventory Optimization Preferences now describes Supply Analysis Interval. Calculations documentation covers separate demand and supply history periods, and the Results Dataset describes projected planning results and separate demand and supply analysis periods.

The Results Workbook adds table views for projected results and service-level comparisons. Two new topics extend segmentation coverage:

New topicCoverage
Inventory Optimization Segmentation DatasetStored segmentation results and supporting calculation values
Inventory Optimization Segmentation WorkbookReviewing category and segment assignments

For planning reviews, distinguish analysis-period settings, projected results, and segmentation assignments rather than treating them as interchangeable views. The update does not supply preference defaults, allowable intervals, or calculation formulas.

What Should SuiteCloud Developers and Workflow Builders Review?

SuiteCloud Developer Assistant setup using Cline in SuiteCloud Extension for VS Code now specifies Cline 4.0.0 or later. Development teams should check that prerequisite when reviewing setup instructions.

The SuiteCloud CLI for Node.js guide adds the config:import command. The update names the command but does not provide syntax or options.

Skills as XML Definitions adds two fields:

FieldDocumentation change
displaynameIncluded in the skills XML definition reference
audienceinternalrolesIncluded in the skills XML definition reference

Custom Tool Scripts as XML Definitions, Custom Tool Script Requirements, and SuiteScript 2.1 custom-tool code samples now address deprecation of the tool SDF custom object. Monitoring, auditing, logging, and custom-tool reference guidance also clarify where to view execution logs for custom tools implemented with toolset.

Review the object-definition and logging references together when maintaining custom tools. These notes do not establish a removal date, migration procedure, or execution-log navigation path.

SuiteFlow adds Best Practices for Workflow Initiation on Record Load. Initiating a Workflow on an Event adds sections about choosing the correct initiation trigger and record-load initiation best practices. Workflow Triggers also expands its trigger-name description. Workflow owners should consult those detailed recommendations before revising record-load initiation logic; the update does not reproduce the recommendations.

Which EPM Release Notes Were Updated?

Release-note topics for NetSuite EPM Connector, Planning and Budgeting Sync, and Close Management and Consolidation Sync now include details for their respective 26.2 versions. The notes identify these component versions but do not summarize their individual changes.

Teams using those components should review the relevant release notes separately rather than infer that all three received the same changes. Related Close Management and Consolidation Sync setup guidance can help frame configuration review.

Who This Affects

  • Administrators: Bulk-processing documentation, AI usage guidance, and system notes for AI-made changes.
  • Developers and workflow builders: AI plug-in documentation, skills XML fields, custom-tool deprecation and logging, Cline prerequisites, CLI commands, and workflow initiation.
  • Banking and tax teams: SFTP directory limits, payment suggestions, reconciliation references, deferred revenue setup, and regional reporting guidance.
  • Inventory and field service teams: Analysis periods, segmentation references, FSM setup, operational records, and reorganized procedures.
  • EPM component owners: Version 26.2 release notes for the three named components.

Key Takeaways

  • Prioritize the 5,000-file SFTP directory limit and manual review of cash-in-transit suggestions.
  • Review tool deprecation, toolset logging guidance, and the Cline 4.0.0 minimum.
  • Refresh FSM procedures and reconciliation references to match renamed and reorganized topics.
  • Use the detailed help topics for permissions, defaults, implementation steps, and limitations not reproduced in these update notes.

Frequently Asked Questions (4)

What SFTP directory limit should teams account for when using Auto Bank Statement Import?
Auto Bank Statement Import documentation identifies a limit of 5,000 files in SFTP directories. The limit appears in both the limitations topic and SFTP connection configuration guidance, so teams should include directory file counts in operational reviews.
Do cash-in-transit bank match suggestions qualify for automatic submission?
No. The updated guidance says cash-in-transit suggestions require manual review, even when using Automatic Submission of High-Confidence Matches. Reconciliation procedures should distinguish these suggestions from matches that can be submitted automatically.
What Cline version is required for SuiteCloud Developer Assistant setup in VS Code?
The setup documentation specifies Cline 4.0.0 or later for using SuiteCloud Developer Assistant with Cline in SuiteCloud Extension for VS Code. Development teams should verify this prerequisite when reviewing their setup instructions.
What should developers review when maintaining SuiteCloud custom tools that use the deprecated `tool` object?
Custom tool documentation now addresses deprecation of the `tool` SDF custom object, while related guidance clarifies where to view execution logs for custom tools implemented with `toolset`. Review the object-definition and logging references together; the update does not provide a removal date or migration procedure.
Source: Help Topics — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in General

View all General articles →