Release Notes 25.11.2

NetSuite for Government 25.11.2 Release Notes

Revision Date: November 05, 2025

Important:

This document summarizes the changes to NetSuite for Government between 25.11.2 and the previous release. These release notes are subject to change every week.

The 25.11.2 enhancements and changes listed in this document are not available to customers until they are upgraded to NetSuite for Government 25.11.2. 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.2 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.11.2 – Release Date November 05, 2025

Finance:

Government Budget Validation on Transactions:
- We are pleased to announce the release of the Parent Level Budgeting feature, designed to provide organizations with enhanced flexibility and control in budget management. This feature will allow budgets to be entered at various levels and then allow the system to validate the budget at a higher parent level in the hierarchy.
  - New System Setup Option:
    The NS4G System Setup page now includes a dedicated option on the Budget Validation tab to enable Parent Level Budgeting. This includes the ability to specify budget actions at a global level or define actions for specific account hierarchies. Please note that actions defined at the account hierarchy level will override the global settings, allowing for tailored budget control.
  - Improved Budget Entry:
    During budget setup, users can enter budgets at both the account hierarchy level and the existing segment (detail) level, offering greater flexibility and alignment with organizational structures.
  - Enhanced Budget Validation:
    During transaction processing, the system now validates available budgets across all budget levels – both the new parent (hierarchy) budgets and the existing segment-level budgets – ensuring comprehensive budget enforcement.
  - Configurable Available Budget Display:
    The Available Budget shown on transaction entries is determined by the “Available Budget” checkbox in the system setup table, giving administrators control over budget visibility.
1099-S Support:
- The Account screen has been updated for 1099 Reporting values to include 1099-S Gross Proceeds and Buyer's Share of Real Estate Taxes.
- The Vendor Bill, Bill Credit and Check forms now allow the transaction lines to be associated with a 1099-S property address. While 1099-S transactions will accumulate without this record, the record will eventually need to be completed and attached to the line in order to represent the additional fields such as property closing date, property description, foreign indicator and buyer's portion of real estate taxes.
1099: 2025 Support:
- The Federal Filing report now includes tax year 2025 for the csv export for all form types.
- The Federal Reporting 1099 csv export will now only report the 5-digit zip code so that the IRS accepts the file, and the forms will have a supported zip code format. Previously, the dash was removed and a 9-digit zip code was a continuous string.

General Ledger:
- Enhanced reporting for Project, Project Task and Grant is now available. Simply, update the NS4G System Setup > Custom Segments > Enable Grant, Project and Project Task segments checkbox to turn on the feature. Once the feature is on, the GL Impact tab will be populated for these segment values which will give enhanced reporting capabilities in the General Ledger Inquiries, General Ledger Summary and also Financial Reports. Additionally, a historical transaction update tool will also be available in the December release.
  
  Note:
  Custom Roles will need to be granted access to the Custom Segments Records on the Customization > Lists, Records, Fields > Custom Segments for Grant Segment, Project Segment and Project Task Segment. Simply, edit the record and add the roles under the Permissions tab.

Purchasing Change Orders:
- The Effective Date on the Purchase Order and Change Order lines must now be greater than the Purchase Order date and within an active accounting period.
- A new Change Order setting called Encumber Option has been implemented to allow configuration of the encumbrance action on Change Orders for: No Action, Pre-Encumbrance or Encumbrance.
Note:
Any agencies using the Change Order functionality need to reset this Encumber Option on the NS4G System Setup screen / Purchasing Tab, otherwise the default behavior of Pre-Encumbrance will be observed.

Fund Segment:
- Ensure users cannot enter duplicate numbers on Fund, Department and Program/Class.
- Removed mandatory requirement from this field to simplify setup for Quick Codes.
- Limit the fund to a single selection for subsidiaries.

AGR - New Integration / Configurable Datasets:
- Standard dataset for users - Additional fields to be added with future releases.
- Introduced a standard saved search for missing metadata and allow reminders to be created when fields are missing.
- Exception reporting for account metadata.
- Standard metadata fields for producing Income Statements, Balance Sheets and user defined reporting requirements. These additional fields allow users to leverage EPM, SuiteAnalytics and Saved Searches for complex reporting requirements.

Various Fixes and Performance Improvements

Human Resources and Payroll:

Pay Stub YTD Value:
- It was identified that pay stub calculations were referencing YTD values based on code name. This has been updated to group YTD values by internal code ID instead. As a result, if a code name changes, the YTD values will remain consistent because the internal code ID does not change.
W2-Box 12 and Big Beautiful Bill:
- Pay Bucket Enhancements
  To support the changes coming in 2025 and 2026, the following pay buckets have been released as part of the "Big Beautiful Bill" updates. Instructions on how to configure this bucket will be released in a future update.
- New Pay Buckets:
  - Name: W2 Box 12TA - Trump Account Employer Contributions
    
    ID: ns4g_w2box12ta_pay
    
    Description: Employer contributions to your Trump account.
  - Name: W2 Box 12TP - Cash Tips
    
    ID: ns4g_w2box12tp_pay
    
    Description: Total cash tips received. This amount should be used when determining the deduction for qualified tips on Schedule 1-A (Form 1040).
  - Name: W2 Box 12TT - Qualified Overtime
    
    ID: ns4g_w2box12tt_pay
    
    Description: Total qualified overtime compensation. This value should be used when determining the deduction for qualified overtime compensation on Schedule 1-A (Form 1040).
- The following pay bucket will be used for the Utah State Transparency Report:
  - Name: Employer Paid Benefit
    
    ID: ns4g_emppdbene_pay
    
    Description: Total employer-paid benefits, used for state reporting purposes.
Employee W2 Records – Automated Updates for Name and Address:
- The system now automatically ensures accuracy when employees change their names or addresses:
  - The First Name, Last Name, and Suffix are always sourced directly from the Employee record, rather than from address fields.
  - Address information (Address 1, Address 2, City, State, and Zip Code) is automatically retrieved from the Employee’s Default Shipping Address for reporting.
  - Blank Address 2 fields are handled automatically to avoid unnecessary blank lines on the PDF form.
  These enhancements apply to the printable PDF version of the W2 and help ensure information accuracy for W2 filings. The underlying data file logic remains unchanged and continues to capture the correct information. No manual intervention is needed, these updates are managed by the system.
The State Unemployment Insurance (SUI):
- The State Unemployment Insurance (SUI) logic has been updated as follows for Payroll Calculation, Importing Payroll History, and Calculating Employee Historical Payroll.
- Payroll Calculation:
  On the Payroll Item Lines:
  - The system defaults to the state listed in the Tax State field.
  - If the SUI Tax State field is populated on the employee record, this value takes precedence.
  - If the employee is marked as exempt, the SUI state field will be set to null.
- Employee State Unemployment Taxable and Total Wages amounts are determined based on the SUI state.
- The system does not accommodate date-based changes to the state; it will always use the value currently set on the employee record during payroll calculation, recalculation, or import. The Payroll Item cannot be edited manually.
Medicare Exempt Logic Updates:
- Payroll Calculation, Payroll History Import, and Historical Payroll Calculation: For employees marked as Medicare Exempt, Medicare Taxable wages are now excluded from all payroll item lines during payroll calculation processes. The system always references the current Medicare Exempt status on the employee’s tax record; date-based changes to the exemption status are not supported during calculation, recalculation, or import. Payroll Item Lines related to Medicare Exempt status cannot be manually edited.
Employee Posting Detail Error View and Resolutions:
- The enhanced Error View now displays employees who have encountered one of the following:
  - A Payroll Calculation Processing Error.
  - A Posting Detail Error.
  - An out-of-sync posting detail with the payroll item line.
- How to Resolve Common Payroll Errors:
  - Payroll Calculation Processing Errors:
    Click the employee’s name (blue link) to review their payroll items. If there is a negative net pay or another processing issue, an error message will display on the impacted payroll item line. Use this message to identify and resolve the problem.
  - Posting Detail Errors:
    If a Posting Detail Error is present, a message will appear directly in the Error View. Use the provided message to troubleshoot and address the error.
  - Out-of-Sync Posting Details:
    If the “Out-Of-Sync Posting Details” column displays “Yes,” the posting has not been calculated since the employee's payroll was last calculated. To resolve this, recalculate the employee’s posting detail:
    For recalculating both payroll items and postings, use the regular calculate payroll process.
    To recalculate postings only, select Calculate Employee Posting Detail button from the menu.
    To recalculate for all employees, keep the Filter By option as “None.”
    To recalculate for specific employees, select “Employee” and choose the individuals you wish to recalculate.
- Improved Posting Detail Error Status:
  The Posting Detail Status field now uses the new status Complete - Errors Occurred or Postings Not Synced, replacing Complete - Error(s) Occurred. This provides clearer information, indicating the status may be due to errors or out-of-sync postings.
Recalculate Employee Posting Detail:
- How to Recalculate Employee Posting Details:
  - To update both payroll items and posting details, use the standard payroll calculation process.
  - To update only the posting details, click the Calculate Employee Posting Detail button in the Payroll Batch menu.
  - For all employees, set the Filter By option to “None.”
  - To recalculate for specific employees, select “Employee” and choose the relevant individuals.
  You should perform a recalculation if the “Out-Of-Sync Posting Details” column displays “Yes,” indicating that postings have not been updated since the employee’s last payroll calculation. Recalculation is also necessary if a processing error message appeared and the underlying issue has been resolved, to ensure the employee’s posting details reflect the correction.

Deferred Compensation:
- Deferred Compensation Table Annual Update:
  The deferred compensation table will now be updated automatically on an annual basis. Limits for the years 2023, 2024, and 2025 have been refreshed and are available for use. The table includes updated deferred compensation limits for 457, 401(a), 401(k)/403(b), and Roth IRA plans.
  
  Note:
  The 401(a) limit has been updated to reflect the combined employee and employer contributions.
  
  Subject to IRS updates or confirmation. The 401(a) limit is the combined maximum for employee and employer contributions.
  
  All limits, including catch-up contributions and applicable eligibility ages, will be maintained automatically to ensure compliance with published contribution limits.
  
  The special catch-up limit will be added in a future release.
Affordable Care Act (ACA) Reporting:
- Plan Start Month on Form 1095-C
  Background:
  The "ACA Plan Start Month" field on Form 1095-C typically reflects the month when the employer’s health plan year begins, not necessarily the month when the employee was hired or became eligible for coverage. For example, if your plan year starts in January, enter “01” as the Plan Start Month, even for employees hired mid-year. This box is required for the 2024 Form 1095-C and cannot be left blank.
  In Payroll and HR Preferences > Compliance > ACA Field Group > Plan Start Month (custrecord_ns4g_payrollhrprefs_acamonthstart) enter the two-digit month (01–12) corresponding to the start month for the employee’s coverage.
  System Logic Updates:
  1. Calculation Logic:
    - During the ACA calculation process, the "Plan Start Month" field in the Employee ACA Record (custrecord_ns4g_1095c_planstartmonth) is populated using the value set in Payroll and HR Preferences > Compliance > ACA Field Group > Plan Start Month (custrecord_ns4g_payrollhrprefs_acamonthstart).
    - This logic enabled for multi-entity organizations and the value should correspond to the Payroll and HR Preferences Entity that matches the employee’s entity.
    - This field can be overwritten on the Employee ACA r0065cord if applicable.
  2. PDF Generation Logic:
    - When printing an employee’s ACA record to generate Form 1095-C, the system will retrieve the "Plan Start Month" value from the Employee ACA Record’s "Plan Start Month" field (custrecord_ns4g_1095c_planstartmonth) for use on the form.
  3. File Generation Logic
    - When committing the Employee ACA reporting period to generate the data file, the system will derive the "Plan Start Month" information from the Employee ACA Record’s "Plan Start Month" field (custrecord_ns4g_1095c_planstartmonth).

Various Fixes and Performance Improvements

Previously the system retrieved the reporting period details multiple times, once for each plan summary instead of retrieving them just once during employee retirement data retrieval. Optimized employee retirement retrieval by fetching reporting period details only once and mapping them to corresponding retirement records, improving processing efficiency.

1 Release Notes 25.11.2