Release Notes 26.4.1

NetSuite for Government 26.4.1 Release Notes

Revision Date: April 01, 2026

Important:

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

The 26.4.1 enhancements and changes listed in this document are not available to customers until they are upgraded to NetSuite for Government 26.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 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.4.1 – Release Date April 01, 2026

Finance:

Balancing Segments:
- Fund balancing is now supported for Deposits on Refunds for Cash Sales.
- Fund Balancing for AR Invoices with Billable Items and Expenses is now supported.
- Fund balancing for Bill Payments where Bill Credits are applied to Bills will now use the Due To account, consistent with how fund balancing is handled for payments of standard Bills.
  
  Note:
  This is only for the Specify option and using Due To/Due From and not the Accounts Payable Account. Historical transactions for Bill Payments may be updated by simply clicking Edit then Save on the record.
- Fund Balancing will no longer run for Employee Center Expense Reports. This change eliminates a recurring error previously recorded in the execution log for these transactions.
  Employee Center Expense Reports are non-posting transactions, so running the plug-in provided no posting benefit and generated unnecessary errors in logs. Final balancing for these transactions is intended to occur as part of the accounting approval process.

Purchasing Change Order:
- The Change Order transformation process has been improved to prevent timing issues and the message "A Change Order has already been created for the selected purchase order". This update improves processing robustness and ensures Change Orders continue to progress reliably through workflow, reducing delays and manual intervention.

Various Fixes and Performance Improvements

Item Override and Balancing Segment processing now runs under a specialized permission to reduce permission-related blocks and prevent processing errors. This update improves reliability by ensuring the required access is applied during processing without impacting standard user permissions.
We have delivered a performance enhancement that makes Quick Code validation faster and more reliable in the UI—especially for transactions with large or complex line sets. By eliminating costly front end validation and reducing heavy sublist updates, this update helps prevent browser freezes and responsiveness issues, improving data entry speed and ensuring transactions can be saved consistently, even at higher volumes.
The design uses a simple rule: when the transaction has many different general ledger segment combinations, the first level validation skips Quick the Code processing and lets the server handle this functionality during Save.
For transactions with more than 40 unique combinations:
- To keep the UI responsive, Quick Code validations are skipped on the front end.
- Because the front end validation is skipped, WARN messages will not appear, and if no matching code is found, the Quick Code field remains blank for user review.
- Users can still proceed to Save, and the server performs full Quick Code validation and population.
- If STOP rules apply, the server will block the Save and return an error. In very large line sets, this could mean re-entering recent changes; in practice, these high-volume transactions are typically created via CSV import or copy from an existing valid transaction, which helps minimize manual rework.
For transactions with 40 or fewer unique combinations the process remains exactly the same. This includes:
- The front end continues to run Quick Code validations and will show WARN/STOP messages before Save, preserving the same experience as before this enhancement.
- The server still performs full validation and correction on Save for defense in depth.
Resolved an error where the Employee Center option to create a Purchase Request presented an error if a custom

Note:
Custom Employee Center roles must have permissions added to the Script Deployment Records:
- NS4G UE Requisition
- NS4G UE Purchase Order
- NS4G SL Get Custom List Values
- NS4G SL Query Run SQL

Human Resources and Payroll:

Oregon State Tax Calculation:
- The Employee State Income Tax Table has been revised to incorporate the 2026 tax brackets for the state of Oregon.
2026 Minnesota State Tax update:
- To setup the applicable filing statuses for the State of Minnesota, navigate to the State Filing Status section.
  - Edit the following statuses and assign them to Minnesota.
    - Single; Married, but legally separated; or Spouse is a nonresident alien
    - Married
    - Married, but withhold at a higher Single rate
- To enable the income tax calculation for an employee:
  - Navigate to the Taxes tab, then Federal & State > State Tax Section.
    - State Tax: Set the State Tax Pay code defined for your agency where the calculation rule is set with State Tax Deduction
    - State: Assign Minnesota as the state.
    - State Dependents/Allowances: Enter the number of Dependent Allowances as per the employee’s Form W-4MN, Line 1.
    - State Extra Withholding: If applicable, input the extra withholding amount provided by the employee as per the employee’s Form W-4MN, Line 2.
- Calculation Notes:
  - The employee's wages will be annualized, and standard deductions and dependent 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 Minnesota: https://www.revenue.state.mn.us/sites/default/files/2025-12/wh-inst-26.pdf
Utah Retirement System:
- Utah Retirement System (URS) 457b Reporting:
  - This update added support for URS 457b 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.
    - 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 457b 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
    - How the System Selects Employees for a Utah 457b Retirement Reporting record (key change)?
      - When you calculate a Utah reporting period, the system now:
        
        Creates a New “457b Retirement Reporting” Record.
        
        During calculation, the system checks whether any URS 457b pay buckets have activity for the reporting period. If any of the following are not zero:
        URS 457b Employee Pre-Tax
        
        URS 457b Employee Post-Tax
        
        URS 457b Employer Pre-Tax
        
        URS 457b Employer Additional
        
        URS 457b 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.
      - What the System Automatically Defaults for 457b Records?
        Benefit Program:
        
        For these reporting records, the system now automatically sets:
        
        Benefit Program = 457b
        
        Because 457b is a defined contribution plan, Tier/Sub Tier do not apply. The system therefore leaves:
        
        Tier = blank
        
        Sub Tier = blank
      - 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 457b Employee Pre-Tax
        Employee Post-Tax Contributions = sum of URS 457b Employee Post-Tax
        Employer contributions
        Employer Pre-Tax Contributions = sum of URS 457b Employer Pre-Tax
        Employer Additional Contributions = sum of URS 457b Employer Additional
        Employer Pickup Contributions = sum of URS 457b Employer Pick Up
        These totals are calculated for payroll results that fall within the reporting period criteria described in the Utah selection logic.
  - Utah Retirement System (URS) Roth Reporting:
    - This update added support for URS Roth 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.
      - 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 Roth Pay buckets:
        
        URS Roth Employee Pre-Tax ns4g_ursRotheepretax_pay
        
        URS Roth Employee Post-Tax ns4g_ursRotheeposttax_pay
        
        URS Roth Employer Pre-Tax ns4g_ursRotherpretax_pay
        
        URS Roth Employer Additional ns4g_ursRotheraddl_pay
        
        URS Roth Employer Pick Up ns4g_ursRotherpickup_pay
      - How the system selects Employees for a Utah Roth Retirement Reporting record (key change)?
        
        When you calculate a Utah reporting period, the system now:
        
        Creates a New “Roth Retirement Reporting” Record.
        
        During calculation, the system checks whether any URS Roth pay buckets have activity for the reporting period. If any of the following are not zero:
        
        URS Roth Employee Pre-Tax
        
        URS Roth Employee Post-Tax
        
        URS Roth Employer Pre-Tax
        
        URS Roth Employer Additional
        
        URS Roth 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.
      - What the System automatically Defaults for Roth Records?
        Benefit Program:
        
        For these reporting records, the system now automatically sets:
        
        Benefit Program = Roth
        
        Because Roth is a defined contribution plan, Tier/Sub Tier do not apply. The system therefore leaves:
        
        Tier = blank
        
        Sub Tier = blank
      - 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 Roth Employee Pre-Tax
        
        Employee Post-Tax Contributions = sum of URS Roth Employee Post-Tax
        
        Employer contributions
        
        Employer Pre-Tax Contributions = sum of URS Roth Employer Pre-Tax
        
        Employer Additional Contributions = sum of URS Roth Employer Additional
        
        Employer Pickup Contributions = sum of URS Roth Employer Pick Up
        
        These totals are calculated for payroll results that fall within the reporting period criteria described in the Utah selection logic.
  - Utah Retirement System (URS) 401k DC Loan Reporting:
    - This update added support for URS 401k DC Loan 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.
      - New URS Pay Buckets
        To support URS 401k DC Loans, the system introduced a new pay bucket that can be used in payroll so amounts flow automatically into URS reporting.
        
        URS 401K Installment Loan Employee Post-Tax ; ns4g_urs401kloaneeposttax_pay
      - How the system selects Employees for a Utah 401k DC Loan Retirement Reporting record (key change)?
        
        When you calculate a Utah reporting period, the system now:
        
        Creates a New “401k DC Loan Retirement Reporting” Record.
        
        During calculation, the system checks whether the URS 401k DC Loan pay bucket has activity for the reporting period. If any of the following are not zero:
        
        401k DC Loan
        
        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.
      - What the System Automatically Defaults for 401k DC Loan Records?
        Benefit Program:
        
        For these reporting records, the system now automatically sets:
        
        Benefit Program = 401k
        
        Because 401k is a defined contribution plan, Tier/Sub Tier do not apply. The system therefore leaves:
        
        Tier = blank
        
        Sub Tier = blank
        
        Because 401k DC Loan is a loan the transaction type is set to DCLN.
      - 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 = 0
        Employee Post-Tax Contributions = Sum of the URS 401K Installment Loan Employee Post-Tax pay bucket
        Employer Pre-Tax Contributions = 0
        Employer Additional Contributions = 0
        Employer Pickup Contributions = 0
        These totals are calculated for payroll results that fall within the reporting period criteria described in the Utah selection logic.
  - Utah Retirement System IRA:
    - Utah Retirement System (URS) Roth Reporting:
      - This update added support for URS IRA 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.
        
        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 IRA Pay buckets:
        URS IRA Employee Pre-Tax ns4g_ursIRAeepretax_pay
        URS IRA Employee Post-Tax ns4g_ursIRAeeposttax_pay
        URS IRA Employer Pre-Tax ns4g_ursIRAerpretax_pay
        URS IRA Employer Additional ns4g_ursIRAeraddl_pay
        URSIRA Employer Pick Up ns4g_ursIRAerpickup_pay
      - How the system selects Employees for a Utah Roth Retirement Reporting record (key change)?
        
        When you calculate a Utah reporting period, the system now:
        
        Creates a New “IRA Retirement Reporting” Record.
        
        During calculation, the system checks whether any URS IRA pay buckets have activity for the reporting period. If any of the following are not zero:
        
        URS IRA Employee Pre-Tax ns4g_ursIRAeepretax_pay
        
        URS IRA Employee Post-Tax ns4g_ursIRAeeposttax_pay
        
        URS IRA Employer Pre-Tax ns4g_ursIRAerpretax_pay
        
        URS IRA Employer Additional ns4g_ursIRAeraddl_pay
        
        URSIRA Employer Pick Up ns4g_ursIRAerpickup_pay
        
        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.
      - What the system automatically Defaults for IRA Records?
        Benefit Program:
        For these reporting records, the system now automatically sets:
        Benefit Program = IRA
        Because IRA is a defined contribution plan, Tier/Sub Tier do not apply. The system therefore leaves:
        Tier = blank
        Sub Tier = blank
      - 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 IRA Employee Pre-Tax
        Employee Post-Tax Contributions = sum of URS IRA Employee Post-Tax
        Employer contributions
        Employer Pre-Tax Contributions = sum of URS IRA Employer Pre-Tax
        Employer Additional Contributions = sum of URS IRA Employer Additional
        Employer Pickup Contributions = sum of URS IRA Employer Pick Up
        These totals are calculated for payroll results that fall within the reporting period criteria described in the Utah selection logic.
Payroll Processing Enhancements:
- Background (What’s changed)?
  - Agencies often include part-time employees in a payroll batch even when they have no earnings in a given pay period. This can result in zero or negative net pay checks, requiring manual cleanup. The Pay Period setup now includes an option to automatically exclude employees whose calculated Net Pay is zero or less, reducing manual batch maintenance.
  - How to use?
    - Exclude employees with zero or negative net pay.
      - To Enable the setting on the Pay Period:
        
        Open the Pay Period record.
        
        Locate the checkbox Exclude Employees with Zero or Negative Net Pay (positioned after “Make available to timesheets”).
        
        Check the box to enable the behavior for that pay period.
        
        Save the Pay Period.
        
        Note:
        If you frequently run special pay periods (e.g., benefits-only or accrual pay periods), you can copy an existing pay period and reuse these settings.
      - To Run Calculate Payroll:
        
        Start the Calculate Payroll process for the pay period.
        
        During calculation, the system evaluates each employee’s Net Pay.
        
        Any employee with Net Pay ≤ 0 is automatically excluded from the payroll batch (they will not be included in batch results or downstream processing).
        
        Recommended process (best practice):
        
        Calculate the payroll batch first with the checkbox not selected.
        
        Review the batch results and identify any employees with a zero or negative net pay check.
        
        Determine whether those employees should or shouldn’t be paid for that payroll (for example, confirm time entry, benefit deductions, accrual-only payrolls, or other expected scenarios).
        
        Once you confirm the employees should be excluded, open the Pay Period record and select Exclude Employees with Zero or Negative Net Pay.
        
        Recalculate the payroll batch. The system will automatically exclude employees with Net Pay ≤ 0 from the batch.
  - What happens during recalculation and uncommit scenarios (system behavior)?
    - If a payroll batch is committed, and an employee has both:
      - an Employee Posting Detail record, and
      - a check record,
      - and the batch is later uncommitted and recalculated such that the employee’s Net Pay becomes zero or negative, the system performs cleanup so the employee can be excluded correctly:
      - The system deletes the related Employee Posting Detail record.
      - The system disassociates the (voided) check from the payroll item by clearing the Associated Payroll Item field on the check.
      - Users can still see the original linkage via System Notes.
2026 Georgia State Tax Calculation:
- Georgia State Income Tax Calculation
  - Setup:
    - To setup the applicable filing statuses for the State of Georgia, navigate to the 'State Filing Status' section.
      - Edit the following statuses and assign them to Georgia.
        
        Single
        
        Head of Household
        
        Married Filing Separately
        
        Married Filing Jointly
    - To enable the income tax calculation for an employee:
      - Navigate to the 'Taxes' tab, then 'Federal & State', and finally, the 'State Tax Section'.
      - State Tax: Set the State Tax Pay code defined for your agency where the calculation rule is set with State Tax Deduction.
      - State: Assign ‘Georgia’ as the state.
      - State Filing Status: Input the employee’s provided ‘State Filing Status’.
      - State Dependents/Allowances: Enter the number of Dependent Allowances as per the employee’s details.
      - State Extra Withholding: If applicable, input the extra withholding amount provided by the employee.
    - Calculation Notes:
      - The employee's wages will be annualized, and standard deductions and dependent 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 Georgia: https://dor.georgia.gov/employers-tax-guide
2026 Nebraska State Tax Calculation (MAPA):
- The Employee State Income Tax Table has been revised to incorporate the 2026 tax brackets for the state of Nebraska.
2026 Arkansas Employee Income Tax Calculation:
- The Employee State Income Tax Table has been revised to incorporate the 2026 tax brackets for the state of Arkansas.
Fund Allocation Enhancements:
- The Over/Under account is used to create transaction lines on Vendor Bills, and employee posting detail record. Accounts with the “Bank” type cannot be selected for Vendor Bill transactions, so cash/bank accounts are not supported for the Over/Under account.
  To avoid selection errors, the Over/Under Payroll Account field has been updated to restrict selection to only the supported account types. In most cases, customers use an account type such as “Other Current Liability” for the Over/Under account.

Various Fixes and Performance Improvements

3 Release Notes 26.4.1