25 Release Notes 25.4.3
NetSuite for Government 25.4.3 Release Notes Hot Fix
Revision Date: April 28, 2025
Important:
This document summarizes the changes to NetSuite for Government between 25.4.3 and the previous release. These release notes are subject to change every week.
The 25.4.3 enhancements and changes listed in this document are not available to customers until they are upgraded to NetSuite for Government 25.4.3. 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 is transitioning from 2024.2 to 2025.1. Customers may be on either release. 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.4.3 – Release Date April 28, 2025
Finance:- Purchasing Change Orders:
- The Documentation Attached field on the Change Order will be automatically checked when the user attaches backup documents to the Change Order. Additionally, a blocking message will be given to the user if the documentation has not been attached prior to save. This is dependent on the NS4G System Setup option to Require Documentation.
- The Selected Fund will always be updated during the Purchase Order Update process to ensure accuracy.
- The Change Order form has a new tab under System Information for the change log of this purchase order to easily identify final changes of each change order version. The log is replaced in each user save to only track final changes between the prior and new versions of the Purchase Order.
- The Change Order Quick Code form has been updated to properly pass any Quick Code changes back to the purchase order.
- Expanded role permissions for Change Order functionality to include SuiteScript Scheduling and SuiteScript under Manage Roles / Permissions / Setup.
- Closed lines may not be modified on a change order. A business rule has been implemented to disallow user changes to lines which are closed.
- Accounts Payable Bills are now sensitive to the encumbrance balance by date to allow for multi-year and mid-year encumbrances on a purchase order.
- The allowable Effective Dates for Change Orders has been implemented to control which transaction dates may be used. The optional settings are controlled on the NS4G System Setup page in the Purchasing / Change Order tab.
- Item Code Account Override:
- The Item Override feature has extended the original expense description to the new GL Impact line for the override account.
- An Item Override Account has been implemented on the NS4G System Setup screen to allow for certain reports to exclude this clearing account.
- The Item Clearing Account will no longer be validated against the budget, nor show the Remaining Budget Amount.
- Customer Support Enhancements:
- Created a standard NetSuite for Government printable PDF document for Government Budgets.
- Created a standard NetSuite for Government printable PDF document for Budget Adjustments.
- The Contract record Type field has been sorted alphabetically.
- Added additional filters for Fund and Account Type within the Utah Transparency report.
- Quick Codes:
- The Quick Code import has been updated to include the Subsidiary.
- Quick Code form transactions will now filter the Quick Code list by subsidiary so that users only see Quick Codes for their subsidiary.
- Quick Code Transaction lines will source Item Account from Item record once Item field is populated. For Items using income Accounts, the Item Account should be sourced only if the Item type is not Inventory.
- A Quick Code form has been published for the Write Checks screen. Also, the CSV import has been updated to include the Quick Code and map to the correct GL segments.
- Resolved an issue where the Quick Code and segment values were out of sync.
- Transactions Performance Improvements:
- Updated for single budget call and adjustment for multi-subsidiary functionality.
- Multiple Calendar Support:
- The GL Inquiries and Summary reports have been updated to properly classify transactions by subsidiary in the totals and data shown on the screen.
- Multiple Subsidiary Support:
- Support has been added for multiple entity budgets with duplicate segments in separate subsidiaries. This works in conjunction with the NS4G System Setting where Budget Validation to Allow multiple budgets is not enabled.
- Resolves issue with non-inventory items for child subsidiaries on the Invoice.
- Encumbrance Point in Time Reporting:
- Purchase Order Encumbrances will use the Account value if the Item Account value is blank.
- Utility Billing Integration:
- An integration between NetSuite for Government and Utility Billing is now available to seamlessly post general ledger transactions.
- The Purchase Order and Vendor Bill screens will drill into the General Ledger Inquiry screen with all the segments populated. Prior to this, the subsidiary field was blank.
- A performance improvement was implemented for the Budget Adjustment screen to query for all budgets at once instead of line by line.
- An issue was corrected where a Bill Payment Void caused an error of Missing a required argument line.
- An issue was corrected where the Validate function was referenced when trying to save a record before the screen finished loading.
- The Vendor Tax ID feature is now enabled by default in all new NetSuite for Government installations.
- Encumbered purchase orders will now have the Project field disabled upon Bill entry so that encumbrance mismatches will not occur.
- The Parent Grant functionality has been corrected from an erroneous circular relationship message.
- Performance improvements around the CS_Transactions script.
- Improvements to performance around budget adjustments.
Human Resources and Payroll:
Various Fixes and Performance Improvements
- Added the Entity field to the Payroll Item and Direct Deposit Record. This will enable appropriate access by entity and add reporting criteria.