5 Release Notes 26.3.4

NetSuite for Government 26.3.4 Release Notes Hot Fix

Revision Date: March 22, 2026

Important:

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

The 26.3.4 enhancements and changes listed in this document are not available to customers until they are upgraded to NetSuite for Government 26.3.4. 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 2025.2 to 2026.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 26.3.4 – Release Date March 22, 2026

Finance:

  • GL Inquiry Screen:
    • This enhancement will add columns Fund, Department, Account in General Ledger Inquires results.
  • Purchasing Change Orders:
    • Change Order encumbrance processing has been updated to include the remaining balance of the Purchase Order when calculating the offset used to derive the new Purchase Order encumbrance amount.
  • Trial Balance for Government:
    • This enhancement will make Trial Balance report accessible to below roles:
      • NS4G - Finance Director
      • NS4G - Accounting manager
      • NS4G - Accountant

Various Fixes and Performance Improvements

  • The GL Plug-ins for the Item Override and Balancing Segments feature will now run Asynchronously to improve performance. The extra transaction edit and save which was required by the plug-in is also no longer necessary and has been deprecated.
  • Printing of Cash Sales and Customer Payments has been addressed to support users clicking the "Save and Print" option on both screens.
  • The NetSuite for Government System Setup screen no longer requires the Default Due To, Default Due From, and Default Cash Account when the Balancing Segment configuration is set to the Specify Option. Additionally, the Undeposited Account is no longer required unless the Balancing Segment feature is enabled.
  • Corrected an issue where the Interest Allocation feature failed to create the Interest Journal due to a comma in the Department or Account name.
  • Corrected an issue where negative lines on a Cash Sale caused the Deposit record to miscalculate the deposit amount.
  • Support for Balancing Segments on Deposits related to Customer Refunds has been added. Additionally, Deposit records now have support for editing and saving transactions. Previously, the balancing lines were removed on an edit and save.

Human Resources and Payroll:

  • Utah Retirement System Report:
    • Created new pay buckets for the 2026 Utah Retirement System report.
    • Utah Retirement System (URS) 401(k) Reporting:
      • This update added support for URS 401(k) reporting by creating new pay buckets, updating how employees are selected for a reporting period, and automating how the system calculates and generates URS reporting records and the export file.
        1. New URS Pay Buckets:

          To support URS defined contribution (DC) plans, the system introduced new pay buckets that can be used in payroll so amounts flow automatically into URS reporting.

          URS 401(k) pay buckets

          URS 401K Employee Pre-Tax (ns4g_urs401keepretax_pay)

          URS 401K Employee Post-Tax (ns4g_urs401keeposttax_pay)

          URS 401K Employer Pre-Tax (ns4g_urs401kerpretax_pay)

          URS 401K Employer Additional (ns4g_urs401keraddl_pay)

          URS 401K Employer Pick Up (ns4g_urs401kerpickup_pay)

          URS 457(b) pay buckets

          URS 457b Employee Pre-Tax (ns4g_urs457beepretax_pay)

          URS 457b Employee Post-Tax (ns4g_urs457beeposttax_pay)

          URS 457b Employer Pre-Tax (ns4g_urs457berpretax_pay)

          URS 457b Employer Additional (ns4g_urs457beraddl_pay)

          URS 457b Employer Pick Up (ns4g_urs457berpickup_pay)

          URS Defined Benefit pay buckets

          URS DB Employee Pre-Tax (ns4g_ursdbeepretax_pay)

          URS DB Employee Post-Tax (ns4g_ursdbeeposttax_pay)

          URS DB Employer Pre-Tax (ns4g_ursdberpretax_pay)

          URS DB Employer Additional (ns4g_ursdberaddl_pay)

          URS DB Employer Pick Up (ns4g_ursdberpickup_pay)

          Utah Preferences:

          The Utah state preferences were updated so these pay buckets can be selected and used for URS calculations and reporting.

        2. How the System selects Employees for a Utah Reporting Period?

          The system changed how it finds which employees belong in a Utah Retirement System reporting period.

          Utah selection rule (key change):

          When you calculate a Utah reporting period, the system now:
          • Reads the Reporting Period “Reporting Date”.
          • Finds Employee Pay Period Totals where the related pay period has a Retirement/PERS Reporting Date that matches that reporting date.
          • Uses the child totals (pay bucket totals and hour bucket totals) from those Employee Pay Period Totals for the calculations.
          • If an employee has no matching Employee Pay Period Totals for that reporting date, the employee is not included for that reporting period.

            Note:

            For Utah, employees are still included even when retirement-eligible wages were zero, because Utah reporting can require reporting employees even with $0 wages.
        3. How the System selects Employees for a Utah Reporting Period?
          When the system needs to reference an employee’s retirement setup, it now looks for an active Employee Retirement record that matches all the following:
          • The employee’s retirement system is Utah Retirement System.
          • The related payroll ID is ns4g_utfpers_retire.
          • The record dates overlap the reporting period (begin date on/before period end, and end date on/after period begin).
          • If more than one retirement record overlaps the reporting period, the system selects the record with the furthest end date.
        4. How the System Chooses the Employee Position and Pay Record?

          For position and pay information, the system now uses:

          • The Primary Position and Pay tied to the Employee Pay Period Totals for the reporting period range.
          • If multiple position/pay records are available, the system uses the primary record with the greatest end date. If none exists, fields that depend on position/pay are left blank (depending on what the report requires).
        5. When the System Creates a New “Defined Benefit Retirement Reporting” Record?

          During calculation, the system checks whether any URS DB pay buckets have activity for the reporting period. If any of the following are not zero:

          • URS DB Employee Pre-Tax
          • URS DB Employee Post-Tax
          • URS DB Employer Pre-Tax
          • URS DB Employer Additional
          • URS DB Employer Pick Up

          The system creates a new Employee Retirement Reporting record for the employee for that reporting period. This record may be created in addition to any other retirement reporting record already generated for the employee.

        6. What the System Automatically Defaults for Defined Benefit Records?

          Benefit Program:

          For these DB reporting records, the system now automatically sets:

          • Benefit Program, Tier and Sub Tier defaults from the associated Employee Compliance Record >Benefit Program, Tier and Sub Tier.
        7. How Contribution Amounts Are Calculated?

          When you run Calculate for a Utah reporting period, the system automatically sums the relevant pay buckets and stores the totals on the Employee Retirement Reporting record.

          Employee contributions

          Employee Pre-Tax Contributions = sum of URS DB Employee Pre-Tax

          Employee Post-Tax Contributions = sum of URS DB Employee Post-Tax

          Employer contributions

          Employer Pre-Tax Contributions = sum of URS DB Employer Pre-Tax

          Employer Additional Contributions = sum of URS DB Employer Additional

          Employer Pickup Contributions = sum of URS DB Employer Pick Up

          These totals are calculated for payroll results that fall within the reporting period criteria described in the Utah selection logic.

        8. When the System Creates a New “401(k) Retirement Reporting” Record?

          During calculation, the system checks whether any URS 401(k) pay buckets have activity for the reporting period. If any of the following are not zero:

          • URS 401K Employee Pre-Tax
          • URS 401K Employee Post-Tax
          • URS 401K Employer Pre-Tax
          • URS 401K Employer Additional
          • URS 401K Employer Pick Up

          The system creates a new Employee Retirement Reporting record for the employee for that reporting period. This record may be created in addition to any other retirement reporting record already generated for the employee.

        9. What the System Automatically Defaults for 401(k) Records Benefit Program?

          For these 401(k) reporting records, the system now automatically sets:

          Benefit Program = 401k

          Tier and Sub Tier

          Because 401(k) is a defined contribution plan, Tier/Sub Tier do not apply. The system therefore leaves:

          Tier = blank

          Sub Tier = blank

        10. How are Contribution amounts Calculated?

          When you run Calculate for a Utah reporting period, the system automatically sums the relevant pay buckets and stores the totals on the Employee Retirement Reporting record.

          Employee contributions

          Employee Pre-Tax Contributions = sum of URS 401K Employee Pre-Tax

          Employee Post-Tax Contributions = sum of URS 401K Employee Post-Tax

          Employer contributions

          Employer Pre-Tax Contributions = sum of URS 401K Employer Pre-Tax

          Employer Additional Contributions = sum of URS 401K Employer Additional

          Employer Pickup Contributions = sum of URS 401K Employer Pick Up

          These totals are calculated for payroll results that fall within the reporting period criteria described in the Utah selection logic.

        11. Days Worked and Hours Worked

          The Utah Retirement System form no longer requires Days Worked and Hours Worked fields.

          Days Worked:

          The system now calculates Days Worked by reviewing timecard entries and counting each day in the reporting period where the employee had more than 0 “reportable” hours (hours that feed the reportable hour bucket).

          Note:

          • Days Worked can be left blank and the system will still generate the retirement reporting record.
          • Days Worked can be left blank and the system will still generate the retirement reporting record.
          Hours Worked:
          The system now calculates Hours Worked by summing the employee’s “reportable hours” hour bucket totals for pay periods whose Retirement/PERS Reporting Date matches the reporting period reporting date.

          Note:

          • Hours Worked can be left blank and the system will still generate the retirement reporting record.
          • URS requires whole numbers for hours in the file; if rounding is needed, it is handled during file output.
        12. File Generation:
          • How Headers and Details Are Organized?

          When the system generates the URS file, it now automatically:

          • Reviews all Employee Retirement Reporting records in the reporting period.
          • Groups employees under header sections based on the unique combination of:
            • Benefit Program
            • Tier
            • Sub Tier

          This makes the output file align with URS formatting expectations for header/detail sections.

        13. Employer Organization Code (Multi-Entity Support)
          • For customers using multiple entities, the system now sources the Employer Organization Code using the Payroll and HR Preferences record that matches the entity on the Employee Retirement Reporting record.
          • This ensures the correct URS employer identifier is used per entity.
        14. Retirement Reporting Date Field (Internal Visibility)
          • The system now displays an internal Retirement Reporting Date field on the Employee Retirement Reporting record, sourced from the reporting period’s reporting date. This field is included to help with internal auditing and reporting; it is not required in the URS file.
        15. Middle Name Output Alignment Fix
          • The file output now places Middle Name/Initial into its own dedicated field so the columns do not shift. If an employee does not have a middle name, the file still includes the correct comma placement to preserve column alignment for all fields that follow.
        16. Additional Fields Added for Utah Records
          • Pay Rate Type (Pay Type)
            • A Pay Rate Type field was added and is sourced from the Utah State Compliance Setup values. It typically defaults to HBS (Hourly Base Salary) unless a user updates it.

Various Fixes and Performance Improvements