22 Release Notes 25.5.1
NetSuite for Government 25.5.1 Release Notes
Revision Date: May 06, 2025
Important:
This document summarizes the changes to NetSuite for Government between 25.5.1 and the previous release. These release notes are subject to change every week.
The 25.5.1 enhancements and changes listed in this document are not available to customers until they are upgraded to NetSuite for Government 25.5.1. Your access to these features and SuiteApps is subject to the terms of service in your NetSuite for Government contract.
Please also review the NetSuite general release notes for a comprehensive view of changes to the release. During this release period, NetSuite version 2025.1 is released. The general NetSuite release notes are accessible at this link:https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/book_N3865324.html
NetSuite for Government Version 25.5.1 – Release Date May 06, 2025
Finance:
- Purchasing Change Orders:
- Change Order encumbrances will be generated based on the Action of each item detail row such as adding a new line, updating an existing line, and closing or removing a line.
- The Terms and Purchase Order Memo field are now transformed to the Change Order as expected.
- Utility Billing Integration:
- The Utility Billing integration with the NetSuite General Ledger has been updated to retain text formatting instead of using an integer to preserve values such as "0000" which previously was reduced to "0".
Various Fixes and Performance Improvements
- Corrected an issue where the message "Please enter value(s) for: Fund, Department, Account" is given on the Quick Code form for Vendor Bill and Purchase Order transactions.
- Corrected an issue where the error message, "An unexpected error occurred in a script running on the page. customscript_ns4g_cs_transaction (post sourcing)" was given when entering a Purchase Request from the Employee Center.
- Corrected an issue with the General Ledger Inquiry and Summary reports where the Year-to-Date option didn't accurately select the associated transactions.
- Corrected an issue with the General Ledger Inquiry report where the Month range option didn't accurately select the associated transactions.
- Payroll Multi Entity Support:
- To meet multi-entity agency requirements, it is essential to provide the
ability to apply entity-specific configurations. When an Entity is chosen within the
Payroll and HR Preferences, the corresponding Payroll and HR Record linked to that
entity will be displayed. Users will have the flexibility to edit individual fields
within the payroll and hr preferences, and upon saving, the base record for that
entity will be updated.
Currently, not all fields are Entity specific. However, the following fields support multi-entity functionality:
- On the Checks Tab: Credit Account, Debit Account, and Fund.
- On the Direct Deposit Tab: Credit Account.
- On the Fund Allocation Tab: Over/Under Payroll Account, Over/Under Payroll Fund, and Over/Under Payroll Department.
Other settings will refer to the Payroll and HR Preferences set for the Parent entity. Additional fields will be enabled over time to further enhance multi-entity functionality.
The entity field will become mandatory. Once an entity is assigned to the payroll and hr preferences record, the system will prevent users from changing the entity to another record or duplicating preference records for the same entity.
When the entity is changed, the page will refresh to retrieve the payroll and hr preferences record specific to that entity. If the entity is modified and no record exists for that entity, a new Payroll and HR Preferences record will be created and will save all the data entered upon saving.
When a payroll and hr preferences record already exists for a selected entity, the inputted record information will be saved. If only one entity exists, users will not have an option to choose from for other entities.
- Once set and saved the users will not be able to change the pay cycle entity. All future calculations, reporting, and scripts relies on this field not changing.
- To meet multi-entity agency requirements, it is essential to provide the
ability to apply entity-specific configurations. When an Entity is chosen within the
Payroll and HR Preferences, the corresponding Payroll and HR Record linked to that
entity will be displayed. Users will have the flexibility to edit individual fields
within the payroll and hr preferences, and upon saving, the base record for that
entity will be updated.
- Employee Position and Pay Fund Allocation Checking:
- The functionality allowing users to choose the “New Employee Fund Allocation” option from the “Employee Position and Pay” record has been restricted. This ensures that users cannot create fund allocation records that do not sum up to 100%. To address this, users should edit the “Employee Position and Pay” record and utilize the sublist feature to accurately set the “Employee Fund Allocation” record. Importantly, users retain the ability to import position and pay records, along with the associated “Employee Fund Allocation” records.
- Minnesota Payroll:
- Minnesota State Compliance setup values are now available to be used in conjunction with the Minnesota PERA report.
- Users can now review the Minnesota PERA employee retirement reporting record and manually edit if needed.
- State Unemployment Insurance Exemption:
- Some employees are exempt from contributing to the State Unemployment Insurance. When an employee is designated as exempt from State Unemployment Insurance, their corresponding wage buckets will be set to null for the calculated payroll batch. The system removes the pay bucket "State Unemployment Eligible Wages" from all hours and pay codes during the calculation process within payroll item lines. The Calculate History Function will also respect the employee's exemption status at the time of calculation, preventing the addition of the associated state SUI taxable wages.
- Utah Retirement System (2025 update):
- On the State Compliance Setup Record a payroll id was added. This will be used to
identify unique values for backend filtering logic. Values have been added to the
State Compliance Setup Record related to configuring the new 2025 Utah Retirement
System. Values were created for the following categories:
- Benefit Program
- Tier
- Sub Tier
- Transaction Type
- Employee Pay Type
- On the State Compliance Setup Record a payroll id was added. This will be used to
identify unique values for backend filtering logic. Values have been added to the
State Compliance Setup Record related to configuring the new 2025 Utah Retirement
System. Values were created for the following categories:
- Resolved an issue where amounts calculated from the Time-Off Carry-Over and Cash-Out rule did not add correctly to the pay buckets, which resulted in inaccurate gross pay and posting discrepancies.