Release Notes 25.4.1

NetSuite for Government 25.4.1 Release Notes

Revision Date: April 08, 2025

Important:

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

The 25.4.1 enhancements and changes listed in this document are not available to customers until they are upgraded to NetSuite for Government 25.4.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 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.1 – Release Date April 08, 2025

Human Resources and Payroll:

Payroll Multi Entity Support:
- The Entity field has been introduced to the Pay Cycle Screen for enhanced functionality. This field allows users to specify the entity associated with a particular pay cycle. It is especially useful for multi-entity agencies, ensuring accurate assignment. Please note that only one entity can be assigned per pay cycle. This field will be mandatory in future releases. Users should set this field to avoid payroll interruptions.
- The Payroll and HR Preferences have been updated to include the Entity field, which will serve as the primary selection criterion for this preference record.
- The Payroll Direct Deposit Bank Detail Record has been enhanced with the addition of the Entity field. This new field provides an opportunity to further specify and categorize bank details by entity. This field will be mandatory in future releases. Users should set this field to avoid payroll interruptions.
Payroll History and Accumulator Tracking:
- Users have the flexibility to choose specific pay or hour codes for their calculations, which can be beneficial in reducing potential errors. By filtering calculations to a particular code, the risk of miscalculations is significantly minimized. In the event of an incorrect pay or hour bucket assignment, users can quickly identify and rectify the error by recalculating that specified hour and pay codes, ensuring accurate categorization and maintaining data integrity.
  1. Hour Code Filters:
    - All: This is the default option, including all hour code payroll line items in the calculation.
    - Specify: When selected, users can choose specific hour codes from a multi-select list. Calculations will only consider the selected hour codes.
    - Exclude: In conjunction with "Specify," users can opt to exclude a particular hour code from the calculation.
    - None: Choosing this option will exclude all hour code payroll items from the calculation.
  2. Pay Code Filters:
    - All: The default selection, encompassing all pay code payroll line items for recalculation.
    - Specify: Users can select specific pay codes from a multi-select list, limiting the calculation to these chosen codes.
    - Exclude: Similar to the hour code filter, users can exclude a specific pay code from the calculation when Specify is chosen.
    - None: No pay code payroll items will be considered for calculation when this option is selected.
- On the Calculate Employee Historical Payroll Totals page, when the employee filter is applied the system will recalculate and regenerate payroll totals exclusively for the specified employee. This targeted approach ensures a swift and accurate process, benefiting both the system's performance and the user's experience.
- The Restore Payroll Totals page has been added to the navigational menu under the following path: Payroll and HR > Other Setup.
Social Security Tax Exemption:
- When an employee is exempt from social security taxes, their social security taxable wage amount should be set to zero for the calculated payroll batch.
  - If the employee's Exempt - Social Security Taxes checkbox is selected.
  - During the payroll calculation process, the system will remove the social security taxable wages pay bucket from all hour codes and pay codes in the payroll item lines. This action ensures consistency with the state tax/SUI wage function but applies the opposite treatment for social security taxes.
Nebraska State Income Tax Calculation:
- Setup:
  1. To setup the applicable filing statuses for the State of Alabama, navigate to the State Filing Status section.
    - Edit the following statuses and assign them to Alabama.
      - Single
      - Head of Household
      - Married
  2. To enable the income tax calculation for an employee.
    - Navigate to the Taxes tab, then Federal & State, and finally, the State Tax Section: Set the State Tax Pay code defined for your agency where the calculation rule is set with State Tax Deduction.
      - State: Assign Nebraska as the state.
      - State Filing Status: Enter the filing status as per the employee’s form.
      - State Dependents/Allowances: Enter the number of allowances as per the employee’s form.
      - State Extra Withholding: If applicable, enter the additional withholding amount provided by the employee as per the employee’s form.
  3. Calculation Notes:
    - The employee's wages will be annualized, and the tax rate allowance values will use annual figures. The final tax amount is then divided by the annual number of pay periods to determine the per-period tax amount.
    - For further guidance and detailed calculation information, refer to the official guide provided by the State of Nebraska: https://revenue.nebraska.gov/sites/default/files/doc/business/Cir_En_2024/2025cir_en_whole.pdf
Oregon State Tax Calculation:
- The Employee State Income Tax Table has been revised to incorporate the 2025 tax brackets for the state of Oregon.
State Compliance Prerequisites and Reports (PERS, SUI, W2):
- To further refine the categorization for the reporting period, the following additional fields have been introduced:
  1. Sub Type:
    - This field is optional and should be utilized when necessary to indicate a more specific sub-type for the reporting period. Values include:
      - Adjustment
      - Retroactive Adjustment
      - Correction
      - Test
      - Amended
  2. Sub Type Number:
    - If a Sub Type is selected, this field becomes mandatory. It serves as a supplementary number, acting as an additional identifier for scenarios requiring multiple amendments or adjustments.
  3. Reporting Date:
    - The reporting date is a critical piece of information, especially for state reports. For detailed instructions on its usage, please refer to the state guide user manual.
Utah Pers Report:
- An employee retirement reporting record has been established, featuring fields tailored to the Utah Retirement System Report (2025 version).
- Added State Compliance Setup Types for Utah PERS:
  - Benefit Program
  - Tier
  - Sub Tier
  - Transaction Type
- Enhanced the Employee Retirement Record with additional fields to the NS4G Utah Retirement System form:
  - Benefit Program
  - Tier
  - Sub Tier
State Compliance Setup Record:
- The State field within the State Compliance Setup record has been updated to be non-mandatory. While the form may visually indicate the field as required, the actual requirement for data entry has been removed.
Affordable Care Act (ACA) File:
- Updated the logic for the AggregatedGroupInd field. For ALE 1094-C records where the AggregatedGroupInd is "All 12 Months" and the Jan-Dec Line 23(d)-35(d) indicates an Aggregated ALE Group membership, set the field value to 1 if the ALE Member is part of the group, and 0 if they are not. The Aggregated Group Member Code remains unchanged:1 for True and 0 for False.

Prevent Duplicate Employee Benefit Plans

When a benefit plan is copied or duplicated, employees may receive duplicate pay codes. To ensure accurate record-keeping, kindly remind users to assign an end date to previous benefit plans, thereby ensuring the associated pay codes are correctly terminated.

System Behavior:

To maintain data integrity, the system will prevent users from saving an Employee Benefit Plan record if it exhibits the following:

Overlapping Coverage Begin and End dates with another existing Employee Benefit Plan Record.
The same Benefit Plan as an existing record.

Example 1:

Plan A: Dental Employee Only, Coverage Begin Date: 01/01/2024 - 09/30/2024

If a user attempts to create:

Plan B: Dental Employee Only, Coverage Begin Date: 09/15/2024 - 12/31/2099

The system will not allow the creation of Plan B due to overlapping dates (09/15/2024 - 09/30/2024) with Plan A. An error message will be displayed: "Employee cannot have two duplicate benefit plans with overlapping coverage dates."

Example 2:

An Employee Benefit Plan Record with the following details:

Benefit Plan: Medical Employee Only
Coverage Begin Date: 01/01/2024 - 09/30/2024

If a user tries to create another record with:

Benefit Plan: Dental
Coverage Begin Date: 01/01/2024 - 09/30/2024

The system will allow for creation because the benefit plans are unique.

The vendor bill generation logic has been updated to sum the actual payline item amounts for each vendor's payroll. The updated logic ensures that the Vendor Bill total matches the payroll line item total exactly, addressing any potential rounding issues.
- Example Scenario:
  - Vendor A:
    - Employee 1 Payroll Item: $22.23
    - Employee 2 Payroll Item: $240.01
  - The total amount on the Vendor Bill should accurately reflect the sum of these payroll items: $22.23 + $240.01 = $262.24.
- GL Impact Adjustment:
  - In cases where there is a slight difference between the vendor bill amount and the incurred liability, under/over adjustment logic has been added to account for any penny-level discrepancies.

Various Fixes and Performance Improvements

The issue pertaining to the inaccurate calculation of additional Medicare on the 941 Report has been rectified.

28 Release Notes 25.4.1