This notice applies to customers who create or update Journal records through integrations (REST, CSV, and SOAP) or imports. This change affects Journal Entry, Intercompany Journal Entry, Advanced Intercompany Journal Entry, and Statistical Journal Entry.
What’s Changing?
Effective with the NetSuite 2026.1 major release, NetSuite will configure Journal line sublists as keyed. This enables precise line-level updates using a unique line key and helps avoid issues that could affect record load or edit if non-keyed sublists were treated as keyed and standardizes behavior across all journal types. Journal Entry was already keyed; this release brings Intercompany Journal Entry, Advanced Intercompany Journal Entry, and Statistical Journal Entry into alignment. Replace-sublist operations will continue to be supported. No downtime is expected.
- Affected areas: Journal Entry, Intercompany Journal Entry, Advanced Intercompany Journal Entry, Statistical Journal Entry.
- Behavior: Line-level Updates are supported via REST, CSV, and SOAP integration when a unique line key is included; Replace All (replace sublist) remains supported.
- Validation: Standard keyed sublist validation applies. Duplicate line keys are rejected, lines without a key are interpreted as additions and are automatically assigned a key. For line-level updates to existing lines, include a unique line key to target the intended line.
What are keyed sublists?
- Keyed sublists: Each line has a stable, unique indexing line element or internal ID used as key. Integrations can precisely update, add, or remove a specific line by referencing its key. The system enforces uniqueness and rejects duplicate keys.
- Non-keyed sublists: Lines don't have an indexing element or internal ID that can be used as key. Integrations cannot reliably target a single line; they must replace the entire sublist to make changes. Positional indexing is not guaranteed and can lead to unexpected results if used as a proxy for a key.
Impacted customers
- NetSuite accounts using standard UI workflows and default settings are not expected to be affected.
- NetSuite accounts using custom integrations that assume non-keyed behavior may see validation errors until mappings are updated.
Required Actions
We recommend reviewing and testing any process that updates Journal lines prior to the production rollout. Please take advantage of your free 2026.1 Release Preview account which is expected to be available at the end of January 2026.
To prepare:
- Review your integrations and determine if they need to be updated
- Follow instructions to request for a release preview account
- Test in a release preview account
- Validate add/modify/remove line scenarios for each affected journal type.
- Confirm that imports and scripts include a unique line key per line for line-level updates.
- Address any validation errors which may pop up.
- Update schedules
- Update schedules as needed and plan your promotion to production ahead of the rollout window.
Important Note:
Previously, several journal variants included a line identifier but were configured as non-keyed sublists. Therefore, integration tools could not reliably update individual lines, and attempts to do so sometimes caused issues that prevented users from loading or editing the affected journals. If your integration reuses the same identifier on multiple lines, updates may fail validation after this change. Update your mappings to use a unique line key. For more information on sublists, see the help topics:
If you have any questions, contact NetSuite Customer Support.