Reporting Release Notes 25.3.2

NetSuite for Government Reporting 25.3.2 Release Notes

Revision Date: March 21, 2025

Important:

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

These release notes are subject to change every week.

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

Finance:

Budget vs Actuals Report:
- Updated the Budget vs Actuals reports to rename the column Transfer to Adjustments. This column includes all budget adjustment types, Transfers, Rollovers, Amendments.
Budget vs Actuals - Multiple Years Report:
- Resolved issue with drill downs when filtering on subsidiary.
- Updated date formats to match the standard date format.
Transactions Report:
- Removed the Statement of Activities Group from the transaction template. This field can still be added as an additional column.
- Renamed GL Impact to Posted on the transactions report.
- Updated the column order to ensure the report is consumable when a user first runs the report.
- Removed Transaction ID from the transaction template. This field can still be added as an additional column.
- The default sort of the transaction report will be by Date.
- Updated the transactions report to include all transaction types - Users can filter on Transaction type or Posted to filter their criteria
- When filtering by posting period, we were not getting expected results. This has now been resolved.

Various Fixes and Performance Improvements

Human Resources and Payroll:

Oregon 132 State Quarterly Report:
- The report has been revised to source the number of hours from the newly designated Employee's Worked Hours eligible for State Reporting bucket (ns4g_reportable_hrs) in the Hours Worked field.
  To ensure effective utilization of this update, users must apply this hour bucket to all applicable worked hours codes, while excluding non-worked hours codes such as vacation and sick leave, thereby adhering to the Oregon PERS guidelines.

Oregon PERS:
- For the Oregon PERS retirement system, agencies with bi-weekly payroll or payroll periods crossing monthly boundaries must submit separate reports for pay periods spanning two months. To ensure accurate wage allocation, the Define Data section of the report has been updated to include the Work Period Begin Date, Work Period End Date, and Work Period Allocation Percentage.
  - Work Period Begin and End Date replaces the previous use of Pay Period Begin and End Date in the file. The work period dates provide a more accurate representation as they may not always align with the pay period dates.
  - Work Period Allocation Percentage This field allows for the input of the allocation percentage corresponding to the work period.
    
    Continue to populate the Reporting Period's > Report Date as the system will only retrieve employee data where the corresponding Pay Period > Retirement / PERS Reporting Date aligns.
  - Pay Periods Crossing Monthly Boundaries:
    When generating reports, consider the following guidelines:
    - If the report covers a period within a single month, a single report with a Work Period Allocation Percentage of 100% is sufficient.
    - For pay periods spanning two months, create two separate reports. These reports should utilize percentage allocations that sum up to 100%, such as 70% and 30% or 100% and 0%, ensuring an accurate distribution of wages.
  - Fields Calculated by Percentage
    The following field values will be calculated by the Work Period Allocation Percentage:
    - Hours Worked (Regular)
    - Hours Worked (Overtime)
    - Subject Salary, Regular
    - Subject Salary, Overtime
    - Non-Subject Salary
    - Lump-Sum Payoff
    - Member Paid After-Tax Contribution (MPAT)
    - Member Paid Pre-Tax Contribution (MPPT)
    - Unit Contribution
    - Employer Paid Pre-Tax Contribution (EPPT)
    - Optional Employer IAP Percentage
    - Optional Employer IAP Contribution
    - Lump-sum Vacation Payoff

Florida Retirement System and Florida Re-employment Report:
- To address the system timeout issue, we added a table to store the report's calculated preview data. This table will ensure that the information is readily available and accessible, eliminating the need to rerun the script on demand. This change was applied to both the Florida Retirement System report and the Florida Reemployment Report to enhance their functionality and user experience.
- The Agent Identifier has been updated to a new format. It now consists of the letter E followed by the State Employer Identification Number (EIN) for the Parent Entity. For example, if the State EIN is 333333333, the Agent Identifier would be displayed as E333333333.
- The system now extracts the full phone number, including the first digit, for the Entity's Address and Phone details. The leading +1 is no longer excluded when pulling the phone number for the Parent Entity, ensuring the correct and complete phone number is obtained.
Iowa's MFPRSI Report:
- The Iowa MFPRSI report is now enabled to run for a designated reporting period such as bi-weekly or quarterly.
- Updated the Define Data on Iowa's MFPRSI Report
  - Removed the Reporting Period Date field and replace it with the following:
    - Reporting Period Begin Date
    - Reporting Period End Date
- Added the following date conditional logic: The Reporting Period End Date must be greater than or equal to the Reporting Period Begin Date.
- Refactored Logic for Iowa's MFPRSI Report: Previously, the report retrieved data based on a specific Retirement/PERS Reporting Date from the Report Definition, searching for pay lines with the same Retirement/PERS Reporting Date as the Reporting Period Date. This logic has been updated to:
  - Search for pay lines where the Retirement/PERS Reporting Date falls within the specified Reporting Period Begin Date and Reporting Period End Date. In other words, the condition is now: Reporting Period Begin Date <= Retirement/PERS Reporting Date <= Reporting Period End Date.
  - For accurate reporting, ensure that when running the report for a specified period, the Begin and End Dates align with the Retirement/PERS Reporting Date as set on the corresponding pay period.

Utah Retirement Report:
- The hourly rates in NetSuite may be displayed with varying decimal precision. For this report, we have formatted the rates to two decimal places to ensure consistency and clarity.

Various Fixes and Performance Improvements

30 Reporting Release Notes 25.3.2