Intelligent Close Manager Now Exposes Task Records for Assignment and Tracking
NetSuite introduces the Close Manager Task record type, giving admins a record-level interface to assign, schedule, and track Intelligent Close Manager (ICM) tasks outside the dashboard portlet. Records are auto-created per task-name/period/subsidiary grouping for the first open accounting period only.
What changed
A new Close Manager Task record type is now available. Previously, Intelligent Close Manager (ICM) tasks were only visible and manageable through the ICM dashboard portlet. These records provide a first-class NetSuite record you can open, assign, set due dates on, and update status for — independent of the portlet UI.
Record creation logic
- NetSuite automatically creates Close Manager Task records only for the first open accounting period. No records are generated for future periods until those periods become the first open period (i.e., after the current period is closed).
- Records are grouped by task name + accounting period + subsidiary. One record is created per unique combination, regardless of how many underlying ICM tasks exist in that group (one-to-many relationship).
- Additional work matching the same task name, period, and subsidiary is associated with the existing task record rather than spawning a new one.
Access requirements
- The Intelligent Close Manager feature must be enabled.
- Users need the Manage Accounting Periods permission to view or edit these records.
Navigation
Close Manager Task records can be accessed from:
- The Close Manager Tasks list (standard list view).
- Linked task names within the Intelligent Close Manager portlet.
What the source does not clarify
Oracle's documentation does not specify:
- The internal record type ID (e.g., whether it is
closemanagertaskor another identifier). Verify via Records Browser orN/recordTypeenum in your environment once the feature is active. - Whether these records are exposed via SuiteScript (
record.load,record.create) or REST/SOAP web services. If you plan to automate task assignment or status updates programmatically, testrecord.loadwith the record type and check the REST Record Browser at/services/rest/record/v1/metadata-catalog. - Whether SuiteFlow (workflow) or SuiteScript triggers (User Event, beforeSubmit/afterSubmit) fire on these records.
- The full field schema — fields like status, assignee, due date, and period are implied but not enumerated.
What to do
- Verify feature enablement. Navigate to Setup > Company > Enable Features > Accounting and confirm Intelligent Close Manager is turned on.
- Check permissions. Ensure users who need access have the Manage Accounting Periods permission in their role.
- Inspect the record type. Open the Records Browser or run a quick SuiteScript test to confirm the internal type ID and available fields. This is essential before building any automation.
- Evaluate automation opportunities. If your close process currently relies on manual tracking (spreadsheets, saved searches against transactions), consider scripting against these records to auto-assign tasks by subsidiary or set due dates based on your close calendar.
- Review existing ICM portlet usage. If you have customizations or scripts that interact with the ICM portlet or related records, verify they still function correctly and determine whether migrating to the new record type offers a cleaner integration point.
Source: Oracle NetSuite Release Notes