2 Release Notes 26.9.1
NetSuite for Government 26.9.1 Release Notes
Revision Date: September 02, 2026
Important:
This document summarizes the changes to NetSuite for Government between 26.9.1 and the previous release. These release notes are subject to change every week.
The 26.9.1 enhancements and changes listed in this document are not available to customers until they are upgraded to NetSuite for Government 26.9.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.9.1 – Release Date September 02, 2026
Finance:
- GL Summary Screens:
- Added the ability to consolidate no department on General Ledger Summary.
- Approved Quick Code List Available on Additional Forms:
- The Approved Quick Code List button is now available on additional transaction forms, making it easier to view and select approved Quick Codes during entry.
- Supported forms now include:
- Government Budget
- Government Budget Adjustment
- Government Budget Request
- Invoice
- Cash Sale
- Cash Sale Refund
- Credit Memo
- Check
- Credit Card Charge and Credit Card Refund
- Expense Report
- Balancing Segments:
- Customer Deposit Balancing for Undeposited Funds:
- The Balancing Segment plug-in has been enhanced to correctly determine the cash account for Deposit Applications created from Customer Deposits that use the Undeposited Funds account.
- Previously, Deposit Applications could inherit the Undeposited Funds account from the Customer Deposit even though that account is not supported on the Make Deposit transaction. This could leave a residual balance in Undeposited Funds that required a manual journal entry to clear.
- With this enhancement:
- When the balancing configuration uses the Transaction method, the plug-in identifies the related Deposit transaction and uses the cash account selected on that Deposit.
- When the balancing configuration uses the Specify method, the plug-in uses the cash account configured for the Deposit transaction on the Exceptions tab. If no Deposit exception is configured, the Default Cash Account is used.
- This update ensures that Deposit Applications are balanced using the appropriate cash account and eliminates the need for manual journal entries to clear Undeposited Funds in this workflow.
- New Warning Message for NetSuite for Government Balancing Segment Transaction Updates:
- A new warning message is displayed when key information is changed on a supported transaction after the NetSuite for Government Balancing Segment workflow has been completed.
- The warning identifies whether later transactions in the payment workflow must be opened, edited, and saved to refresh their balancing segment information. This helps prevent downstream transactions from retaining outdated fund balancing values after an earlier transaction is changed.
- This release expands support to the following transaction types:
- Bill
- Cash Sale
- Credit Memo
- Net Fund Transfer Entries:
- Balancing Segments now nets offsetting debit and credit amounts before creating fund transfer entries for general ledger transactions.
- This enhancement reduces unnecessary balancing entries by posting only the net amount required to transfer cash between funds. For example, when a transaction’s mainline fund is the General Fund, the system creates balancing lines only for the net amount transferred to other funds rather than reversing the full amount from the General Fund and reallocating it back.
- Customer Deposit Balancing for Undeposited Funds:
- Budget Validation: Program Code Support:
- Budget validation now includes the Program code as a supported budget segment.
- To enable validation by Program, navigate to NS4G System Setup > Budget Validation and select Program in the Budget Segments and Fields multi-select, along with any other applicable budget segments. The Available Budget field on transactions, as well as the budget validation, will now include relevant Program budgets.
- NetSuite Next:
- The NS4G System Setup Custom record has been locked since the preferred method to access this information is through the System Setup Suitelet. Please contact support if access to this record may be needed.
Various Fixes and Performance Improvements
- Corrected a Balancing Segment penny-rounding issue affecting complex, multi-fund, multi-line for the same fund source transactions paid through multiple partial payments. In certain cases, prior rounding could cause a penny-level fund imbalance when unpaid amounts were estimated rather than accumulated from the reversed source-line unpaid amount.
- Corrected an issue where the Fund and Department on Quick Code forms was accessible to the user when paying an encumbered purchase order line. These fields are now disabled like the other GL string components to preserve accurate encumbrances.
- Background Validation for Bills, Purchase Orders, and Journal Entries:
- Background Validation moves Quick Code, Budget, and Fund Validation to asynchronous processing, allowing users to save transactions without waiting for validation to finish.
- Before submitting a transaction for approval, confirm its Validation Status is Validated - Success. Do not use Save and Submit while validation is pending and avoid editing transactions until validation completes.
- Validation status is available on the transaction:
- Pending Validation or Validating: Validation has not finished.
- Validated - Success: The transaction is ready for approval.
- Validated - Errors: Correct the listed errors, then validate again.
- Administrators must enable Background Validation in “NS4G System Setup” and review Approval Routing settings for Bills and Purchase Orders. Validations are processed in entry order and may take longer during high-volume periods. Transactions may also be revalidated overnight when conditions, such as available budget, change.
- Support has been added for the Employee Center with the new Quick Code Department Restrictions feature. Please note that custom employee center roles will need additional access to the below script. All existing custom Employee Center roles have been added with this release, so this applies only to roles added after 26.9.1 was released. Add custom Employee Center roles to Approved Quick Code List suitelet deployment external roles:
- Go to Customization > Scripting > Scripts
- Open suitelet - NS4G SL Approved Quick Code List
- Go to Deployments subtab; open and edit the script deployment
- Under the Audience subtab in the External Roles field, multi-select the custom employee center roles.
- Ensure that the standard Employee Center role is still part of the selections.
- Save the script deployment.
Human Resources and Payroll:
- Timecards and Payroll calculation:
- Calculate Approved Time only:
- Payroll and HR Preferences now includes Calculate Approved Time Only on the Time Tracking tab. When selected for the entity associated with the pay period, Calculate Payroll includes only otherwise eligible Actual Time time bills whose Approval Status is Approved. Existing payroll eligibility checks remain in place.
- Configuration:
- Open Payroll and HR Preferences for the entity processed by the pay period.
- Open the Time Tracking tab and select Calculate Approved Time Only. The preference defaults to unchecked.
- Leave the field unchecked (or null) to preserve existing behavior, including the handling of approved and unapproved eligible time.
- Apply the setting separately for each entity that should calculate only approved time.
- Operating guidance:
- If time is approved after an employee has already been calculated and the batch is not committed, confirm the NS4G Pay Period is populated with the current pay period and recalculate the employee to include the newly approved hours.
- When enabled, time in statuses other than Approved, such as Rejected, Open, or Pending Approval, is excluded if otherwise eligible.
- The preference applies during payroll calculation only and does not replace existing time-record eligibility logic.
- Null is treated as False to support existing preference records.
- Calculate Approved Time only:
- ACA Processing:
- Recalculate 1094-C:
- A Recalculate 1094C button is available on the ACA Reporting Period next to Calculate. It re-runs the existing 1094-C calculation logic after manual Employee 1095-C changes so related 1094-C totals and calculations are refreshed.
- Use and verification:
- Open the applicable ACA Reporting Period.
- Before the reporting period is committed, select Recalculate 1094C after making permitted Employee 1095-C changes.
- Monitor the Reporting Period status using the existing calculation-status behavior until processing completes.
- Review the recalculated 1094-C totals and values.
- The Recalculate 1094C button is not displayed when the Reporting Period is committed.
- ACA - Employee Coverage for partial year employment:
- ACA processing now applies Box 14 code 1H and Box 16 code 2A for full calendar months in which an already-generated employee ACA record has no coverage and the employee was not employed. The rule runs after existing ACA record-generation and coverage logic and does not replace it.
- Expected Behavior:
- The rule applies to full months before the employee hire date or after the HR/Payroll termination date when there is no coverage.
- Actual coverage dates take precedence. A month covered after termination, such as prepaid coverage, is not changed to 1H/2A.
- Existing ACA eligibility, record generation, and covered-month logic remains unchanged.
- For employees with multiple employment periods, the rule uses the available hire, termination, and coverage data; non-covered full months are populated after existing processing.
- Recalculate 1094-C:
- Federal Compliance:
- W-2 Box 12 and Box 14b support:
- Employee W-2 records and the rendered W-2 now support the new Box 12 codes 12TA, 12TP, and 12TT. The W-2 PDF also renders the two Box 14b Treasury Tipped Occupation Code fields when they are entered on the Employee W-2 record. Values in the three Box 12 fields are included in the EFW2 output when present.
- Configuration:
- Map the applicable pay codes to the following pay buckets so Calculate can populate the Employee W-2 record when the employee’s reporting-period total is greater than zero.
Purpose Pay bucket ID Employee W-2 field ID Box 12TA - Trump Account Employer Contributions ns4g_w2box12ta_pay custrecord_ns4g_empw2_box12ta Box 12TP - Cash Tips ns4g_w2box12tp_pay custrecord_ns4g_empw2_box12tp Box 12TT - Qualified Overtime ns4g_w2box12tt_pay custrecord_ns4g_empw2_box12tt - Use and verification:
- Calculate W-2 records for the applicable reporting period after the new pay-bucket mappings are in place.
- Confirm a positive pay-bucket total populates the corresponding Employee W-2 Box 12 field; zero or null does not populate a value.
- Enter Treasury Tipped Occupation Code(s) Primary and/or Secondary on the Employee W-2 record when applicable, then render the W-2 PDF.
- Commit the W2 reporting period to generate the EFW2 file, then confirm populated 12TA, 12TP, and 12TT values are included.
- Form 941 totals update:
- The 941 Federal Report adds Line 5e, Total social security and Medicare taxes, and Line 6, Total taxes before adjustments. The report also adds a quarterly Total Actual Withheld from Payroll based on the existing federal income tax, Social Security, and Medicare withholding and employer-paid tax buckets.
- Expected Behavior:
- Line 5e Calculated Withheld equals the applicable Calculated Withheld amounts from Lines 5a, 5c, and 5d.
- Line 5e Actual Withheld equals the applicable Actual Withheld amounts from Lines 5a and 5c.
- Line 6 combines Line 5e with Line 3 using the report’s defined calculated and actual withholding logic.
- When payroll is configured correctly, calculated and actual totals match; differences remain visible when they do not.
- Form 941 Schedule B:
- The 941 Quarterly Federal Tax Return Report now includes Schedule B (Form 941) as page 2. Existing page 1 totals remain unchanged. Schedule B shows daily federal tax liability by payment date for the three months in the selected quarter.
- Report content:
- Daily liability is calculated from committed pay periods using the payment date. Days without payroll activity remain blank.
- For each payment date, the report combines Federal Income Tax Withheld, Social Security Tax Withheld, Social Security Employer Paid, Medicare Tax Withheld, and Medicare Employer Paid.
- The report displays the tax liability for each month and the total liability for the quarter.
- The three month columns align to the selected quarter and include rows for days 1 through 31.
- Use:
- Generate the 941 Quarterly Federal Tax Return Report for the applicable quarter.
- Review Schedule B on page 2 and reconcile the daily amounts to committed payroll activity by payment date.
- Review the Month 1, Month 2, Month 3, and quarterly total liability amounts.
- W-2 Box 12 and Box 14b support:
- Calfornia ACA Reporting:
- California transmission manifest:
- ACA commit now generates a California transmission manifest when at least one employee with an already generated ACA record is identified as a California resident. The CA manifest is stored with the existing ACA files and uses the CA-prefixed naming convention.
Example: CAManifest_1094C_Request...xml.
- Configuration:
- Open Payroll and HR Preferences > Compliance > Affordable Care Act Reporting.
- Enter the California Transmitter Control Code (CA-TCC) in the new California Transmitter Control Code field. The field is alphanumeric and limited to five characters.
- Use the CA-TCC issued for the environment and submission type being processed.
- Confirm the employee’s Tax State or address state is California for employees expected to be included in the CA output.
- Expected behavior:
- The CA manifest is generated only when at least one qualifying, already-generated employee ACA record is associated with California.
- The CA manifest contains CA-specific manifest elements and values while unchanged federal values are retained where the specifications are the same.
- The manifest uses a CA Transmission ID and the configured CA-TCC; CA record and submission counts reflect the CA-resident-filtered transmission.
- The CA manifest and its form-data file use matching file-name and checksum values.
- California transmission manifest:
- Payroll Postings:
- Mutually exclusive hour-code posting options:
- The Hour Code record now prevents users from selecting both Include in Payroll Posting Rules and Do Not Post. Selecting either checkbox disables the other; clearing the selection re-enables both choices. The control is enforced in both the user interface and server-side processing.
- Use and verification:
- Open an Hour Code record and select either Include in Payroll Posting Rules or Do Not Post.
- Confirm the other checkbox becomes unavailable.
- Clear the selected checkbox and confirm both options are available again.
- Review existing Hour Code configuration and correct any conflicting selections before payroll posting.
- Mutually exclusive hour-code posting options:
Various Fixes and Performance Improvements