Reporting Release Notes 25.8.1

7 Reporting Release Notes 25.8.1

NetSuite for Government Reporting 25.8.1 Release Notes

Revision Date: August 05, 2025

Important:

This document summarizes the changes to NetSuite for Government Reporting 25.8.1 and the previous release.

These release notes are subject to change every week.

The NetSuite for Government Reporting 25.8.1 enhancements and changes listed in this document are not available to customers until they are upgraded to NetSuite for Government Reporting 25.8.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 Reporting Version 25.8.1 – Release Date August 05, 2025

Finance:

Budget vs Actuals - Multiple Years:
- Added ability to drill down Last year to Date column.

Various Fixes and Performance Improvements

Human Resources and Payroll:

Oregon PERS:
- The Oregon PERS retirement system has specific requirements for reporting work periods, which cannot span two months within a single report. The file format must include allocation percentages for dollars and hours, clearly separated by the work period's start and end dates.
  The Oregon PERS report now correctly accommodates pay periods that span two months and allows the user to separate the pay period into two work periods.
  
  Note:
  The Reporting Period Date will continue to be used to pull in committed payroll batches where the associated Pay Period Retirement/PERS Reporting Date matches exactly.
  Primary Work Period
  - When the pay period's start and end dates fall within a single month, only one work period needs to be reported. In this case, the "Primary Work Period" can be utilized, assign the pay period's start date to the "Primary Work Period Begin Date" and the last day of the pay period as the "Secondary Work Period End Date". Leave the Work Period Allocation Percentage defaulted as 100.
  Split Work Periods
  - If the pay period spans two months, two work periods are necessary. For the primary work period, assign the pay period's start date to the "Primary Work Period Begin Date" and set the last day of the first month as the "Primary Work Period End Date".
  - Modify the "Work Period Allocation Percentage" to an integer value between 1 and 99, representing the percentage allocation of dollars and hours to be reported in the primary work period.
  - Users must select the "Pay Period Crosses Monthly Boundaries" checkbox. For the secondary work period, assign the first day of the second month as the "Secondary Work Period Begin Date" and the last day of the pay period as the "Secondary Work Period End Date”.
  Additional changes include renaming the "Employer IAP" field to "Optional Employer IAP Percentage" and implemented validation to ensure values fall within the acceptable range of 1 to 6.
  
  Reporting Logic Changes:
  - When users opt out of the "Pay Period Crosses Monthly Boundaries" checkbox, a streamlined approach is taken. Only one report is generated, reflecting the employee's related retirement pay and hours, multiplied by the Primary Work Period Allocation Percentage (set at 100%).
  - Selecting the "Pay Period Crosses Monthly Boundaries" checkbox triggers a more detailed report. A single report with two lines per employee is created, representing each work period.
    - The first line calculates pay and hours by multiplying the respective values by the Primary Work Allocation Percentage, with the result rounded to two decimal places. All other non-pay/hour fields remain unaffected.
    - The second line ensures accuracy by determining the pay and hour amounts through subtraction. It takes the original values and subtracts the rounded values from the first line, preventing any inconsistencies due to rounding.
      For the second employee line, the logic remains consistent, but the Secondary Work Period Begin and End Dates are used instead of the primary dates.
      Examples:
      - If Subject Salary, Regular is $99.23, and the Primary Work Period Allocation Percentage is 50%, the calculation is as follows:
        
        Primary: 0.5 * $99.23 = $49.615, rounded to $49.62.
        
        Secondary Line: $99.23 - $49.62 = $49.61.
      - With a Primary Allocation of 60%, the calculation becomes:
        
        Primary: $99.23 * 0.6 = $59.538, rounded to $59.54.
        
        Secondary Line: $99.23 - $59.54 = $39.69.
      - For a Primary Allocation of 20%:
        
        Primary: $99.23 * 0.2 = $19.846, rounded to $19.85.
        
        Secondary Line: $99.23 - $19.85 = $79.38.
      All other field calculations not mentioned above remain consistent with the original logic.
Arizona PERS:
- Updated the reporting field: "Hours Worked during Pay Period" to use the hour Hour Bucket: "Employee's Worked Hours eligible for State Reporting (ns4g_reportable_hrs)". This modification ensures we accurately track and report hours for state compliance, replacing the previous field with a more specific and informative label.

Various Fixes and Performance Improvements

Updated the employee query REST call selection criteria to accommodate employee IDs in batches of 500. This scalable approach benefits larger clients who previously encountered performance issues. Additional logic has been added to write to the table after every 1,000 records are retrieved. This addresses the previous limitation of Netsuite, which could only transfer 1,000 records at a time, resulting in dropped employee and payroll data.
When the retirement plan code length exceeds the maximum allowed characters for the specified column, it results in a report disruption. To address this, we updated the column length for each table column. This will prevent further disruptions and ensure accurate reporting.