Who should check?
Organizations using Cloud EPM EPM Automate or REST jobs with account-prefixed usernames, clients older than 26.09, or legacy encrypted password files. This is not a general NetSuite ERP deadline.
Published milestones
- 26.11 — November updateAccount-prefixed usernames cease to be accepted by affected login interfaces.
- 26.12 — December updateOlder clients and the legacy password-file format are no longer accepted by Cloud EPM.
Check your Oracle account notice before scheduling an update.
What to do next
- Identify affected jobs, client versions, username formats and any EPM Agent dependency without collecting secrets.
- Have the authorized credential owner upgrade/test clients and regenerate files in the compatible sequence.
- Test representative scheduled jobs, alerts and recovery before the environment update; record owner acceptance.
What we’ll review
Environment and client versions; sanitized username-format examples; job/host and owner inventory; password-file generation version without secrets; EPM Agent version where used; actual environment maintenance notices.
Sources and updates
Oracle documentation
NetSuite Cloud EPM October actions and considerations ↗Oracle publication/update date not stated on this page. · Source checked:
Cloud EPM October actions and EPM Agent qualification ↗Oracle publication/update date not stated on this page. · Source checked:
Update history
- 2026-10-20 — Published this guide after reviewing Oracle’s documentation.