Table of Contents
maxLevel 1 indent 1px style none

...

Bug Fixes

• Corrected the Account Change process to prevent it from creating the July posting period of the next fiscal year.  The changes also resulted in performance improvements

Improvements

• Subject Code changes per ODE for FY23 have been implemented
  • For full list see Release Notes
• Budget Account Activity Report (canned) performance improvements (55-75%)
  • Forecast Line Number also added as Sort Option
    
  • Reminder: Users should be utilizing the canned version of reports whenever possible. The canned reports (on the Report menu) are enhanced for performance so they will run much quicker than their template counterparts. We've been continuing to update the canned reports to attempt to ensure the same functionality is available in the canned version. Primary reason to use the template version at this point is if they have customized the version to add/remove columns or require a change formatting.
• Created a rule to prevent invoicing a future fiscal year purchase order in the current fiscal year. This is a mandatory rule that cannot be disabled. 
  • Error: Invoice date is in a fiscal year prior to the PO date.
  • Example. The current period is June 2023 and the district has started to create their 7/1/23 POs so July period is also open. When they invoice on of those POs, they accidentally let the date default to 6/15/23. The Invoice would "reduce" the encumbrances, but the encumbrances aren't actually added to the account until the PO date of 7/1/23 so this could cause an issue with a negative carry over.
    • Now that the rule has been implemented, the user will receive an error when attempting to save the Invoice with a 6/15/23 date.
    • In order to post the invoice, they can either change the Invoice date to July OR modify the PO to a June date.
• Updated the anonymizer to remove the File Store data

Patches

• Correct account change job status for specific district
  • Be cautious if there is an account change job running before restarting an instance.

...

• The STRS Advance Reports were updated to use the pay group date ranges.
• Payroll initialization validations were updated so they are performed when a current payroll is saved or updatedspecial pay is initialized as well as when pay amounts are created or modified in Current pay.
• An issue with employee's Medicare YTD Applicable Gross being negative and causing an error stating NPE:  Cannnot get 'hiGross' on null object on the Error Report has been corrected.
• If an employee was only paid out of accrued wages, they could be excluded from the STRS Advance Positions Report even if there were Compensation Adjustments for work days.  This change updated the report to check the Adjustments in addition to the Contract Days Worked field to determine if an employee should be included on the report.
• Issue with a missing Pay Account (account was deleted) which caused the Audit Report to fail was corrected.
• A payroll validation was added to assure the Supplemental Tax Options across entire employee pay are the same.  This prevents to ability to choose different supplemental tax options (Apply Annuities to Supplemental and Apply Annuities to Regular) across multiple Miscellaneous/Termination Pay Types.

  • All Applicable Pay Amount Supplemental Tax Options Must Be The Same For All Positions Being Paid

...