2 Reporting Release Notes 25.11.1
NetSuite for Government Reporting 25.11.1 Release Notes
Revision Date: November 05, 2025
Important:
This document summarizes the changes to NetSuite for Government Reporting 25.11.1 and the previous release.
These release notes are subject to change every week.
The NetSuite for Government Reporting 25.11.1 enhancements and changes listed in this document are not available to customers until they are upgraded to NetSuite for Government Reporting 25.11.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.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 Reporting Version 25.11.1 – Release Date November 05, 2025
Human Resources and Payroll:- California Public Employees Retirement System(CalPERS):
- Data Entry:
- The ‘Type of Transaction’ field is no longer available on the Data Definition screen. There is no need for manual selection; transaction type is determined automatically during report processing.
- The Program Type field will default to “California Public Employees’ Retirement System (CalPERS) (CPE)” as no other types are currently supported.
- Report Generation:
- Upon generating a report, all employees are initially assigned the EPR transaction type by default.
- If an employee has zero or null contributions in all of the
following pay buckets, the system will overwrite their
transaction type to EPN:
- ns4g_calperstaxedeecontr_pay
- ns4g_persee_pay
- ns4g_perser_pay
- ns4g_calperssurvivorcont_pay (PERS Survivor Contribution)
- ns4g_calpersspoussurvcont_pay (PERS Survivor Contribution Spouse)
- ns4g_calpersschildsurvcont_pay (PERS Survivor Contribution Children)
- ns4g_perstxeeaddl_pay (PERS Taxed Member Additional Contribution)
- ns4g_perstxdefereraddl_pay (PERS Tax Deferred Employer Paid Additional Contribution)
- Data Entry:
- EEO-4 Report:
- To Generate the Report:
- Login as NS4G-Payroll Administrator role, or role with appropriate access assigned by your agency.
- Go to Reports > State Filing > Export.
- On the State Filing Reports page, click New.
- The Generate State Filing Report page opens.
- On the Report section, select Your State from the State drop-down and EEO-4 Report from the Report drop-down. This report is state agnostic and is available for any state. It does not need to be run separately for employees living in a different state.
- On the Reporting period section, enter the year in the Reporting Year field and select any or all entities for to include Entity from the drop-down.
- You will be redirected back to the State Filing Reports page. If the report status is not set to Expired, Errors or Still in Progress, the report is available to review and export.
- Click the link under the Report column to preview the results and export the report.
- To Preview and Export Reports:
- On the State Filing Reports page, click the link
under Reports column.
- If the report status is set to Expired or Errors, then the report is not available to review and export.
- If any source data has changed, users should a generate a new report as those changes will not be reflected in the previously run reports.
- The report preview displays on the screen.
- To export the file required for state filing, select .CSV (Use for State Filing) format from the Export drop-down. This exports the file with the data and formatting required for state submission.
- Once you receive notification that the download has started, go to the file location to validate the file has exported. The file download location can be configured according to your web browser settings.
- On the State Filing Reports page, click the link
under Reports column.
- Complete the Report Template:
- Copy and paste the generated data, excluding header rows and columns, from each report into the corresponding tab of the EEO4 template. Use the EEOC provided template to ensure accuracy and compliance.
- Report Logic:
- To understand how the report was generated and to troubleshoot inaccurate results, use the following logic as a guideline:
- The system will find the employee’s Position and Pay record where:
The priority is primary, and the entity matches one of the entities selected in the Define Data:- Employee has at least one active record where the record begin date <=June 30, Reporting period year <= Pos and Pay end date. Unique employees are included int the report. Use the primary position and pay record that meets this criteria (begin date <=June 30, Reporting period year <= Pos and Pay end date) with the greatest end date in below logic. (Employees may have multiple position and pay records, don't assume records with greatest end date should be used, but still must meet the date criteria above).
- Full-Time Tab:
The system generates the Full-Time report by including only those employees who have one Position and Pay record with a Position FTE (Full-Time Equivalency) of exactly 1. It considers:
- Employees whose Hire Date is on or before the start date of the reporting period.
- Employees with split FTEs across multiple positions (e.g., 0.5 + 0.5 in different roles) are not included; those cases must be handled manually.
- Field Sources:
- Job Category: Taken from the Position record’s Job Category field.
- Function: Based on the Job Category ID from the Position record.
- Annual Salary: From the Annual Salary field in the Employee Position and Pay record, divided by 1,000 to show “In Thousands” in column C.
- Full-Time Equivalency: From the Position FTE value.
- Gender: From the Employee’s Personal Tab > Gender.
- Race: From the Employee’s Personal Tab > Race.
- Hispanic or Latino: From the Employee’s Personal Tab > Hispanic or Latino checkbox.
- Hire Date: From the Employee’s Personal Tab > Hire Date.
- Other than Full-Time Tab:
This section includes employees with a Position FTE that is not equal to 1 (e.g., part time, less than full time):
- It includes only employees with Hire Dates on or before the reporting period begin date.
- Employees with split FTEs must also be handled manually.
- Field Sources:
- Field sourcing is the same as in the Full-Time tab.
- New Hires During Fiscal Year:
This tab lists employees who were hired after the reporting period begin date:
- Only one Position and Pay record per new hire is counted.
- The system calculates and enters the number of unique employees for each category.
- Field Sources:
- Sourcing for Job Category, Function, Annual Salary,
Full Time Equivalency, Gender, Race, Hispanic or Latino, and
Hire Date is the same as described for the other tabs.
Note:
When using this tab, race and Hispanic fields are disabled, and the ethnicity field is hidden.
- Each employee is counted only once in their applicable tab based on their Position and Pay record.
- If an employee’s assignments do not fit the standard logic (e.g., split FTEs), manual adjustment may be required.
- Sourcing for Job Category, Function, Annual Salary,
Full Time Equivalency, Gender, Race, Hispanic or Latino, and
Hire Date is the same as described for the other tabs.
- Cash and Deposits Report for Local Government:
- Overview: We are pleased to announce the release of the new Cash and Deposits Report for local government agencies. This report is designed to provide comprehensive visibility into all cash receipts processed within NetSuite, supporting transparency and compliance for external stakeholders.
- Key Features:
- Comprehensive Coverage: The report lists all cash receipts, including those linked to invoices with payments as well as stand-alone cash sales.
- GL Detail Included: Full General Ledger (GL) detail is provided for each transaction, enabling stakeholders to clearly identify which budget lines are credited for revenues.
- External Consumption-Ready: The report layout and data structure are optimized to support external audits, regulatory requirements, and public reporting.
- To Generate the Report:
- State Retirement Reports Missing Employees:State Field No Longer Required for Retirement Reporting.
- The following issues are now resolved and implemented:
- Employees were previously missing from retirement reports when the State Tax field was absent on the Payroll Item Line. The State field is no longer required for the retirement (PERS) report. This update ensures that employees exempt from state taxes—who may have no state specified—are correctly included. This fix applies to all PERS reports, and was specifically identified in the Texas TCDRS and Utah PERS reports.
- Employee Criteria Logic (with State field no longer required):
- Using the "Reporting Period Date" set in the Report
Definition, the system searches all pay lines where the
"Retirement/PERS Reporting Date"
(custrecord_ns4g_payline_persdate) matches the Reporting
Period Date. Employees with an active retirement record for
the retirement system (record name: "Employee
Retirement/Compliance Misc", record ID:
customrecord_ns4g_empretire) are included if:
- The employee's state retirement system (custrecord_ns4g_empretire_retiresys) matches.
- The report includes pay lines only for employees with a qualifying state retirement record and where:
- The retirement record begin date is on or before the Reporting Period End Date.
- The retirement record end date is either not set (null) or on or after the Reporting Period Begin Date.
- If there are multiple records overlapping the reporting period, the system selects the record with either a null end date or the latest end date.
- The following issues are now resolved and implemented:
- Arizona Reports:
- Updated the Arizona W2, SUI, PSPRS, and PERS reports to support multi-entity selection.
- State Compliance Reports:
- Resolved: Improved State Report Dashboard Performance.
The Dashboard view in the Apex State Report now automatically removes detail lines for expired reports. A nightly job has been implemented to delete expired reports and their associated views from both the database and user interface. This update resolves the performance issues found on the home page, which was previously slow due to system checks on the status of all reports (expired or available).
- Result:
- The Home page now loads significantly faster, as expired report data no longer impacts dashboard performance.
- Resolved: Improved State Report Dashboard Performance.
- Utah W-2 File Format Update:The Utah W-2 file has been updated to comply with state wage and tax reporting requirements:
- Section RV > 58–72: Total Utah Tax Wages
- The value has been updated to now include a decimal point to
reflect the correct wage amount.
- Example: 4411476.27 (previously reported as 441147627)
- The value has been updated to now include a decimal point to
reflect the correct wage amount.
- Section RV > 73–87: Total Utah Income Tax Withheld
- The value has been updated to now include a decimal point to
reflect the correct tax withheld.
- Example: 176022.89 (previously reported as 17602289)
- The value has been updated to now include a decimal point to
reflect the correct tax withheld.
- Section RV > 58–72: Total Utah Tax Wages