...

• USPS-R 5.21.1 Release Notes (12/19/2018)
  • Included 2019 tax table updates
  • Patched two W2 related issues
• USPS-R 5.22.0 Release Notes (01/02/2019)
  
  • Included W2 city equivalent for ITCs. 
  • Added payroll item configurations with taxable employer amounts to city tax UI.
  • Allows budget distribution report to be generated prior to posting a payroll
  • Added options to W2 report to select by pay group and to generate the report for errors only.
    
• USPS-R 5.22.1 Release Notes (01/04/2019)
  • This was a very targeted release that corrected an issue for a single district that was caused by having pay history for an employee, which had no payroll items withheld.
• USPS-R 5.22.2 Release Notes (01/10/2019)
  • Fixed two limited W2 related issues. 

Upcoming Scheduled Releases

• USPS-R 5.22.3 Scheduled Issues (scheduled for release on 01/16/2019)
  • We are removing the federal and state totals from the additional W2 generated for employees with more than two localities as the Edge pre-processor is not dealing with this scenario when totaling. 
    • The W2s are still printed correctly based on reports we have received in this scenario, but the report Edge generates is to high as the additional W2 is being added into the total
  • The W2 abbreviation field is being required for cities in USPS-R and the W2 is not defaulting to the city name when that field is not present.
  • An ACH checksum issue was detected internally, which only affects the debit and credit depository clearing account options. 
    • This is not a commonly used configuration option and to our knowledge no school has yet experienced this issue in production.
• USPS-R 5.23.0 Scheduled Issues (scheduled for release on 01/18/2019)
  • A rule has been added, which will prevent a non-concealed employee from having a duplicate SSN.
    
    • The user can control whether this will be a warning or an error (default) based on enabling / disabling rules.
  • The STRS / SERS per pay reports will have a mechanism to allow voids from a prior payroll to be reported on the submission file.
  • E-mail direct deposit jobs will now list whether the job succeeded or failed for each e-mail address in the highlight viewer of the job scheduler. 
    • This should help tremendously in determining problems with e-mail addresses.
    • The job will continue on if a bad e-mail address is encountered, so a single bad e-mail address does not cause others to not receive their notices.
    • Please note we cannot verify successful delivery, just that the e-mail address was "valid" per e-mail address validation rules.
  • We have been working with infohio staff and this release will include an SSDT template report, which will be in the format needed for infohio.
  • As mentioned previously this release also contains some additional logging to help debug performance issues.