1 Release Notes 25.12.1

NetSuite for Government 25.12.1 Release Notes

Revision Date: December 10, 2025

Important:

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

The 25.12.1 enhancements and changes listed in this document are not available to customers until they are upgraded to NetSuite for Government 25.12.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 2025.2 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 25.12.1 – Release Date December 10, 2025

Finance:

  • General Ledger Impact View:
    • A new button is available on GL posting transactions to show general ledger impact in a consolidated view. The View GL Details button will show a combined fund total as well as the line detail. Additional functionality will be released to aggregate detail lines with a zero balance as well as exporting to CSV and printing in a fund specific view.
  • Purchase orders:
    • Corrected an issue where the Purchase Order Effective Date was not reset when the record was copied. Now, the Effective Date will be cleared on copy and reset to the PO Date on save.
  • Purchasing Change Orders:
    • Corrected an error with Purchase Change Orders where the Effective Date is blank but is expected for the Purchase Order update. This occurred only when a Change Order was already in process prior to the October release which had the new Effective Date field implemented.
    • The Purchase Change Orders process will now pass the Change Order Effective Date to the Purchase Order Close Date to allow for date specific encumbrance impact during the Close PO process.
    • The Interest Allocation Next Approver field has been updated to a more versatile name NS4G Next Approver which supports custom transaction types of Change Orders and Budget Adjustments. This is a label change only, so existing reports and workflows are not impacted.
  • Government Budget Validation Setup:
    • The Show In functionality on Quick Codes and Accounts was enhanced with a new category for “Budget” which allows for budget only accounts. If there are Quick Codes or Accounts which should only be used in parent-level budgets, then define the Show In field with just the Budget category.

      Previously, Budget was included with the financial category, so a data update script has been run to enable any existing client Quick Codes or Accounts to select both Financial and Budget to maintain the existing functionality.
  • Quick Codes:
    • We are excited to announce an enhancement to the NetSuite for Government Quick Code functionality, offering greater flexibility and control for your transaction validation processes.

      Configurable Validation Segments:

      The NetSuite for Government System Setup > Quick Code tab now allows administrators to select which segments (e.g., Fund, Department, Account) are required in Quick Code validation. This enables organizations to tailor the validation framework to their specific business needs.

      Advanced Matching Logic:

      When additional fields (such as Program, Grant, or Project) are included in Quick Code definitions, the system will seek an exact match first when deriving a Quick Code from segments. If none exists, validation will fall back on the required segments (as configured), ensuring compliance while maintaining flexibility.

      Editable Segment Values on Transactions:

      Users can now manually enter or modify values for Quick Code segments when creating transactions. While the fields remain editable, validation rules will enforce the use of valid combinations based on your configuration.

      Best Practice Recommendation:

      For robust control, we recommend setting your NetSuite for Government Quick Code settings to Mandatory and Block. This ensures only valid combinations can be used in transactions, preventing incomplete or incorrect data entries.

      Benefits:
      • Customized enforcement of data governance and accounting policies.
      • Improved user experience and broader support for unique organizational requirements.
      • Greater flexibility in configuring transaction controls without restricting data entry.
  • Item Code Account Override:
    • Corrected an issue where the GL Impact Posting Flag was not set on final workflow approval. Prior to this change, the GL Impact could be left in a mixed posting status of Yes and No with a workflow approval.
    • The Item Account field will now filter out Accounts which are defined with a Type of Accounts Receivable or Accounts Payable to avoid conflicts with the sub-ledger integrity.
  • Project and Grant Segments:
    • We are pleased to announce significant enhancements to our Project and Grant functionality within NetSuite for Government. You can now seamlessly integrate Project and Grant segments with General Ledger (GL) Impact, bringing more robust tracking and reporting to your financial processes.

      Key Benefits:

      • Project and Grant data available in the GL: Enhanced transparency and control over project and grant-related financial activities directly within the General Ledger.
      • Preserves the relationship of the transaction line Project and Grant to the General Ledger impact for comprehensive reporting.
      • Expanded functionality: In addition to the General Ledger, additional features will benefit from this integration, including:
        • Bill Capture now includes the Project and Grant Segments.
        • Allocation Schedules can apply overhead and recurring journal entries.
        • Financial reporting will include Project and Grant for columnar formats.
        • Additional future enhancements such as securing access to these segments will also be available.
      Additionally, A Data Update tool is now available to populate the Project and Grant Segments on historical transactions.

      Note:

      Contact Support and see the product announcement on the support portal for additional information.
  • 1099: 2025 Support:
    • The Federal Filing for 1099 report has been updated to run in the background, and with this change, users are no longer directly linked to the File Cabinet. Instead, the user will remain on screen and an email notification will be sent when the process completes. 1099 files are released to a secure File Cabinet location under: Documents > Files > File Cabinet and found in the folder structure SuiteApps > Com.Oracleslg.ns4g > 1099 Reports > Year > Form type.
    • Enhanced the 1099-G Vendor Payment reports to also contain a grouping for the Tax Year so that each 1099-G form will appear as a separate row on the saved search.
    • Federal and State Income Tax will show as positive amounts on 1099 reports, even though they are entered as a negative line, or credit tax line, on the Vendor Bill, Bill Credit and Check screens.
    • The 1099 Federal Filing report has a new option under State Reporting for "Include all Vendor Payments". When this box is checked, all payments for a particular vendor will be reported to the payer's state only within State 1 Income Tax. Without this box checked, multiple states may be reported on the 1099 State 1 and State 2 boxes, based upon the recipient payment address.
  • 1099-S Support:
    • The 1099-S Vendor Payment Report Saved Search is now available to support reporting real estate transaction sales for Internal Revenue Service reporting. Real estate transactions will be reported when a transaction line item for Vendor Bills, Vendor Credits or Checks coded to an Account defined as 1099-S Gross Proceeds or 1099-S Buyer's Part of Real Estate Taxes. Additionally, there is a new 1099-S field on these same transaction lines which allow for further defining the IRS reporting to include items like the Close Date and Property Address. Ensure all desired vendor payments for 1099-S form reporting have the 1099-S field populated with these IRS reporting items.
  • Reporting - New Integration / Configurable Datasets:
    • Budget vs Actuals dataset for SuiteAnalytics (NetSuite)

      Overview

      A new SuiteAnalytics dataset, “Budget vs Actuals”, is now available to help financial analysts compare budgeted amounts, adjustments, actuals, and encumbrances by accounting period, including monthly views. This supports government reporting, audit readiness, and financial oversight.

      What’s new

      • New dataset: “Budget vs Actuals” in SuiteAnalytics Workbooks.
      • Standardized measures for Adopted Budget, Adjustments, Actuals, Encumbrances, and Monthly totals.
      • Flexible filtering and segmentation by Department, Fund, Period/Date Range, and Account.
      • Pivot/grouping capabilities across key financial dimensions.
      • Built-in validation approach and documented formula logic for transparency.
      • Updated training/help text and controlled access via roles and permissions.

      Key fields and measures

      Dimensions: Department, Fund, Period, Account, plus other relevant segments as applicable in your environment. Measures and sources:

      • Adopted Budget: Totals from Government Budgets Transactions for the selected segments and period.
      • Adjustments: Totals from Government Adjustments Transactions for the selected segments and period.
      • Actuals: Totals of posted transaction amounts from all transactional data for the selected segments and period.
      • Encumbrances: Totals from Encumbrance Transactions for the selected segments and period.
      • Monthly: Totals filtered to transactions whose ending month matches the selected date range end (month-end view).

      Filtering and analysis

      Filters: Department, Fund, Period/Date Range, Account.

      Analysis: Group or pivot by the above dimensions to compare budget vs actuals and drill into variances at monthly or period level.

      Accuracy and validation

      • Values are cross-checked against representative NetSuite transactions and system totals.
      • Formulas validated for edge cases (e.g., periods with adjustments only, no encumbrances, or zero-activity months).
      • If underlying transaction types change, formulas and mappings should be reviewed and updated (see Documentation).

      Documentation and support

      Included: Guide outlining field mappings and formula logic, plus maintenance instructions if transaction sources change. Help text in the workbook explains how to interpret each measure/column and common use cases (variance analysis, period-to-period review).

      Access and permissions

      Dataset is shared to appropriate roles to maintain data security and compliance. If you cannot see “Budget vs Actuals”, request access through your administrator. Ensure use aligns with your organization’s data governance policies and period-close practices.

      Getting started

      • Open SuiteAnalytics Workbooks and select “NS4G Budget vs Actuals.”
      • Apply filters for Department, Fund, Period/Date Range, and Account.
      • Use grouping or pivoting to view totals and monthly breakdowns.
      • Export or share results as needed, following security and compliance guidelines.

      Known considerations

      Monthly measure reflects totals where the transaction’s ending month equals the selected date range end; adjust filters if your reporting period differs. If new custom transaction types are introduced, update the dataset mappings and formulas accordingly.

Various Fixes and Performance Improvements

  • Corrected an issue for the Quick Code Vendor Bill screen where an error was given, "Please choose an Item to add", when using only the Expenses tab.
  • Carry forward Encumbrances at Year-End: The Mass Update process has been updated to remove the error message associated with Vendor Bills.
  • The Show In functionality associated with the Accounts and Quick Code screens has been updated to correctly assign the category to the transactions. Previously, all transaction types were using the category of Purchases. Now, Customers, Financial, Payables and Purchases are assigned correctly.

    Note:

    Please make sure to update the Account and Quick Code screens Show In field to enable the applicable record to be displayed in the dropdowns.

Human Resources and Payroll:

  • Over Time, FLSA Regular Rate Multiplier:
    • Applicability:

      This calculation rule is designed for use with 7–28 day FLSA overtime cycles. It must be paired with the new Overtime Cycle Logic.

    • Assignment:

      Assign this rule to overtime hour codes where appropriate. Set the multiplier (e.g., 0.5) in the Default Amount field on the hour code. The multiplier determines how the overtime rate is calculated.

    • System Calculation Process:

      Identifying Additional Pays (Non-Discretionary), The system will include additional pay records where:

      • The Add Pay’s start date is on or before the Pay Period End Date.
      • The Add Pay’s end date is on or after the Pay Period Begin Date.
      • The Pay Code is marked as "Additional Pay" and "Include in Add Pay Rate" is enabled.
    • Determining Pay Amounts:

      For each eligible additional pay record:
      • Record the value of “Payouts Per Year.”
      • Use the employee’s Pay Code Amount.
      • If the amount is a percentage (%), the system will produce a processing error. Percentages are not supported.
      • If no amount is supplied, the system will use the Default Amount (again, must not be a percentage).
    • Calculating Add Pay for the FLSA Cycle:

      For each additional pay record, the system applies:
      • Add Pay Cycle Amount = (Amount × Payouts Per Year / 364) × Days in Cycle.
      • The system sums all applicable Add Pay Cycle Amounts for the current overtime cycle.
    • Examples:
      • $50 × 26 / 364 × 7 = $25
      • $50 × 24 / 364 × 28 = $92.31
      • $50 × 12 / 364 × 21 = $34.62
      • $500 × 1 / 364 × 7 = $9.62
    • Base Wages Calculation:

      The system aggregates all eligible wages added to the Overtime Cycle’s primary pay bucket for time entries in the current Overtime Period.
    • Cycle Hours Calculation:

      The system sums all hours in the Overtime Cycle’s primary hour bucket for timecard entries linked to the current Overtime Period.
    • Calculating the Regular Rate:

      Formula:

      • Regular Rate = (Total Base Wages + Total Add Pay Cycle Amount) / OT Cycle Hours
    • Determining the Overtime Rate:

      The system multiplies the regular rate by the multiplier specified on the hour code (Default Amount field, e.g., 0.5).
    • Final Overtime Pay Calculation:

      The system calculates final overtime pay by multiplying the overtime rate by the total hours recorded for the overtime hour code.

      Note:

      This rule ensures overtime pay reflects the FLSA Regular Rate, using all non-discretionary incentive pay and base wages in the calculation process. Assign only to the appropriate hour codes as defined by your organization's payroll practices.
  • Vermont Municipal Employee Retirement System Defined Contribution:
    • Employee Retirement Configuration
      1. On the Employee record, select the Compliance tab and the Retirement/Compliance Sub tab. Open the Employee Retirement Record.
      2. Set the Vermont Municipal Employee Retirement System DC in the State Retirement System field.
      3. Assign the effective Begin Date for this record.
      4. The Scheduled Daily Hours, Service Credit and State Retirement Plan fields are not required at this time.
      5. When an employee terminates or becomes ineligible for the retirement system, set the Closed check box and enter an end date after the final reporting file has been submitted.
    • Reporting Processing and Filing
      Payroll and HR Preferences Configuration
      1. On the Payroll and HR Preferences page, select the applicable entity and click the Compliance tab.
      2. On the Public Employee Retirement System section, in the Agency PERS ID field, enter the Agency PERS ID, also known as the Employer Number.
      3. In the State Retirement Reports File Cabinet Location field, enter the internal id of the folder that will store state report files.
      4. Select the State Preferences tab.
      5. On the Primary State section, from the State drop-down, set the state to Vermont.
      6. Select the following check boxes for the correct forms to default.
        1. Use State Employee Retirement Form
        2. Use State Position Form
        3. Use State Employment Retirement Reporting Form
      7. Click the Save button.
    • Reporting Period
      1. On the main menu, navigate to Payroll and HR > Compliance Reporting > Reporting Period.
      2. Click the New Reporting Period button.
      3. From the Type drop-down, select.
        1. State Retirement and Vermont Municipal Employee Retirement System DC for the State Retirement System.
        2. Enter the Year and Begin/End Dates
        3. Enter Reporting Date for the Reporting Period. This date will be used to identify which Employee Payroll Totals records are included. Only records linked to pay periods where the Pay Period > Retirement/PERS Reporting Date exactly matches the Reporting Period > Reporting Date will be included in the report.
        4. Select the Entity(s) to be included in the file.
      4. For most reports, leave Sub Type and Sub Type Number blank. These fields function similarly to Supplemental Pay Periods. If a new reporting period is needed with the same fields in order to generate a correction report, you may use the Sub Type. Multiple reports can be created by using different Sub Type Numbers.
      5. Click the Save button.
    • Calculate
      1. On the Reporting Period page, click the Calculate button.
      2. The Reporting Period will default but the period and filter can be changed if needed. Click Submit.
      3. Employee Calculation Criteria
        1. During the Calculation the system will search Employee Retirement records and only employees with the following criteria will be returned:
          1. Employee Retirement Record where the state retirement system is set as the Vermont Municipal Employee Retirement System DC.
          2. Employee Retirement Record where the record begin date <= Reporting Period End Date and the record end date >= Reporting Period Begin Date
        2. During the Calculation the system will search Employee Pay Period Totals Records where the related pay period has a Retirement/PERS Reporting Date that exactly matches the Reporting Date field on the Reporting Period and matches the reporting period and whose entity matches the Reporting Period Entity.
        3. To determine which position and pay record to use, the system will use the related Employee Pay Period Totals>Primary Position and Pay this reporting period date range. If multiple position and pay records return for this reporting period, the system will use the record set as primary with the greatest end date. If this is null for all employee payroll totals, then fields requiring the position and pay record will be left as blank.
    • Review or Edit
      1. After submitting the calculation, the system redirects you to the Reporting Period record. When the status changes to complete the records are ready to view.
      2. To review or edit results, click the Employee Retirement Reporting subtab.
      3. Click an employee link to validate the results.
      4. To manually update a record, click the Edit button.
      5. A record can be manually added by selecting the New Employee Retirement Reporting Record. Any manually created records should be validated prior to committing. Recalculating the reporting period may alter manually created records.
      6. To recalculate, click the Calculate button and calculate as many times as needed.
  • Payroll GL Transaction Refactor:
    • The following enhancements have been added to the system to improve the accuracy, user control, and stability of Payroll GL Transaction processing.
      1. Payroll GL Transaction Script Refactored

        The script that generates Payroll GL Transaction records now sources data directly from Employee Posting Detail Transaction records, rather than relying on the previous scheduled script logic.

        When you commit a payroll batch:

        • The status of the Posting Detail on the payroll batch will update to Commit-Submitted.
        • A refactored script will automatically generate the Payroll GL Transaction Record using data from the Employee Posting Detail Transaction records.

        Note:

        Minor rounding differences may occur due to “splitting the penny” during detail record generation, potentially causing greater variance than before when compared to summarized postings.

        Manual Overrides:

        • You can manually edit and override Employee Posting Detail records as needed. All manual changes will be accurately reflected in the generated Payroll GL Transaction Record.

        Employee Detail Preference:

        • If the “Include employee detail in the Payroll GL Transaction” option (in Payroll and HR Preferences) is enabled, detailed GL transaction records will continue to be generated.
        • If the option is disabled, summarized Payroll GL Transaction records will be created as before.

        Unposted State:

        • Payroll GL Transaction records are created in an unposted state by default.
        • This update does not alter existing workflow approval processes.
        • When running the Uncommit process, any unposted Payroll GL Transaction records related to the batch will be deleted.

        Additional Changes to Payroll Batch Usability:

        • The Calculate and Commit buttons are now hidden on the payroll batch until the Posting Detail Status is set to Complete or Completed with Errors.
        • In the Calculate Payroll Suitelet, the pay period selection is hidden unless the Posting Detail Status is Complete or Completed with Errors.
        • If a Payroll GL Transaction record is generated via the new Employee Posting Detail Transaction process, it will be locked and non-editable. Older Payroll GL Transaction records not tied to Employee Posting Detail can still be edited for corrections.
        • Once a Payroll GL Transaction record is posted, associated Employee Payroll Detail records will become uneditable, and the Posting Detail Status will update to Committed.
      2. New “Regenerate Payroll Posting GL Transaction” Button

        You can now use the Regenerate Payroll Posting GL Transaction button on any payroll batch with a status of Commit-Submitted to streamline corrections.

        How to Use:

        • The button becomes visible when the payroll batch status is Commit-Submitted.
        • Upon clicking, you will see a confirmation prompt:

          This action will generate a new Payroll GL Transaction Record using the Employee Posting Detail Records. A new record will generate only if no current Payroll GL Transaction record exists, or if all current related records are voided. If an existing Payroll GL Transaction record is present, it will be deleted and replaced. If any related record is posted, the new transaction record will not be generated.

        After you confirm:

        • If no related Payroll GL Transaction record exists, a new one will be created.
        • If only unposted or voided records exist, a new record(s) will be generated.
        • If any related record is posted, no new record will be generated and an error will be logged in the memo field.
        • You may cancel the operation at the prompt if desired.
      3. Correction Guidance

        Corrections to payroll postings should be performed using the Regenerate Payroll Posting GL Transaction button with the batch in Commit-Submitted status; do not use the Uncommit process solely for General Ledger corrections.

  • Payroll Frequency Group:
    • Background

      Supplemental pay periods are run frequently (12-50 times a year), and agencies must carefully manage which pay codes and hour codes are included. Other groups of pay codes such as benefits and reimbursements may run on specified pay periods. The current process, relying on manual exclusion of codes not intended for supplemental runs (like benefit plans, deductions, and accruals), is error-prone and time-consuming, especially for new users. This new "Frequency Group" approach streamlines the selection of pay and hour codes for various payroll scenarios to reduce manual work and mistakes.
    • Overview

      The Pay Period form now includes a new section, Payroll Frequency Group Options, enabling enhanced control of pay and hour code processing within payroll runs. This update introduces three new multi-select fields, each providing users with distinct options to tailor payroll code inclusions or exclusions for a given pay period.
    • Payroll Frequency Group Options:
      • Users may select an option in only one of the three fields at any given time.
      • Once one field is selected, the remaining two are disabled.
      • If the selected value is cleared (all options deselected), all three fields become available again.
        1. Run Additional Payroll Frequency Group: Selected group(s) will have associated codes processed in addition to the usual frequency logic.
        2. Run Only Payroll Frequency Group: Only the codes in the selected group(s) are processed; all other codes are excluded regardless of frequency set on the code.
        3. Exclude Payroll Frequency Group: Codes in selected group(s) are excluded from processing; all other logic remains unchanged.

          If none of the Payroll Frequency Group options are selected, standard payroll frequency logic applies.

          Note:

          The system ensures codes are not processed more than once if they qualify via both standard and frequency group logic.
    • Creating a Payroll Frequency Group
      1. Navigate to the Frequency Group Setup
        • Go to Payroll and HR > Other Setup in your system menu.
        • Ensure you are in either the Accounting Center or Classic Center as the record is available to both.
      2. Create a New Frequency Group Record
        • Click New to add a Payroll Pay/Hour Code Frequency Group.
        • Review the Last Modified field, which will display when the record was last updated.
      3. Enter Group Details
        • Name/Description
        • Pay Codes: Choose the pay codes to include in this frequency group.
        • Hour Codes: Choose the hour codes to include in this frequency group.
      4. Save the Group
        • After entering all necessary details, click Save to finalize the frequency group setup.
    • Roles and Security
      • NS4G - Payroll Administrator: Edit Access
      • NS4G - Finance Director: Edit Access
      • NS4G - Scripts: Full Access
      • Administrator: Full Access

      Custom roles will need to be updated to include edit access the Payroll Frequency Group custom record.

    • Best Practices and Notes
      • Use clear, descriptive names so users can easily identify the purpose of each frequency group.
      • Only select pay and hour codes that are relevant for the specific supplemental or special pay run.
      • Review your selections each pay period to ensure compliance with your agency’s payroll guidelines.
      • Leverage the generative text feature for efficient group descriptions.
    • Summary

      By using the Payroll Frequency Group, agencies can efficiently run supplemental payrolls and other special pay cycles without repetitive, manual updates for each pay code, substantially reducing the risk of errors.

  • Consistent Decimal Formatting in Employee W2 PDF:
    • The system has been updated to ensure all dollar values displayed on Employee W2 PDFs - including those in Boxes 1 through 12hh and Box 14 (“Other”) - consistently show decimal points for improved readability and compliance.

      Key Updates:

      • All relevant Employee W2 fields (Boxes 1-12, 16-19) previously defined as Decimal type have been updated to the Currency type. This change leverages NetSuite’s native display format, ensuring accurate placement and rounding of decimal values on both the Employee W2 records and W2 PDF outputs.
      • Box 14 (“Other”) values are correctly displayed using decimals, referencing the pay bucket value.
      • Employee SSN, Employer ID number, and Employer’s State ID number fields are excluded from this update.
      • Employee W2 fields for Boxes 1-6 are now set to “Show In List,” enabling easier access and visibility within the application.
      • Historical data integrity has been preserved - no existing values in these fields have been cleared or lost.

    • Viewing W2 PDFs with Consistent Decimal Formatting:

      • Open the Employee W2 record from the relevant employee profile.
      • Review Boxes 1–12, 14, and 16–19. All dollar values now display with decimals, formatted using the standard Currency type.
      • When viewing or printing the Employee W2 PDF, confirm that all monetary values - including those in Box 14 (“Other”) - appear with decimal points.
      • To review these values in list views, Boxes 1–6 are now visible due to the “Show In List” setting.
      • Employee SSN, Employer ID number, and Employer’s State ID number display unchanged by this update.

      Notes for Administrators & Users:

      No steps are required to migrate or update old records - historical data remains intact.

      PDFs and associated reports are unaffected aside from the updated formatting.

  • W2 Address Formatting:
    • Configuration Summary: W2 Address Formatting Overview:

      The following system updates have been completed to enhance W2 PDF address formatting for compliance and standardization and in the instance where the W2 address differs from the address set on the Entity record:

      • Employer Address Formatting:
        • Default sourcing from the shipping address field at the entity level has been removed.
        • The employer address in W2 PDFs is now pulled from HR Preferences.
    • Update W2 Address Information Before Processing W2s
      • To ensure W2s display corrected and compliant address formatting, please update the employer address details prior to running the W2 process:
        1. Navigate to Payroll and HR Preferences:
        2. Go to Payroll and HR Preferences > Compliance Tab > W2 Field Group.
        3. Complete All Applicable W2 fields include the new Address Fields:
        4. For each entity, locate and fill in the following fields with the most current and accurate information:
          • W2 Employer Name
          • W2 Location Address
          • W2 Delivery Address
          • W2 City
          • W2 State
          • W2 ZIP Code
        5. Save Your Changes
        6. Ensure all information is correct before saving. This step will ensure the updated address details are used in W2 record calculations and on W2 PDF outputs.

          Reminder: Updating these fields before processing W2s guarantees the correct format and compliance with USPS and business requirements.
  • System Automation for Overtime Period Assignment:
    • The Overtime Period will be assigned time records automatically in field: NS4G Overtime Period (Field ID: custcol_ns4g_timesheet_otperiod. The assignment will run every 15 minutes.
    • Assignment Logic
      • The system will analyze each employee's position and pay record to determine their overtime cycle. If a timecard entry date falls within the start and end dates of a relevant Overtime Period record, the time tracking record will be updated automatically.
      • The field will only be updated if it is currently empty (null) to prevent overwriting any manual updates.
      • Skip employees without an overtime cycle defined in their position and pay record (e.g., exempt employees).
    • Field Permissions
      • The NS4G Overtime Period Field (custcol_ns4g_timesheet_otperiod) will be restricted to users with roles specified under Payroll and HR Preferences > Timecard Pay Period Edit Permissions.
  • The Georgia State Income Tax rate:
    • Georgia State Income Tax Calculation Setup
      1. To set up the applicable filing statuses for the State of Georgia, navigate to the 'State Filing Status' section.
        1. Edit the following statuses and assign them to Georgia.
          1. Single
          2. Head of Household
          3. Married Filing Separately
          4. Married Filing Jointly
      2. To enable the income tax calculation for an employee
        1. 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
          1. State: Assign ‘Georgia’ as the state.
          2. State Filing Status: Input the employee’s provided ‘State Filing Status’.
          3. State Dependents/Allowances: Enter the number of Dependent Allowances as per the employee’s details.
          4. State Extra Withholding: If applicable, input the extra withholding amount provided by the employee.
      3. Calculation Notes:
        1. 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.
        2. 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.
  • Payroll Posting Improvements:
    • To enhance payroll processing efficiency and minimize delays caused by posting issues, the following enhancements have been implemented:

      Key Changes:
      • Flexible Payroll Batch Processing:

        You can now calculate and commit payroll batches even if the payroll posting detail status is not "Complete" or "Completed with Errors." This allows payroll to be processed in a timely manner, with the option to make corrections to postings after payroll has been paid.
      • Warning on Early Commit:

        If you try to commit payroll when the posting status is not "Complete”, the system will display a warning:

        “It is recommended to wait until the posting status is complete before committing. If you choose to commit beforehand, you will need to regenerate the Payroll GL transaction.”
      • Posting Detail Status Updates:

        When a payroll batch is committed and the posting detail status was "Complete", the status will change to Commit-Submitted to align with the Payroll Batch status.
        • If the status was Complete - Errors Occurred, the status will remain unchanged.
        • When uncommitting, if the status is Commit-Submitted, it will revert back to Complete or align with the Payroll Batch status. If the status is Complete – Errors Occurred, it remains as is.
        • Manual generation of Payroll GL Transactions is only allowed when the status is not Complete - Errors Occurred. When generating Payroll GL Transactions manually with status Commit-Submitted, the status will briefly update to "Processing" before returning to Commit-Submitted.
      • Editing and Access Restrictions:
        • Once the related Payroll GL Transaction is posted, all associated Employee Posting Detail records become locked and non-editable.
        • The sublist within the Payroll GL Transaction is disabled when there are associated Employee posting details.

        Note:

        Payroll GL Transaction records are not editable once posted.

Various Fixes and Performance Improvements

  • The Utah State Tax rate has now been updated.