7 Release Notes 26.3.1

NetSuite for Government 26.3.1 Release Notes

Revision Date: March 04, 2026

Important:

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

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

Finance:

• Interest Allocation:
  • The Interest Allocation feature now support Other Current Asset allocation instead of just Bank Accounts to allow for greater flexibility in account types to allocate.

• Balancing Segments:
  • Fund Balancing Segments now supports the Transaction option for Item Receipts on inventory transactions. It is recommended to use the Accrued Purchases account for balancing as it will seamlessly integrate with accounts payable for the inventory purchase workflow.
  • Fund Balancing Segments now supports the Transaction option for Inventory Adjustments to consume warehouse inventory.
  • Fund Balancing for Journal Entry transactions will now post the net amount of the debits and credits to each fund, eliminating the unnecessary and additional accounting entries.
  • Balancing Segment Default Account field will now only show Accounts which belong to the selected subsidiary.

• Purchase Change Order:
  • Creation of a Purchase Change Order will now redirect the user to a transformation page where the Change Order is created in the background and displayed upon completion. This enhancement will increase the speed in which the Change Order is created so the user is not left waiting during the transformation process. Any errors encountered during this process will be sent to the user in an email notification.

    Note:

    If your custom workflow approval is locking the Purchase Order record, the workflow will need to be updated on the Lock Record Action to remove the Context of "Scheduled Script".

• Show In Functionality:
  • The Show In functionality on Item Accounts has been implemented to only allow the appropriate accounts for the transaction type.

Note:

Any existing Requisition will need to have an edit/save performed in order for the Requisition to Purchase Order transformation process to run successfully.

Various Fixes and Performance Improvements

• A new printed form has been added for Purchasing Change Orders. The new form has been modified to include helpful vendor information on the current and previous Change Orders. If the Purchase Change Order has a custom client-defined form, then the administrator should add this new template to the custom form to enable usage.

Human Resources and Payroll:

• Payroll GL Memo:
  • The Payroll GL Transaction is now enabled to record the Pay Period in the memo line.
    • To enable this feature, navigate to Payroll and HR Preferences > Fund Allocation and select Default Payroll GL Transaction Memo w/ Pay Period.

      When enabled, the system automatically includes the Pay Period name in the Parent Record memo and in the memo on each transaction line whenever a Payroll GL Transaction record is generated. For performance reasons, this applies only to Payroll GL Transaction records and does not update Employee Posting Detail records.

• Time Off Calculation Rules (Update):
  • The system calculates an employee’s months of service using the following formula:

    (Pay Period End Date Year − Accrual Longevity Year) × 12

    (Pay Period End Date Month − Accrual Longevity Month)

    (Pay Period End Date Day ÷ Days in Month − Accrual Longevity Day ÷ Days in Month)

    What's Changed?

    Earlier, the final result was rounded down to a whole month. The system has been updated to retain and use the decimal value (no rounding down) when determining the employee’s accrual tier.

    Example:

    Accrual Longevity Date = 11/30/2020;

    Pay Period End Date = 12/19/2025

    2025-2020 = 5 years = 60 months

    12-11 = 1 month

    (19/30)-(30/30) = -0.3667

    Total: 60 + 1 − 0.3667 = 60.633 months

    Earlier, this would be rounded down to 60 months, which could delay movement to the next accrual tier. The system now uses 60.633 (the decimal result) to determine the appropriate accrual tier.

• Payroll Check Form Update:
  • A new Check Form has been created to support payroll check generation using Quick Code logic while ensuring pay stubs print with full detail. This is achieved by enabling the Associated Payroll Item field on the form and updating form settings to display the appropriate Quick Code fields and hide fund validation field.
    If your agency uses Quick Codes (instead of Fund Validation), assign the new form in preferences:

    • Navigate to Payroll and HR Preferences > Checks
    • In Check Form, select NS4G - Payroll Check - Quick Code
    • Save your changes.
• Payroll Frequency Group:
  The following changes have been implemented for agencies with a weekly pay cycle:

  • Added Pay Period Number values 28–53 to support weekly pay periods.
• Utah PERS 2025 Changes:
  • Middle Initial Field Alignment in Export File:

    Issue: The export currently places the employee’s middle name/initial in the same field as the first name. Because there is no dedicated Middle Initial field, all subsequent columns shift one position to the left.

    Update: The file now includes a dedicated Middle Initial field immediately after First Name to maintain correct column alignment.

    Behavior:

    • If a middle initial exists, it will populate the Middle Initial field.
    • If the middle initial is blank, the field will still be included as an empty value (i.e., the delimiters remain) so all following columns stay in the correct positions.
    Example (with middle initial):

    Was:

    02,REGL,490000107,Winters,Camryn A,,,,2115.38,0.00,120.58,0.00,118.46,31.73,0.00,1,75,26.44,HBS,

    Now:

    02,REGL,490000107,Winters,Camryn, A,,,,2115.38,0.00,120.58,0.00,118.46,31.73,0.00,1,75,26.44,HBS,

    Example (no middle initial):

    02,REGL,490000107,Winters,Camryn, ,,,,2115.38,0.00,120.58,0.00,118.46,31.73,0.00,1,75,26.44,HBS,

• Clock In Clock Out:
  • Overview

    The timesheet entry experience has been enhanced to support manual corrections—including negative hours—directly on the timecard. This helps with common scenarios such as correcting prior-period time entered under the wrong hour code (for example, moving hours from Regular to Sick) and zeroing out balances at termination without using separate “zero out” hour codes.

    What’s New?

    Two new fields have been added to the Track Time screen to allow supervisors/payroll users to override the entered duration. These fields are only available on the Track Time screen and are not shown on the Weekly Timesheet view or standard NS4G forms.

  • Override Duration (checkbox):

    Purpose: Enables a duration override for the line.

    How it works?

    Select this checkbox to override the original duration, then enter the number of hours (positive or negative) in Duration Override (Hours). The system will automatically update the Duration field using NetSuite’s standard time formatting (e.g., -5.5 → -5:30).

    Rules:

    • The Override Duration checkbox is always enabled.
    • If Override Duration is not selected, Duration Override (Hours) is disabled.
    • If Override Duration is selected:
      • Duration Override (Hours) becomes enabled.
      • Duration, Clock In, and Clock Out are disabled to prevent conflicting inputs.
      • When a value is entered in Duration Override (Hours), NetSuite formats Duration accordingly:
        • 5.5 displays as 5:30
        • -5.5 displays as -5:30
    • • Because employees may not fully understand the process of adding both a positive and an offsetting negative time entry, we recommend that supervisors or payroll users assist employees when making these corrections.
      • Payroll users typically have access to make these edits on the employee’s behalf (with the employee’s permission), in accordance with your standard operating procedures.
      • Negative hours cannot be entered from the Weekly Timesheet view. To access the correct time entry screen from the Employee Center, navigate to Home > Time Tracking > Track Time.
      • Alternatively, Payroll users can create the entry from the NetSuite Employee Record > Time Tracking > New Time.
  • Scenario 1: Correcting time entered under the wrong hour code (prior pay period).
    If an employee entered incorrect time on a prior timesheet (for example, 8 hours of Regular time on Friday, Feb 27, but they were actually sick), the correction depends on payroll status:

    • If payroll has not been completed: Edit the original timecard entry and recalculate the employee.
    • If payroll has been completed and the employee has already been paid:
      • Create a new time entry for the hour code that should have been used (e.g., Sick) by navigating to Employee Record > Time Tracking > New Time, and enter 8 hours for Feb 27.
      • Create an additional time entry for Feb 27 for Regular time, select Override Duration, and enter -8 in Duration Override (Hours).
      • The system will update Duration to -8:00.
      • The negative Regular entry offsets (“washes”) the original Regular hours.

    Note:

    This approach assumes the employee’s rate is the same for both pay codes, resulting in no financial impact. Some hour codes may affect the rate of pay.
• Louisiana State Tax Calculation:
  • Louisiana state income tax withholding is now available for use.
    Setup / Entry Instructions:

    1. Employee tax setup:
       1. Navigate to Employee Record > Tax tab > State Tax.
       2. In State, select Louisiana.
       3. Enter the related pay code used to calculate Louisiana state tax withholding.
       4. Filing Status: Louisiana does not use filing statuses in this calculation. Leave the Filing Status field blank.
       5. State Dependents/Allowances: Only populate State Dependents/Allowances with one of the following values:
          1. 0 (or blank/null)
          2. 1
          3. 2
       6. These values correspond to Louisiana Form L‑4, Block A.

          Reference: https://dam.ldr.la.gov/taxforms/1300(1_25)F.pdf

• California Tax Tables Update (2026):
  • California payroll tax tables have been updated to the 2026 rates and thresholds. This update ensures tax withholding calculations align with current California requirements for 2026 payroll processing.
• Timesheet Enhancements:
  • Timesheet Position Selection (Position & Pay Records):
    • What’s Changed?

      Timesheet position selection has been updated so that future-dated Position and Pay records are no longer shown until they are active for the selected week/date range.

    • How It Works?
      • When entering a weekly timesheet (and on the daily track time records), the Position dropdown will only display Position and Pay records that are valid for the timesheet week (or the time bill date).
      • A Position and Pay record becomes selectable only when its Begin Date falls within the timesheet week/date range. The record remains available through its End Date.
    • Why This Matters?
      • This change reduces confusion when employees have multiple similar roles and helps prevent validation errors caused by selecting a position that is not yet active.
    • Example:
      • If an employee has a Position and Pay record with a Begin Date of 11/19/2025:
        • It will appear in the timesheet Position drop-down starting with the timesheet week that includes 11/19/2025.
        • It will continue to be available until the Position and Pay End Date.
        • It will not be selectable on timesheets for any earlier weeks.

Various Fixes and Performance Improvements