Release Notes 26.7.1

Revision Date: July 08, 2026

Important:

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

The 26.7.1 enhancements and changes listed in this document are not available to customers until they are upgraded to NetSuite for Government 26.7.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 2026.1 is released. 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.7.1 – Release Date July 08, 2026

Finance:

GL Inquiry Screens:
- Resolved issue where the wrong Grant field (record) was being shown on the details page of General Ledger Inquiries. This is part of the effort is to continue data clean up with the Grant segment.
GL Summary Screens:
- Government Budget Adjustments now use the transaction date to determine the applicable reporting period, rather than following the same date ranges as the Government Budget.
  When reviewing budget adjustments, the budgetary impact will be reflected in the month in which the transaction occurred for both Monthly and Year-to-Date (YTD) reporting. This aligns budget adjustments with how actual transactions are reported, while still reflecting budgetary activity.
- Resolved an issue in the General Ledger Summary report where special characters in memos or other text fields could cause exported files to generate unintended additional columns.
Trial Balance for Government:
- Added the ability to use the project number on the Government Trial Balance.
Departmental Reporting /Budget vs Actual:
- Enhancement to the Budget vs Actuals Report:
  - Remove Date from Pivot Table
  - Change names of fields for ease of use
  - Use custom segment fields for Projects and Grants
Balancing Segments:
- Balancing Segments for the Specify method has been updated to skip unnecessary additional balancing lines on the Deposit record for Customer Payments and Customer Refunds if these transactions are not posting to the Undeposited Account. If instead, the Undeposited Account is used in the configuration screen "Transaction Cash Account" for the Customer Payment, the additional balancing lines to transfer from Undeposited to Cash will continue as it does today.
- New Exception Saved Search for Balancing Segment by Fund
  - A new saved search named “Fund Balancing Exception Report by Fund” is now available for use with the NetSuite for the Government Balancing Segment feature. This search identifies transactions that are not in balance by fund.
  - This is an exception-only report, meaning results are displayed only when transactions are out of balance. If no transactions appear in the search results, no balancing exceptions were found.
- Fund Balancing Support for SuiteTax Sales Tax Amounts
  - NetSuite for Government Balancing Segments now supports fund balancing for included sales tax amounts used by SuiteTax on the Tax Details tab.
  - This enhancement applies to related transactions in the AR/CR workflow. Sales tax amounts are posted to the sales tax payable account within the fund associated with the sales tax lines on the original transaction, and the sales tax amount is then carried forward to related transactions for cash collection.
  - For Invoices, Credit Memos, Cash Sales, and Refund Cash Sales, the original transaction accrues or reverses the sales tax liability from the transaction. Other transactions in the workflow continue to collect the receivable or due to/from amounts which include the sales tax.

Various Fixes and Performance Improvements

Resolved issue with different roles not being able to choose child entities.
Resolved issues with project numbers on the General Ledger Summary and Inquiry screens.
Deposit Account Updates Preserved for Cash-Related AR Transactions
- An issue has been corrected where the deposit account for cash-related AR/CR transactions could revert to the default account by payment method when the transaction was opened in edit mode.
- The following transaction screens now preserve user-updated deposit account values instead of reverting them to the default:
  - Cash Sales
  - Customer Payments
  - Customer Refunds
  - Customer Deposits

Human Resources and Payroll:

Standard Leave upper-limit checking:
- Standard Leave with Limit Checking now caps an earning at the configured upper limit. If the limit is 5 hours and the calculated earning is 6 hours, only 5 hours are allowed. The issue affected certain environments.
  Configuration and User guide:
  - No setup change is required.
    - Confirm the existing Upper Limit on the leave setup.
    - Calculate a test earning above the limit and confirm the result is capped.
    - Calculate an earning below the limit and confirm normal processing is unchanged.
Utah Pers 2026 Changes (Ineligible Employees):
- An employee marked Ineligible on the active Utah Employee Retirement record now reports Retirement Salary as 0.00 on every generated benefit-program record. When the employee has a non-zero URS contribution, Calculate also creates a PE / INEL / 009 placeholder record and updates header counts.
  - Confirm the employer is configured for Utah Retirement System and the employee’s active record overlaps the reporting period.
  - Set Tier to Ineligible and confirm Status Code is consistent with the employer’s onboarding process.
  - Run Calculate; verify Retirement Wages/Salary is 0.00 on all records for the employee.
  - For contribution activity, confirm the PE / INEL / 009 placeholder retains Gross Wages, contains no contributions, and is included in file counts.
Utah Pers 2026 – Roth 401(k) and Roth 457(b):
- Calculate now creates separate R401k and R457b reporting records when at least one corresponding plan bucket is non-zero. Member Roth contributions normally report in Employee Post-Tax. Adjustments use the existing ADJT workflow.
  Map pay codes to the existing Utah Roth buckets:
  
  Plan Contribution Buckets:
  
  Plan: R401k | Employee Buckets: Pre-Tax: ns4g_ursr401keepretax_pay; Post-Tax: ns4g_ursr401keeposttax_pay | Employer Buckets: Pre-Tax: ns4g_ursr401kerpretax_pay; Additional: ns4g_ursr401keraddl_pay; Pickup: ns4g_ursr401kerpickup_pay
  Plan: R457b | Employee Buckets: Pre-Tax: ns4g_ursr457beepretax_pay; Post-Tax: ns4g_ursr457beeposttax_pay | Employer Buckets: Pre-Tax: ns4g_ursr457berpretax_pay; Additional: ns4g_ursr457beraddl_pay; Pickup: ns4g_ursr457berpickup_pay
  - Confirm Utah activates Benefit Program values R401k and R457b and that participating employees have active Utah retirement records.
  - Run Calculate and confirm records are created only for plans with non-zero bucket activity.
  - Verify Benefit Program, Employee Post-Tax, employer contributions, and any ADJT dates/amounts before generating the file.
Note:
No new Utah UI, reporting fields, pay buckets, or compliance values are required.
Texas Municipal Retirement System (TMRS):
- The module now generates the monthly TMRS-2 as a 62-character fixed-width text file with one row per eligible employee and no header, totals, or delimiters. Multiple payroll results are aggregated; employees with zero salary and zero deposit are excluded.
  Configuration and use:
  - Set Payroll and HR Preferences > State to Texas and enter the TMRS five-digit City Number in Agency PERS ID. Preserve leading zeros.
  - Use the NS4G Texas Retirement System form for Employee Retirement and Employee Retirement Reporting records. Re-test TCDRS when adopting the shared Texas form.
  - Map eligible earnings to Retirement Eligible Wages (ns4g_retire_pay) and employee deposits to PERS Employee Contribution (ns4g_persee_pay).
  - Create active TMRS Employee Retirement records with dates that overlap the reporting month. • Create the monthly Reporting Period, run Calculate, and verify one aggregated row per eligible employee per city/month.
  - Generate the file and validate the 5-digit City Number, 9-digit SSN, salary/deposit cents, and 33-character member name.
Note:
Continue using the employer’s current TMRS submission process and companion TMRS-3 requirements.
Payroll Register Enhancements:
- Payment Date Range detail:
  - Payment Date Range mode aggregates employee detail across committed batches. It uses AMOUNT instead of CURRENT, removes YTD and check/payment-period details, shows the selected date range, alphabetizes codes, suppresses zero lines, and displays the employee’s applicable state taxable-wage bucket.
    - Select Payment Date Range, enter beginning and ending payment dates, and apply normal filters.
    - Generate Employee Detail and confirm Date Range, Entity above Department, AMOUNT, and no YTD.
    - Confirm Pay Period, Pay Date, Memo, Checks & Direct Deposits, and the entity watermark are omitted.
    - Review the applicable state wage bucket and zero-line suppression.
  o Save to File Cabinet:
  - Pay Period and Payment Date Range PDFs can be processed server-side and saved directly to a selected File Cabinet folder, supporting larger report volumes.
    - Select Save Report to the File Cabinet and choose a folder available to your role.
    - Run the report, then confirm the completed PDF appears in the target folder.
California PERS Employee Retirement Reporting:
- Scheduled Full Time Hours per Week now accepts decimals without replacing existing values. The California form displays Rate Type values Hourly (HRY), Daily (DLY), and Monthly (MTY), and Benefit Formula is hidden from non-California forms.
  Configuration and User guide:
  - Confirm Payroll and HR Preferences > State is California and the NS4G California PERS form is used.
  - Verify Rate Type offers HRY, DLY, and MTY and Benefit Formula appears only on the California form. (The rate type will dynamically be reflected in the CA PERS report in an upcoming release).
  - Enter decimal Scheduled Full Time Hours per Week and select Rate Type when applicable.
  - Run the CalPERS report and confirm scheduled hours transfer in ####.## format.
Idaho PERSI Arrivos:
- The module now supports the pipe-delimited Arrivos Transmittal file with Header, Detail, and Footer records; Idaho-specific forms, fields, State Compliance values, Reporting Period Frequency, and pay buckets are included.
  Employee and Payroll setup:
  - Set State to Idaho; activate PERSI/ORP plan values and Member Types REG, WRM, RCM, RTW, and NPE.
  - Enter the four-character Agency PERS ID. All entities in a multi-entity period must share it.
  - Use the NS4G Idaho Retirement System forms for Employee Retirement and Employee Retirement Reporting records.
  - Map Idaho Compensation, Other Pay, Non-Pensionable Compensation, Employee Contributions, and reportable worked hours.
  - Create the Reporting Period with Entity, dates, Reporting Date, and required Frequency.
  Employee and file steps:
  - On the Employee Retirement record, enter a non-SSN PERS ID, Plan Type, and Member Type; set Sick Leave Participation, Elected Official/Appointed, and School District Employee as applicable.
  - Run Calculate and review compensation, contributions, hours, and unused sick leave units.
  - Complete Earning Explanation when Other Pay exists; use Contract Percent only for school district employees when Hours is not reported.
  - For a prior-cycle replacement, update Begin/End Dates and select NCA Indicator.
  - Generate the file and confirm one Header (1), Detail records (4), and one Footer (9), with pipe-delimited non-wrapping rows.
  - Submit Enrollment first, Class/Status Change second when needed, and Transmittal last.
Timecard Quick Code Enhancements:
- A Time Tracking preference now controls whether Quick Code-derived Fund, Department, Program, Project, Project Task, Grant, and custom segments are locked or editable on Time Bill and Weekly Timesheet entry.
  Quick Code Preference Behavior:
  
  Locked Preference Enabled: Quick Code populates and disables segment fields. Clearing the Quick Code clears the related segments and enables the fields.
  
  Preference Disabled: Quick Code populates segments, but users may edit them. Clearing the Quick Code leaves the current segment values in place.
  Configuration and User guide:
  - Open Payroll and HR Preferences > Time Tracking > Lock GL Segments when Quick Code is Applied.
  - Enable the preference to prevent segment overrides; disable it when users may edit populated segments.
  - Test selection and clearing of a Quick Code in both Time Bill and Weekly Timesheet entry.
Note:
Other Quick Code and custom-segment work items from the source page are not included.

Various Fixes and Performance Improvements

2 Release Notes 26.7.1